Unable to Connect Using DigiRig or AIOC

77 views
Skip to first unread message

Mark

unread,
Jun 22, 2026, 6:36:32 PMJun 22
to WoAD Support
I have reviewed the configuration for each device, yet I am unable to make a connection. I heat the initial transmission from the radio go out (using a second radio to monitor the freq.) but then the transmission ends with no connection or handshake. I am able to make a connection with both DigiRig and AIOC via my Windows device with Vara FM and Packet.
I realize it is likely my settings, but I cannot seem to get it to connect.
Any help would be appreciated.

Mark
KJ5JYX

(Upload-from-mobile-1782163862)1000019366.jpg(Upload-from-mobile-1782164906)1000019367.jpg
(Upload-from-mobile-1782165107)1000019364.jpg(Upload-from-mobile-1782165227)1000019365.jpg

WoAD Support

unread,
Jun 22, 2026, 7:57:58 PMJun 22
to WoAD Support
Hi Mark,

If you can hear the outgoing packet on a second radio then presumably the PTT is working. The most likely problem is the volume, which you have set to 75, based on the images you included.
I would try playing around with that - likely to a lower setting. This will depend on the radio you're using, any mic gain settings on that radio, etc.

The other suggestion I would have made would be to increase the Tx delay under TNC settings, but it looks as if you have already increased that to 500ms. This can help address problems in a slow response from the PTT command.

It shouldn't really matter but it looks as if you have enabled the option for PTT using "PTT tone". Everything should still work if you switch that off, as presumably the AIOC is using DTR for PTT control, and the digirig is using RTS.

Hope that help,s

Andrew
VA7YAA 

WoAD Support

unread,
Jun 22, 2026, 9:08:50 PMJun 22
to WoAD Support
And also ensure you have any and all sound enhancements switched off on the Android device. These might be things like Dolby Atmos, equalizer settings, 3rd party audio enhancements apps, etc.

Mark

unread,
Jun 22, 2026, 11:37:27 PMJun 22
to WoAD Support
Thank you for your reply. I will check on the items you mentioned.



73
Mark
KJ5JYX

--
You received this message because you are subscribed to the Google Groups "WoAD Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to woad-support...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/woad-support/6cb90292-eae8-4af9-b757-ad9b3f3cc137n%40googlegroups.com.

Mark

unread,
Jul 6, 2026, 12:21:32 PMJul 6
to WoAD Support
I really like the concept, to be able to access Winlink via RF without taking my Surface Pro with me; however, at this point I will be giving up as I can not seem to get WoAD to connect.

I was trying to locate someone near by that is using it so I could see any errors on my part. 

If you have any updates or hear of an obscure  setting that may help, please let me know.

73
Mark
KJ5JYX

Mark

unread,
Jul 9, 2026, 7:27:17 PM (11 days ago) Jul 9
to WoAD Support
I was able to get it to work with assistance from KB7ITU. I have connected consistently the last couple days.

Since was able to get this working, I thought I would try my Samsung tablet. However, when trying to connect, I keep getting a 'RTS disable exemption' error.
Have attached my log.

Thanks,

Mark

WoAD_log_2026-07-09 20-52-50.txt

WoAD Support

unread,
Jul 9, 2026, 8:01:45 PM (11 days ago) Jul 9
to WoAD Support
Good to hear that things are working. It would be much appreciated if you could share what the problem was in the group so that others with a similar problem will hopefully find the solution without the same level of effort.

The "USB enable: exception" and "USB disable: exception" messages result from an exception thrown by the USB serial driver, either because the selected driver doesn't support DTR, or the command failed. Given that things are working on your first device I would first check the settings for any differences between the PTT configurations on the two devices. For the next release of WoAD will also give the underlying exception message, which may help in tracking down problems.

Not sure I have anything else useful to add as if things are working on one device they should be working on the other, assuming you have similar versions of WoAD and Android.

All the best,

Andrew
VA7YAA

Don VA7QU Poaps

unread,
Jul 9, 2026, 8:13:29 PM (11 days ago) Jul 9
to WoAD Support
I have a Samsung Tablet Active5. I been trying to get Woad running with VGC N7600. The Packet is being sent by Bluetooth. I'm wondering if the Mobilink dongle would use the same settings. 

73

Don



Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE



Winlink: va7...@winlink.org
Subject://wl2k          

ALLSTAR  530780
HOIP          104292



                   


--
You received this message because you are subscribed to the Google Groups "WoAD Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to woad-support...@googlegroups.com.

Mark

unread,
Jul 10, 2026, 12:32:50 AM (11 days ago) Jul 10
to WoAD Support
So how I was able to connect was to change some configure settings below, reducing my ht volume and setting the packet volume to 74.

My Tab 7 (getting the errors) is running Android v 14, my phone (S22 Ultra, Android v. 16. Since I am using DigiRig I have the PTT setting for RTS, not DTR. If that makes any difference.

73
Mark
KJ5JYX

--

WoAD Support

unread,
Jul 10, 2026, 1:01:40 PM (10 days ago) Jul 10
to WoAD Support
First you want to check that you have the Digirig mobile (and not the Digirig lite). The former uses RTS, while the latter uses GPIO. Assuming that is all good, then the only suggestion that comes to mind would be to re-select the USB port associated with the "PTT USB RTS". And ensure all the other PTT choices are unchecked.

Hope that helps,

Andrew
VA7YAA

Mark

unread,
Jul 14, 2026, 1:55:23 PM (6 days ago) Jul 14
to WoAD Support
Thanks.
It is a DigiRig Mobile, I usr the RTS with the DIgiRig on the USB port, all other options for the PTT are unchecked.
I have updated the app. i am still getting the  'RTS disable: exception: Control transfer failed: 7 / 512 -> -1' After the update it provides a little more information. I have not had any other USB errors before. but I have never used it for this level of communications either.

Any help is appreciated.

Mark
KJ5JYX
Reply all
Reply to author
Forward
0 new messages