Den 2021-06-14 kl. 15:45, skrev andy pugh:
On Mon, 14 Jun 2021 at 14:24, Nicklas SB Karlsson <n...@nksb.eu> wrote:
It would probably work if position is scaled down to correct number of
pockets first adding an offset to get angle of the pockets correct.
I had rather assumed that the encoder index would be aligned to the
base pocket.
Aligned the flat surface on encoder shaft with screw locking it. No idea
where index ended up in relation to pockets and have not checked yet,
only made first test run.
Think it is good either to add support for angle sensor
in current carousel component or simply forking of a different variant
Can you raise it as an issue on GitHub and assign it to me? Just to
make it harder to forget?
Yes, looking into code it should however not be to hard figure out by
myself.
Not sure if could be fitted in a good way in current component. What
think is needed with an incremental encoder is:
1) Input signal for angle s32 should work also then it overflow,
though a little bit theoretic float will eventually lose digits if
rotating long enough but wear and aging operator should be more of a
problem due to many digits in double.
2) Input signal for index pulse, angle not valid until reached so
valid signal will make the trick and may also make sense for other sensors.
3) Parameter number of pockets per turn, guess there also may be
chain driven with turns and pockets. so maybe a rational number p/q in
mathematical litterature or better expressed for this purpose pockets/turns.
4) Parameter angle offset to first pocket.
5) Output enable rotation, may be connected to unlock and/or relay to
rotate.
6) Parameter distance to turn off backward and forward signals.
7) Outputs rotate backward and forward signals, it is common both are
needed for frequency inverters and also relays. Parameter for delay
after enable rotation is turned on?
8) Output Angular distance to target pocket, make sense then possible
to control rotational speed, may be connected to PID regulator in this
case. Absolute value may be useful then using backward and forward
signal with some frequency inverters but may also be added externally.
9) Output pocket reached, probably with parameters for delay
tolerances for angle sensor.
10) Error handling and output signal if not rotating then turned on
or other problem.
If I think correct above should work equally well with absolute value
angle sensor, it is possible to connect valid signal to true if unused
so no problem with that. Incremental and absolute angle sensor are very
common.
11) Enable signal, Jog forward/backward inputs, current position
position, homed or OK ready to be used and most probably current state
are part of current carousel and still make sense.
With my carousel most of the above are useful. Though only one of the
backward/forward signals are needed and do not currently use distance
value but would be useful if replacing relay with frequency inverter.
You should be able to interlock the brake with carousel.is-active ?
Output enable signal will tell if carousel should be locked, should be
possible to add extra logic externally if needed.
Name it carousel_angle.comp ? Or integrate with current carousel.comp?
Regards Nicklas SB Karlsson
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
