I’m trying to connect my SATNOGs system to my Yaesu G450C rotator which I’ve got a Hy-gain RC1-G PC controlled unit. The RC1-G uses a RS232 which I’ve had to buy a RS232 to USB cable to connect to the RPi.
I’m struggling to get the rotator working, the debug is showing ERROR - Cannot connect to socket 127.0.0.1:4533 which means I’m not talking to my rotator I believe
Any help appreciated
That sounds more like you have not started the hamlib rotctld server, I think. I can give more details if that’s the case.
Ok since my earlier post after digging around I can send commands using rotctl directly to the rotator via the command line, I can also see the rotator listening on 0.0.0.0:4553 but when I schedule an observation the rotator does not move.
Logs show:
Error on request:
Nov 28 20:49:06 raspberrypi satnogs-client[540]: Traceback (most recent call last):
Nov 28 20:49:06 raspberrypi satnogs-client[540]: File “/var/lib/satnogs/lib/python2.7/site-packages/werkzeug/serving.py”, line 209, in run_wsgi
Nov 28 20:49:06 raspberrypi satnogs-client[540]: execute(self.server.app)
Nov 28 20:49:06 raspberrypi satnogs-client[540]: File “/var/lib/satnogs/lib/python2.7/site-packages/werkzeug/serving.py”, line 197, in execute
Nov 28 20:49:06 raspberrypi satnogs-client[540]: application_iter = app(environ, start_response)
Nov 28 20:49:06 raspberrypi satnogs-client[540]: File “/var/lib/satnogs/lib/python2.7/site-packages/flask/app.py”, line 1997, in call
Nov 28 20:49:06 raspberrypi satnogs-client[540]: return self.wsgi_app(environ, start_response)
Nov 28 20:49:06 raspberrypi satnogs-client[540]: File “/var/lib/satnogs/lib/python2.7/site-packages/flask_socketio/init.py”, line 42, in call
Nov 28 20:49:06 raspberrypi satnogs-client[540]: start_response)
Nov 28 20:49:06 raspberrypi satnogs-client[540]: File “/var/lib/satnogs/lib/python2.7/site-packages/engineio/middleware.py”, line 47, in call
Nov 28 20:49:06 raspberrypi satnogs-client[540]: return self.engineio_app.handle_request(environ, start_response)
Nov 28 20:49:06 raspberrypi satnogs-client[540]: File “/var/lib/satnogs/lib/python2.7/site-packages/socketio/server.py”, line 360, in handle_request
Nov 28 20:49:06 raspberrypi satnogs-client[540]: return self.eio.handle_request(environ, start_response)
Nov 28 20:49:06 raspberrypi satnogs-client[540]: File “/var/lib/satnogs/lib/python2.7/site-packages/engineio/server.py”, line 290, in handle_request
Nov 28 20:49:06 raspberrypi satnogs-client[540]: socket = self._get_socket(sid)
Nov 28 20:49:06 raspberrypi satnogs-client[540]: File “/var/lib/satnogs/lib/python2.7/site-packages/engineio/server.py”, line 421, in _get_socket
Nov 28 20:49:06 raspberrypi satnogs-client[540]: raise KeyError(‘Session is disconnected’)
Nov 28 20:49:06 raspberrypi satnogs-client[540]: KeyError: ‘Session is disconnected’
Hey,
Are you running the latest version of the satnogs rpi image or a custom installation?
In the first case make sure that you have added the right arguments in satnogs setup for rotctld (HAMLIB_UTILS_ROT_OPTS) and that the flag for no rotor setup is properly set (HAMLIB_UTILS_ROT_ENABLED should be set to True).
In the second case, make sure you run rotctld with the correct arguments before running the client.
Let us know if you managed to fix the issue.
I have the latest version of satnogs RPI.
This is what I have done so far.
I can rotctl directly to the DCU-1 unit via command line, so I can confirm that I have the right arguments (tty/USB0, baud, model number seem correct).
I can see the 4553 port being listened to
I can move the rotator via commandline
I have used Basic configuration and clicked YES to ROT_ENABLED
However when I schedule an observation the rotator does not move. I get an error which I’ve shared in the thread, not sure if this relates but the error is related to server.py? This may not be related though.
I am using a RS232 to USB cable so it’s connected on tty/USB0, the rotator unit is DCU-1 protocol.
Hi Carl (I think),
if your error still is the same as described below:
then I think that you did not understand the way hamlib works. You need to run rigctld with correct arguments (which are the same as with rigctl), then you can start rigctl with arguments “-m 2” to connect to rigctld. Or any other program to communicate with rigctld. rigctld delivers the socket to connect to.
Hope this is explained understandable. If not, please feel free to ask.
To get more help it would be useful to see your commandline for rigctl that works…
HTH, 73,
Patrick, DL4PD
Sorry for your troubles @m6lzt
Can you post here the settings as listed by satnogs-setup so we can review?
The port is 4533; not 4553. Could this be the root cause of your issue?
We have done with @m6lzt some debugging in pm…
The parameters for rotctl are -m 403 -r /dev/ttyUSB0 -s 4800
So it seems that with rotctl works fine but when the same parameters are given to rotctld and @m6lzt tries to connect and send a command with rotctl -m 2 -r localhost:4533 \set_pos 30 20, he gets:
rot_open: error = IO error
[2]+ Exit 1 rotctld -m 403 -r /dev/ttyUSB0 -s 4800
looking on 403 device, it says that it is untested:
403 Hy-Gain DCU-1/DCU-1X 2010-08-23 Untested
So, maybe there are some issues with this rotator and hamlib.
This is interesting… The library underneath is the same. Why is the client working but the server doesn’t?
Sorry that was a typo, I’m using 4533