paddax Posted January 30, 2015 Share Posted January 30, 2015 Our system has Endat encoders with 100,000 counts per mm, the first three motors are orthogonal linear axis The following command issued from a part program causes the first three motors to move until trigger JOG1..3^1000000^0 If the trigger is found within the specified distance system works as expected however if the trigger is not found motor 1 will stop after exactly 10mm however motor 2 never stops (EOT at 100mm) and Motor 3 stops after 11.5mm Issuing the following command in a part program or Rotary buffer did something entirely unexpected. JOG2,3^1000000^0 Motor 2 stopped after 10mm but motor three moved in a NEGATIVE direction and seemed to be moving indefinately (at least 100mm). Please note that if the trigger is found the axis does stop, even if it is going in the wrong direction. Individually JOGn^1000000^0 the program worked as expected. Link to comment Share on other sites More sharing options...
JeffLowe Posted January 30, 2015 Share Posted January 30, 2015 Our system has Endat encoders with 100,000 counts per mm, the first three motors are orthogonal linear axis The following command issued from a part program causes the first three motors to move until trigger JOG1..3^1000000^0 If the trigger is found within the specified distance system works as expected however if the trigger is not found motor 1 will stop after exactly 10mm however motor 2 never stops (EOT at 100mm) and Motor 3 stops after 11.5mm Issuing the following command in a part program or Rotary buffer did something entirely unexpected. JOG2,3^1000000^0 Motor 2 stopped after 10mm but motor three moved in a NEGATIVE direction and seemed to be moving indefinately (at least 100mm). Please note that if the trigger is found the axis does stop, even if it is going in the wrong direction. Individually JOGn^1000000^0 the program worked as expected. For our multiaxis jog until trigger we set the Motor[x].ProgJogPos set to the appropriate end targets then use jog1,3=*^0; Link to comment Share on other sites More sharing options...
paddax Posted January 31, 2015 Author Share Posted January 31, 2015 Thanks for the work-around but I think I'd prefer the bug was verified and if necessary fixed. Link to comment Share on other sites More sharing options...
steve.milici Posted February 3, 2015 Share Posted February 3, 2015 I have tried this on my test setup and in the absence of any trigger both motors stop a 1000000 counts relative. What is your firmware version? Link to comment Share on other sites More sharing options...
paddax Posted February 26, 2015 Author Share Posted February 26, 2015 I have tried this on my test setup and in the absence of any trigger both motors stop a 1000000 counts relative. What is your firmware version? 1.6.1.1 Link to comment Share on other sites More sharing options...
steve.milici Posted February 26, 2015 Share Posted February 26, 2015 We are not aware of any issues like this with the 1.6.x.x versions. I have tested with 1.6.1.202. We have a new release on the Forum's FileDepot: 2.0.0.1 Link to comment Share on other sites More sharing options...
Recommended Posts