So, is the issue related to jogging only or to job execution also?
Below was a situation we had faced.
The issue related to step/unit. we put following number
407.4357 >> worse, jog very slow <this number is work fine with parallel port system before)
407.436 >> jog move better , but not fast as normal ( normal = parallel port)
407.44 >> jog fast as normal, but some time Y1 and Y2 not synchronize result in jerking (Y2 is slave axis) -
After customer and I tried hard to installed, learned to replace parallel port system with brand new PoKeys , We agreed to get rid of jerking problem by writing VB script to control a DPDT relay to switch back and forth signal for Y2 motor driver. During homing, we let Y2 have its own signal ( Y1 and Y2 both have their own homing signal). During normal run, we let Y2 to obtain Y1 step/direction signal.
After several hours of trial and error with PoKeys57E, we thought that reached to expectation and calm situation, all everything seem to work fine, then We let night shift operators to handle their job as usual.
Next morning, I got the report that operators experienced Mach3 stop working occasionally and present execution line is reversed back to beginning. However, I made a test at my office in another day (dry run, not motor driver) and found that only Limit signal is triggered occasionally, which possible that the night shift operator had encountered this issue and did not know how to handle and made a wrong report.
Same morning, Then we decided to remove PoKeys from the system just for time being and reinstalled parallel port system back in place.
The answer to your question is Both.
Guest
Show Posts
