1. Are you sure you don't have a pinout or cable issue?
the pins listed are DB25 pin for a 1-1 HDR26 --> DB25 flat cable
with pins 1 -->1 and HDR pin 26 unconnected
2. Be very careful with bare I/O pins. Connecting them to a voltage >7V or
more likely less than -0.7V will damage the I/O pin. Its very easy to apply
less than -0.7V due to HF ground noise, so just connecting an input to frame
ground will likely destroy that pin. You can protect against this kind of damage
with a series resistor in the 470 Ohm region.
You might Ohm out the flat cable. We had quite a few problems with the latest lot
of those (they passed out tests but the strain relief doesn't work well and its easy to
break wires on the DB25 end)
Do I need to check all the wires of a flat cable with a device? Then it is strange - after all, halscop sees signals A and B with encoder. And I ran the 5i25 with the prob-rfx2 firmware and my motors worked from this connector. But if necessary, I will check this cable. Thanks for the help!!!
If you see the hal pins hm2_5i25.0.encoder.NN.input-a and hm2_5i25.0.encoder.NN.input-b
changing then the encoder should work (+- any hal setup issues)
I see the signal hm2 5i25.0.encoder.03.input-a on halscop, but on hal metr hm2 5i25.0.encoder.03.position, changes only occur by 0.005 and that's it. So with encoder 01 and 05. And encoder 00, 02, 04 work. The signal level for halscop from different encoders is the same. Only even encoders work
