Functioning Fadal conversion from Gmoccapy to Probe Basic

@LCVette,
There is a deleted post in this topic made by you, did you delete it?
Need to know if we should restore it or permanently delete.
Thank you.

Doesn't the widget just pull from the CAROUSEL component after it is referenced? Shouldn't the turret widget just track carousel.N.homing and carousel.N.homed?

When you say copy that over, do you mean into the carousel.comp file?

@tommylight you can permanently delete, hit delete while trying to hit edit, so just started the post over.. /o\

i have not dug into the carousel comp, but the dynatc items in straight macro driven atc is just in the Mxx macros in sections that are commanding carousel movement and that is how the widget is synchronized to the machine movement commands  if you want to post up your atc macros we could look at them.  wouldn't be a bad thing to add them to a fadal conversion file in probe basic.

The carousel component is really nice. I don't see too many ATC setups if any that will not work with carousel component. What element do i need to tie my "carousel.0.homed" to? You should consider including pins to allow user to tie the carousel component pins to your widget turret.

Also, Gmoccapy has "analog-enable" pins to tie to physical overrides. It makes override setup very easy. Example below

setp     gmoccapy.rapid.rapid-override.analog-enable 1
net      rapid-override-gmoc      gmoccapy.rapid.rapid-override.direct-value    <=    rapid.override-output