Back
[02:02:38] <DJ9DJ> moin
[06:22:15] <awallin> is there a tutorial somewhere for adding a tab into AXIS. I'd like to show a graph of some HAL values on the tab..
[06:22:39] <jthornton> with gladevcp?
[06:23:02] <awallin> whatever is easiest
[06:23:49] <jthornton> I'm guessing easy and graph don't go in the same sentence :)
[06:24:01] <awallin> well just number widgets at first
[06:24:08] <jthornton> but I may be full of it and not know it
[06:24:18] <jthornton> pyvcp is the easy way to show a number
[06:24:31] <jthornton> the manual is full of examples for it
[07:14:45] <Loetmichel> mornin'
[07:15:11] <archivist> look at your watch or clock!
[07:15:42] <archivist> must be a coffee failure
[07:16:41] <Loetmichel> morning is when i think its time to get up. *Basta!* ;-)
[07:17:17] <archivist> layzeee
[07:19:14] <jthornton> LOL
[07:20:05] <archivist> past 1 pm here and he is an hour earlier, or should be
[07:25:46] <Loetmichel> an horr later
[07:25:49] <Loetmichel> hour
[07:25:57] <Loetmichel> its about 14:13 over here
[07:27:59] <Loetmichel> so what? its sunday, i already had the car de-iced, driven 20 minutes for 5km through the snow to get some bread buns, crossiants and butter ;-)
[07:47:55] <MattyMatt> anyone need a big chunk of cheap titanium alloy?
http://www.ebay.co.uk/itm/55-00-MM-DIA-TITANIUM-BAR-END-Spec-6AL4V-/271117266252
[07:52:46] <Loetmichel> MattyMatt: too expensive. i stay with silver steel or aluminium 7075, sufficient for my projects ;-)
[07:54:59] <MattyMatt> I noticed it's cheaper than a cast iron slug of similar size
[07:56:08] <MattyMatt> I'll point it out to andypugh. his cycling & boating may have a use
[08:20:30] <MattyMatt> rats. I missed out on a 4 jaw burnard. ebay seems expensive atm. people must be getting lathes for christmas
[08:59:18] <pilla_> Can someone point me towards the correct library that commands LinuxCNC to move the axis to a certain point, and the commands that linuxCNC sends on destination reach?
[08:59:56] <pilla_> I need to program something but I have no clue how to make it interact with LinuxCNC. I'm working in C++
[09:00:03] <archivist> libraary, are you asking the right question
[09:00:28] <archivist> linuxcnc responds to gcode
[09:01:53] <archivist> what are you really trying to do
[09:02:55] <pilla_> I need to make a program that automatically makes a scan of what's on the table. I need the program to command LinuxCNC to move the axis to a certain point, to stop there and send a signal to tell it's received then the camera will send its feed to the program.
[09:03:06] <pilla_> sorta
[09:03:34] <archivist> write out a gcode file that has the commands
[09:03:57] <pilla_> can linuxcnc automatically grab this gcode file?
[09:04:47] <archivist> also see image2gcode
http://www.imagetogcode.com/
[09:05:28] <pilla_> the cnc machine acts as a scanner
[09:05:59] <pilla_> I need it to move its axes to scan
[09:06:26] <archivist> there are scanning gcode programs too that output points
[09:06:54] <gmouer> sounds like you need to write a g-code program to move the axis around, pause in predetermined places and send a digital output during that pause
[09:07:30] <gmouer> a M command can send that digital output during the pause
[09:07:33] <archivist> like
https://github.com/cnc-club/linuxcnc-engraving-comp/blob/master/scan-surface.ngc
[09:07:57] <archivist> all been done :)
[09:24:22] <pilla_> but, so, linuxcnc can just grab these gcodes?
[09:27:59] <gmouer> depends what you mean by "grab" linuxcnc can load and execute gcode files
[09:28:35] <gmouer> that image to gcode example given outputs a gcode file which can then be executed
[09:30:52] <pilla_> I realized I asked a dumb question. Nevermind! :)
[09:30:57] <gmouer> your C++ program could command linuxcnc to execute a loaded file via a HAL pin
[09:32:10] <archivist> almost anything is possible, but is it the right thing to do
[09:33:09] <gmouer> "almost anything is possible" I realize that more and more with linuxcnc, quite amazing
[09:34:11] <archivist> but reinventing a wheel is not needed when it already exists, just search a bit
[09:35:29] <gmouer> yes, but finding some of that info can be a trick searching, that site you gave github.com is one that I have not found before
[09:36:35] <archivist> but google found it for me, the trick was nothing more than sensible search terms linuxcnc scan
[09:37:24] <gmouer> ;) google has been my friend many times in finding info I do it just like you did linuxcnc infoIwant
[09:39:57] <gmouer> Andy: my friend is going forward with his VMC retrofit and those redcap motors. Right now he is sorting out the fanuc spindle motor and getting it to run off a baldor vector drive vfd, soon it will be on to bldc component and those redcap axis motors
[09:48:41] <Aero-Tec> the problem with a google search some times is not having the right terms to use so the search gets what you want
[09:50:26] <Aero-Tec> I have had times where I had to keep searching different things, trying descriptions, or something close as I did not know just the right word or term or name of something
[09:50:50] <Aero-Tec> can get frustrating at times
[09:50:58] <pilla_> English isn't my native language either
[09:52:12] <gmouer> tell me! google comes up with hundreds of hits that you have to weed through to find the one that might actually be of interest I especially hate all the ebay items that come up when searching !
[09:54:06] <gmouer> I bet google seach power users can customize it to eliminate a lot of those spam hits in a search
[10:12:50] <Aero-Tec> can you not put -ebay in the search and it will not show any ebay?
[10:56:17] <JT-Shop> http://semo.craigslist.org/tls/3457247209.html
[10:58:35] <andypugh> Looks like a sturdy bit of kit
[10:59:05] <JT-Shop> yea, more than he bargined for
[10:59:11] <archivist> hehe, there is no way I would let that go, simple to roll off :)
[10:59:14] <JT-Shop> he is about 50 miles from here
[10:59:22] <archivist> go fetch
[10:59:34] <JT-Shop> no room
[10:59:55] <JT-Shop> My lathe is the size he wants
[10:59:57] <archivist> only needs another shed, you know how that works :)
[11:00:04] <JT-Shop> I bet he would trade
[11:00:13] <JT-Shop> first I have to build up some ground
[11:00:14] <Jymmm> JT-Shop: You of course DID make the walls on the new shop modular
[11:01:02] <andypugh> Sounds like a sensible swap, if his lathe is in good condition.
[11:05:02] <Jymmm> JT-Shop: Still have your unloading timbers? =)
[11:05:25] <Aero-Tec> I thought G64 would make a smooth transition from move to move
[11:05:51] <Aero-Tec> I am making springs on the mill
[11:06:07] <Aero-Tec> the spindle is not turned on
[11:07:44] <Aero-Tec> it is just a tool holder and I have a 5th axis that I use for making springs, it is a universal 4th axis, portable, just a motor and planetary gear box that I connect wire forms to
[11:08:35] <Aero-Tec> anyway, it is stopping at each move, it is a spring so it should wind the spring in one move not 3 starts and stops
[11:09:11] <Aero-Tec> any help would be nice, the stops eat up time, and I have 4000 of them to make
[11:09:20] <andypugh> Aero-Tec: It should. Even normal path-following should blend rotary moves.
[11:09:44] <Aero-Tec> so what am I doing wrong?
[11:09:52] <Aero-Tec> back lash is turned on
[11:10:05] <Aero-Tec> would that make a difference?
[11:10:22] <andypugh> I am wondering why it is three moves anyway, why not a single 1080 degree move?
[11:10:31] <archivist> G64 Px.xxx (blend tolerance mode) have you tried a tolerance
[11:10:46] <archivist> any reversals
[11:11:16] <Aero-Tec> F190000
[11:11:18] <Aero-Tec> G1G91X-0.03B100
[11:11:20] <Aero-Tec> G1G91X-0.01B60
[11:11:22] <Aero-Tec> G1G91X-.01B500
[11:11:24] <Aero-Tec> G1G91X-1B3240 ;4680
[11:11:25] <Aero-Tec> G1G91X-0.02B530
[11:11:27] <Aero-Tec> G1G91B-860
[11:11:29] <Aero-Tec> that the meat of the Gcode
[11:11:39] <JT-Shop> Jymmm: sure
[11:11:46] <Aero-Tec> yes I did try the G64 pxx
[11:11:59] <archivist> I do backlash for the rotary in my gcode,
[11:12:07] <Aero-Tec> G64 P0.015
[11:12:26] <Aero-Tec> that is just under the preamble
[11:12:48] <Jymmm> JT-Shop: Heh, now you need to make them into un/load timbers =)
[11:12:50] <andypugh> There is some wierdness about how rotary and linear moves coordinate.
[11:13:00] <Aero-Tec> comes to a complete stop before doing the next move
[11:13:27] <andypugh> I have a vague recollection that inverse-time mode works better.
[11:13:38] <archivist> I would make the P larger to try
[11:14:03] <Aero-Tec> what would you suggest?
[11:14:28] <archivist> I dont know as I want exact stop :)
[11:14:51] <andypugh> You could also try a config with the rotary as your Y axis set up as a linear. That should blend the moves for you.
[11:15:00] <Aero-Tec> inverse time is controlled feed based on spindle speed is it not?
[11:15:18] <Aero-Tec> I have no spindle feed or encoder on spindle
[11:15:28] <Aero-Tec> speed
[11:16:01] <andypugh> No, that's feed per rev. Inverse Time is the _other_ mode.
[11:16:12] <skunkworks> if the accelleration is set really low - it will appear like exact stop
[11:16:22] <andypugh> Where you say how long the move will take.
[11:16:53] <JT-Shop> http://imagebin.org/238660
[11:17:35] <andypugh> Plasma slats?
[11:17:49] <archivist> hmm support...but only just :)
[11:18:35] <Aero-Tec> so can someone explain inverse time to me?
[11:18:37] <andypugh> A plasma cutter would be a better tool for the job, but I guess there is a bootstrapping problem there :-)
[11:18:38] <JT-Shop> yea, new ones fitted into the tank
[11:18:47] <Tom_itx> i like the nice yellow stickers
[11:19:04] <JT-Shop> I cut the first ones using the plasma on saw horses :)
[11:19:18] <Aero-Tec> I was sure it also was feed per rev not done in a different way
[11:20:53] <JT-Shop> https://www.youtube.com/watch?v=EC1_TTlsOrM
[11:21:23] <andypugh> In G93 mode, G1 X10 A20 F2 means that the move should take half a minute. F4 means 15 seconds. (which is why it is "inverse" time).
[11:24:13] <Aero-Tec> so what possible good does that do?
[11:24:22] <Aero-Tec> what use is it?
[11:28:13] <toastyde1th> coordinating axes that are in different units
[11:28:31] <toastyde1th> if you're doing 3+ axis machining with rotary tables, their units are in degrees
[11:28:49] <toastyde1th> so when you have a feed rate of "15," and one axis is in inches and the other is in inches
[11:28:59] <toastyde1th> that's probably not what you wanted
[11:29:28] <toastyde1th> so inverse time takes care of that and you calculate how long the move should take, and does an end-run around the problem of trying to coordinate the axis feeds
[11:32:55] <Aero-Tec> cool
[11:33:36] <Aero-Tec> I just set the speed insanely high and let the machine try to hit it
[11:34:20] <Aero-Tec> I needed the speed high for deg of rotation
[11:35:05] <Aero-Tec> I have noticed that the rotary axis speeds are not at full
[11:35:18] <Aero-Tec> nor is the linear one
[11:35:42] <Aero-Tec> linear can run at 45 but maxes out at 16
[11:36:07] <toastyde1th> 45 what
[11:36:21] <Aero-Tec> and the rotary one I am not sure what speed it is going but now where near max
[11:36:30] <Aero-Tec> IPM
[11:37:04] <toastyde1th> how long is the move
[11:37:14] <Aero-Tec> is that not what the DRO is set at?
[11:37:18] <Aero-Tec> IPM
[11:37:26] <Aero-Tec> 1 inch
[11:37:43] <toastyde1th> a one inch move isn't going to get an axis up to maximum speed
[11:38:12] <toastyde1th> you'll have to make a long ass move because the machine needs to accomodate the accel/decel
[11:38:12] <Aero-Tec> it hits 16 fast and holds
[11:38:28] <toastyde1th> weird
[11:38:35] <Aero-Tec> it could hit higher for sure
[11:39:25] <toastyde1th> you might want to talk to someone who actually knows about emc, because something could be set wrong?
[11:39:50] <Aero-Tec> I was hoping I was talking to a emc guy
[11:40:09] <archivist> it wont hit top speed if the rotary is holding it back
[11:40:10] <toastyde1th> hah, no
[11:40:24] <toastyde1th> i'm just a machinist, not an emc guy
[11:40:31] <Aero-Tec> would a G93 move make a difference?
[11:41:08] <archivist> I dont think so because it is a co-odinated move
[11:41:15] <L84Supper> http://www.muktware.com/4946/ubuntu-1304-will-allow-instant-purchasing-right-dash#.UMOo39Fts_g
[11:41:16] <Aero-Tec> I have changed G64 P0.015 to G64 P0.15
[11:41:21] <Aero-Tec> will try that
[11:42:28] <L84Supper> this the just the angle we needed to get LinuxCNC into new machines.... open source flexible machine controller and now Instant Purchasing of Music and software
[11:43:53] <Aero-Tec> so G93, how does one calculate F setting?
[11:44:45] <Aero-Tec> if one used F 1,000,000 would that make the machine go as fast as it can?
[11:44:48] <toastyde1th> very few people actually calculate g93 by hand, it's for CAM packages
[11:45:41] <L84Supper> "that end mill must bet getting dull by now, how about one of these new from Whizzly or Emko?, press here for instant ordering and delivery"
[11:46:06] <Aero-Tec> LOL
[11:46:11] <Aero-Tec> good one
[11:46:34] <Aero-Tec> your coolant is low, press here to reorder
[11:46:46] <Aero-Tec> could work
[11:46:48] <Aero-Tec> lol
[11:46:50] <L84Supper> yeah
[11:47:47] <L84Supper> not sure how Canonicomical gets their cut
[11:47:59] <Aero-Tec> will try g64 first, then G93
[11:48:05] <Aero-Tec> see what happens
[11:49:04] <L84Supper> http://blog.canonical.com/2012/12/07/searching-in-the-dash-in-ubuntu-13-04/
[11:49:37] <IchGuckLive> hi all B)
[11:51:02] <Aero-Tec> G64 P0.15 did nothing new
[11:51:09] <Aero-Tec> no change at all
[11:51:23] <IchGuckLive> Aero-Tec: more speed requierd
[11:52:00] <Aero-Tec> F190000
[11:52:09] <Aero-Tec> that is the speed setting now
[11:52:21] <Aero-Tec> and it stops at each move
[11:52:21] <IchGuckLive> whow can you post your ini
[11:52:37] <Aero-Tec> can do
[11:52:38] <archivist> Aero-Tec, add more p
[11:53:12] <IchGuckLive> Aero-Tec: please to check it Thanks
[11:53:37] <Aero-Tec> I started with G64 P0.015 and went to G64 P0.15 and there was no change
[11:53:48] <Aero-Tec> what P do you think I should go to?
[11:53:55] <IchGuckLive> it is maybe a simple ini foult
[11:53:58] <Aero-Tec> will do
[11:53:59] <archivist> enough to see a difference
[11:54:17] <IchGuckLive> Aero-Tec: is it a stepper or servo
[11:54:34] <Aero-Tec> the mill is stepper
[11:54:55] <Aero-Tec> should have just said stepper
[11:54:56] <archivist> IchGuckLive, he is doing a coordinated rotary with x
[11:55:04] <IchGuckLive> then i need your worst latency and stepper friver modell to get proper numbers to you
[11:55:09] <JT-Shop> what is the max speed and accel for each axis?
[11:55:27] <IchGuckLive> JT-Shop: i told hiom to post the in i
[11:55:42] <Aero-Tec> I am getting the ini for you
[11:56:09] <andypugh> You could have been on part 2000 by now...
[11:57:00] <Aero-Tec> lol
[11:57:07] * JT-Shop goes to wash the opposum grease off my face
[11:57:10] <Aero-Tec> close but not that high
[11:57:23] <Aero-Tec> I can do about 200 per hour right now
[11:57:57] <IchGuckLive> aero is it the laser cutter with 40mm/rev speed
[12:01:36] <Aero-Tec> knee mill
[12:01:44] <Aero-Tec> I set it up to make springs
[12:01:57] <Loetmichel> *grrr*, i hate small series... 60min building of a clamp for 20 min milling the groove into the 9 locks ... inefficient :-( ->
http://www.cyrom.org/palbum/main.php?g2_itemId=13805
[12:05:30] <toastyde1th> no vise?
[12:06:27] <IchGuckLive> Loetmichel: snow hight
[12:07:17] <Loetmichel> toastyde1th: the vise is underneath tha white table
[12:07:30] <Loetmichel> but the locks have to be in the same position
[12:08:04] <Loetmichel> and are bigger at the down side, so the vise wouldnt grip them right without some distance plates
[12:08:16] <Loetmichel> IchGuckLive: about 10 cm or so
[12:08:17] <andypugh> You could have spent twice as long on a truly generic lock-holder for next time.
[12:08:48] <andypugh> I would have thought you could have clamped them with two V-blocks though?
[12:09:10] <Loetmichel> andypugh: i made a clamp the mast time... but i haven't found it today... :-(
[12:09:45] <Loetmichel> http://www.cyrom.org/hajo/schlossnut.avi
[12:12:04] <Aero-Tec> http://pastebin.com/AMUdeE08
[12:12:09] <Aero-Tec> my INI
[12:12:15] <Aero-Tec> sorry for taking so long
[12:12:53] <Aero-Tec> the windows/linux networking did not want to play nice
[12:13:05] <IchGuckLive> MAX_ACCELERATION = 7.5
[12:13:57] <IchGuckLive> Aero-Tec: on axis 2 16
[12:14:19] <IchGuckLive> STEPGEN_MAXACCEL = 22 for axis 2
[12:15:10] <IchGuckLive> MAX_VELOCITY = 30. for ayis 3 why so low it is a rotation
[12:15:35] <IchGuckLive> your scale is 500 go up to 360
[12:15:46] <IchGuckLive> on axis 3
[12:16:10] <IchGuckLive> MAX_ACCELERATION = 3600 on axis 3
[12:16:26] <IchGuckLive> STEPGEN_MAXACCEL = 4500 on axis 3
[12:16:28] <Aero-Tec> it is a large rotary table, 10 inch, maybe more, would have to remeasure it
[12:16:56] <IchGuckLive> axis 4 STEPGEN_MAXACCEL = 4000.0
[12:17:14] <Aero-Tec> that is 500 per deg
[12:17:28] <IchGuckLive> check the limits for axis 4
[12:18:08] <IchGuckLive> yes you can go 22.000 steps per sec /500
[12:18:30] <Aero-Tec> that is a motor connected to a planetary gear, I use it for making springs
[12:18:41] <Aero-Tec> so it turns allot in one dir
[12:18:45] <IchGuckLive> no matter
[12:18:58] <IchGuckLive> your latency is 25K
[12:19:14] <Aero-Tec> not sure what it is
[12:19:16] <IchGuckLive> so at least 20k steps per second
[12:19:30] <Aero-Tec> the wiz will not go below 100K
[12:19:31] <IchGuckLive> with no loos
[12:19:58] <Aero-Tec> EMC has not complained
[12:20:12] <Aero-Tec> not sure of lost steps
[12:20:23] <Aero-Tec> so far it is looking good
[12:20:33] <IchGuckLive> if you put this numbers here the real latency and your driver modell then we can interaxt to the Hal as well
[12:20:38] <Aero-Tec> but have not had time to hammer it hard to find out
[12:21:27] <Aero-Tec> do you want my hal as well?
[12:21:38] <IchGuckLive> min and max are U32 so your numbers will give a standart error but will run
[12:21:44] <IchGuckLive> no hal is not needet
[12:21:48] <Aero-Tec> I can post the number of the tester
[12:22:23] <Aero-Tec> 12500 if mem serves me
[12:22:37] <Aero-Tec> some where around there
[12:22:55] <Aero-Tec> can retset and find out the exact number
[12:23:01] <Aero-Tec> retest
[12:23:02] <IchGuckLive> let it run with 4 times glxgears and copy somthing around the HDD
[12:23:15] <Aero-Tec> ok
[12:23:19] <Aero-Tec> BRB
[12:36:11] <Aero-Tec> sure bogged it down
[12:36:21] <Aero-Tec> took forever for things to come up
[12:36:29] <Aero-Tec> 8855
[12:36:34] <Aero-Tec> 10712
[12:36:40] <IchGuckLive> good and your driver
[12:36:55] <Aero-Tec> that was jitter
[12:36:56] <IchGuckLive> a gecko leadshine ....
[12:37:05] <Aero-Tec> not sure what you asking now
[12:37:14] <IchGuckLive> the stepper driver
[12:37:18] <Aero-Tec> gecko
[12:37:19] <andypugh> FWIW the stopping at the end of each move has nothing at all to do with latency.
[12:37:26] <IchGuckLive> 201 203
[12:37:31] <IchGuckLive> 540
[12:37:37] <Aero-Tec> 201 I believe
[12:37:47] <IchGuckLive> let me calculate
[12:37:53] <Aero-Tec> the cheapest ones they had 15 years ago
[12:37:54] <Aero-Tec> lol
[12:40:56] <IchGuckLive> ok calculation on your numbers is 22kSteps/sec max save
[12:41:15] <IchGuckLive> get your latency to 15000 in the ini
[12:41:28] <Aero-Tec> ok
[12:41:36] <IchGuckLive> in Hal set sreplen to 1 for eatch axis
[12:41:44] <IchGuckLive> stepspace to 2
[12:41:53] <IchGuckLive> dirsetup to 1
[12:42:01] <IchGuckLive> and dirhold to 3
[12:42:20] <IchGuckLive> stepgen.xxxxx
[12:44:10] <Aero-Tec> anything else need changing?
[12:44:20] <IchGuckLive> Axis 0and 1 MAX_VELOCITY = 1.2
[12:44:31] <IchGuckLive> MAX_ACCELERATION = 12
[12:44:36] <Aero-Tec> also how do I stop the stopping per move?
[12:45:06] <IchGuckLive> STEPGEN_MAXACCEL = 18
[12:45:53] <IchGuckLive> Axis 2 why is there sutch a high scale
[12:46:17] <Aero-Tec> when I had it set that high I would loose steps when the machine is cold
[12:46:34] <Aero-Tec> right now axis 2 is not used
[12:47:01] <Aero-Tec> I did not use the Z with mach as it was wanting to plunge through the table
[12:47:12] <Aero-Tec> and what ever else was in the way
[12:47:15] <IchGuckLive> then Axis 3
[12:47:25] <IchGuckLive> MAX_VELOCITY = 40
[12:47:32] <Aero-Tec> was very erratic
[12:47:41] <IchGuckLive> MAX_ACCELERATION = 400
[12:47:53] <Aero-Tec> ax 3 and 4 are rotary
[12:47:58] <IchGuckLive> STEPGEN_MAXACCEL = 500
[12:48:11] <IchGuckLive> yes i know
[12:48:19] <Aero-Tec> 3 is a large rotary table
[12:48:24] <IchGuckLive> AXis 4
[12:48:29] <Aero-Tec> 10+ inch
[12:48:40] <Aero-Tec> with worm drive
[12:49:03] <Aero-Tec> ax 4 is a motor and a planetary drive
[12:49:16] <Aero-Tec> used for making springs
[12:49:43] <Aero-Tec> clamped into vise and a wire form connected to it
[12:50:19] <IchGuckLive> MAX_VELOCITY = 0.51
[12:50:36] <IchGuckLive> MAX_ACCELERATION = 4
[12:50:45] <IchGuckLive> STEPGEN_MAXACCEL = 5
[12:51:09] <IchGuckLive> get the limits within 12digits
[12:51:15] <archivist> the rotary is a serious restriction
[12:51:18] <Aero-Tec> are you saying I should set ax 4 to that?
[12:51:27] <IchGuckLive> yes
[12:51:50] <IchGuckLive> then you got the max speed out of your drives
[12:52:28] <IchGuckLive> diont forget the stepgen numbers thease are the most imported ones for eatch axes
[12:52:32] <IchGuckLive> in the hal
[12:52:33] <archivist> max speeds are no good if they cause step loss
[12:52:50] <IchGuckLive> Save speed no loos at this numbers
[12:53:02] <IchGuckLive> there is a 2x safty in
[12:53:13] <archivist> you dont know the machine how can you say that
[12:53:17] <Aero-Tec> I got near max with v being 900, not 0.51
[12:53:33] <Aero-Tec> deg per min is it not?
[12:53:43] <IchGuckLive> deg/sec
[12:53:44] <Aero-Tec> 0.51 would take forever
[12:54:14] <IchGuckLive> Axis 4 SCALE = 38.889 steps per deg
[12:54:26] <Aero-Tec> it has low steps per deg
[12:54:31] <Aero-Tec> yes
[12:54:33] <IchGuckLive> you can only go 22k steps per secc
[12:54:37] <Aero-Tec> and 900 works
[12:54:42] <IchGuckLive> so its 0.51 deg /sec
[12:55:17] <Aero-Tec> 300 was low, went to 600, then 900
[12:55:36] <IchGuckLive> sooy im wrong it is 38dot
[12:55:57] <Aero-Tec> is the other settings your getting me to make going to make that much difference?
[12:56:28] <IchGuckLive> MAX_VELOCITY = 510
[12:56:44] <IchGuckLive> MAX_ACCELERATION = 4000
[12:56:53] <IchGuckLive> STEPGEN_MAXACCEL = 5000
[12:57:00] <IchGuckLive> for axis 4
[12:57:04] <Aero-Tec> will try
[12:57:07] <IchGuckLive> O.O
[12:57:16] <archivist> back up, so you can restore sense after trying
[12:57:20] <Aero-Tec> with max speed I had to set the acc to 2000
[12:57:47] <IchGuckLive> yes 900 is way to mutch per sec
[12:57:56] <Aero-Tec> I set it to 3000 as I was not getting max speed in my moves for making the spring
[12:58:19] <IchGuckLive> i need to go off for 10min
[12:58:33] <Aero-Tec> when will you be back?
[12:58:38] <Aero-Tec> any idea
[12:58:48] <Aero-Tec> thanks for the help
[13:12:31] <IchGuckLive> Aero-Tec: Back
[13:12:39] <Aero-Tec> me to
[13:12:46] <Aero-Tec> will post hal
[13:12:58] <Aero-Tec> I am confused about what to do with it
[13:13:17] <Aero-Tec> stepgen.xxxxx
[13:13:26] <Aero-Tec> not sure what to do with that one
[13:13:39] <IchGuckLive> in hal there are 4 entries of stepgen per axis
[13:14:17] <IchGuckLive> this difines the timing of your driver Gecko towards the latency
[13:15:59] <IchGuckLive> Aero-Tec: why is your scale on 0 and 1 so high i calculated a good 2540 woudt give you a very good acuracy acording to your backlash
[13:16:18] <IchGuckLive> 1/2540 = 0.0004
[13:17:04] <IchGuckLive> SCALE = 16010.0 is way tpo mutch change your leadscrew if you can
[13:18:23] <IchGuckLive> with a stepper a leadscrew TR20x4 is best to go as 400Steps/rev at the stepper gives you a metric 0.01 acuracy
[13:18:38] <IchGuckLive> and a vewry high speed
[13:19:18] <IchGuckLive> 0.01mm=0.00039inch
[13:20:11] <IchGuckLive> 1/16010 is better then the atomic clock O.o
[13:20:58] <IchGuckLive> 0.0015mm
[13:21:14] <Aero-Tec> my hal
[13:21:16] <Aero-Tec> http://pastebin.com/dk0ub2TB
[13:21:23] <IchGuckLive> ok EDM will need this
[13:21:33] <archivist> he is coil winding where is accuracy and resolution needed
[13:21:56] <IchGuckLive> setp parport.0.reset-time 5000
[13:22:05] <IchGuckLive> there is a zero missing
[13:22:19] <IchGuckLive> that is your main problem
[13:23:43] <Aero-Tec> just wanting to fine tune things
[13:23:44] <IchGuckLive> setp stepgen.0.stepspace 2 FOR all Axis
[13:24:11] <Aero-Tec> the main thing was it stopping 2 times making 3 moves
[13:25:29] <IchGuckLive> setp stepgen.2.dirhold 45000
[13:25:51] <IchGuckLive> yes it will not stop
[13:26:05] <IchGuckLive> setp stepgen.2.dirsetup 20000
[13:26:19] <IchGuckLive> give this to all axis
[13:26:23] <IchGuckLive> in hal
[13:26:48] <IchGuckLive> and dont forget the latency BASE_period in ini to be set to 15000
[13:27:09] <Aero-Tec> the ini is all done to your specs
[13:27:19] <Aero-Tec> thanks for all this help
[13:27:24] <IchGuckLive> zhen you will se your g-code runnning at nice speed no sto p
[13:28:58] <IchGuckLive> http://www.youtube.com/watch?v=g6h39Aun_Q0
[13:30:11] <Aero-Tec> as for the lead screw and steps per inch
[13:30:32] <Aero-Tec> I have a planetary on it
[13:30:41] <Aero-Tec> more power but slower
[13:30:57] <Aero-Tec> It is a acme screw right now
[13:31:08] <Aero-Tec> soon to be upgraded to ball
[13:31:34] <IchGuckLive> balls are very cheep in this days
[13:31:43] <Aero-Tec> true
[13:32:00] <Aero-Tec> I started with nothing and a shoe string
[13:32:08] <IchGuckLive> i looked in a shop anounce 5years ago it wars 10times that price
[13:32:48] <Aero-Tec> my money has gone to tooling and supplies
[13:33:13] <IchGuckLive> http://stores.ebay.de/cnc-discount/Kugelumlaufspindel-20mm-/_i.html?_fsub=2960857013&_sid=1025469733&_trksid=p4634.c0.m322
[13:33:37] <Aero-Tec> getting close to where I can now afford to redo the screws and other updates like new electronics
[13:37:13] <Aero-Tec> bought a new lathe and mill so I could use it for redoing the old lathe and mill
[13:37:39] <IchGuckLive> ok im off for today have a nice day
[13:37:40] <Aero-Tec> would hate to rip the old apart and not have anything to use if needed
[13:37:43] <IchGuckLive> BY
[13:37:47] <Aero-Tec> bye
[13:38:02] <IchGuckLive> getting the last snow shuffle of the day
[14:20:48] <skunkworks> the mesa resolver interface - only interfaces with the 50pin (like 5i20...)
[14:21:05] <skunkworks> (7I49)
[14:21:15] <skunkworks> nothing for the 5i25 yet?
[14:21:22] <skunkworks> maybe I already asked this..
[14:27:33] <andypugh> Yes, it's a 50pin board.
[14:27:59] <andypugh> However, it is probably possible to use it with a 5i25, it's mainly a matter of wring.
[14:28:23] <andypugh> I am liking my 7i49.
[14:28:57] <andypugh> 16777216 cpr encoders :-)
[14:31:34] <skunkworks> wow
[14:32:10] <skunkworks> andypugh: and firmware?
[14:32:32] <andypugh> I think that Mesa say that the numbers are only realy good to 16 bits.
[14:33:04] <awallin> how do you get 16 M counts?
[14:33:04] <andypugh> I think you would have to build a custom 5i25 / 7i49 firmware, then flash it to the 5i25.
[14:33:16] <skunkworks> ok - thanks
[14:33:18] <andypugh> The numbers out of the board are 24bits
[14:35:21] <awallin> ? specs say 14bit adc with about 12bit absolute accuracy
[14:36:27] <andypugh> There is a tracking filter so that the position accuracy can be greater than the individual sample accuracy.
[14:37:43] <skunkworks> http://www.cnczone.com/forums/showthread.php?p=1206851#post1206851
[14:42:01] <skunkworks> andypugh: sounds like a job for bldc.comp as he wants to do it on the cheap...
[14:42:38] <skunkworks> He could buy a cheap amc drives and use bldc.comp to do the phasing...
[14:42:41] <skunkworks> maybe
[14:43:53] * JT-Shop thinks the new slats will be 1000% better than the old slats
[15:11:18] <Tom_itx> shame mouser didn't have that opto, i'd have tried one out
[15:15:33] <skunkworks> andypugh: for someone that has more time than money....
[16:09:19] <JT-Shop> yikes Tornado Warning!
[16:19:05] <skunkworks> yikes?
[16:19:09] <skunkworks> !
[16:19:39] <JT-Shop> yea, the watch area is more to the north but we are on the edge so keeping an eye out
[16:25:50] <skunkworks> be careful
[16:28:47] <DJ9DJ> gn8
[16:32:58] <JT-Shop> aye
[16:55:05] <adb> aye ?
[17:12:24] <Tom_itx> JT-Shop, kinda hard to see em comin in your area isn't it?
[17:12:34] <Tom_itx> at least it's flat here
[17:13:05] <JT-Shop> you can hear them, I know from experiance
[17:13:10] <JT-Shop> all passed now
[17:13:17] <Tom_itx> good
[17:13:45] <Tom_itx> gettin kinda chilly here
[17:13:52] <Tom_itx> around 32f right now
[17:14:33] <Tom_itx> still droppin.. now 30
[17:15:27] <JT-Shop> they was on the edge of that cold front
[17:15:28] <Nick001-Shop> Still trying to get yesterdays project going. I have a vertical slide that advances and retracts with M codes. There is an end of travel switch that I have connected to a hal pin. How do I convert that true and false signal into something that M 66 can read.
[17:22:24] <JT-Shop> what does the M66 do?
[17:22:51] <micges> read hal input into gcode variable
[17:22:51] <Tom_itx> waits for input
[17:23:07] <Tom_itx> but it doesn't say where it comes from other than input 0..3
[17:23:13] <JT-Shop> I mean in his M1xx code...
[17:24:59] <Nick001-Shop> m66 waits for a signal
[17:25:03] <Tom_itx> how do you define the inputs though?
[17:26:16] <JT-Shop> M1xx stops executing of G code until it is finished so you don't need M66
[17:26:37] <Nick001-Shop> my M105 and M106 code is parport .0.08-out true and false to a selinoid
[17:27:17] <Tom_itx> JT-Shop, how would you define those on a mesa card though?
[17:27:22] <JT-Shop> ok so your doing a M105 then a M66 Px
[17:27:38] <JT-Shop> you just connect them in hal
[17:27:55] <JT-Shop> motion.digital-in-nn <= input pin
[17:28:00] <Nick001-Shop> I need to hold M106 from executing until the end of travel switch activates witch is parport.0.pin10-in
[17:28:01] <Tom_itx> oh ok
[17:28:43] <JT-Shop> did you connect the paraport pin in hal?
[17:29:20] <JT-Shop> net slide-input motion.digital-in-00 <= parport.0.pin10-in
[17:29:37] <Nick001-Shop> yes - I can see it switchine as the switch is on and off
[17:30:00] <Nick001-Shop> switching
[17:30:58] <Nick001-Shop> just the net slide or also the motion.digital--
[17:32:07] <JT-Shop> so M105 and M106 work as expected?
[17:32:43] <Nick001-Shop> yes
[17:33:01] <JT-Shop> and you have the net line similar to the one above?
[17:33:41] <Nick001-Shop> not yet - witch lin do I use
[17:33:49] <Nick001-Shop> and would M66 P00 L3 be correct format?
[17:34:08] <JT-Shop> yes, only one 0 for P is needed
[17:34:19] <JT-Shop> net slide-input motion.digital-in-00 <= parport.0.pin10-in
[17:34:44] <JT-Shop> example from the manual M66 P0 L3 (wait for digital input 0 to turn on)
[17:35:50] <Nick001-Shop> thats what I was reading but couldn't fin the net slide info
[17:36:14] <Nick001-Shop> find
[17:36:18] <JT-Shop> an example would help in the manual...
[17:36:30] <JT-Shop> I'll speak to the manual guy in the morning
[17:37:06] <Nick001-Shop> I guess thats why I couldn't find it -)
[17:37:13] <Nick001-Shop> Ill go put this in now and be back
[17:37:18] <JT-Shop> ok
[17:40:35] <Aero-Tec> what is the best way to get one smooth movement from multi linear and rotary sync moves?
[17:42:13] <Aero-Tec> does one need to use G93?
[17:43:25] <Aero-Tec> F190000
[17:43:27] <Aero-Tec> G1G91X-0.03B100
[17:43:29] <Aero-Tec> G1G91X-0.01B60
[17:43:30] <Aero-Tec> G1G91X-.01B500
[17:43:32] <Aero-Tec> G1G91X-1B3240 ;4680
[17:43:34] <Aero-Tec> G1G91X-0.02B530
[17:43:35] <Aero-Tec> G1G91B-860
[17:43:37] <Aero-Tec> that the meat of the Gcode
[17:44:03] <Aero-Tec> should I be using G93 for this?
[17:44:32] <Aero-Tec> G65 did not work to make it one smooth movment
[17:46:42] <Aero-Tec> G64 P0.15 did not help with smooth movement
[17:47:13] <JT-Shop> is B a rotary axis?
[17:48:27] <Aero-Tec> yes
[17:48:38] <Aero-Tec> a and b are
[17:48:47] <JT-Shop> if your using a rotary and a linear together in blended movement G93 is what is normally used
[17:49:09] <JT-Shop> your making very small moves on X and pretty big angle changes on B
[17:49:10] <Aero-Tec> instead of G1?
[17:49:21] <Aero-Tec> yes
[17:49:28] <Aero-Tec> it is a spring
[17:49:45] <Aero-Tec> using a mill to make a spring
[17:50:12] <JT-Shop> so in effect your wanting to spiral out as the spring winds?
[17:51:53] <Aero-Tec> not sure what your seeing in your minds eye
[17:52:11] <Aero-Tec> motor is held in vise
[17:52:23] <Aero-Tec> spindle is tool holder
[17:52:39] <Aero-Tec> spindle off
[17:53:21] <Aero-Tec> motor in vise is laying along the x axis
[17:54:07] <Aero-Tec> wire form in connected to motor in vise
[17:55:06] <JT-Shop> I'm not sure either, do you have a photo?
[17:58:29] <Aero-Tec> not yet
[17:58:55] <JT-Shop> making an extension or compression spring?
[18:00:47] <Aero-Tec> compression
[18:01:17] <JT-Shop> I think I understand what your making now
[18:01:37] <Aero-Tec> I have a nice camera here somewhere
[18:01:56] <Aero-Tec> land of the lost right now
[18:03:22] <JT-Shop> so it makes a momentary stop at the end of each line of G code?
[18:05:41] <JT-Shop> you do know G1 and G91 are modal?
[18:05:59] <Aero-Tec> yes to stop
[18:06:17] <Aero-Tec> what do you mean by modal?
[18:06:25] <JT-Shop> I get an error trying to run your sample
[18:06:48] <JT-Shop> modal is they stay in effect until something else is commanded
[18:07:02] <Aero-Tec> ok
[18:07:04] <Aero-Tec> yes
[18:07:53] <Aero-Tec> same with G93
[18:08:07] <JT-Shop> I get indexing axis B can only be moved with G0 when I try and run your snippet
[18:08:51] <JT-Shop> http://linuxcnc.org/docs/devel/html/gcode/overview.html#sec:Modal-Groups
[18:16:55] <Aero-Tec> that was just the main part
[18:17:19] <Aero-Tec> it works fine
[18:17:37] <Aero-Tec> would like it to be one long smooth run and not stop
[18:25:31] <Aero-Tec> found camera
[18:26:54] <JT-Shop> can you pastebin the G code?
[18:27:28] <toastyde1th> if your program is stopping after every line, there is an exact stop mode that might need to be disabled
[18:28:12] <JT-Shop> 3 done 3 to go
http://imagebin.org/238708
[18:28:16] <Aero-Tec> http://pastebin.com/nZVDbQ8a
[18:28:56] <toastyde1th> also the machine has to know it has a contouring b axis for it to allow g1 moves
[18:29:15] <toastyde1th> (to jt-shop)
[18:29:23] <Aero-Tec> that is the new G93 version
[18:29:58] <JT-Shop> contouring axis?
[18:30:02] <Aero-Tec> can convert it back to old version if needed
[18:30:28] <Aero-Tec> they move at the same time
[18:30:32] <toastyde1th> JT-Shop, i'm not sure how emc handles it, but machines can have two types of rotary axes
[18:30:33] <Aero-Tec> B and X
[18:31:06] <toastyde1th> indexing, where the table cannot actually cut during a move, so the machine locks all other axes down and disallows g1 or any other type of cutting move while the axis is unlocked
[18:31:21] <toastyde1th> and contouring, where the axis is like any other lineaer axis and can handle cutting forces
[18:31:22] <JT-Shop> ah let me look that up
[18:31:31] <toastyde1th> *linear
[18:32:00] <Aero-Tec> it just stops for a split second between moves
[18:32:03] <toastyde1th> i'm also 95% sure that EMC implements an exact stop mode, which is something Aero-Tec should look for
[18:32:14] <toastyde1th> because it's bad to have on unless you need it
[18:32:29] <JT-Shop> ah the sim had it configured as a locking rotary
[18:33:36] <Aero-Tec> G64, is that not suppose to disable exact stop?
[18:33:44] <JT-Shop> no error now but nothing moves
[18:33:55] <toastyde1th> i don't know what emc does with g64, because i am used to Fanuc, not emc
[18:34:15] <JT-Shop> http://linuxcnc.org/docs/devel/html/gcode/overview.html#sec:Modal-Groups
[18:35:26] <toastyde1th> emc handles exact stop very differently from fanuc, so i can't help other than to say it sounds like an exact stop problem
[18:36:06] <Nick001-Shop> JT-Shop> put the net slide info in and it came up with zero timeout with wait type !=immediate return error - Put a Q timeout and it continued to load. Only now it operates to the timer weather pin 10 is high or low - what did I miss?
[18:39:24] <JT-Shop> does motion.digital-in-00 toggle in a watch window when you toggle the switch?
[18:39:47] <JT-Shop> Aero-Tec: it runs smooth in the sim with constant velocity
[18:40:56] <Nick001-Shop> ill set the q for 30 sec so the switch will hit and go true and see what happens brb
[18:43:35] <JT-Shop> ok
[18:44:36] <Aero-Tec> that was the new code
[18:44:48] <Aero-Tec> I have not tryed it yet
[18:44:59] <Aero-Tec> but it should run smooth
[18:45:10] <Nick001-Shop> the switch goes true but the motion.digtal stays false
[18:53:08] <Aero-Tec> http://imagebin.org/238710
[18:53:16] <Aero-Tec> very bad pix of setup
[18:53:21] <Aero-Tec> needed more light
[18:53:31] <jdh> really very very bad
[18:54:21] <JT-Shop> really bad
[18:54:44] <Aero-Tec> I can add some light and try again
[18:55:57] <JT-Shop> Nick001: what is the hal line you used to connect the parallel port to the dio pin?
[18:56:57] <JT-Shop> This is what I use on my plasma M66 P0 L1 Q2 (Wait 2 seconds for Arc OK from Torch)
[18:57:21] <JT-Shop> as I understand it should be L3
[18:59:49] <JT-Shop> http://www.youtube.com/watch?v=uonWwpgor7U
[19:06:29] <Nick001-Shop> found the prob - forgot a dash in the net slide line and now motion digital is switching
[19:07:30] <JT-Shop> cool
[19:10:33] <Nick001-Shop> be back in 30 min and tell you what happened - boss called and dinner is ready -)
[19:10:50] <JT-Shop> I'm waiting for the same call
[19:11:04] <tjb1> JT-Shop: dinner is ready.
[19:12:39] <JT-Shop> what did you cook for me honey?
[19:12:47] <JT-Shop> did you see my new slats?
[19:13:58] <tjb1> hot dogs
[19:14:00] <tjb1> and no
[19:14:47] <JT-Shop> Nathens?
[19:14:49] <JT-Shop> 3 done 3 to go
http://imagebin.org/238708
[19:14:54] <Aero-Tec> http://imagebin.org/238715
[19:15:12] <JT-Shop> looks like a pile of springs
[19:15:17] <Aero-Tec> http://imagebin.org/238714
[19:15:42] <Aero-Tec> http://imagebin.org/238713
[19:15:50] <JT-Shop> crappy photo but I get he idea now
[19:15:57] <Aero-Tec> almost 300 of them
[19:16:00] <tjb1> Why dont the arc?
[19:16:02] <tjb1> they
[19:16:10] <JT-Shop> ?
[19:16:19] <Aero-Tec> arc?
[19:16:20] <tjb1> Should arc your slats
[19:16:31] <JT-Shop> they do form an arc
[19:16:42] <tjb1> Thats a tiny arc :P
[19:16:48] <Aero-Tec> crappy camera
[19:16:50] <JT-Shop> no it is a huge arc
[19:17:11] <tjb1> You knew what I meant...
[19:17:16] <JT-Shop> yes
[19:17:50] <JT-Shop> it's 1" in 60"
[19:18:02] <tjb1> Since mesa is still in the 90s, I cant order until tomorrow
[19:18:10] <Tom_itx> JT-Shop, what's your latest conversion you were working on?
[19:18:13] <Tom_itx> your lathe?
[19:18:16] <JT-Shop> the last ones are straight and still good after 4 years of use
[19:18:50] <JT-Shop> Tom_itx: fixing my plasma table and making lift and spins
[19:19:15] <tjb1> JT-Shop: I took about 2.5lbs off my Z
[19:19:17] <Tom_itx> hmm i thought you were rewiring something recently
[19:19:29] <JT-Shop> tjb1: did that help?
[19:19:54] <tjb1> A bit, also added a bunch of litium grease
[19:19:58] <JT-Shop> hmmm I don't think so, last conversion was the BP from Anilam to LinuxCNC
[19:20:11] <Tom_itx> ahh
[19:20:22] <Tom_itx> get it all workin?
[19:20:29] <Tom_itx> you were having noise problems or something
[19:20:37] <JT-Shop> it's cutting the slots for the plasma table slat supports now
[19:21:00] <JT-Shop> yep, still do from time to time but not enough to raise the hair on my neck
[19:21:05] <tjb1> What is a realistic acceleration number?
[19:21:25] <Tom_itx> probably depends on your setup
[19:21:36] <tjb1> Well I am pretty sure 30 isnt real
[19:21:48] <tjb1> Is acceleration like in machine units squared
[19:21:53] <tjb1> *Isn't...
[19:22:44] <JT-Shop> tjb1: I find that 10-20 times the max velocity is about right
[19:22:45] <icee> tjb1: what's your peak speed?
[19:23:14] <tjb1> JT-Shop: So if you have 7 for velocity you set your accel at 70+?
[19:23:22] <JT-Shop> yea
[19:23:22] <icee> it all depends on the machine
[19:23:40] <icee> for some, accelerating from max vel one way to the opposite in 1/10th of a second is not sane
[19:23:54] <JT-Shop> dinner bell
[19:24:51] <icee> especially with gantries and stuff, you need to think in terms of torques and power required and leadscrew loading
[19:24:57] <JT-Shop> tjb1: all the machines in my shop fall in that range, of course that may not work for machines that would not fit in my shop
[19:25:29] <tjb1> I set my max on x and y to 400 now
[19:25:36] <tjb1> Still doesnt stop on limits
[19:26:08] <JT-Shop> plasma x and y
[19:26:09] <JT-Shop> MAX_VELOCITY = 7
[19:26:10] <JT-Shop> MAX_ACCELERATION = 125
[19:26:10] <JT-Shop> STEPGEN_MAX_VEL = 8.4
[19:26:10] <JT-Shop> STEPGEN_MAX_ACC = 150
[19:26:20] <JT-Shop> dinner bell for real
[19:26:32] <Tom_itx> heh
[20:25:36] <Iron> Saludos
[20:25:43] <Iron> alguien que hable español
[20:25:45] <Iron> ?
[20:27:00] <Tom_itx> no
[20:31:35] <Iron> How can I make linuxcnc not print me upside down images that I want graphic with cnc machine
[21:03:05] <Aero-Tec> looks like the new code is doing the exact same thing
[21:03:36] <Aero-Tec> JT-Shop: are you still around?
[21:06:21] <Tom_itx> i doubt it
[21:07:20] <Aero-Tec> any EMC gurus?
[21:45:51] <skunkworks> Aero-Tec: what is the issue?
[21:46:25] <Aero-Tec> still doing the stopping on move end
[21:47:32] <Aero-Tec> does G64 stop that
[21:48:19] <Aero-Tec> G93 did not stop it
[21:50:29] <Aero-Tec> http://pastebin.com/AJrFHxfG
[21:50:32] <Aero-Tec> the code
[21:51:38] <Aero-Tec> trying to get it to make spring in one continuous move
[21:52:53] <Aero-Tec> http://pastebin.com/nZVDbQ8a
[21:53:05] <Aero-Tec> a G93 version of the code
[21:54:35] <Aero-Tec> skunkworks: you still there?
[21:56:03] <Aero-Tec> G64 is go as fast as possible in one continuous move
[21:56:18] <Aero-Tec> or am I wrong
[22:00:46] <Valen> sure its the mill?
[22:01:09] <Valen> bah sure its EMC, not backlash in the mill
[22:02:43] <Aero-Tec> there is backlash
[22:04:06] <Aero-Tec> and backlash comp is turned on
[22:04:25] <Aero-Tec> the moves are all in the same dir so backlash would not be a problem
[22:04:26] <Valen> if there is backlash you will still get a mark
[22:04:31] <Valen> fairynuff
[22:05:19] <Aero-Tec> it is winding springs
[22:05:23] <Aero-Tec> so no mark
[22:05:53] <Aero-Tec> but I do not want the waste of time stopping 2 times when making a spring
[22:12:10] <Valen> bit busy at the moment so I can't really have a good look at it yet
[22:13:56] <Aero-Tec> I am thankful of any help I can get
[22:14:13] <Aero-Tec> new to EMC
[22:54:18] <Aero-Tec> ran out of things to try
[22:54:34] <Aero-Tec> turned off backlash comp
[22:54:49] <Aero-Tec> have G64 in the code
[22:55:03] <Aero-Tec> still stops
[22:55:20] <Aero-Tec> and have tried using G93
[22:55:30] <Aero-Tec> with G64
[22:56:06] <Aero-Tec> thought G64 was to stop the stopping
[22:59:36] <Aero-Tec> I have gone through the HAL and the INI
[22:59:49] <Aero-Tec> a few times
[23:01:05] <Valen> I think i saw something about this on the mailing list recently?
[23:02:57] <Aero-Tec> I just joined that a few days ago
[23:04:45] <Valen> something about repeted moves in the same direction or something
[23:04:57] <Valen> what is making your gcode? it looks nasty
[23:10:17] <Valen> if it jumps into / out of a sub I think it will/may stop
[23:10:28] <Aero-Tec> lol
[23:10:34] <Aero-Tec> I made the code
[23:10:38] <Aero-Tec> hand done
[23:10:41] <Valen> rofl
[23:10:46] <Valen> dude spaces are allowed ;->
[23:10:46] <Aero-Tec> was made for Mach
[23:11:05] <Aero-Tec> then added sub for counting
[23:11:15] <Aero-Tec> then maded it for EMC
[23:11:19] <Aero-Tec> moded
[23:11:41] <Valen> you don't need to set G91 every line
[23:11:47] <Aero-Tec> yes it looks like hell, but it is my little hell....LOL
[23:11:57] <Aero-Tec> I know
[23:12:13] <Valen> I'm just thinking something in there may be confusing EMC
[23:12:16] <Aero-Tec> or do G1 like I did
[23:12:43] <Valen> G1 isn't a bad idea, but G91 is a modal, so it may cause the planner to hiccough
[23:12:45] <Aero-Tec> F19000000
[23:12:46] <Aero-Tec> G1G91X-0.03B100
[23:12:48] <Aero-Tec> G1G91X-0.01B60
[23:12:50] <Aero-Tec> G1G91X-.01B500
[23:12:52] <Aero-Tec> G1G91X-1B3240 ;4680
[23:12:54] <Aero-Tec> G1G91X-0.02B530
[23:12:55] <Aero-Tec> G1G91B-860
[23:12:57] <Aero-Tec> that is the code of the code
[23:13:15] <Aero-Tec> it should have no problems doing that in one go
[23:13:28] <Valen> I suggest taking the G91 out just to rule it out
[23:13:29] <Aero-Tec> it is tight and neat
[23:13:46] <Aero-Tec> will do the G1s as well
[23:13:52] <Aero-Tec> only need one
[23:13:53] <Valen> so its stopping on each line there?
[23:14:03] <Aero-Tec> yes
[23:14:04] <Valen> we use G1's and its ok
[23:14:15] <Valen> also what version are you using?
[23:14:26] <Aero-Tec> 2.5 I think
[23:14:32] <Aero-Tec> just updated
[23:14:35] <Valen> ok
[23:14:45] <Aero-Tec> mind you that was the lathe
[23:15:02] <Aero-Tec> have to check if mill got updated
[23:15:58] <Valen> The only other thing I can think of is its the rotaty axis
[23:16:46] <Aero-Tec> G93 should fix that
[23:16:50] <Aero-Tec> but it did not
[23:17:42] <Valen> mmm sorta
[23:18:02] <Valen> 93 is just another way of speccing a feed rate isnt it?
[23:18:09] <Valen> if you used 95 then sure
[23:19:50] <Aero-Tec> G93 I am told is to be used when 2 different units are involved in a move
[23:20:05] <Aero-Tec> Inch and Degree
[23:20:18] <Aero-Tec> or what ever combo
[23:20:36] <Valen> makes sens
[23:20:38] <Valen> e
[23:20:52] <Aero-Tec> going to try your idea
[23:20:56] <Aero-Tec> BRB
[23:24:43] <Aero-Tec> still stopping
[23:25:01] <Aero-Tec> G91 was not the problem
[23:25:15] <dhoovie> Yeah, I think Valen is right. It's the rotary axes. I havn't got path blending to work with a rotary axes.
[23:25:33] <dhoovie> It always stops...
[23:25:43] <Aero-Tec> I know someone that has
[23:25:44] <Valen> can you redefine your rotary axis as a linear axis temporarily?
[23:25:50] <Aero-Tec> will post vid
[23:26:04] <dhoovie> Really? sweet!
[23:26:08] <Aero-Tec> how would one do that?
[23:26:12] <dhoovie> maybe he did something in his setup
[23:26:33] <Aero-Tec> he posts how he did it on his web site
[23:26:40] <dhoovie> link?
[23:26:44] <Aero-Tec> will have to look at it
[23:26:53] <Aero-Tec> but it was threading
[23:29:09] <Aero-Tec> http://jmkasunich.com/cgi-bin/blosxom/shoptask/fusee-1.html
[23:29:21] <Aero-Tec> watch the vid
[23:31:00] <Aero-Tec> he uses G64
[23:33:25] <Aero-Tec> so what do you guys think?
[23:34:04] <Valen> have you tried setting a tollerence?
[23:34:57] <Aero-Tec> for G64?
[23:34:59] <Aero-Tec> yes
[23:35:01] <Valen> yeah
[23:35:03] <Valen> ok
[23:35:04] <Aero-Tec> and with out
[23:35:35] <Aero-Tec> why will G64 not work for me?
[23:35:40] <Valen> guy is too smart by half lol
[23:35:50] <dhoovie> so firstly, that was a mind blowing video
[23:36:14] <dhoovie> and I don't think he uses any angular axes.
[23:36:30] <Aero-Tec> your right
[23:36:38] <Valen> be spinde synchronised motion at best no?
[23:36:52] <Aero-Tec> for him yes
[23:36:56] <Aero-Tec> he is threading
[23:37:12] <Valen> damn quick too lol
[23:37:17] <dhoovie> if you use only linear axes, G64 works. Put one rotary axes in there and it doesn't.
[23:37:20] <Aero-Tec> G33 if mem serves
[23:37:47] <Valen> "After roughing out the part, the next step is the threading. The code to do the threading looks very similar to the roughing code, except that it uses G33 spindle-synchronized moves instead of ordinary G1 linear moves."
[23:37:57] <Aero-Tec> he sure does some hoging cuts
[23:38:41] <Aero-Tec> so all rotary axis moves stop?
[23:39:14] <Valen> that would be my sense of it at this instant, but somebody who knows more about the guts would be a better place to ask
[23:39:17] <dhoovie> I think so. But I probably don't know enough about linuxcnc to say that for certain.
[23:39:36] <Aero-Tec> that sucks
[23:39:37] <Valen> try the mailing list or here in like 12 hours or so when america is awake
[23:39:51] <dhoovie> you can browse the code for the g64 code and see if you can figure something out :D
[23:39:59] <Aero-Tec> will do
[23:40:05] <Aero-Tec> do you have a link?
[23:40:10] <Valen> to the list?
[23:40:23] <Aero-Tec> the G64 code
[23:42:01] <Aero-Tec> you had said something about browsing the G64 code
[23:42:09] <Valen> he means the source code
[23:42:21] <dhoovie> uhm, afraid not. can download the source of linuxcnc from the site and have to find it :S
[23:42:55] <Aero-Tec> thought you meant Gcode samples
[23:43:07] <Aero-Tec> it is late here
[23:43:19] <Aero-Tec> way to late for looking at source code
[23:43:23] <dhoovie> ohh no, the source code of linuxcnc. it's a bit of a beast as well.
[23:44:24] <dhoovie> haha. yeah. if you find a solution I'm interested in it as well. but so far I'm not sure where to start either.
[23:48:16] <Valen> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Simple_Tp_Notes for trajectory planner notes
[23:51:01] <Valen> Aero-Tec: not a good answer but perhaps a quick one, change the rotary axis into a linear axis?
[23:51:53] <Aero-Tec> can that be done?
[23:52:17] <Valen> not in G code but if you change the ini file
[23:53:00] <Aero-Tec> one would need to figure out how, then how much to move it for the right rotation
[23:53:40] <Valen> changing to a non rotary axis is pretty straight forward
[23:53:54] <Aero-Tec> I would think so
[23:54:02] <Valen> then its just a question of translating your units
[23:54:24] <Aero-Tec> but knowing how much movement did X amount of rotation might be trick
[23:54:46] <Valen> I suggest posting your problem on the mailing list, going to bed and seeing what turns up, and if the answer is, "can't do it yet" then look at doing it this way
[23:54:53] <Aero-Tec> guess one could play with it
[23:54:54] <Valen> shouldn't be too hard, is it a stepper or servo machine?
[23:55:13] <Aero-Tec> I have posted to mailing list
[23:55:16] <Aero-Tec> user one
[23:55:27] <Aero-Tec> steppers
[23:55:49] <Aero-Tec> should I post to developer one as well?
[23:55:55] <Valen> probably not
[23:55:59] <Valen> devs read the user list
[23:56:07] <Valen> they will tell you to post there
[23:56:12] <Valen> how long ago did you post?
[23:56:36] <Aero-Tec> right about the time you diged me
[23:56:40] <Valen> actually the movement should be the same if the "scale" is the same
[23:57:16] <Aero-Tec> steps per deg
[23:57:22] <Aero-Tec> steps per inch
[23:57:29] <Aero-Tec> that should work
[23:57:33] <Valen> yeah just leave them the same so yeah
[23:57:42] <Valen> suggest trying it in a "safe" way first lol
[23:57:48] <Aero-Tec> lol
[23:57:54] <Valen> copy the config don't replace what you have
[23:58:10] <Aero-Tec> make a new config
[23:58:21] <Valen> your using stepconf arent you ;-P
[23:58:34] <Aero-Tec> the whacky rotary linear
[23:58:46] <Aero-Tec> I hand code
[23:59:00] <Aero-Tec> but base it on the wiz
[23:59:24] <Aero-Tec> run a fake wiz config and move the info over
[23:59:39] <Aero-Tec> got tiered of it over writing my changes
[23:59:51] <Valen> I think you could just copy the ini file and change the line that says rotary or linear and be done ;-> you need to change the gcode to match the axies but still