Menu

#397 Jogging after switching to metric is inconsistent behavior-wise

2.6
closed-fixed
nobody
None
5
2014-11-02
2014-10-22
macpod
No

If linuxcnc is started in imperial and switched to metric mode via the '!' shortcut, jogging is inconsistent. I have seen:

-Flipping to metric causes the machine to jog slower WITHOUT changing the jog speed control bar. (normally what happens). I would expect the machine to jog at the same speed as before.

-Holding down shift can cause the machine to jog SLOWER than when it is not pressed in metric mode (in these situations the 'jog speed' was set to half of the 'max velocity'). This only sometimes happens... I'm still trying to figure out how to make this repeatable.

Repeating this involves:

  1. Start computer
  2. Launch linuxcnc
  3. disable e-stop
  4. toggle machine power
  5. enter keys:
    z [home]
    x [home]
    y [home]
  6. Set jog speed to roughly half max velocity
  7. jog to roughly the middle of the machine's travel
  8. enter key: [!]
  9. jog again to observe a slower job speed.

Discussion

  • Chris Radek

    Chris Radek - 2014-10-29

    I can't reproduce the first half. Flipping to metric with ! and then doing a regular jog by pressing an arrow gives the same actual jog speed (Vel readout matches the new, higher, readout of the jog speed slider).

    The second half I reproduced. If shift-arrow gave 72in/min, changing to mm display with ! would give 72mm/min, which is too slow.

    Any more information you can give about reproducing the first problem would be appreciated.

     
  • Chris Radek

    Chris Radek - 2014-10-29

    Part two of the bug (shift-jog) is fixed in 2.5 and newer branches; I also found and fixed a problem with UVW jogs being wrong when displaying non-native units. It would be great if you would test these changes and let me know your results. Thanks for the careful bug report.

     
  • Chris Radek

    Chris Radek - 2014-11-01
    • status: open --> open-fixed
     
  • macpod

    macpod - 2014-11-02

    I have updated to the 2.6.4 that was in the repos today and this seems to have corrected the issues that you have addressed. Thank you for the fix!

     

    Last edit: macpod 2014-11-02
  • Sebastian Kuzminsky

    macpod reports the issue is fixed in 2.6.4.

     
  • Sebastian Kuzminsky

    • status: open-fixed --> closed-fixed
     
MongoDB Logo MongoDB