Back
[07:36:27] <alex_joni> jepler: seen
http://sphinx.pocoo.org/ ?
[11:03:16] <jthornton> I wonder if there is a way to incorporate tttscale into truetype-tracer???
[11:22:49] <alex_joni> jthornton: surely there is
[11:23:05] <alex_joni> but I thought ttt already does g-code scaling..
[11:23:17] <alex_joni> e.g. you have a parameter which scales the whole text
[11:23:45] <jthornton> I can't remember
[11:24:22] <jthornton> I think what tttscale does is allow you to tell it how long you want it or something like that
[11:28:39] <alex_joni> well.. without tttscale you have to:
[11:28:41] <alex_joni> a. load it in AXIS
[11:28:46] <alex_joni> b. look at the length
[11:29:19] <alex_joni> c. calculate the new scale = old_scale * needed_length/current_length
[11:29:24] <alex_joni> d. edit file and reload
[11:29:32] <alex_joni> hardly something hard to do..
[11:29:43] <jthornton> and it allows you to specify the X and Y offsets
[11:29:54] <alex_joni> there is touch off for that
[15:53:29] <micges> hello all
[15:54:37] <micges> I've messing with joints_axes3 and I noticed that overriding limits are done only in joint mode not teleop
[15:55:14] <micges> that means I can't put off from limit my gantry machine without skew it
[15:56:11] <SWPadnos> limits are a joint thing, not world
[15:56:30] <SWPadnos> I don't know if that analysis helps ;)
[15:56:55] <micges> heh
[15:57:59] <micges> I can't tell this to our customer :D
[15:59:03] <SWPadnos> I think the override only applies to the joints that are on a limit
[15:59:18] <SWPadnos> I'm not sure that you're allowed to jog other joints
[16:00:04] <micges> overrides applies to all joints, I can jog any joint
[16:00:29] <SWPadnos> ok
[16:01:43] <micges> I hope that I'll figure out some solution for this
[16:01:44] <micges> bbl
[20:19:44] <andypugh> I am about to write a component for which I have no hardware to test it. Should I even bother?
[20:20:17] <andypugh> This is the 6-wire version of the BLDC-Hall component.
[20:20:28] <micges> I would get hardware
[20:21:06] <andypugh> I don't really want the hardware, I have better hardware.
[20:22:53] <andypugh> I could probably cobble something up, but then I will only really be testing the cobbled-up hardware.
[20:24:46] <micges> If you know what you're doing you should write comp, someone with hardware could test (ideal case)
[20:25:56] <andypugh> I have tested the closely-related 3-wire version, so I am fairly confident.
[20:26:30] <SWPadnos> andypugh, you have a >6 channel scope to look at the outputs with ...
[20:26:47] <SWPadnos> so you could make it work right according to halscope, and wait for bug reports :)
[20:27:32] <micges> andypugh: If I'll get some spare time I'll look at your comp, we had this programmed to avr :)
[20:30:12] <andypugh> I will be posting a better version to the mailing list, probably tonight.
[20:35:56] <awallin> andypugh: did you get the IRAMS powerstage to work well?
[20:38:38] <andypugh> Not at all at the moment, but I think that is problems with my Arduino-based driver. I plan on transferring what I have learned from the bldc-hall drivers in EMC2 to that, and should be able to get it going. It looks like the arduino code is generating the wrong patterns.
[20:39:40] <andypugh> There is a lot going on with that hardware, including a resolver to hall-signal conversion. It makes a lot more sense to use the sinusoidal component, thinking about it.
[20:50:24] <micges> for consideration: patch removing compile warnings:
http://www.pastebin.ca/1885351
[20:50:48] <micges> (half warnings to be precise)
[21:33:12] <alex_joni> micges: looks ok for master
[21:33:32] <alex_joni> (just skimming over it, not in depth reading, but I assume all of it is like the first 3)
[21:34:32] <micges> yes for master