-
-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LilacSat-2 KISS transport locks up #614
Comments
Can you share a link to the raw IQ file (or |
I have seen that if I modify the SatYAML to remove everything except the 4k8 transmitter, then |
I think it is the kiss_to_pdu that locks up, using hexdump disables it, right ? Same as removing the kiss/kiss3 in the yaml. |
I think so, but I'd have to check the code. If the kiss_to_pdu doesn't have anything connected at its input, then I guess it makes sense that it doesn't terminate. |
What should we do with this issue? My reading was that if the SatYAML is such that it leaves some |
I initially thought it was the kiss block that behaved erratically when fed with for example only the escape characters, the other details was more of selecting which blocks that was active. |
Trying to figure out what's the state of the issue and action to take. My last comment in #614 (comment) suggested that this is expected behaviour and a non-issue (a particular case of a modified SatYAML that causes the flowgraph to run forever because it leaves some blocks in the flowgraph with a disconnected PDU input). It might be that I missed something. |
While measuring deviation on observation 9873340 I noticed that the gr_satellites app did not exit after running through the file.
gr_satellites lilacsat-2 --iq --rawint16 iq_9873340_48000.raw --samp_rate 48000
seems to work fine.I did cut out a piece of a seemingly strong frame
dd bs=$((4*48000)) if=iq_9873340_48000.raw of=cut.raw skip=314 count=2
and ran with a satyaml that only contains the 4k8 transmitter because I wanted to look at the waveform.gr_satellites LilacSat-2_48.yml --iq --rawint16 cut.raw --samp_rate 48000 --dump_path dump --disable_dc_block
It prints one pdu and does not exit, the dump files does not get bigger and on cpu hogging going on.
When I add
--hexdump
it prints two frames and exits cleanly.The last one contains a bunch of
C0
which is KISS FEND character.The text was updated successfully, but these errors were encountered: