rigctl function crashes

[tgrossner]

Hi there! I am using a script to keep SDR++ and my transceiver rig in sync, and nearly without fail the rigctl connection to SDR++ eventually dies and I have to restart SDR++. Any workarounds or potential for improving it's stability? Is there anything I can provide to maybe help resolve the issue? I am using a script developed at https://github.com/g0fcu/gqrx-hamlib for the sync.

Thanks in advance!

[AlexandreRouma]

Hello,
There is no way for me to know what's going on without more details (start sdr++ in a terminal and send the full logs when a disconnection happens).
What I suspect is going on is you're using a tool made for GQRX that is likely using GQRX specific commands that are not supported in SDR++.

[tgrossner]

Understood. I will see about generating that later this evening. And, agreed, it's likely something gqrx specific, though my intention is just to change frequency and keep it in sync with the rig.

…

On Wed, Jan 19, 2022, 10:17 AM AlexandreRouma ***@***.***> wrote: Hello, There is no way for me to know what's going on without more details (start sdr++ in a terminal and send the full logs when a disconnection happens). What I suspect is going on is you're using a tool made for GQRX that is likely using GQRX specific commands that are not supported in SDR++. — Reply to this email directly, view it on GitHub <#598 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALTNUUFDDPGCHLHXPE3A6TUW3PYPANCNFSM5MJYR3XA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[tgrossner]

[2022-01-19 12:27:16.316] [info] Rigctl command: 'f' [2022-01-19 12:27:16.540] [info] Rigctl command: 'f' [2022-01-19 12:27:16.764] [info] Rigctl command: 'f' [2022-01-19 12:27:16.987] [info] Rigctl command: 'f' [2022-01-19 12:27:17.213] [info] Rigctl command: 'f' [2022-01-19 12:27:17.436] [info] Rigctl command: 'f' [2022-01-19 12:27:17.660] [info] Rigctl command: 'f' [2022-01-19 12:27:17.883] [info] Rigctl command: 'f' [2022-01-19 12:27:18.106] [info] Rigctl command: 'f' [2022-01-19 12:27:18.329] [info] Rigctl command: 'f' [2022-01-19 12:27:18.553] [info] Rigctl command: 'f' [2022-01-19 12:27:18.777] [info] Rigctl command: 'f' (stops responding)

…

On Wed, Jan 19, 2022 at 10:32 AM Tim Grossner ***@***.***> wrote: Understood. I will see about generating that later this evening. And, agreed, it's likely something gqrx specific, though my intention is just to change frequency and keep it in sync with the rig. On Wed, Jan 19, 2022, 10:17 AM AlexandreRouma ***@***.***> wrote: > Hello, > There is no way for me to know what's going on without more details > (start sdr++ in a terminal and send the full logs when a disconnection > happens). > What I suspect is going on is you're using a tool made for GQRX that is > likely using GQRX specific commands that are not supported in SDR++. > > — > Reply to this email directly, view it on GitHub > <#598 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AALTNUUFDDPGCHLHXPE3A6TUW3PYPANCNFSM5MJYR3XA> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.*** > com> >

[tgrossner]

...it lasts about 5-7 min before dying, if that helps. I am looking to see if there is a command line extension that can run with more verbose output.

…

On Wed, Jan 19, 2022 at 12:30 PM Tim Grossner ***@***.***> wrote: [2022-01-19 12:27:16.316] [info] Rigctl command: 'f' [2022-01-19 12:27:16.540] [info] Rigctl command: 'f' [2022-01-19 12:27:16.764] [info] Rigctl command: 'f' [2022-01-19 12:27:16.987] [info] Rigctl command: 'f' [2022-01-19 12:27:17.213] [info] Rigctl command: 'f' [2022-01-19 12:27:17.436] [info] Rigctl command: 'f' [2022-01-19 12:27:17.660] [info] Rigctl command: 'f' [2022-01-19 12:27:17.883] [info] Rigctl command: 'f' [2022-01-19 12:27:18.106] [info] Rigctl command: 'f' [2022-01-19 12:27:18.329] [info] Rigctl command: 'f' [2022-01-19 12:27:18.553] [info] Rigctl command: 'f' [2022-01-19 12:27:18.777] [info] Rigctl command: 'f' (stops responding) On Wed, Jan 19, 2022 at 10:32 AM Tim Grossner ***@***.***> wrote: > Understood. I will see about generating that later this evening. And, > agreed, it's likely something gqrx specific, though my intention is just to > change frequency and keep it in sync with the rig. > > On Wed, Jan 19, 2022, 10:17 AM AlexandreRouma ***@***.***> > wrote: > >> Hello, >> There is no way for me to know what's going on without more details >> (start sdr++ in a terminal and send the full logs when a disconnection >> happens). >> What I suspect is going on is you're using a tool made for GQRX that is >> likely using GQRX specific commands that are not supported in SDR++. >> >> — >> Reply to this email directly, view it on GitHub >> <#598 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AALTNUUFDDPGCHLHXPE3A6TUW3PYPANCNFSM5MJYR3XA> >> . >> Triage notifications on the go with GitHub Mobile for iOS >> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> >> or Android >> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. >> >> You are receiving this because you authored the thread.Message ID: >> ***@***.*** >> .com> >> >