That is odd, can you modify a line to show the command that is run in the script ?
Change this line to:
echo "$PRG running at $SAMP sps: $GRSBIN $GROPT"
1 Like
Hiā¦
same info on log fileā¦
(GRBAlpha.yml is also supported by grsat)
https://network.satnogs.org/observations/9472710/
Monitoring journalctl show this, I believe, is normalā¦(??) VE2DSK
May 04 16:55:13 raspberrypi satnogs-client[407]: netrigctl_close: done status=Command completed successfully
May 04 16:55:15 raspberrypi satnogs-client[1108]: gr-satellites: Observation: 9472710, Norad: 47959, Name: 0_OBJECT_AD, Script: satnogs_fsk.py
May 04 16:55:15 raspberrypi satnogs-client[1108]: gr-satellites: Stopping observation 9472710
May 04 16:55:15 raspberrypi satnogs-client[1108]: /usr/local/bin/grsat-wrapper.sh: line 68: kill: (915) - No such process
915 is the grsat_1461.pid terminated process.
Hi, I got those error lines each time new process startā¦ VE2DSK
May 04 13:59:38 raspberrypi satnogs-client[25952]: parse error: Invalid numeric literal at line 2, column 0
May 04 13:59:38 raspberrypi satnogs-client[25957]: parse error: Invalid numeric literal at line 2, column 0
May 04 13:59:38 raspberrypi satnogs-client[25948]: gr-satellites: Observation: 9472215, Norad: , Name: , Script:
That most likely comes from jq, that is responsible for getting the norad id and satellite name from the TLE.
Which either means something has changed, or ā¦ not sure. Is it on all the passes or just some ?
Could you add a echo "$TLE" on a separate line at that point to make it print the raw TLE.
Thatās the resultā¦
May 09 20:41:11 raspberrypi satnogs-client[5616]: UHF antenna selected
May 09 20:41:11 raspberrypi satnogs-client[5620]: 2024-05-09T19-41-11
May 09 20:41:11 raspberrypi satnogs-client[5624]: parse error: Invalid numeric literal at line 2, column 0
May 09 20:41:11 raspberrypi satnogs-client[5629]: parse error: Invalid numeric literal at line 2, column 0
May 09 20:41:11 raspberrypi satnogs-client[5620]: gr-satellites: Observation: 9501700, Norad: , Name: , Script:
May 09 20:41:11 raspberrypi satnogs-client[5620]: gr-satellites: Starting observation 9501700
May 09 20:41:12 raspberrypi satnogs-client[5620]: gr-satellites: running at 48000 sp
That looks like the date is in the TLE positionalā¦ are you using SATNOGS_PRE_OBSERVATION_SCRIPT set to satnogs-pre {{ID}} {{FREQ}} {{TLE}} {{TIMESTAMP}} {{BAUD}} {{SCRIPT_NAME}} ?
Yesā¦
satnogs_pre_observation_script: /home/pi/satnogs-pre {{ID}} {{FREQ}} {{TIMESTAMP}}
{{BAUD}} {{SCRIP_NAME}}
But that doesnāt match, and is a pretty good explanation of why it fails. {{TLE}} is missing, and it absolutely has to be in the correct position.
Ohhhā¦
Youāre rightā¦
{{TLE}} missingā¦ Thankā¦ VE2DSK
1 Like
Better lookā¦
VE2DSK
May 09 21:21:20 raspberrypi satnogs-client[6515]: VHF antenna selected
May 09 21:21:20 raspberrypi satnogs-client[6519]: {"tle0": "0 PCSAT", "tle1": "1 26931U 01043C 24130.56269912 .00000435 00000-0 19578-3 0 9994", "tle2": "2 26931 67.0513 71.3346 0006543 281.9715 78.0653 14.31206508180424"}
May 09 21:21:20 raspberrypi satnogs-client[6519]: gr-satellites: Observation: 9502118, Norad: 26931, Name: 0_PCSAT, Script: {{SCRIP_NAME}}
May 09 21:21:20 raspberrypi satnogs-client[6519]: gr-satellites: Starting observation 9502118
May 09 21:21:21 raspberrypi satnogs-client[6519]: gr-satellites: running at 48000 sps
Hi, the EIRSAT-1.yml file indicate 9600 bd FSK modulation type.
My monitoring lineā¦:
gr-satellites: Observation: 9594096, Norad: 58472, Name: 0_OBJECT_L, Script: satnogs_fsk.py
Is the FSK and GMSK are the same gr_satellites decoding process ā¦?
All my EIRSAT-1 observations didnāt decode any data.
https://network.satnogs.org/observations/9594096/
As example, here some other station with decoded data.
https://network.satnogs.org/observations/9596012/
https://network.satnogs.org/observations/9592975/
I believe Norad: 58472, Name: 0_OBJECT_L should be Norad: 58472, Name: EIRSAT-1
VE2DSK
I think the flowgraph used for both is fsk. the implementation does not care what flowgraph is running, only how it calculates the sample rate is the difference, even the cw flowgraph should work as the lowest udp sample rate is 48k.
While a observation is running, do a ps ax|grep -v grep|grep gr_satellites and see what exact command is running. If it doesnāt show up, then is either launched improperly or the satyaml is broken somehow.
To test the basics, try gr_satellites 58472 --samp_rate 48e3 --udp, if it stays running for like 10s it should be fine. Depending on log level and version, it could print udp_source :info: Listening for data on UDP port 7355. terminate with Ctrl-C.
According to the TLE, the name is a bit odd, but does not matter here.
Hiā¦
here the resultā¦:
EIRSAT-1 401.360 MHz Mode U - GMSK9k6 observation..:
15044 ? Sl 0:17 /usr/bin/python3 /usr/local/bin/gr_satellites 58472 --samp_rate 48000 --iq --udp --udp_port 57356 --udp_raw --start_time 2024-05-30T15:48:19 --kiss_out /tmp/.satnogs/grsat_9615299.kss --ignore_unknown_args --use_agc --satcfg
Monitoring lineā¦:
gr-satellites: Observation: 9615299, Norad: 58472, Name: 0_OBJECT_L, Script: {{SCRIP_NAME}}
TIGRISAT 435.000 MHz FSK 9600 observation..:
13367 ? Sl 0:06 /usr/bin/python3 /usr/local/bin/gr_satellites 40043 --samp_rate 48000 --iq --udp --udp_port 57356 --udp_raw --start_time 2024-05-28T22:40:44 --kiss_out /tmp/.satnogs/grsat_9606411.kss --ignore_unknown_args --use_agc --satcfg
Monitoring lineā¦:
gr-satellites: Observation: 9606411, Norad: 40043, Name: TIGRISAT, Script: satnogs_fsk.py
I believe EIRSAT-1 doesnāt have defined script processā¦
VE2DSK
EIRSAT-1 and gr-satellites work fine SatNOGS Network - Observation 9600409
One thing that could be missing is the following sat specific config file:
/var/lib/satnogs/.gr_satellites/sat.cfg
Here are the entries:
35933 --clk_bw 0.3
37855 --clk_bw 0.1
46276 --clk_bw 0.1
47960 --disable_dc_block
48900 --disable_dc_block
58472 --input_gain -1
58472 --input_gain -1 is a specific EIRSAT-1 option.
1 Like
That one I have missed, I updated the repo now.
1 Like
Hi,
Thank for precisions guyā¦
Lot of time I have broken undefined python scriptā¦ Script: {{SCRIP_NAME}}
I leave my station like that for the momentā¦
Many thank for this adventureā¦ VE2DSK
1 Like
Hiā¦
gr-satellites otionsā¦:
I have include new Bluebird_0x.yml on my station, but seem na have decoding result dataā¦(?)
https://network.satnogs.org/observations/10242598/
https://network.satnogs.org/observations/10242599/
https://network.satnogs.org/observations/10235063/
I donāt know if norad ID and name are correct.
ve2dsk
gr-satellites: Observation: 10235063, Norad: 61049, Name: SPACEMOBILE-004, Script: {{SCRIP_NAME}}
gr-satellites: Starting observation 10235063
gr-satellites: running at 48000 sps
rig_init: rig does not have rx_range!!
network_open: hoststr=127.0.0.1, portstr=4532
[INFO] Opening HackRF One #0 71c469c824757243...
netrigctl_close: done status=Command completed successfully
gr-satellites: Observation: 10235063, Norad: 61049, Name: SPACEMOBILE-004, Script: satnogs_fsk.py
gr-satellites: Stopping observation 10235063
This is still wrong, in the pre script SCRIP_NAME is missing a T. It needs to be exactly {{SCRIPT_NAME}}
Donāt type them in, copy and paste to avoid typos. Exactly as in the head of the pre- and post-script says respectively.
When experimenting, you can enable the GRSAT_KEEPLOGS=yes feature to save the output from gr_satellites in a file for each observation. There you will see all the output, errors and warnings. Remember to clear the logs out and perhaps disable that unless you want to fill the tmpfs up with logs (:
Opsā¦ I redo that, thanks ve2dsk
98800 is Bluebird 05 (SPACEMOBILE-001)
98804 is Bluebird 01 (0_OBJECT_B)
98846 is ION SCV-12 (0_OBJECT_DK)
98840 is LUR-1 (0_OBJECT_AN)
Just infoā¦:
98804 is Bluebird 01
gr-satellites: Observation: 10256066, Norad: 61046, Name: SPACEMOBILE-005, Script: satnogs_fsk.py
The Log say grsat_10256066.log Satellite 61046 not found.
ve2dsk