qtvcp issues

I just remembered that I forgot to add that almost all my work is done in factions of inches and not mm.

Ok I pushed updates to include your latestest design and reworked the names to use your defaults - other then I fixed a miss spelling of length.
It's on going work of course.

Chris M

hmm I see my probe screen is not exactly the same as your posted pic.
I pulled again without change - did you push that design ?

Chris M

I will check to make sure. I did do a pull after I pushed and it looked ok to me then but there is always a possibility that I overlooked some thing. I will check later today and correct it if I locate the issue you are seeing.

I was finishing up some jogging code for all three jog modes I have along with their individual slow/fast modes for each and I have not found a separate action for setting the angular jog rate. I did find separate action and status for the linear and angular increments. So that leads to me asking if the jog rates for linear and angular jogging use the same rate action.

There are 4 rog rate setting commands:

ACTION.SET_JOG_RATE( rate):
ACTION.SET_JOG_RATE_ANGULAR(rate):
ACTION.SET_JOG_INCR(incr, text):
ACTION.SET_JOG_INCR_ANGULAR(inc, text)

there jog rate will always be in machine units

Chris M

Ok I was missing the Angular rate one.

I’m not sure what the 'text' is used for in the increments, Just been setting it at 0 (zero) for now and everything works fine as far as incremental movement for all 16 of my increments for linear and the 16 for angular movement. Continuous jog has also been checked out for the x1mill gui.

All jogging required values and info for labelling the buttons and setting true state values for buttons is derived from the the .ini file. I’m using lists to handle configuration data.