[BUG] Rig Control with Yaesu 817ND

[onzarob]

Describe the Bug

Using Web, Rig Control is Detected, but no comms with Rig

Rig set to 38400 Baud

Works with all other control software FT8, FT commander, Omnirig etc.

Expected Behavior

When I click PTT rig should key up, Frequency should be displayed

Screenshots

Environment

• Windows 11
• Chrome 145, Firefox 147, Safari 17]
• Running As: Web browser
• Tried with Firewall on and off
• can connect to https://localhost:5555

Additional Context

Tried deleting and reconfiguring/download. no luck

73! VE1KTD

[ceotjoe]

@accius I'm not sure if we should really go into all that USB CAT interfacing stuff too much.

Problem is, this takes probably a lot of time to test with different rigs. If it works, fine, but if not users should use flrig or rigctld (HAMlib) with rig-bridge. They mastered that stuff already and we can simply use a unified API. That's why I was choosing that from start, because I like flrig for exactly this reason.

We can keep our own USB approach for easy start, but mid term users should use flrig or rigctld.

From my perspective it's better for users to take a common approach for all of their applications interfacing with flrig or rigctld. This just blocks the USB port once and all applications can then connect via network to flrig or rigctld.

My approach would be, get rid off rig-daemon and rig-listener and concentrate on rig-bridge integrating everything there. Or we call it OHC_bridge in the end and integrate all bridging there. Even the other bridges we have. User then only has one app as universal bridge for everything. What do you think?

Only my 5 cents. :-)

[accius]

@ceotjoe Id have to agree, i created riglistener as a simple approach for users to have access without having to setup a whole bunch of crap locally. Alot of our users just want it to work on the website. If we can come up with a unified approach that works on both local hosted and website platforms that doesnt take too many extra steps, I would be down with that.

[accius]

@ceotjoe you gonna take this project on?

[ceotjoe]

@accius yes, I'll take it. I will concentrate on bringing all to rig-bridge somehow. Maybe giving it some more modular structure where we can plugin bridges as needed. To make it easy to integrate new bridges and reduce code interference. We can then ask the maintainers of the other bridges to provide their modules as plugins.

[ceotjoe]

/assign

[accius]

Thank you @ceotjoe

[ceotjoe]

Will probably not be a quick shot, but I take care. :-)

[ceotjoe]

@onzarob please test rig-bridge (not rig-listener) which will be updated with #620 most probably with the release next week.

[onzarob]

@ceotjoe I tried today,

I get this if that helps. i did run as administrator as well to check. the config page came up perfectly

[ceotjoe]

@ceotjoe where did you take rig-bridge from?

Current version will be within the release of next week Tuesday. Currently it is still in staging https://github.com/accius/openhamclock/tree/Staging/rig-bridge.

From error message it could also be that the COM3 port is possibly in use by something else currently. There is no other SW running on that machine accessing the COM port currently?

[onzarob]

@ceotjoe

Nothing using com3, i did a restart to make sure.

I downloaded the files from openhamclock
/rig-bridge/

I can try from the link you posted?