ekinnee / sharpcat Goto Github PK

We need a standard way to define a radio and its commands / capabilities.

Currently SharpCAT is using a cs file that defines a radio. This is clunky and requires recompilation for radio config changes.

On Windows there's a max of 256 com ports, why not support using all of them?

Add async support.

Implement the flrig protocol so that SharpCAT may be used in place.

Create a client component that can utilize remote serial ports handled by SharpCAT as if they were local ports. For example, make local COM2 actually be on a remote host running SharpCAT.

Greetings,

I am very interested in your project. I am working on a project that could use a native CAT library. My project is outlined at http://www.hambus.org however it isn't up to date as I have changed strategies on how the buses will communicate from using UDP to SignalR. Also with this change, BusMaster is now the main hub that all other buses talk to with SignalR.

The idea behind HamBus is Any Radio, Any Computer, Any Application, Anywhere.

Right now I have a RigBus for Kenwood CAT protocol and a VirtualRigBus that also speaks as a Kenwood radio would. The idea is until application authors can add HamBus Rig API to their application users will be able to point applications to a virtual rig which will send the commands to the real radio(s).

The code is in somewhat of a mess, I have been adding code trying to get something working for Field Day and it isn't as clean as I would like for it to be.

It seems like our two projects can really help each other.

You can contact me at "darryl at wagoner.me"

thanks and 73
Darryl DE WA1GON