I am working on a MD-01 SPID rotator. I tried changing the motor parameters in command line - for example setting the minimum acceptable azimuth value to 160. Hence I ran
rotctl -m 903 -r /dev/ttyUSB0 -s 115200 -C min_az=160 -L
The -L returns the rot parameters, among which
min_az : "Minimum rotator azimuth in degrees"
default: -180, Value:160
which shows that the change is effective. However, I subsequently asked a move that went below the minimal value I had previously set. Furthermore, in my MD-01 settings the minimum azimuth value hasn't been modified (as shown on the MD-01 display). So it looks like the communication between the command line using the Hamlib librairy and my MD-01 doesn't handle this kind of settings changes. Does anybody have an idea on how to overcome the issue ?
Thanks,
Glenn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The limit only works for set_position.If you want to limit the move command you need to poll for position and stop it yourself since move has no azimuth or elevation argument.
Mike W9MDB
I am working on a MD-01 SPID rotator. I tried changing the motor parameters in command line - for example setting the minimum acceptable azimuth value to 160. Hence I ran
rotctl -m 903 -r /dev/ttyUSB0 -s 115200 -C min_az=160 -L
The -L returns the rot parameters, among which
min_az : "Minimum rotator azimuth in degrees"
default: -180, Value:160
which shows that the change is effective. However, I subsequently asked a move that went below the minimal value I had previously set. Furthermore, in my MD-01 settings the minimum azimuth value hasn't been modified (as shown on the MD-01 display). So it looks like the communication between the command line using the Hamlib librairy and my MD-01 doesn't handle this kind of settings changes. Does anybody have an idea on how to overcome the issue ?
Thanks,
Glenn
MD-01 SPID_ROT2PROG: changing motor parameters in cmd
Thank you for your answer. Here are a few points I noticed :
- It is true that the limit I set in command line works for the position (P command), and not for the move.
- However, the limit which is previously set directly on the hardware MD-01 works for both P and M instructions in command line. Hence the problem lies in the way hardware settings can be changed through command line. Do you have an idea why my -C min_az=160 instruction does not apply onto the hardware ? How would you proceed to change the MD-01 settings via the Hamlib librairy ?
Thank you again for your responsiveness, Glenn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Hamlib community,
I am working on a MD-01 SPID rotator. I tried changing the motor parameters in command line - for example setting the minimum acceptable azimuth value to 160. Hence I ran
rotctl -m 903 -r /dev/ttyUSB0 -s 115200 -C min_az=160 -L
The -L returns the rot parameters, among which
min_az : "Minimum rotator azimuth in degrees"
default: -180, Value:160
which shows that the change is effective. However, I subsequently asked a move that went below the minimal value I had previously set. Furthermore, in my MD-01 settings the minimum azimuth value hasn't been modified (as shown on the MD-01 display). So it looks like the communication between the command line using the Hamlib librairy and my MD-01 doesn't handle this kind of settings changes. Does anybody have an idea on how to overcome the issue ?
Thanks,
Glenn
The limit only works for set_position.If you want to limit the move command you need to poll for position and stop it yourself since move has no azimuth or elevation argument.
Mike W9MDB
Hello Hamlib community,
I am working on a MD-01 SPID rotator. I tried changing the motor parameters in command line - for example setting the minimum acceptable azimuth value to 160. Hence I ran
rotctl -m 903 -r /dev/ttyUSB0 -s 115200 -C min_az=160 -L
The -L returns the rot parameters, among which
min_az : "Minimum rotator azimuth in degrees"
default: -180, Value:160
which shows that the change is effective. However, I subsequently asked a move that went below the minimal value I had previously set. Furthermore, in my MD-01 settings the minimum azimuth value hasn't been modified (as shown on the MD-01 display). So it looks like the communication between the command line using the Hamlib librairy and my MD-01 doesn't handle this kind of settings changes. Does anybody have an idea on how to overcome the issue ?
Thanks,
Glenn
MD-01 SPID_ROT2PROG: changing motor parameters in cmd
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Thank you for your answer. Here are a few points I noticed :
- It is true that the limit I set in command line works for the position (P command), and not for the move.
- However, the limit which is previously set directly on the hardware MD-01 works for both P and M instructions in command line. Hence the problem lies in the way hardware settings can be changed through command line. Do you have an idea why my -C min_az=160 instruction does not apply onto the hardware ? How would you proceed to change the MD-01 settings via the Hamlib librairy ?
Thank you again for your responsiveness, Glenn
I have no documentation that shows how to set the limit in the controller.That could be added if there's documentation to support it.