Doppler control bug w/ IC-910

[sudobob]

This issue is closely related to the issue with the 9700 - https://github.com/csete/gpredict/issues/181

I'm using

Gpredict 2.2.2 rigctl Hamlib 4.5.5 Apr 05 11:43:08Z 2023 SHA=6eecd3

Gpredict radio configuration:

Movie of display behavior https://i.imgur.com/aISSRul.mp4

I read that this was apparently fixed for the IC-9700 but apparently it hasn't for the IC-910?

Here is a rigctld -vvvv -Z output:

ic910-doppler-issue-trace.txt

..Or should this issue be taken up with hamlib?

Thanks for all the great software!

[mdblack98]

Could you please add one more v to the debug output?

This is a hamlib problem.

Mike W9MDB

On Sunday, January 28, 2024 at 11:47:10 AM CST, Bob Coggeshall @.***> wrote:

This issue is closely related to the issue with the 9700 - #181

I'm using

Gpredict 2.2.2 rigctl Hamlib 4.5.5 Apr 05 11:43:08Z 2023 SHA=6eecd3

Gpredict radio configuration: image.png (view on web)

Movie of display behavior https://i.imgur.com/aISSRul.mp4

I read that this was apparently fixed for the IC-9700 but apparently it hasn't for the IC-910?

Here is a rigctld -vvvv -Z output:

ic910-doppler-issue-trace.txt

..Or should this issue be taken up with hamlib?

Thanks for all the great software!

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[sudobob]

I ran the -vvvvv.. I was getting different and inconsistent behavior and was noticing alot 'rig rejected commands'. My IC-910 baud rate was set to Auto. I set it to 19200 and also explicitly started rigctl with --serial-speed=19200 and now things seem more consistent.

You can close this issue. Thanks.

[mdblack98]

You mean it's working now?

On Sunday, January 28, 2024 at 01:55:02 PM CST, Bob Coggeshall @.***> wrote:

I ran the -vvvvv.. I was getting different and inconsistent behavior and was noticing alot 'rig rejected commands'. My IC-910 baud rate was set to Auto. I set it to 19200 and also explicitly started rigctl with --serial-speed=19200 and now things seem more consistent.

You can close this issue. Thanks.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

[sudobob]

Yes. So far as I have tested It looks like the erratic behavior was all due to serial line errors. If I do leave it for a long time they crop up. Also things don't work right if I stay in the radio control window and try to switch satellites.. these issues are resolved be exiting and re-entering the radio control dialog..

[wkitty42]

On 1/29/24 8:07 AM, Bob Coggeshall wrote:

Yes. So far as I have tested It looks like the erratic behavior was all due to serial line errors. If I do leave it for a long time they crop up.

have you tried 9600? it is slower but generally also less susceptible to noise... i'm curious if they still crop up after a while, the same, longer, or shorter than what you are seeing at 19200... or maybe they are in time with other electrical events... i have other thoughts but they are more on the serial side than gpredict so i'll stop here ;)