rot:rot_init called
initrots3_easycomm called
rot_register (201)
rot_register (202)
rot_register (204)
rot:rot_open called
Opened rot model 204, 'EasycommIII'
Backend version: 0.4, Status: Alpha
Rotator command: p
rotctl_parse: input_line: p
easycomm_rot_get_position called
easycomm_transaction called: AZ EL
write_block(): TX 7 bytes
0000 41 5a 20 45 4c 20 0a AZ EL .
read_string(): Timed out 0.203147 seconds after 0 chars
easycomm_transaction read_string failed with status -5
easycomm_rot_get_position got error: -5
get_pos: error = Communication timed out
The "Data" LED on the WRAPS comes on with a "p" command and goes off with the next "p" command, which isn't the normal behaviour, but tells me that I've got the right port and it's getting bits to the WRAPS.
Suggestions?
David, ky7dr
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've got Hamlib 1.3.1 built using Macports on macOS Sierra 10.12.3.
I'm trying to drive a WRAPS rotor, which I'm told uses "EASYCOM".
WRAPS is a pseudo-kit (really a custom board, programmed PIC, shopping list of parts, and some instructions).
Here's a blurb on WRAPS, if you're not familiar: http://ww2.amsat.org/xtra/wraps-mark-spencer-wa8sme-qst-jan-2014-copyright-arrl.pdf
I have successfuly driven my WRAPS with a Windoze box running SatPC32.
I'm trying to get this Mac to drive it.
I've tried -m 201 (EasycommI), -m 202 (EasycommII), and -m 204 (EasycommIII) but I always get a time out error:
jellyfish:~ david$ rotctl -r /dev/tty.usbserial-DA01GYOH -s 9600 -m 204 -vvvvvv
rotctl, Hamlib 3.0.1
Report bugs to hamlib-developer@lists.sourceforge.net
rot:rot_init called
initrots3_easycomm called
rot_register (201)
rot_register (202)
rot_register (204)
rot:rot_open called
Opened rot model 204, 'EasycommIII'
Backend version: 0.4, Status: Alpha
Rotator command: p
rotctl_parse: input_line: p
easycomm_rot_get_position called
easycomm_transaction called: AZ EL
write_block(): TX 7 bytes
0000 41 5a 20 45 4c 20 0a AZ EL .
read_string(): Timed out 0.203147 seconds after 0 chars
easycomm_transaction read_string failed with status -5
easycomm_rot_get_position got error: -5
get_pos: error = Communication timed out
The "Data" LED on the WRAPS comes on with a "p" command and goes off with the next "p" command, which isn't the normal behaviour, but tells me that I've got the right port and it's getting bits to the WRAPS.
Suggestions?
David, ky7dr