ROTCLD Easycomm Won't Control Rotor, Error -5

I’m a brand new Gpredict user trying to get a homebrew stepper Az/El rotor to work with a controller running Easycomm. I can issue Az and El commands and receive back current rotor positions using a terminal program, but not with Gpredict.

Running Windows 10, Gpredict 2.2.1, Hamlib w64-4.7.0

I can execute rotcld.exe and get the following status. But as soon as I attempt to move the rotor, the error appears and Gpredict crashes.

Thanks in advance for any suggestions.
Randy WB0VHB

rot_init called
initrots4_easycomm called
rot_register (201)
rot_register (202)
rot_register (204)
rot_open called
serial_open: serial port COM4 is OK
serial_open: COM4
serial_setup: tcgetattr
serial_setup: cfsetispeed=9600,0x000d
serial_setup: cfsetospeed=9600,0x000d
serial_setup: data_bits=8
serial_setup: stopbits=1
serial_setup: parity=0
serial_setup: Handshake=None
serial_setup: tcsetattr TCSANOW
ser_set_dtr: DTR=0
ser_set_rts: RTS=0
Opened rot model 202, ‘EasycommII’
Backend version: 20231218.0, Status: Stable
Connection opened from ::ffff:127.0.0.1:58007
rotctl(d): p ‘’ ‘’ ‘’ ‘’
rot_get_position called
easycomm_rot_get_position called
easycomm_transaction called: AZ

write_block(): TX 3 bytes
0000 41 5a 0a AZ.
read_string_generic called, rxmax=32 direct=1, expected_len=1
read_string_generic(): Timed out 0.201 seconds after 0 chars, direct=1
easycomm_transaction read_string failed with status -5:Unknown error
easycomm_rot_get_position got error: -5
rotctl_parse: NETROTCTL_RET -5

I have no clue :slight_smile: but are you sure your DIY rotor controller speaks easycomm protocal and not GS232A or B ?

Here is the project I used:

No ll problema è comune su Gpredict per windows, anche io ho provato e riprovato, si riesco a muovere il rotore Stnogs originale, ma non ho il feedback della posizione percio’ il rotpre poi ha problemi di posizionamento. nessun problema inceve con linux ubuntu

Si tratta di una cosa mai risolta sembra che easycommin abbinata con Gpredict, ma anche PST rotator è la solita cosa, non intermpretino bene i comandi esaycomm II del rotore. Anche trasformando il protocollo in easycom III stessa cosa pero’

IZ5RZR