Martin Hebnes Pedersen

This seems like a reasonable feature to add without too much complication. I think we should name the parameter `rig_mode` to further avoid confusion (pactor is also referred to as...

Later we can add logic to allow the user to enable a default rig_mode per transport, or something like that. But I think we should do that in a later...

> I would also like to add bandwidth as a transport URL parameter, but that's a bigger change, and not strictly required right now. I believe this could be implemented...

> I tried separating Disconnect for just RF and Close for RF and TCP, but it turns out the VARA program doesn't tolerate that well (doesn't seem to like rapid...

@xylo04 - What's the status on this? Are you awaiting my review and merge?

> ... and that has taken me off on a tangent of setting up my own RMS. Been there 😆 👍 Thanks for taking the time. My experience is that...

Thanks for reporting this 🙂 Could probably replace this with a reference to `pat env` for simplicity.

Thanks! It sounds to me like the default should be "state 3" then, and users should be able to override this in the config. From `man rigctld`: ``` T, set_ptt...

Thank you for the detailed response :) I agree. State 3 seems to be a more reasonable default, and we should include a config option for it per "rig". I...

It would be great if we could verify that "state 3" is indeed a better default for most rigs out there. If someone is willing to do some testing with...