AXIS Jog Rate display not updating after calling set_jograte() functions
- scsmith1451
-
Topic Author
- Offline
- Senior Member
-
Less
More
- Posts: 52
- Thank you received: 2
12 Sep 2025 16:21 #334889
by scsmith1451
AXIS Jog Rate display not updating after calling set_jograte() functions was created by scsmith1451
In my gladevcp panel I have configured two buttons to set the jog rate. One to set to the lowest value that I use for positioning my crosshair laser, the other to set to the max value that I use. I have tried both ACTION.SET_JOG_RATE(rate) and GSTAT.set_jog_rate(rate), but neither affect the jog rate display in AXIS. The documentation for GSTAT.set_jog_rate(rate) mentions that after setting the jog rate, the jograte-changed signal is emitted which I would expect to update the AXIS display but there is no feedback indicating that the rate has changed. Is this a known issue or am I doing something wrong?
FYI - I also have a combo box to select the current system offset system which does change the AXIS display after a new offset is selected, so I would expect these two functions to work the same.
Kind Regards,
FYI - I also have a combo box to select the current system offset system which does change the AXIS display after a new offset is selected, so I would expect these two functions to work the same.
Kind Regards,
Please Log in or Create an account to join the conversation.
- unknown
- Offline
- Platinum Member
-
Less
More
- Posts: 601
- Thank you received: 201
12 Sep 2025 22:28 #334905
by unknown
Replied by unknown on topic AXIS Jog Rate display not updating after calling set_jograte() functions
I believe the axis GUI doesn't respond to changes such as you described, that can be seen in the example Sim configurations supplied with the standard Linuxcnc install.
Just thinking out loud, it would probably require digging into the axis code, exposing Hal pins for the GUI elements you would want to modify and implementing the code to respond to the Hal pins. This is part speculation.
But yes I've often thought that external interaction with the Axis GUI elements would be an idea, I still very much like axis. As much as many call the look dated, it works reliably.
But word on the street has it Axis is written in some language that only vets of The Editor Wars truly understand. I not too sure how many Vi or Emacs users are left.
Sorry for the dad joke at the end of this post, it really doesn't add much to answer your initial question.
Just thinking out loud, it would probably require digging into the axis code, exposing Hal pins for the GUI elements you would want to modify and implementing the code to respond to the Hal pins. This is part speculation.
But yes I've often thought that external interaction with the Axis GUI elements would be an idea, I still very much like axis. As much as many call the look dated, it works reliably.
But word on the street has it Axis is written in some language that only vets of The Editor Wars truly understand. I not too sure how many Vi or Emacs users are left.
Sorry for the dad joke at the end of this post, it really doesn't add much to answer your initial question.
Please Log in or Create an account to join the conversation.
Moderators: HansU
Time to create page: 0.096 seconds