Thanks
We encoutered an error, encoder data conversion error on joint 2 also cannot read encoder value jt2. Do you have some suggestions? We moved it 1m from its previous position and now this apeared.
Thanks
We encoutered an error, encoder data conversion error on joint 2 also cannot read encoder value jt2. Do you have some suggestions? We moved it 1m from its previous position and now this apeared.
My experience with this type of error has been based on intermittent connectivity from encoder all the way back to the 1GB Board, either:
- Connections loose/not secure.
- Internal harness failure where conductor is internally worn and shorting to internal shield ground when robot moves in a particular area.
Therefore, if you cannot clear the error, then:
1. Remove side plate for JT2 Motor Axis and confirm cable/harness is not damaged/pinched in any of the internal clamps.
2. Check X3A Connector on Rear of Robot is firm and secure (remove first and also check no pins are bent/pushed in).
3. Check X3 Connector on Controller is firm and secure (remove first and also check no pins are bent/pushed in).
4. Check CN2 Connector on 1GB is firm and secure by removing and reconnecting with audible click and pull test.
5. Manual Brake release on JT2 (you will need assistance with gravity/support of JT2 axis) and try and return JT2 position to nearby the position you started from and watch 'monitor screen for position values changing with manual movement'.
6. See if the error can be cleared again - This may result in you having to also re-zero JT2 also.
7. If so, then manually get the robot in a position where you can move JT2 across the full envelope without colliding with peripherals.
8. Use Joint mode and jog JT2 across full envelope.
9. If error re-occurs during this, I suspect internal harness maybe stretched at certain position causing break in conductor/short circuit.
- This would mean internal harness requires replacing.
10. If error does not re-occur, then it is possible when moving JT1 or JT3, this could influence cable stretch causing error on JT2 instead.
- This would mean internal harness requires replacing.
I think from memory, JT1/JT2/JT3 uses same route/cable for internal harness, so if you could check individual JT1-JT3 motion, this would prove internal harness issue - this is not an uncommon problem considering age of robot.