Re: MacBook OS and Failure to Transmit

 

Yep. Was there. Not to be picky, but as a newbie to /this/ subject, I was not sure what
"GPIO3 (RA-Board)" actually meant...because it doesn't /say/ needs extra purchase, as many of the other digirig pages do when extra hardware is needed. I have used lots of GPIO devices in the past, and I was left wondering how I accessed GPIO3. Disassemble the digirig? Solder a wire? Attach a PTT switch to the wire?

"GPIO3 (aka "RA Board" which is the GPIO 3 pin of the C-Media 108 usb sound card chipset)" doesn't mean anything TO THE UNENLIGHTENED. We call lotsa things what they ain't, and "RA Board" could mean anything.

So now I see that I need to buy another board...otherwise, the digirig lite is just another SignaLink to me (not that I have a problem with that...I use SL regularly). And "RA board" aware software must be used. It seems that this software (fldigi appears to support it) sends a command to the RA board that is plugged into the USB port, the board then sends a command to the digirig, in addition to the audio stream, to toggle GPIO3. Why the board is needed is not clear. It seems that the digirig lite does not accept what ever the RA board accepts. So, to get the same functionality that I have already with the digirig, I need a $50 board, another piece of hardware, and I get to not use a COM port (Windows)...which has always worked for me. Still, I see the benefit of the digirig lite, if it relies only on VOX, because of the smaller form factor and simpler cabling. (Though I note that digirig recommends if you use one of their cables designed to work w the digirig, you tape the unused connector. As an aside, I might use masking tape for that but I'd never use electrical tape on a TRS plug. I'd likely just find something reusable to slide over the plug.)

I think that the digirig site could benefit from some clarity, some links to relevant 3rd party hardware, and perhaps a line diagram or actual image of what a setup looks like.

Thanks for taking the time to write that explanation, though.


Re: MacBook OS and Failure to Transmit

 

(look in the PTT methods row)
OK. I was wrong about the regular digirig mobile -- it can't do the "RA Board" PTT method. It can do PTT via CAT command or by COM port RTS line (for radios without CAT, like HTs).
The Digirig Lite and DR-891 can both do PTT via GPIO3 (aka "RA Board" which is the GPIO 3 pin of the C-Media 108 usb sound card chipset) and Active VOX on the right audio channel (never used it, I guess it does "real PTT" when it hears something on the right channel).
The DR-891 can also do PTT via CAT command.
I remember doing the GPIO3 (RA Board) method with Digirig Lite and an HT and VARA FM because I did it recently. Before when I did FLDIGI, AndFLMSG, and PSKDroid with a regular Digirig, I must have used RTS on the serial port (no CAT commands on HTs).
For the GPIO3 (RA Board), VARA FM supports it by the name "RA Board", and I believe I believe on FLDIGI it's under the name Cmedia with GPIO-3 IIRC. FLrig and others also support COM port RTS line for PTT for the regular digirig.
I believe it's called "RA Board" because of another product called "RA Board" from Masters Communications that also uses a similar C-Media USB soundcard chip as digirig (or vice versa -- I think the Masters Communications boards have been around longer than digirig).
Hope that clarifies.


Re: MacBook OS and Failure to Transmit

 

I have a regular digirig, and this is the first I've heard about RA Board. I did some research, and it seems (can't find an /explicit/ statement on the digirig site) that with the digirig lite you either
use VOX, which is what the original digirigs were supposed to eliminate as a source of message inefficiency, OR
buy a separate board, and use software that recognizes the RA Board, and will send a "PTT" signal to it, apparently causing the RA board to then send a command to the digirig to toggle GPIO3 on the main chip.

Is this correct?

~R~

On 2025-03-24 11:44:, W4MRP via groups.io wrote:
lite doesn't have a serial port. The other way should work on both and works through a GPIO pin on the audio chipset. They call this "RA Board" or "GPIO3".


FLRIG 2.0.05.93 Rigcontrol with IC-7300

Anders Georgsson
 

I am having problems doing CW Keying from the FLRIG program. When I go to Keyer | CW Keyer and type a message and press Send/Pause, the transmitter doesn't transmit but the software acts as if though it is (marquees the message that I typed).
If I do the same but use the FSK Keyer - it DOES trigger the rig to transmit.. I have the following settings for Xcvr and PTT-Generic:
Can someone help me figure this out? I am hope that fixing this - will carry over to CW working in FLDIGI as well..
Oh - while I'm at it - can you tell me - when you use FLDIGI to transmit/decode CW with the IC-7300, is your radio set to CW or LSB-D/USB-D ?

Thank you!


Re: MacBook OS and Failure to Transmit

 

I've used "real" PTT via digirig on HT with both digirig and digirig lite. Been a while tho.
There are at least two ways to PTT with a digirig. One is via the serial port. This is only with a regular digirig since the lite doesn't have a serial port. The other way should work on both and works through a GPIO pin on the audio chipset. They call this "RA Board" or "GPIO3". I've used this method with VARA FM (Winlink) with Baofengs. Never used VOX on them. It think actually triggering PTT is way more gooder than VOX.
You also see support for it in flrig. I can't remember if you have to use the "CMedia" or "GPIO" PTT method in flrig config. But if you have a full size digirig, you may can just use COM port. Again, It's been a while.
Digirig Lite is a real sweet setup for HTs.


Re: Cannot set Port Audio

 

Can you post the specifics of what you did? Did following Tobias' steps do the trick?
Thanks,
~R~

On 2025-03-23 22:41:, George Stein - NJ3H via groups.io wrote:
Thanks to all. After a few tries I was quick enough to get to the list. I did find a post from a few years ago about editing one of the xml files, but the method in this thread worked.


Re: Cannot set Port Audio

 

Thanks to all. After a few tries I was quick enough to get to the list. I did find a post from a few years ago about editing one of the xml files, but the method in this thread worked.
Of course this brings up the question why were 12 of my 15 VACs ok, but as it turned out 3 weren't. There was no other software that used audio running when this situation happened.
Again thanks,
George


Re: How to log to DXKeeper?

 

Gordon, On Dave's site index page there is a link to 3rd party software, the one you want is FlDigi - DX Labs Gateway.
- which brings you to N2AMG's place - You need the full version and the update.

I'm currently using V1.7.0 (the update) with Win10 and it works perfectly. I set it up to use FlRig as the rig control,
and as I have DXKeeper running all tie time, it connects on the local TCPIP loopback port 52000.
When I log a contact in FLDigi, it logs automatically in DxKeeper with all the info filled in.
Is that what you are looking for?

I can provide screenshots of my setup if you need them.

73, Paul VA3PC

On 2025-03-23 13:17, Gordon LaPoint N1MGO via groups.io wrote:

Can I have fldigi log to DXKeeper, and if so how?

Thanks,

Gordon - n1mgo





--
This email has been checked for viruses by AVG antivirus software.
www.avg.com


Re: How to log to DXKeeper?

 

Try here I have used it for years with no issues.
73, Bob N3PPH


How to log to DXKeeper?

 

Can I have fldigi log to DXKeeper, and if so how?

Thanks,

Gordon - n1mgo


Re: Cannot set Port Audio

 

Your Port Audio playback device is the same as your audio alerts. I would start by disabling audio alerts. Maybe then you can activate Port Audio and fix the playback device.


Re: Cannot set Port Audio

 

If Win 10 is current, is permission given for apps to access the mic? See Privacy.

73 Rich NE1EE
The Dusty Key
On the banks of the Piscataqua


Re: Cannot set Port Audio

 


Hi George,

I am not sure that this will help, but please try the following 2 items.


In your VAC control panel, set the minimum supported sample rate to a really low value, this shouldn't hurt and maybe FLdigi tries to use 8000 or so at least in some cases.

From the very beginning, I have even set it to 2000 (= 0...1000 Hz audio, an unusually low value which I hardly ever use for signal processing), but even this low limit value was accepted and has never caused an issue.


On the other hand, I can also reproduce the error message in certain cases, and then it's just a question of trying to click and select a device you know to work ok, e.g. microphone input, and attemt clicking just fast enough before the error occurs. This is a bit iffy at times, in Windows at least, but my proven 'debug sequence' is as follows:

0. PortAudio is unchecked following an error message.

1. Click to activate PortAudio.

2. Immediately thereafter (!!!) click on the 'Capture' list (if this is the one causing the issue).

3. The 'not available' error message pops up (never mind).

4. Close the error message.

5. If you were fast enough, you should now have the device selection list visible where you can select a working device.

6. PortAudio is still unchecked.

7. Click to activate PortAudio.

8. PortAudio is selected (checked) and fully available again, and so is the device selection list.


I hope this will work for your problem as well. Tested here on fldigi ver4.2.06.19 and Win7.


Good Luck!


73s and Best regards

Tobias
.-.-.
Am Sonntag, 23. März 2025 um 00:54:46 MEZ hat George Stein - NJ3H via groups.io <nj3h@...> Folgendes geschrieben:


Greetings,
I am using the latest version of FLDigi on my Win 10 desktop.
I was trying to select one of my Virtual Audio Cables and I get the message shown on the attached picture.
I have Restarted the computer and the message persists.
How can I clear this error and select the input that I want?
I have attached the screen capture and the VAC Control Panel.
I would appreciate any help with this issue.
Thanks,
George, NJ3H
Redmond, Oregon USA


Re: Cannot set Port Audio

 

I meant to say, that clearing the message leaves Port audio grayed out. except for its radio button. Clicking on it yields the error message once again.


Cannot set Port Audio

 

Greetings,
I am using the latest version of FLDigi on my Win 10 desktop.
I was trying to select one of my Virtual Audio Cables and I get the message shown on the attached picture.
I have Restarted the computer and the message persists.
How can I clear this error and select the input that I want?
I have attached the screen capture and the VAC Control Panel.
I would appreciate any help with this issue.
Thanks,
George, NJ3H
Redmond, Oregon USA


Re: MacBook OS and Failure to Transmit

 

I don't have or use a digirig so I apologize if my earlier comments were misleading. My primary use of fldigi and flrig are for HF data modes where the radio is directly exposed to the software in the OS as a sound card and a serial port.

With a VHF/UHF HT and digirig, how is ptt handled?

When I have done VHF packet radio with a Baofeng HT and a Mobilinkd TNC3, the radio has to be put into Vox mode so it goes into transmit when the Mobilinkd device starts outputting audio.

If the digirig somehow does signal PTT directly (not vox) then presumably the digirig also exposes a serial port for PTT/CAT control, but that is an assumption I would need you to confirm.

I may have mentioned previously that sometimes I do observe fldigi indicating Transmit mode and printing output characters even though the radio never went into TX. I assume this is a breakdown either in the localhost network traffic between fldigi and flrig or a problem with the serial port comms between flrig and the radio. It isn't a rare occurrence and others have confirmed similar behavior, but it isn't reproducible on demand and I haven't spent any time trying to troubleshoot the issue. Usually initiating a 2nd TX does put the radio into TX.

So,

1. Please confirm how the digirig handles PTT. Does it expose a serial port for CAT control and PTT?

2. Verify the serial port settings in flrig. The document you shared was for fldigi and flmsg settings, but if you are using flrig then it is flrig that actually keys the PTT. A screenshot of your flrig transceiver setup might be helpful.

3. With the current OS and config that is not working, does it fail 100% of the time, or can you sometimes get the radio to go into TX? What about if you click the Tune button in fldigi?

I have a MacBook M3 Pro and I have done some transmitting with it, but it isn't my main shack computer and I don't have it up to date. More critically, I don't own a digirig so that's where my ability to troublsehoot is limited.

73,
Daniel (AE4ON)

On Fri, Mar 21, 2025, 2:09 PM Thomas M. Fields WA7CHF via <fieldstom45=[email protected]> wrote:

Hi Daniel,
Thank You for your response, and I apologize for my delayed response. As I stated in my first inquiry, I am somewhat of a novice in setting up my MacBook using Fldigi/Flmsg. When trying to use Fldigi my radio will not transmit. I included a Word document identifying my Fldigi settings for my Macbook Pro in my initial inquiry. I will include that again herein.
With my radio (Kenwood TH-D74) connected to my MacBook and my Digirig, I will try and send a message. The message is processed within the Fldigi software and appears that it is being transmitted. However when I observe the radio, it is not transmitting. I basically have the same settings I had for the Sonoma OS, and prior to upgrading to Sequoia OS, the software and radio operation worked perfectly. Now the radio is not transmitting. It is important to note that when the radio is transmitting you will see a red line come on indicating the radio is in transmit mode. That is not happening now. There is no tones or other audible indicatoin that the radio is actually transmitting.
I think you may be onto something with PTT settings, but I am not sure where or how to make those setting adjustments. The radio is simply not transmitting when Fldigi is showing that a message is being sent. I am not sure what else I can tell you. You can refer to all my current settings for the radio in the file I have included.
Thanks for your help.
Tom


Re: FLrig control for Icom IC-738

 

Taking the CIV plug on a IC 746. I was giving info on how to create a patch cord, the female plugread sleeve and the tip took that data and moved or changed the VFO. I used that radio on Winlink Gateway for a long time. I imagine that the CIV port had the same plug etc in older Icom radios

Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU VOICE


Winlink:va7dgp@...
Subject://wl2k

ALLSTAR 530780
Hamshack Hotline
5971
Mid-Island Phone Mesh
2210
2232



On Fri, Mar 21, 2025 at 4:17 PM Philip Rose via <gm3zza=[email protected]> wrote:
The IC-738 is an IC-736 without the internal PSU. I foolishly bought an IC-736 second-hand but never got it working with CAT software. It's 1990's vintage radio. It does have a CI-V interface, but I never found info about the signal levels involved and never got the interface active.

73 Phil GM3ZZA

From: [email protected] <[email protected]> on behalf of Dave via <w1hkj25=[email protected]>
Sent: 21 March 2025 6:39 PM
To: [email protected] <[email protected]>
Subject: Re: [winfldigi] FLrig control for Icom IC-738
No plans at this time.

On Fri, Mar 21, 2025 at 11:46 AM Dave Garber via <ve3wej=[email protected]> wrote:

If this is an old icom perhaps getting the xml for the 735 would work,but changing the radio code

sent by ve3wej on samsung s21+

On Fri, Mar 21, 2025, 11:55 a.m. Steve Toquinto via <kb6hoh=[email protected]> wrote:
I'm hoping Dave see's this.
Dave do you have any plans to add this radio to the list?
Tnx de Steve KB6HOH


Re: FLrig control for Icom IC-738

 

The IC-738 is an IC-736 without the internal PSU. I foolishly bought an IC-736 second-hand but never got it working with CAT software. It's 1990's vintage radio. It does have a CI-V interface, but I never found info about the signal levels involved and never got the interface active.

73 Phil GM3ZZA


From: [email protected] <[email protected]> on behalf of Dave via groups.io <w1hkj25@...>
Sent: 21 March 2025 6:39 PM
To: [email protected] <[email protected]>
Subject: Re: [winfldigi] FLrig control for Icom IC-738
No plans at this time.

On Fri, Mar 21, 2025 at 11:46 AM Dave Garber via <ve3wej=[email protected]> wrote:

If this is an old icom perhaps getting the xml for the 735 would work,but changing the radio code

sent by ve3wej on samsung s21+

On Fri, Mar 21, 2025, 11:55 a.m. Steve Toquinto via <kb6hoh=[email protected]> wrote:
I'm hoping Dave see's this.
Dave do you have any plans to add this radio to the list?
Tnx de Steve KB6HOH


Re: MacBook OS and Failure to Transmit

 

Tom

I see D74 and Digirig.

I'm assuming that Digirig is plugged into Mic and Speaker port on the radio.

If so Playback on computer is TX (PTT) and Recieve is Mic on the computer. The squelch is off other wisescreen black.

Is this your setup??

73

Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU VOICE


Winlink:va7dgp@...
Subject://wl2k

ALLSTAR 530780
Hamshack Hotline
5971
Mid-Island Phone Mesh
2210
2232


Re: MacBook OS and Failure to Transmit

 

Thanks for the update...
Your comment below ...
I have observed in Windows when either fldigi can't find the audio service OR permission to access the "mic" is turned off, fldigi complains at startup. Not too long ago, it would actually hang, requiring the task manager to kill it. But that bug was fixed...I think in 2024...and now fldigi pops a message saying it can't find the audio device.

You write that the message appears to be sent, according to the fldigi TX pane, so fldigi must think it has a audio device and port to talk to.

That suggests either
the hardware is not handling the radio correctly or
the OS is not talking to the hardware (digirig) correctly.

You have indicated in the past that the digirig handles the radio, IIRC, so that leaves the possibility that the port is not configured correctly in the OS.

These are not definitive statements, but some ideas to kick around. I am not familiar with Mac OS, so no help there...

~R~

On 2025-03-21 16:34:, Dave Garber via groups.io wrote:
On Fri, Mar 21, 2025, 3:09 p.m. Thomas M. Fields WA7CHF via <>groups.io <fieldstom45=<mailto:[email protected]>[email protected]> wrote:
With my radio (Kenwood TH-D74) connected to my MacBook and my Digirig, I will try and send a message.� The message is processed within the Fldigi software and appears that it is being transmitted.