Orient component revised

1 sorry my message is not clear, i speak about S=0rpm and orient is enable i think strange to not see spindle.x.on=true (not speak about multi spindle).

2 yes i think with setting 0rpm and orient disabled imo is better to stop spindle completely.
i'm not an expert, maybee this is needed for some servo/stepper spindle but in this way i think this need to be the same with orient. (and allow to have a more easy hal config for orient)

3 yes it is


For orient i need to pass through the enable signal for spindle controler
If ask M19 allow to ask spindle.0.on this not be needed anymore, but removing input/output from component lock the possibility to force enable from jog mode so these change nothing.

alkabal wrote: 1

2 yes i think with setting 0rpm and orient disabled imo is better to stop spindle completely.
i'm not an expert, maybee this is needed for some servo/stepper spindle but in this way i think this need to be the same with orient.

Well I don't disagree. setting S to 0 should set the spindle to stop turning, but it shouldn't require m3/m4 to start it again, you should be able to set S to a positive number and it should turn. It's a subtle difference but useful and consistent ideology.

using the new multispindle frame work i added an indexer to my mill.
I use the second spindle commands to operate at. the S command specifies the position in degrees. it works fine but if you specify S0 then the indexer is tuned off rather then move to 0 degrees. it also requires M3 to start again.
While I realize this is extending the spindle to unintended use - it works very well and is easy to add to a config. My discussion about S0 really comes down to it allows one to do more with linuxcnc and does not affect any standard gcode program out there. I don;t think it is usual for people to actually set S to 0, one would use M5

I'll have to look at your code and see if I could use it on my indexer. ultimately i would like to be able to select spindle mode and indexer mode.

Chris

Yes off course ii think like you : nobody use S0 for stop spindle.

I hope my code can work for your setup but i think need more work. you can use HAL exemple inside comp (need to add the pid setting)

Attached Orient pid pyvcp panel + last revision


I have do the test with 2.9
Start spindle from GUI or from M3/M4
set S0 (spindle stop moving, hal signal = false but Axis gui button stay pushed...)
Set S100 does not restart spindle, need to push GUI button again.

Well i think this is not really logic mostly regarding the GUI status.

Edited for last revsion

now i understand why you want spindle on with S0, but it is better to have your setup or use a orient component ?

can i ask more about what you have do in your config ?

I don't have anything to contribute, but I'm trying to follow this conversation. I've had a horrible time trying to program a working Orient on my machine.