Back
[00:18:27] <kwallace2> NickParker: I didn't find the manual I recall using to get mine working, but I found a Level II Programming Manual that has information on connecting the RS232 port and covers some of the G codes. I don't have it scanned, but I can if you think you will need it.
[00:19:20] <mozmck> Anyone here have git not see change to a file that is in the repository?
[00:49:54] <NickParker> it's no problem kwallace i got the manual off the previous owners
[00:49:59] <NickParker> time for a kinkos run tomorrow
[01:31:29] <Valen00> can one do threading on a lathe with steppers and the parallel port?
[01:31:46] <Valen00> if so do you use an index pulse and encoder or just an index pulse?
[02:00:35] <Jymmm> I believe you need an encoder on the spindle
[02:16:26] <DJ9DJ> moin
[02:35:34] <archivist> Valen00, yes a parallel port can do it I have a 48 slot disk and an index pulse on my little lathe
[07:36:42] <Tom_itx> looks like another rainy day
[07:36:50] <Tom_itx> wettest July on record iirc
[07:41:11] <jdh> it rained all of june and most of july here
[08:22:04] <jdh> does anyone know the difference between an SFU1605 ball screw/nut and RM1605?
[08:23:28] <archivist> I would if I studied the data sheets
[08:24:09] <alosindustrials> hi
[08:24:20] <alosindustrials> problem with PLT PCI port
[08:24:54] <JesusAlos> ubuntu recognize lpt card
[08:25:11] <JesusAlos> with lspci -v
[08:25:34] <JesusAlos> but linuxcnc don't write neither read in lpt
[08:26:07] <JesusAlos> I connect phisical scope in lpt pins
[08:26:37] <jdh> haven't seen any real data sheets.
[08:27:37] <jdh> Jesus: did you specify the correct address for the port?
[08:28:16] <JesusAlos> I use default
[08:28:18] <JesusAlos> 0x378
[08:28:43] <JesusAlos> with lspci -v don't see the addres
[08:30:31] <jdh> -vvv will show more info. maybe try: dmesg | grep parport also
[08:33:08] <JesusAlos> http://imagebin.org/265982
[08:33:14] <JesusAlos> don't show
[08:37:31] <jdh> might try d000 or d010
[08:39:09] <jdh> looks like RM1605 might be the screw and SFU1605 is nut
[08:48:42] <JesusAlos> yes
[08:48:48] <JesusAlos> d010
[08:48:53] <JesusAlos> thank
[10:50:00] <Aero-Tec2> what is the longest line length allowed in Gcode?
[10:51:21] <archivist> your machine size I would assume
[10:51:32] <Aero-Tec2> I have one 254 and will not load, the error is line is to long
[10:52:18] <archivist> you mean text line length
[10:52:25] <Aero-Tec2> yes
[10:52:51] <Aero-Tec2> was 246 with 2 spaces
[10:53:07] <Aero-Tec2> thought spaces did not count
[10:53:18] <archivist> A permissible line of input code consists of the following, in order, with the restriction that there is a maximum (currently 256) to the number of characters allowed on a line.
[10:54:15] <Aero-Tec2> oops 256
[10:54:43] <archivist> http://www.linuxcnc.org/docs/2.4/html/gcode_overview.html
[10:54:45] <Aero-Tec2> how many can be sent to a sub?
[10:56:57] <cradek> from here you can find that answer with one click:
http://www.linuxcnc.org/docs/html/
[10:57:22] <cradek> (hint: O codes)
[10:59:03] <archivist> has anyone written a gleason lookalike bevel gear generator yet?
[11:02:49] <Aero-Tec2> I have no idea what that is, will have to google it
[11:03:51] <archivist> gleason developed machines to generate gears, with cnc we can do it in code
[11:11:04] <Aero-Tec2> what cutter are you wanting to use?
[11:11:34] <archivist> will probably be making/grinding the cutter
[11:12:10] <Aero-Tec2> single tooth gear hod, ok so a fly cutter type cutter
[11:12:24] <Aero-Tec2> so the code should be easy
[11:12:44] <archivist> hod is a think for carrying bricks
[11:12:48] <archivist> thing
[11:13:04] <Aero-Tec2> thought you were wanting to use a slitting saw and do multi passes per tooth to get the profile
[11:13:33] <archivist> I do use a slitting saw for escape wheels
[11:14:04] <Aero-Tec2> so you do clocks
[11:14:08] <archivist> I want a better quality surface to the drive face
[11:14:18] <Aero-Tec2> hobby or do you make a living making them?
[11:14:34] <archivist> I have done some clock work, was a job
[11:19:13] <Aero-Tec2> I am guessing making a living making clock is just a tad better then as a shoe cobbler. with china and the low cost of buying things it get hard to find sales for hand made quality stuff
[11:19:59] <archivist> er yes hence I got the chop
[11:20:05] <Aero-Tec2> we had a shoe cobbler in town and he had to shut down, nt enough work
[11:21:16] <Aero-Tec2> sorry to hear that
[11:21:17] <archivist> I have been asked to quote some tiny bevel gears but I can forsee some days experimentation for not a lot of pennies
[11:21:23] <Aero-Tec2> it would be cool to be a clock maker
[11:22:05] <Aero-Tec2> how tiny?
[11:22:23] <archivist> 16mm dia 29 teeth
[11:22:49] <archivist> 15.5mm actual
[11:23:06] <Aero-Tec2> has he tried to buy it on the net?
[11:23:31] <archivist> yes, what he wants does not exist :)
[11:24:13] <archivist> stuff available is cheap though, but only in fixed ratios
[11:24:54] <Aero-Tec2> doing a custom job of impossible to find item is fine, doing it to be cheaper and save the guy a few $$ is nuts, unless your wanting to make it and looking for a excuse to do it...lol
[11:25:53] <Aero-Tec2> is the profile of that gear the same as a normal gear?
[11:26:24] <archivist> that depends on which gear book you read
[11:26:32] <Aero-Tec2> would a standard gear cutter work?
[11:27:06] <Aero-Tec2> I was reading that the gear teeth are straight
[11:27:31] <Aero-Tec2> thought that meant no tapper of the profile
[11:28:09] <Aero-Tec2> I have a machinists hand book
[11:28:18] <Aero-Tec2> I could look it up there
[11:28:32] <Aero-Tec2> the net was quick
[11:29:12] <archivist> if I buy a form type cutter the process is different
[11:34:56] <Aero-Tec2> I am guessing your trying to match a existing gear, or do you have to make to matting gears?
[11:35:07] <Aero-Tec2> two
[11:35:10] <Aero-Tec2> sorry
[11:35:57] <Aero-Tec2> just did a quick read through the section of the book
[11:36:07] <Aero-Tec2> looks very trick
[11:36:22] <Aero-Tec2> tons of fun
[11:37:27] <archivist> a pair
[11:38:08] <Aero-Tec2> standard gear cutter will work but 2 passes at different angles, I was wondering how they could do a straight cut
[11:38:14] <archivist> depending on face width the inner is close to a .3 mod gear
[11:39:49] <Aero-Tec2> should be easy with a profile cutting cutter and some code programming
[12:16:13] <IchGuckLive> hi all B)
[12:42:06] <IchGuckLive> im off BBq
[12:45:57] <Aero-Tec2> thought skipped lines were ignored
[12:46:27] <Aero-Tec2> the sub had a line over 300 chr long
[12:48:56] <Aero-Tec2> still not loading
[12:50:52] <Aero-Tec2> ok sub call is 253 chr long 255 it you count a possible 2 chrs for return chr
[12:51:46] <Aero-Tec2> so why if the command line to long error coming up?
[12:52:50] <Aero-Tec2> that 253 is with 2 spaces that should not even count
[12:53:08] <Aero-Tec2> o<g76st-2> call [#<TXS>][#<TZS>][#<TSD>][#<TP>][#<TPI>][#<TIE>][#<TZE>][#<RZS>][#<RZE>][#<TUNN>][#<TFNT>][#<TFNR>][#<TSE>][#<TTC>][#<TFCS>][#<TDD>][#<TNSC>][#<TCSA>][#<TDT>][#<TWE>][#<TSOHS>][#<TRTN>][#<TTN>][#<TMRCD>][#<TRRC>][#<TRFC>][#<TRFR>][#<TIM>]
[12:53:36] <Aero-Tec2> anyone see a problem with that?
[12:54:14] <archivist> what are you editing with
[12:54:36] <Aero-Tec2> Gcode editor, win based
[12:55:01] <Aero-Tec2> I have ultra edit as well
[12:55:16] <Aero-Tec2> that is what I am using for chr count
[12:56:09] <archivist> be everso careful with windows based stuff as it can throw in utf stuff
[12:56:31] <Aero-Tec2> uft?
[12:57:04] <Aero-Tec2> I know the return chrs are different
[12:57:22] <archivist> utf8 or utf16 character sets, multibyte
[12:57:32] <Aero-Tec2> but text edit in linux seems to read it OK
[12:58:11] <Aero-Tec2> OhmEye, as far as I know there is non of that
[12:58:46] <Aero-Tec2> the editor is a bought dedicated Gcode editor
[13:00:57] <archivist> I looked at that line in a hex editor, you should do that too but include the line ends to see if any rubbish
[13:01:09] <Aero-Tec2> so far the test editor in linux has had no problems with showing the gcode the right way, so looks like the win return chr are working, have written Gcode before with it and it ran NP
[13:03:05] <archivist> before you assume the editor is blameless test the WHOLE line including end/s in a hex editor
[13:03:41] <mutilator> anyone here use the makerbot exturder with linuxcnc?
[13:03:44] <mutilator> extruder*
[13:03:48] <Aero-Tec2> 255 with hex
[13:05:03] <Aero-Tec2> 0D 0A
[13:05:10] <Aero-Tec2> are the return chr
[13:05:45] <archivist> Aero-Tec2, another thing I am not sure of is data expansion and real resulting line size where the [#<TTN>] is replaced by the value
[13:05:57] <Aero-Tec2> I have done written severl Gcode programs from scratch with it and had NP
[13:06:05] <archivist> that would catch you out there
[13:06:48] <archivist> 28 parameters!
[13:06:54] <Aero-Tec2> yes
[13:07:06] <Aero-Tec2> cool sub
[13:07:11] <archivist> somewhat excessive
[13:07:11] <Aero-Tec2> for threading
[13:07:29] <Aero-Tec2> does INT and EXT
[13:07:46] <Aero-Tec2> also resizes the stock/hole
[13:08:25] <Aero-Tec2> so it will resize stock for ext and bore out hole for INT
[13:08:41] <Aero-Tec2> and then cut thread
[13:09:06] <archivist> the other ops probably belong in their own smaller ocode routines
[13:09:36] <Aero-Tec2> lol
[13:09:52] <Aero-Tec2> they are but called from the sub
[13:10:16] <Aero-Tec2> so lots of the prams are pass through
[13:10:28] <jdh> you should post them to the wiki or somewhere
[13:10:31] <archivist> bad
[13:10:49] <Aero-Tec2> bad?
[13:10:57] <Aero-Tec2> pass throughs are bad?
[13:11:34] <Aero-Tec2> it does checking so one can not run sub unless things are set right
[13:11:49] <archivist> I think you are making unmaintainable code, I do know about gcode abuse and know when not to go overboard
[13:12:15] <Aero-Tec2> Gcode abuse?
[13:12:29] <Aero-Tec2> the idea is that you code it and forget it
[13:12:52] <Aero-Tec2> fill in a list of values and run sub
[13:13:00] <jdh> with a GUI front end
[13:13:16] <Aero-Tec2> the stock/ hole gets resized IF needed and the threads get cut
[13:13:39] <archivist> you never forget it because next time you want some shoulder groove/taper that is different
[13:13:39] <Aero-Tec2> no GUI
[13:13:46] <Aero-Tec2> just hand coding
[13:14:12] <Aero-Tec2> that is precut before running sub
[13:14:14] <jdh> right. You should add a gui to drive it.
[13:14:21] <archivist> then you have to shoehorn something in the middle
[13:14:33] <Aero-Tec2> ?
[13:14:52] <Aero-Tec2> middle of what?
[13:14:58] <Aero-Tec2> nothing says you can not resize pre sub call
[13:15:16] <Aero-Tec2> the sub check and if no resizing is needed it does not get done
[13:16:35] <Aero-Tec2> one could machine each end of the threaded section call sub and it will resize only the thread section and do thread
[13:18:09] <Aero-Tec2> so with so many prams the data the prams represent maybe to long?
[13:18:33] <archivist> I think so yes
[13:18:59] <Aero-Tec2> makes sense I guess
[13:19:20] <archivist> that is a feature that needs a comment in the docs/a bug report I think
[13:20:33] <Aero-Tec2> would be nice to be able to have long lines, or a line continue chr so lines of code can span more then one line
[13:21:52] <archivist> there is probably some structure internally in some old crusty C that wont let that happen unless someone fixes it
[13:21:54] <Aero-Tec2> it just made sense to me to have a sub that cut to spec threads
[13:22:40] <archivist> I see the start and finish states of threads vary too much to think like that
[13:23:02] <archivist> and I often work in odd threads
[13:24:28] <Aero-Tec2> it even has tool wear and tool point comp
[13:25:07] <Aero-Tec2> each tool has a different point on it so the code had correction for each tool
[13:25:45] <Aero-Tec2> one need to tweak it in the sub, but once done it will know what cutter and change the math to match
[13:25:53] <archivist> that could/should be in the tool table
[13:26:48] <Aero-Tec2> guess it could be done there
[13:27:16] <Aero-Tec2> the programmer in me got a tad over the top
[13:27:17] <Aero-Tec2> lol
[13:27:57] <archivist> linuxcnc already ha wheels :)
[13:28:01] <archivist> has
[13:28:01] <Aero-Tec2> I find it a pain some what to work with the tool table
[13:28:37] <archivist> tool table works well with a tool changer
[13:28:59] <Aero-Tec2> I zero the tool and the point is blunt
[13:29:02] <`Nerobro> tool table?
[13:29:15] <Aero-Tec2> how do I com for the tool point?
[13:30:59] <Aero-Tec2> the idea for tool correction in the sub is, if the threading tool is used for resizing it will cut the the right size, but if use for threading it will not unless the code comps for the missing point
[13:31:44] <Aero-Tec2> so with my code the threading tool can be used for resizing and for threading as well and work well for both
[13:32:43] <Aero-Tec2> archivist, you said "I see the start and finish states of threads vary too much to think like that" what did you mean?
[13:32:50] <archivist> 99% of the users will use a proper tool for the sizing not the threading tool
[13:33:27] <Aero-Tec2> true
[13:33:46] <archivist> as the threading inserts have radiuses for each thread form
[13:34:45] <Aero-Tec2> that is what I was comping for
[13:34:50] <archivist> that way one adjusts the thread depth on its own tool entry
[13:34:53] <jdh> if you use gang tooling, how do you specify the offsets to each tool?
[13:35:26] <archivist> just add the constant of the spacing
[13:35:32] <Aero-Tec2> it is a threading sub, so only does it for the threading tool
[13:36:11] <archivist> now perhaps you see why the drilling and boring use their own tools not the threading
[13:36:46] <Aero-Tec2> each threading call can have it own set if threading data, including tool if needed
[13:37:17] <jdh> no method for automagically recentering the ganged tool like a G55/56/etc or G92?
[13:38:53] <Aero-Tec2> I zero tool 1, every thing is done off that, if ganging the tool the Gcode would have tool position offsets if tool post can be moved and not alway the same
[13:41:22] <archivist> `Nerobro,
http://linuxcnc.org/docs/html/gcode/tool_compensation.html
[13:42:03] <`Nerobro> aaaah
[13:42:41] <Aero-Tec2> I just checked, the data is way smaller then the call
[13:43:12] <Aero-Tec2> most are just 1 chr
[13:43:47] <Aero-Tec2> the long are still shorter that the longest var name
[13:47:02] <Aero-Tec2> I also have fudge/tweak vars that are passed to sub, start with it being zero, cut a thread and check, should be very close, add fudge to get it perfect
[13:49:00] <Aero-Tec2> both threading and resizing have there own fudge to you can get as exact as needed, but the sub does all the math so it should be almost exact with 0 fudge
[13:51:42] <Aero-Tec2> one thing nice about doing in Gcode threading tool point comp is that you can clean the thread tops with the threading tool and not have to do a tool change for that
[13:52:42] <Aero-Tec2> thread top deburing with threading tool
[13:53:29] <cradek> it's nice to clean those tips and then do one more pass through the thread to deburr
[13:53:56] <cradek> given unlimited cash, it's better to use a full profile insert though, I imagine
[13:54:21] <Aero-Tec2> archivist, how would you set up threading tool comp in the tool table for threading tools?
[13:54:22] <archivist> the finish of a full profile tip is luverly
[13:54:34] <Aero-Tec2> full thread cutters are nice
[13:55:02] <archivist> I do not spoil those by using them for turning
[13:55:27] <Aero-Tec2> I have run of the mill points
[13:55:46] <Aero-Tec2> and some points are more to the point then others
[13:56:28] <archivist> and you should see
http://www.linuxcnc.org/docs/devel/html/gcode/overview.html#_equality_and_floating_point_values before you assume the size of your variables
[13:58:42] <Aero-Tec2> still well short of that
[14:00:24] <Aero-Tec2> archivist, for threading what do you use for threading tool zero? and then how do you work out cut thread depth from that zero?
[14:00:56] <jdh> can you debug/print/log the call line args?
[14:01:17] <archivist> I tend to be fiddling for a one off so am not fussy where my 0 is
[14:02:13] <Aero-Tec2> if you know your point is 100% a point then one can calc the thread depth needed, if one knows the % of point missing one can also calc the depth
[14:04:01] <Aero-Tec2> mine are supposed to be points, but fall shy, so I zero what point there is and do a gcode calc that assumes 100% point and do a tool number based comp for the missing %
[14:04:55] <Aero-Tec2> does that sould like a good way to go?
[14:06:53] <Aero-Tec2> I am open to learn new and better way
[14:07:46] <jdh> do you want to do production style runs over and over and have the routine work for that, or do one-offs of everything and have the operator to touch offs for every part
[14:08:35] <Aero-Tec2> I do production runs
[14:08:43] <Aero-Tec2> so tons of tool holders
[14:09:28] <Aero-Tec2> and the tooling tends to stay with tool holder for each job
[14:09:51] <archivist> http://linuxcnc.org/docs/html/lathe/lathe-user.html#_radius_amp_diameter_mode
[14:09:56] <Aero-Tec2> if I can reuse a set tool for other jobs I do
[14:10:31] <archivist> see that next section with the tip radius
[14:11:09] <archivist> I have never bothered trying to check that against a threading tool though
[14:11:47] <Aero-Tec2> but if boring bar need to be set up deeper for new job then what is set up then buy tool and holder for that job and give it a new number in my master tool table and copy that info over to the tool table as needed
[14:12:30] <archivist> I do not remember any docs about control point and threading tools
[14:23:34] <Aero-Tec2> I was wondering if one could set tool point dia for threading tools and had it work
[14:34:00] <Aero-Tec2> jdh, when you said "can you debug/print/log the call line args?" was that for me?
[14:34:26] <Aero-Tec2> I would love to know how to do it if one could do ti
[14:35:25] <jdh> yes
[14:36:22] <Aero-Tec2> would love to have the error code work for subs as well, line x of a sub name has error x
[14:36:49] <jdh> (print, #<var1> #<var2>...)
[14:37:01] <jdh> or debug/log instead of print
[14:37:51] <jdh> http://www.linuxcnc.org/docs/devel/html/gcode/overview.html#sec:log
[14:37:55] <Aero-Tec2> I just shorted the call sub line by one chr will see if that works
[14:40:12] <Aero-Tec2> nope
[14:40:13] <Aero-Tec2> still error
[14:40:40] <jdh> did it log anything?
[14:41:55] <Aero-Tec2> does file logging work for just opening a file?
[14:42:09] <Aero-Tec2> thought that was only for running Gcode
[14:42:40] <Aero-Tec2> the error come up when loading the file
[14:42:45] <jdh> oh
[14:42:52] <jdh> nevermind then :)
[14:42:57] <jdh> use the source.
[14:43:18] <Aero-Tec2> do you mean use the force?....lol
[14:43:52] <Aero-Tec2> not sure what you mean by use the source
[15:00:29] <Aero-Tec2> archivist, so do you think I am guilty of Gcode abuse? also what is Gcode abuse, never heard of that
[15:08:07] <JT-Shop> does dmesg show any errors
[15:11:57] <andypugh> I am really annoyed with myself now. I corrected the swing of the table on my hobber to be the right way. I made a new blank. I tried hobbing again and got exactly the same bad result.
[15:12:36] <JT-Shop> I hate when that happens
[15:12:51] <andypugh> Then I realised, I was looking at the wrong cell in my spreadsheet. It so happens that a 14 tooth gear has the same PCD as the OD of a 12 tooth gear. I have been cutting 14 teeth on a 12-tooth blank. With limited success.
[15:13:59] <andypugh> Coffee, and start all over again, I reckon.
[15:14:30] <andypugh> (Well, I will first try cutting 12 teeth on one of the bits of scrap)
[15:21:21] <jdh> aero: I mean look at the parser source, see what trips that error.
[15:21:34] <Tom_itx> i bet you run outta material before it's done cutting :)
[16:00:18] <DJ9DJ> gn8
[17:31:47] <andypugh> Tom_itx: Fortunately not.
[17:36:39] <andypugh> Came out a lot better this time:
https://picasaweb.google.com/lh/photo/LetFvt7Y_4UQfw5H3Sli5dMTjNZETYmyPJy0liipFm0?feat=directlink
[17:39:14] <cradek> pretty. what's the diameter?
[17:39:16] <kwallace2> Woo, that's purdy.
[17:41:17] <andypugh> 29.63mm diameter gear.
[17:41:26] <andypugh> (12 DP, 12 teeth)
[17:41:49] <andypugh> It's pretty chunky for a home-made gear.
[17:43:25] <JT-Shop> nice
[17:49:57] <Aero-Tec2> sorry had stepped out
[17:50:38] <Aero-Tec2> JT-Shop, what is dmesg?
[17:50:46] <Aero-Tec2> never heard of it
[17:50:58] <andypugh> Aero-Tec2: It's how you view the kernel log.
[17:51:11] <andypugh> Just type "dmesg" at the terminal prompt.
[17:51:24] <Aero-Tec2> cool
[17:51:30] <Aero-Tec2> will try
[17:56:44] <JT-Shop> Aero-Tec2:
http://www.linuxcnc.org/docs/html/common/Linux_FAQ.html#_bootup_messages
[18:00:39] <Aero-Tec2> that looks like it is for computer boot up
[18:00:39] <Aero-Tec2> will it also have info for linuxcnc startup?
[18:01:04] <Aero-Tec2> actually I need info for file loading
[18:01:36] <Aero-Tec2> every thing works fine, and so do other file based subs, just this one is being a pain right now
[18:02:01] <Aero-Tec2> the error shows up when I try to load the test file to test the sub
[18:06:45] <eric_unterhausen> is it possible that the xenomai kernel will have a driver for my wireless card?
[18:06:49] <eric_unterhausen> Ethernet controller: Atheros Communications Inc. AR2413/AR2414 Wireless Network Adapter
[18:06:53] <JT-Shop> yes many things show oup on dmesg
[18:06:54] <Aero-Tec2> did it and did not see anything that looked helpful for the loading error
[18:07:20] <eric_unterhausen> Aero-Tec2, you can always post the output of dmesg to pastebin
[18:07:28] <JT-Shop> clear dmesg and run again
[18:07:36] <Aero-Tec2> ok will do a clear command and then reload the file and see what comes up
[18:07:41] <JT-Shop> pastebin the output
[18:08:17] <Aero-Tec2> where should I look to find this file?
[18:08:49] <Aero-Tec2> would it be in the root dir?
[18:11:21] <eric_unterhausen> which file, the output of dmesg?
[18:11:41] <eric_unterhausen> type dmesg > blahblah.txt
[18:14:30] <Aero-Tec2> I cleared dmesg and checked it was clear
[18:15:34] <Aero-Tec2> loaded the gcode file and ran dmesg and it was blank
[18:15:57] <Aero-Tec2> still getting error of the command line being to long
[18:16:49] <Aero-Tec2> do I need to direct it to a file for it to work?
[18:17:49] <JT-Shop> instructions are in the link
[18:17:50] <Aero-Tec2> I have no problem with linuxcnc startup that I know of, just when loading this gcode file
[18:19:28] <Aero-Tec2> it says to get info about linuxcnc startup
[18:19:54] <JT-Shop> one of my favorite shows theme song
http://www.youtube.com/watch?v=o2In5a9LDNg
[18:19:57] <Tecan> (o2In5a9LDNg) "Take 5" by "TheWhiteAlbum1968" is "Music" - Length: 0:04:22
[18:20:08] <JT-Shop> and errors sent to stderr IIRC
[18:20:38] <Aero-Tec2> and when I cleared dmesg and did a load gfile the cleared the error the dmesg was still empty
[18:21:16] <JT-Shop> ok then it is not sent to stderr
[18:21:35] <JT-Shop> does the G code give you an error when you load it?
[18:22:45] <Aero-Tec2> yes
[18:22:57] <Aero-Tec2> command line to long at line 120
[18:23:11] <Aero-Tec2> or was it around line 120
[18:23:30] <Aero-Tec2> 119 is the call to the file based sub
[18:23:50] <Aero-Tec2> with the long line of variables
[18:24:21] <JT-Shop> ok, so you know what the problem is then
[18:24:28] <Aero-Tec2> I looked in the sub and found a rem line over 300 chrs trimmed that and still got the error
[18:24:48] <JT-Shop> http://www.linuxcnc.org/docs/html/gcode/overview.html#_format_of_a_line
[18:25:45] <Aero-Tec2> the line is under 256, even when you include the spaces that should not count
[18:28:18] <Aero-Tec2> I have read that before and I look to be within the right parameters
[18:28:20] <JT-Shop> a space is a character too
[18:28:23] <Aero-Tec2> it should work
[18:28:45] <Aero-Tec2> well I am still under the line length even counting them
[18:29:52] <JT-Shop> how long does the line evaluate to?
[18:30:11] <Aero-Tec2> the line is 255 including the 2 return chrs that are hidden, used ultra edit and hex to see the complete line code
[18:30:43] <Aero-Tec2> I even shortened it by 1 chr and it still gave the error
[18:30:44] <JT-Shop> how long is it when you evaluate the variables?
[18:31:03] <Aero-Tec2> should be way short of 256
[18:31:30] <JT-Shop> http://www.linuxcnc.org/docs/html/gcode/overview.html#sub:Number
[18:32:16] <JT-Shop> take the variables out and use numbers and see if that is the problem
[18:32:32] <Aero-Tec2> http://pastebin.com/dU9vLE7r
[18:32:43] <Aero-Tec2> this is the info sent
[18:33:04] <Aero-Tec2> the pitch was shortened to pt
[18:33:22] <JT-Shop> debug show 6 digits after the point
[18:33:54] <Aero-Tec2> o<g76st-2> call [#<TXS>][#<TZS>][#<TSD>][#<P>][#<TPI>][#<TIE>][#<TZE>][#<RZS>][#<RZE>][#<TUNN>][#<TFNT>][#<TFNR>][#<TSE>][#<TTC>][#<TFCS>][#<TDD>][#<TNSC>][#<TCSA>][#<TDT>][#<TWE>][#<TSOHS>][#<TRTN>][#<TTN>][#<TMRCD>][#<TRRC>][#<TRFC>][#<TRFR>][#<TIM>]
[18:34:23] <Aero-Tec2> the tp was also shortened tp just p to drop one more chr
[18:34:52] <Aero-Tec2> even for whole numbers?
[18:34:54] <JT-Shop> that would evaluate to 252 for the variables only if only one number to the left
[18:35:27] <JT-Shop> use debug to show you what the variables evaluate to
[18:35:47] <JT-Shop> #<TXS> = 0 (THREAD X_Start)
[18:36:01] <JT-Shop> (DEBUG, #<TXS>)
[18:36:31] <Aero-Tec2> will debug work for file load?
[18:36:41] <Aero-Tec2> thought that was for Gcode running
[18:36:53] <JT-Shop> works in MDI as well
[18:37:01] <Aero-Tec2> cool
[18:37:02] <JT-Shop> or just make a short file
[18:37:32] <Aero-Tec2> so why 6 places after the dec?
[18:37:45] <Aero-Tec2> only 4 are used
[18:38:00] <Aero-Tec2> and why all numbers?
[18:38:16] <Aero-Tec2> whole numbers should be 0 after
[18:38:47] <Tom_itx> nice one andypugh
[18:40:41] <JT-Shop> Numbers may have any number of digits, subject to the limitation on line length. Only about seventeen significant figures will be retained, however (enough for all known applications).
[18:41:37] * Tom_itx is waiting to see some anodizing
[18:41:41] <Aero-Tec2> it showed ######
[18:41:51] * JT-Shop is too
[18:41:54] <Aero-Tec2> witch could be 0.0000
[18:41:58] <JT-Shop> what is an it?
[18:42:03] <Tom_itx> :)
[18:42:34] <Aero-Tec2> (DEBUG, #<p>) in MDI
[18:42:50] <JT-Shop> what was the line before that?
[18:43:09] <Aero-Tec2> the gcode was not run so it had no value assigned to it yet
[18:43:24] <Aero-Tec2> not sure
[18:43:30] <Aero-Tec2> G0 or something
[18:44:01] <Aero-Tec2> I could assign a value and then look and see
[18:44:01] <JT-Shop> you must assign a value to p first in mdi
[18:44:07] <Aero-Tec2> ok
[18:44:16] <JT-Shop> ##### means nothing assigned to that
[18:44:19] <JT-Shop> I guess
[18:45:57] <Aero-Tec2> lol
[18:46:07] <JT-Shop> Tom_itx: I got the circulation pump in yesterday need to get that plumbed up and tested
[18:46:14] <Aero-Tec2> p=0 come out as 0.000000
[18:46:23] <Aero-Tec2> just like you siad
[18:46:27] <JT-Shop> yep
[18:46:27] <Aero-Tec2> ouch
[18:46:39] <Aero-Tec2> that sucks
[18:46:40] <Aero-Tec2> lol
[18:46:40] <JT-Shop> opps back to the drawing board?
[18:47:21] <JT-Shop> make one for internal and one for external
[18:47:39] <Aero-Tec2> so 30 would be 30 single digits left of dec
[18:47:54] <Aero-Tec2> that should be made more clearer in the docs
[18:47:57] <JT-Shop> 30 would be 30.000000
[18:48:09] <JT-Shop> where should that be in the docs?
[18:48:21] <Aero-Tec2> the docs say I can pass 30 variables
[18:49:00] <JT-Shop> yep that is the limit
[18:49:15] <JT-Shop> and you have used up a minimun of 240 chars
[18:49:29] <Aero-Tec2> it says nothing that I found about 30 single left of dec variables
[18:49:56] <JT-Shop> what is a single left of dec?
[18:50:21] <Tom_itx> JT-Shop, saw that you did
[18:50:23] <Aero-Tec2> 0-9
[18:50:30] <Aero-Tec2> 10 would be 2
[18:50:35] <JT-Shop> There are several types of parameter of different purpose and appearance, each described in the following sections. The only value type supported by parameters is floating-point; there are no string, boolean or integer types in G-code like in other programming languages.
[18:51:31] <JT-Shop> http://www.linuxcnc.org/docs/html/gcode/overview.html#sec:parameters
[18:51:40] <Aero-Tec2> so then floting point should have a fixed size no matter the value of the number, right?
[18:51:57] <JT-Shop> and it appears to be fixed at 6
[18:53:02] <JT-Shop> I see the need for a link from oxxx call to parameters overview
[18:53:56] <JT-Shop> by the way you don't have to call a sub with 30 parameters you can use #31 and above with oxxx call
[18:54:21] <JT-Shop> or named just depends on your desired result
[18:54:34] <Aero-Tec2> 31 would be global
[18:54:54] <Aero-Tec2> I could just use a few global named ones
[18:55:31] <JT-Shop> yep
[18:55:51] <JT-Shop> or up to #5000 or named
[18:56:33] <JT-Shop> named global - #<_globalvalue>
[18:56:43] <JT-Shop> http://www.linuxcnc.org/docs/html/gcode/overview.html#sec:parameters
[18:58:09] <Aero-Tec2> it should be explained that passed parameters always have 6 to the right of dec point passed
[18:58:30] <Aero-Tec2> so 1000 is 1000.000000
[18:58:35] <Aero-Tec2> I tried that
[18:59:17] <JT-Shop> http://imagebin.org/266028
[18:59:52] <JT-Shop> it's no fun if you know everything up front :)
[19:00:06] <Aero-Tec2> lol
[19:00:09] <JT-Shop> Tom_itx: ^
[19:00:33] <Aero-Tec2> the docs should say the data is 6 to the left of dec in size
[19:01:18] <Tom_itx> fancy that
[19:01:33] <Aero-Tec2> looks very nice JT-Shop
[19:01:42] <Tom_itx> the real money's in selling the filters
[19:02:33] <Aero-Tec2> unless he make a large whack of them for very good $$$$
[19:02:39] <JT-Shop> the filter is cheap the housing it $$$$
[19:03:01] <Aero-Tec2> JT-Shop, thanks a mill for the help
[19:03:11] <JT-Shop> no problem
[19:03:17] <Aero-Tec2> I was lost and did not know what was wrong
[19:03:30] <JT-Shop> without problems we would not get to chat
[19:03:55] <JT-Shop> I would get lonely and get lots of work done
[19:03:59] <JT-Shop> LOL
[19:04:20] <Tom_itx> and cost your buddies lots of $$$
[19:04:53] <Aero-Tec2> archivist, did point that data size could have been the problem but neither of us know just how big the data load was
[19:05:33] <Aero-Tec2> so a shout out to archivist, thanks for your help as well
[19:08:29] <Aero-Tec2> I used this info in the docs to get a max count of data size to be 4 to the left of dec
[19:08:31] <Aero-Tec2> Numbers used for specific purposes in RS274/NGC are often restricted to some finite set of values or some to some range of values. In many uses, decimal numbers must be close to integers; this includes the values of indexes (for parameters and carousel slot numbers, for example), M codes, and G codes multiplied by ten. A decimal number which is supposed be close to an integer is considered close enough if it is within 0.0001 of an integer.
[19:09:57] <Aero-Tec2> it gave me the impression that max data load was 4 to the right of dec
[19:10:21] <Aero-Tec2> the other should have been max 4 to the right not left of dec
[19:12:01] <Aero-Tec2> now it is time for me to get some work done as well
[19:20:47] <Aero-Tec2> Ok, I am here doing the math to see just how far I am over sized
[19:21:13] <Aero-Tec2> 28 X 8 IS 224
[19:21:59] <Aero-Tec2> 8 being x.xxxxxx
[19:23:05] <Aero-Tec2> there are 2 with minus signs and 2 over 10 and 1 over 100
[19:23:20] <Aero-Tec2> that makes a extra 5
[19:23:47] <Aero-Tec2> do they come with plus and minus signs as well
[19:27:44] <Tom_itx> JT-Shop, does that come in more than one size?
[19:27:50] <Aero-Tec2> when I programmed a floating point was X size, 8 bit, 16 bit, 32 bit, 64 bit or 128 bit even a few 256 depending on the size of the CPU and if it was double precision or single
[19:27:54] <Tom_itx> or is this a one off for you?
[19:29:20] <Aero-Tec2> it would seem that data size would be the some for 1 as for 10000000000000.000000
[19:29:55] <Aero-Tec2> the number of digits should not be a problem
[19:30:33] <Aero-Tec2> number of chrs on a line could be a problem
[19:49:32] <Aero-Tec2> got it loading with full 28 data, the number of chr per line for a file based sub call is lower then 255 including the 2 hidden return chrs I chopped off 3 or 4 more and it worked
[19:50:11] <Aero-Tec2> did not try to find the exact cutoff chr count yet
[19:50:31] <Aero-Tec2> will post when I do
[19:55:52] <Aero-Tec2> it was 255 with the 2 hidden chrs for line end and return would not load, took 4 more off and it loaded, so 251 including the 2 hidden ones loaded
[20:05:03] <Aero-Tec2> should have been the data size would be the SAME
[21:26:50] <skunkworks> https://www.youtube.com/watch?v=M65mJgyxlsg
[21:27:36] <tjb1> french?
[21:27:48] <Aero-Tec2> it has been a very long time since I did any programming so it is taking some time to get back up to speed
[21:28:58] <Aero-Tec2> Spanish/ Latin
[21:30:17] <tjb1> got enough passes on there
[21:30:41] <Aero-Tec2> I have no idea what he is saying
[21:39:46] <Tom_itx> skunkworks, got a belt guard for that?
[21:39:59] <Tom_itx> one day the belt will rip those lines right off there
[21:42:55] <Aero-Tec2> was that skunkworks talking?
[21:43:49] <Aero-Tec2> was it his lathe as well or a borrowed one for the video?
[21:44:15] <Tom_itx> i'll wait to hear him tell the story
[22:03:56] <jdh> I can't get to mine to measure it either.
[22:10:03] <Aero-Tec2> what are we measuring?
[22:10:25] <Aero-Tec2> so is there a Gcode checker program?
[22:10:27] <jdh> the outer/protruding ring on my keling 570oz stepper
[22:12:28] <Aero-Tec2> one that does a quick check to make sure if uses EQ and not = and other cool little things that linuxcnc complains about but does not tell you anything and even less if it is in a sub?
[22:12:41] <Aero-Tec2> it should be very close to spec
[22:12:44] <jdh> debug the sub standalone?
[22:13:10] <Aero-Tec2> look up fame data for it and it should have the size you should be using
[22:13:28] <jdh> they are almost n23, but not quite.
[22:13:47] <Aero-Tec2> I did load the sub as a program and it did not find problem
[22:15:50] <Aero-Tec2> should be to nema specs
[22:16:14] <Aero-Tec2> if not faulty motor as it should be to spec
[22:17:15] <Aero-Tec2> so you have a nema 23? there are bigger sizes if it is way off it could be a larger motor size
[22:17:50] <jdh> it's mostly NEMA23 :)
[22:19:03] <Aero-Tec2> what measurements are not to n23 spec?
[22:19:51] <jdh> The center part of the face
[22:20:05] <jdh> mounting holes are the same.
[22:20:57] <Aero-Tec2> the nema 23 is only for face of motor, so hole spacing and size of housing at the face and size of step for centering motor
[22:21:33] <Aero-Tec2> wow that sucks
[22:21:48] <Aero-Tec2> all my motors from him have been spot on
[22:21:57] <jdh> it is just this one motor
[22:22:48] <Aero-Tec2> how much is it out by?
[22:23:52] <jdh> perhaps I'm wrong. The drawing shows it 38.1mm/1.5". Same as another N23 on his site.
[22:24:02] <Aero-Tec2> if your not wanting to mod the motor or the mount then make a shim plate between the motor and mount
[22:24:36] <jdh> I'm making the mount, it's no big deal to make the recess
[22:26:04] <Aero-Tec2> so back to the gcode checking program
[22:26:13] <Aero-Tec2> is there such a beast?
[22:26:22] <Aero-Tec2> if not would there be a need for one
[22:26:47] <Aero-Tec2> as if there is not one I am tempted to write one
[22:27:04] <tjb1> Your eyes
[22:27:18] <Aero-Tec2> lol
[22:27:31] <Aero-Tec2> easy to miss things
[22:27:44] <jdh> start writing
[22:28:02] <Aero-Tec2> was hoping not to have to write one
[22:28:59] <Aero-Tec2> would be good exercise for the old noggin
[22:29:14] <Aero-Tec2> bring back some old mems
[22:30:35] <Tom_itx> on the topic:
http://www.cnczone.com/forums/general_cam_discussion/2639-computer-numeric-control_g_code_verification_simulation.html
[22:30:46] <jdh> until you get about 63% of the way through writing it and it jsut gets boring.
[22:34:04] <Tom_itx> we used some commercial ones but i dunno how or if they handled subs
[22:34:10] <Tom_itx> n-see was one
[23:04:11] <Aero-Tec2> jdh, yes there has been a few that I wished I did not start part way through
[23:06:46] <jdh> just a few?
[23:07:09] <archivist> axis and vismach
[23:35:07] <Aero-Tec2> so why is #<_lathe_radius_mode> triggering a error?
[23:35:16] <Aero-Tec2> that is a built in one
[23:45:58] <Aero-Tec2> can one file sub call another file sub?
[23:46:37] <Aero-Tec2> getting error, remed out the code for #<_lathe_radius_mode> so bypassed that for now, got to get the machine running
[23:49:23] <Aero-Tec2> never mind, file name was in caps