rigsync speed slow?

[timgrossner]

Hi, I was using this tool a year or so ago, and had it working really well. New system, recompiled, etc, and for some reason, while it eventually does sync the two rigs, it can take up to a minute or so to get them synced. Any ideas what might be the cause?

username@SkullCanyon:~/rigsync$ ./rigsync -d 10 -m 2 -r localhost:4533 -m 2 -r localhost:4532 -n 2
DEBUG: debug level set: 10
DEBUG: rig count = 2
DEBUG: opened rig: model 2, port localhost:4533, speed 0
DEBUG: opened rig: model 2, port localhost:4532, speed 0
DEBUG: rig 0: reading initial state
DEBUG: rig 0 is dirty: old= 0.00Hz/ new= 14208000.00Hz/USB
DEBUG: clearing dirty flag
DEBUG: rig 1: reading initial state
DEBUG: rig 1 is dirty: old= 0.00Hz/ new= 14208000.00Hz/USB
DEBUG: clearing dirty flag
DEBUG: reading states again
DEBUG: rig 1 is dirty: old= 14208000.00Hz/USB new= 14209000.00Hz/USB
DEBUG: dirty rig: 1
DEBUG: rig 0 is dirty: old= 14208000.00Hz/USB new= 14209000.00Hz/USB
DEBUG: rig_write_state() req= 14209000.00Hz/USB act= 14209000.00Hz/USB
DEBUG: rig 1 is dirty: old= 14209000.00Hz/USB new= 14210000.00Hz/USB
DEBUG: dirty rig: 1
DEBUG: rig 0 is dirty: old= 14209000.00Hz/USB new= 14210000.00Hz/USB
DEBUG: rig_write_state() req= 14210000.00Hz/USB act= 14210000.00Hz/USB

The time it took to get rig 1 to 14210000.00Hz/USB was around 60 seconds.

[timgrossner]

In doing more testing, I believe this to probably be an issue on the SDR's hamlib implementation. Testing with netcat, I am seeing response slowness issues on that side. Thanks, and sorry for the fire drill. :-)

[daveriesz]

Please let me know if you discover that it really is rigsync. What are the rigs you're using?

[timgrossner]

An SDR++ and my FTDX-10.

…

On Fri, Oct 20, 2023, 10:38 AM Dave Riesz ***@***.***> wrote: Please let me know if you discover that it really is rigsync. What are the rigs you're using? — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANKNA2BP7DJCT766EQPAK3YAKLGZAVCNFSM6AAAAAA6HP25BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSHE3TCMJZGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>