Basic question for SatNOGS ground station [Help needed]

rotator

#21

We keep on fighting…

just in case we changed the configuration order

Also don’t know why now response to command $ ps aux | grep rotctld doesn’t show user hamlib-+

watching RP journal we saw an error we were not getting before, as shown in the image below in yellow, RP is trying to connect to 127.0.0.1:4533
Maybe satnogs client is expecting AZ and EL from that connection?

should we also configure “-T 127.0.0.1 -t 4533”?
https://www.systutorials.com/docs/linux/man/1-rotctl/

Also used to specify the host and port to connect to a listening rotctld daemon on POSIX:
-r localhost:4533
and on Win32:
-r 127.0.0.1:4533


#22

Patrick,
don’t know why the “d” is missing but as shown in other replies hamlib-+ is running rotctld.
Baudrate is already fixed at 19200 seems to work fine.


#23

well… something did the trick…
maybe it was the change in parameter’s order or maybe it was just turning everything ON with everything connected (sometimes we connected the arduino with RP already ON)

dont really know what was happening!

thank you all very much!


#24

No, that’s wrong! As I told you before: if your code sets up a baudrate at 9600 baud and you need to change it to 19200 in the application connecting to that code there is something really wrong! Most probably the microcontroller is running at the wrong speed. This will cause more problems in the future as all the timing your code is using will be wrong.


#25

sorry I could not follow you, now both the speed in the arduino’s code and in rotctl (RP) are set to 19200 baudios.
Or do you mean that it should have also worked with both at 9600?
Now is actually working, we would really prefer not to change more stuff just in case we go back to square one


#26

This is the default socket address:port of rotctld, no need to set it in command line.

Glad to hear it! :slight_smile:
It would be great sometime in future to find out what happened… maybe by experimenting again with the parameters order and/or the other things you changed.


#27

Ok, that was not as clear as now in your previous posts - I did not get it :wink:

So if both baudrates are set correct (in the arduino C code and the connecting interface) you are free to choose whatever you prefer! Glad it works now!