seems like we solved Raspberry’s problems, but we are still fighting with this rotor, It still do not respond to commands.
We edited a rule so our device always appears as
/dev/ttyHOTSPOT that’s why
rotctl -r use that device.
root@TheNewHotSpot:/etc/udev/rules.d# vi 99-com.rules
As shown in the picture, we tried sending
P 90 45 and at least got the Rx blinking in the Arduino board (no movement though)
And as shown in the next image, when tried to get the actual position using command
p we are getting some kind of time out error, we believe because the Arduino is not answering
To go further with debbuging the issue, we decided to send commands directly from IDE serial monitor, now confident that we are sending commands in the correct format
AZ90.0 EL45.0 or even
AZ90.0 EL45.0 UP000 XXX DN000 XXX., but we still see no movement after the homing rutine. (I believe this shows the motors and drivers work fine)
(Picture below are not the actual attemps we made, it’s just for show)
We have tried modifing our drivers A4988 Pololu’s Vref in order to get higher current in the stepper motors (aprox 1A at this point), but nothing changed except the noise the motors are making while staying parked (supposly waiting for instructions) and the heat in both driver’s heatsinks which is kind of scary after a few minutes turned on. It’s important to make clear that both steppers are free to move at the moment (no torque on them yet, first we are tring to get them to move as instructed).
Any suggestion on what could be not working will be highly appreciated, and any tips on how to debug this issue will be taken in count.