Auto-switching from satellite to satellite


#1

Greetings,

I have been monitoring the WX satellites (APT) recently and thought I could have to RTL-SDR change frequency automatically when a new satellite was overhead.

For the receiver, I have AOS and LOS signalling selected. Are there extra settings?

Best regards,
Fred N7FMH


#2

Hi Fred,

Please be a little more specific about what exactly you have tried and what is not working as expected.

Alex


#3

Sorry about that!

I have a module with 4 satellites: NOAA 15, NOAA 18, NOAA 19, METEOR-M 2.
I am using an RTL-SDR for the receiver. In its configuration, I have checked AOS and LOS signalling.

As a satellite comes over the horizon, the radio control doesn’t “Engage” automatically. I have the Radio Control open and am also watching SDR#.

I can click “Engage” and then the RTl-SDR will be controlled. After the pass is over, it dis-engages automatically. It does not auto engage for the next pass.

Thanks!

Best regards,
Fred N7FMH


#4

I don’t know why that happens. If you have autotrack enabled, it should just switch to the next satellite and also tune the radio to that frequency. I suspect the dis-engage is because SDR# stops responding to commands. Unfortunately, I do not have experience with it, so perhaps @w41 can enlighten us.

In the meanwhile, you can take a look at the message log under the File menu to see if any errors are displayed when the dis-engage happens.


#5

According to the log (thanks for the reminder!) there are some errors.

Since I am using a SDR# plug-in I was not using Hamlib’s rigctld. This is what the log file looked like

2019/02/04 17:05:30|3|sat_log_init: Session started
2019/02/04 17:05:30|4|sat_cfg_load: Everything OK.
2019/02/04 17:25:33|2|…/src/tle-update.c:read_fresh_tle: Two different statuses for 25338 (NOAA-15) at the same time.
2019/02/04 17:25:33|2|…/src/tle-update.c:read_fresh_tle: Two different statuses for 28654 (NOAA-18) at the same time.
2019/02/04 17:25:33|2|…/src/tle-update.c:read_fresh_tle: Two different statuses for 33591 (NOAA-19) at the same time.
2019/02/04 17:25:33|2|…/src/tle-update.c:read_fresh_tle: Two different statuses for 37849 (SUOMI NPP) at the same time.
2019/02/04 17:25:33|2|…/src/tle-update.c:read_fresh_tle: Two different statuses for 43013 (NOAA 20) at the same time.
2019/02/04 17:44:20|1|_send_rigctld_command: SIZE ERROR 13 / 12
2019/02/04 17:44:20|1|_send_rigctld_command: SIZE ERROR 2 / 1
2019/02/04 17:44:20|1|…/src/gtk-rig-ctrl.c:check_get_response: get_freq_simplex rigctld returned error (RPRT 0
2019/02/04 17:44:20|1|)
2019/02/04 17:44:20|1|_send_rigctld_command: SIZE ERROR 4 / 3
2019/02/04 17:44:20|1|_send_rigctld_command: SIZE ERROR 2 / 1
2019/02/04 17:44:20|1|…/src/gtk-rig-ctrl.c:check_get_response: get_freq_simplex rigctld returned error (RPRT 0
2019/02/04 17:44:20|1|)

Then I restarted everything after starting rigctld:

2019/02/04 17:47:48|3|sat_log_init: Session started
2019/02/04 17:47:48|4|sat_cfg_load: Everything OK.
2019/02/04 17:48:11|1|gtk_sat_data_read_sat: Error reading NAME from C:\Users\SPB_Data\Gpredict\satdata\28932.sat (Key file does not have key “NAME” in group “Satellite”)
2019/02/04 17:48:11|1|gtk_sat_data_read_sat: Error reading NAME from C:\Users\SPB_Data\Gpredict\satdata\39430.sat (Key file does not have key “NAME” in group “Satellite”)
2019/02/04 17:48:11|1|gtk_sat_data_read_sat: Error reading NAME from C:\Users\SPB_Data\Gpredict\satdata\41790.sat (Key file does not have key “NAME” in group “Satellite”)
2019/02/04 17:48:11|1|gtk_sat_data_read_sat: Error reading NAME from C:\Users\SPB_Data\Gpredict\satdata\39430.sat (Key file does not have key “NAME” in group “Satellite”)
2019/02/04 17:48:11|1|gtk_sat_data_read_sat: Error reading NAME from C:\Users\SPB_Data\Gpredict\satdata\41790.sat (Key file does not have key “NAME” in group “Satellite”)
2019/02/04 17:48:11|1|gtk_sat_data_read_sat: Error reading NAME from C:\Users\SPB_Data\Gpredict\satdata\28932.sat (Key file does not have key “NAME” in group “Satellite”)
2019/02/04 17:48:11|1|gtk_sat_data_read_sat: Error reading NAME from C:\Users\SPB_Data\Gpredict\satdata\39430.sat (Key file does not have key “NAME” in group “Satellite”)
2019/02/04 17:48:21|1|_send_rigctld_command: SIZE ERROR 13 / 12
2019/02/04 17:48:21|1|_send_rigctld_command: SIZE ERROR 2 / 1
2019/02/04 17:48:21|1|_send_rigctld_command: SIZE ERROR 4 / 3

It does seem to be functioning now with rigctld running. Now to work on getting a clean signal.

Thanks!
Fred N7FMH


#6

Sounds like a problem in the gpredict connector plugin when receiving the aos/los messages. I will have a look at this.


#7

In case it helps, eventually the log ends with:

2019/02/04 19:28:52|1|_send_rigctld_command: SIZE ERROR 2 / 1
2019/02/04 19:28:52|1|…/src/gtk-rig-ctrl.c:check_get_response: get_freq_simplex rigctld returned error (RPRT 0
2019/02/04 19:28:52|1|)
2019/02/04 19:28:53|1|_send_rigctld_command: SIZE ERROR 2 / 1
2019/02/04 19:28:53|1|…/src/gtk-rig-ctrl.c:check_get_response: get_freq_simplex rigctld returned error (RPRT 0
2019/02/04 19:28:53|1|)
2019/02/04 19:28:54|1|_send_rigctld_command: SIZE ERROR 2 / 1
2019/02/04 19:28:54|1|…/src/gtk-rig-ctrl.c:check_get_response: get_freq_simplex rigctld returned error (RPRT 0
2019/02/04 19:28:54|1|)
2019/02/04 19:28:54|1|…/src/gtk-rig-ctrl.c:rigctl_run: MAX_ERROR_COUNT (5) reached. Disengaging device!
2019/02/04 21:35:16|1|get_current_pass: Returning a pass for NOAA 18 that starts after the seeded time.
2019/02/05 05:53:30|1|get_current_pass: Returning a pass for NOAA 19 that starts after the seeded time.
2019/02/05 11:36:42|1|get_current_pass: Returning a pass for NOAA 18 that starts after the seeded time.
2019/02/05 11:39:59|1|get_current_pass: Returning a pass for NOAA 18 that ends before the seeded time.

Thanks!

Best regards,
Fred


#8

So i tried to recapitulate the problem but without success. I used the following setup:

  • Gpredict v2.3.37
  • SDR# v1.0.0.1700
  • GpredictConnector v0.3

I configured gpredict with a list of 9 ham radio sats. AOS and LOS signaling was active. I selected autotrack and let the whole thing run for 24 hours. Everything was working fine. No connection loss and the sats where switched automatically.

The signaling of AOS/LOS is ignored by GpredictConnector and does not lead to an connection abort.

@cruelshoes Did you use the latestversion of GpredictConnector? (v0.3)

73!
Alex


#9

Installed last June:
GPredictConnector, v2
GPredict, Windows 2.2.1
SDR#, v1.0.0.1605

I can go through and update.

Is there an order to starting each package?

I seem to remember reading that if using hamlib, then rigctld should be started first. Since I currently took my FT857D out of the radio list and am not using anything except an RTL-SDR. I don’t start rigctld at all.

I thought this was working for me last June.

Thanks for looking into this Alex!

Best regards,
Fred N7FMH


#10

It may not make any difference with your problem, you could try the 2.3.37 snapshot:

It does fix some networking issues and should overall be better than 2.2.1 :slight_smile:


#11

I set up the latest for SDR# and GpredictConnector. Things appear to be functioning as designed.

I really think it worked previously. I had added a second radio and then deleted it. Is it possible that caused something unusual?

I will look at the 2.3.37 snapshot. I have had some “crashes” withthe current version on occasion. I haven’t taken any notes so there is nothing to act on.

Thanks to everyone for your help!

Best regards,
Fred N7FMH