Machsupport Forum
Third party software and hardware support forums. => NC Pod => Topic started by: Greolt on January 14, 2007, 11:49:02 PM
-
Disabling legacy mode in bios has made comunication more stable.
However I have a funny problem.
Set all DROs to zero, run the roadrunner, DROs not ending on zero. Gcode last move is go to zero but DROs not returning to zero.
Watching the Z axis DRO during code execution. Z spends most of the time at -0.1 and goes up for rapids returning to -0.1
Each time (or most) it returns 0.0025 different than the last. So they add up to a cumulative error by the end.
See pic for screen capture at the end of roadrunner execution.
-
I only ran the roadrunner a few time since I got the comuncations fixed. I noticed the same thing with the Z positioning and returning to zero.
-
Glad it is not just me.
It always feels better if someone else is having the same problem. ;D
-
Beta Team,
Art is aware of this issue and at the moment is talking with the Pod developer about it. The Pod and Mach 3 is accurate to +/- 1 step (provided you have the latest version of Mach 3 and the Pod firmware update). I will re-visit this with Art to get an update on his thoughts regarding this matter.
Dave
-
Set your servo time to .00087 and you should be good :)
I have been running tests and it is working well for position. you need to have the latest software on everything.
-
How do we know when a new firmware comes out?
-
Dave and/or I will be sure to post that it is out here :)
-
Brian,
What does that servo time setting actualy do? I just want to know what these settings do so I can understand what affects what.
-
Guy's and Gal's,
I will start a locked thread that I will keep updated with the links to the latest Mach3, NC Pod Mach3 Driver and NC Pod Firmware Updates.
Dave
-
Set your servo time to .00087 and you should be good :)
I have been running tests and it is working well for position. you need to have the latest software on everything.
I tried to set servo time to .00087 but it would not stay and reverted to last setting.
So I downloaded latest Plugin and it had a selection in the drop down of .00084 so tried that. Still not returning to zero.
Then I did a clean install of the latest Mach version R2.0.036 set up motors and estop again.
Now the gcode window and line count jump and it stalls around line 980 of the roadrunner.
Tried updating the plugin just in case it changed. Still the same.
Have the latest firmware. Mach version and plugin. Legacy mode turned off for USB
I think to save my frustration I will set this aside for now and watch for updates to come out.
-
OK I'm a dill ;D I should be "dropped from a great height and publicly peed upon" as my uncle used to say ;D ;D
Forgot to reinstall my licence dat. Now it does not stop at around 980
The gcode window and counter still jumps and at the end it still does not return to Zero.
-
Greolt
Can you do us a favor, if it is not returning to Zero, is it because it is what you are reading on the DRO or is your machine physically not returning to Zero. If it is the DRO that you are concerned about, work out your step pulses, is the error + or - 1 step of the commanded destination or is the error greater?
Dave
-
Dave I have refitted a LPT BOB to my mill. I need it running. :)
So I can't really do any testing in the machine now.
I need to get on with my new half built router and hope the Pod is sorted by the time I'm ready for a controller.
I can dry run it (5v and USB only connected) but that may not be a valid test.
-
Didn't really answer your question did I Dave. ;D
I was only "air cutting" the roadrunner on my mill, so as the error was only about 0.2mm I didn't notice a physical position error.
Steps away from zero varied from 1 to 80. on the DRO.
I just tried a "dry run" with only 5v and USB connected and it still does the same thing
Don't know if this is valid without drivers connected. S'pose it would not make a difference but I'll leave that to the experts. ;D
-
Greolt,
Thanks for clarifying that. The greater the steps/mm or steps/inch the less error you will see. If 1 step moves your maching 0.5mm then you could be out on a commanded position of up to +/- 0.5mm the smaller the movement per step the smaller your error. If you have a whole number in your steps per MM it will also make a difference (better) than if you have a decimal. This whole +/- 1 step is constantly being looked at, we want the pod to be 100% at the end of the Beta period.
Regards
Dave