My solution for rotctld

For those who use windows or those who use linux and have the problem that the arduino interface is ticked or the pc ticked, I found a precarious solution.
Is install Gpredict 1.4 . hamlib probe several and they all work, not so the Gpredict that the new one does not work, or the old one, but version 1.4 work good.

Julio :grinning: :crossed_fingers:
LW2DYB

more problems, version 1.4 does not lower the transponders. No solution then. yet

Please describe exactly what problems you have.
gpredict version 1.4 is outdated!

Hi. Im big problem no link good. I dont for what. Please help!!

$ rotctld -m 604 -r /dev/ttyACM0 -t 4533 -vvvvv
rotctld, Hamlib 4.0
Report bugs to hamlib-developer@lists.sourceforge.net

rot_init called
initrots4_gs232a called
rot_register (601)
rot_register (609)
rot_register (610)
rot_register (602)
rot_register (603)
rot_register (611)
rot_register (612)
rot_register (604)
rot_register (605)
rot_register (606)
rot_register (607)
rot_register (608)
set_conf: called
rot_open called
serial_open called
serial_setup called
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=9600,0x000d
serial_setup: cfsetospeed=9600,0x000d
serial_setup: data_bits=8
serial_setup: parity=0
serial_setup: tcsetattr TCSANOW
serial_flush called
tcflush
Opened rot model 604, β€˜GS232/F1TE Tracker’
Backend version: 20200424.0, Status: Beta
Connection opened from localhost:57640
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): P β€˜98,52’ β€˜10,75’ β€˜β€™ β€˜β€™
rot_set_position called az=98.52 el=10.75
rot_set_position: south_zero=0
gs232_rot_set_position called: 98.519997 10.750000
write_block called
write_block(): TX 9 bytes
0000 57 30 39 39 20 30 31 31 0d W099 011.
rotctl_parse: NETROTCTL_RET 0
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): S β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_stop called
rotctl_parse: NETROTCTL_RET -11
Connection closed from localhost:57640
Connection opened from localhost:57642
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): P β€˜106,90’ β€˜11,69’ β€˜β€™ β€˜β€™
rot_set_position called az=106.90 el=11.69
rot_set_position: south_zero=0
gs232_rot_set_position called: 106.900002 11.690000
write_block called
write_block(): TX 9 bytes
0000 57 31 30 37 20 30 31 32 0d W107 012.
rotctl_parse: NETROTCTL_RET 0
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): p β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_get_position called
rotctl_parse: NETROTCTL_RET -11
rotctl(d): S β€˜β€™ β€˜β€™ β€˜β€™ β€˜β€™
rot_stop called
rotctl_parse: NETROTCTL_RET -11
Connection closed from localhost:57642

If put -m 601, 602, o 603 tild interface but -m 604 error up.

*************** it is the same in windows as in linux *****************
Julio
LW2DYB

1 Like

A few initial things to check:

  • is the port correct?
  • is your rotator supporting the protocol GS232a?
  • does it respond to anything if you connect a serial terminal directly to that port?

If you look, the first send of data makes it correct and then it does nothing. I am trying to solve with another soft that is not the rotctld because I do not understand how it handles everything.

Hello,

I have very similar problem. I have β€œrotctl_parse: NETROTCTL_RET 0”… My configuration is Gpredict 2.3.37 on Windows 10 and Hamlib (Rotctld) 4.3.1 on linux. Is there any progress in solving this problem?

Add.
But Gpredict v1.4 + Rotctld 4.3.1 works well… Newer version of Gpredict don’t work anymore.

v1.4 is absolutely outdated and does not work with any radio.
Please update and report issues!

Hi,
here https://community.libre.space/t/anyone-connected-alfaspid-rot2prog-usb-to-raspberry-pi/4407 I found a solution to my problem with rotctl (rotctld). In my case, there was a problem in timing between two commands. After adding the β€œ-C post_write_delay=300” parameter, the current version now works well.