开云体育

I use KM4ACK's scripts on my existing raspberry pi-based radios.
They're Icom units, so it's different because there's cat control and individual audio ports presented to the Pi.

Is there any chance of getting the sBitx v2 to support 73Linux/BAP?? More info here:

I'm comfortable in the CLI of Linux, but the current versions of Jason's scripts depend on cat & audio hooked into flrig. I believe that the sBitx is just calling hamlib directly, and there aren't any cat control or audio ports to tap into.

It seems to me that there's a fairly small hurdle to cross (flrig support) to make these two fantastic projects compatible with each other.

It seems to me that there's a fairly small hurdle to cross (flrig support) to make these two fantastic projects compatible with each other.

I think that my question got understood backwards.
I have a functioning sbitx v2.

?

I want to use the 73 Linux/Build-A-Pi software on it.

That software depends on cat control and an identified tx/rx audio port.

?

Or have I misunderstood your reply?

Is there any chance of getting the sBitx v2 to support 73Linux/BAP?? More info here:

I'm comfortable in the CLI of Linux, but the current versions of Jason's scripts depend on cat & audio hooked into flrig. I believe that the sBitx is just calling hamlib directly, and there aren't any cat control or audio ports to tap into.

It seems to me that there's a fairly small hurdle to cross (flrig support) to make these two fantastic projects compatible with each other.

I think that my question got understood backwards.

I have a functioning sbitx v2.

I want to use the 73 Linux/Build-A-Pi software on it.

That software depends on cat control and an identified tx/rx audio port.

I hope this helps..

Hamlib support on the sBitx is controlled by ?which provides a very limited interface on port 4532. This port is also non-routable outside the sBitx by default.

Flrig will not work unless you can somehow use the Hamlib NET rigctl library with it.

The use case involves pat/winlink with ardop, js8call, and all the modes that don't exist as part of the sbitx software package.

Following your directions to attempt to get wsjtx going still has me at a dead stop

In general, I expect to see hamlib running, as well as rigctl running.

?

It looks like the sbitx executable itself has these functions baked in, rather than building off the existing packages?

?

Or, again, am I completely not understanding what's being conveyed?

Looks like we need a rig.xml () or to at least define what the values are so we can take advantage of them?

Once that exists then flrig can ride on top of fldigi (which is already functional) and then the rigctl functions from other packages can proceed as per normal, passing it on down the line to get to the sbitx SDR.

We do know the audio ports, we just need the serial ports for controlling the radio.

?

(Or, again, am I way off base? )

In general, I expect to see hamlib running, as well as rigctl running.

It looks like the sbitx executable itself has these functions baked in, rather than building off the existing packages?

Looks like we need a rig.xml () or to at least define what the values are so we can take advantage of them?

Once that exists then flrig can ride on top of fldigi (which is already functional) and then the rigctl functions from other packages can proceed as per normal, passing it on down the line to get to the sbitx SDR.

We do know the audio ports, we just need the serial ports for controlling the radio.

The use case involves pat/winlink with ardop, js8call, and all the modes that don't exist as part of the sbitx software package.

Following your directions to attempt to get wsjtx going still has me at a dead stop

In general, I expect to see hamlib running, as well as rigctl running.

?

It looks like the sbitx executable itself has these functions baked in, rather than building off the existing packages?

?

Or, again, am I completely not understanding what's being conveyed?

1. Start sbitx and wait at least 30 seconds for it to build the network loopback connection
2. Set the mode to digital
3. Open your third-party app
4. Configure as seen in the screen shots below.

I greatly appreciate these.
It's not exactly how I wanted things to get going, because it's not nicely packaged.

Any ideas on how to get ardop going?