WoAD with digirig

[Kyle]

Hi all!

Having some trouble getting WoAD  1.4.73 running with digirig.

In WoAD I am able to get the the radio to xmit using the "digirig" session I created, yet my outbox has messages remaining after the xmit event. I was successful in getting messages sent from outbox with a Telnet session.

What I am seeing in the WoAD logging is:

node I’m trying to reach < my call [last] C|R=Command U_SetAsyncBalanceMode P=1

Also that I am start/stop the "digirig" session that I created. That's it!

I’m new to WinLink but shouldn’t there be some kind of syn/ack that takes place?

In reading through some threads here, I found a snip of some else log and it looks like there should be at least a response.

Packet,2022-11-02 23:42:36Z,"KE6RLG-0 < AJ7C-10 [last] C|R=Command S_ReceiveReady N(R)=0 P=1","digirig" Packet,2022-11-02 23:42:27Z,"AJ7C-10 < KE6RLG-0 [last] C|R=Command U_SetAsyncBalancedMode P=1","digirig"

I also notice my log entry doesn't reference the session name at the end, like it does in the snip I found.

Other questions I have...

After reading through the WoAD manual it shows there should be a *Debug* option in logging to turn on. I don't seem to have this option. Has it been deprecated and is now enabled by default? I have enabled all other logging options.

When exporting the log, where does it go? Trying to search through the file structure from / and haven't been able to find it yet. Admittedly my *nix foo is pretty weak.

Besides logs what else would be useful to gain assistance?

TIA. Kyle

[Kyle]

Answered one of my own questions here. I guess I was not exporting the log correctly, because now when I export the log it tells me exactly where it is saving it.

/data/user/0/com.sumusltd.woad.files/*.txt

Hooray! One down.

[Andrew Walker]

Hi Kyle,

A lot of questions there so feel free to follow up if I miss anything.

The initial exchange consists of a  U_SetAsyncBalancedMode (SABM) packet being sent, the correct response to which is a U_UnnumberedAcknowledge (UA) packet. If you're not seeing the UA packet then the first step in debugging would probably be to listen in with a second radio on the relevant frequencies and check that you can hear the packets being transmitted from your radio and if there is any response from the node.

Also, be sure to check the settings for Session -> Settings -> TNC configuration -> Channel. The digirig expects this to be set to "Right" whereas the default is "Left" (or possibly vice versa).

The manual shouldn't reference the Debug option, as that was never exposed.

All the best,

Andrew

VA7YAA

[Kyle]

Thanks for the feedback Andrew.

I've spent a bit more time troubleshooting this. I kind of provided a bum steer with the above info.

The only reason I was getting any PTT at all was because my radio was still set to VOX from using another android app (APRSdroid). So when turning off VOX I get no PTT.

My phone is a Pixel 6a XL. I am using the included Pixel USB-C to USB-C cable into a Digirig. The phone sees the Digirig when I plug it in and asks what program I want to use it with. In WoAD, it sees the Digirig as Silicone Labs:CP2102N USB to UART Bridge Controller [/dev/bus/usb/002/004]. Regardless of my settings in WoAD I cant get it to transmit.

When I plug the Digirig into a windows machine I can get it to xmit with RTS via the UZ7HO Soundmodem application, so I think that the Digirig device is working OK.

Any additional thoughts on troubleshooting I can do here? I'm really at a loss here as to why I can't trigger PTT.

TIA,

Kyle

[Andrew Walker]

Hi Kyle,

If you send the exported settings for your digirig session I can take a look.

I'm assuming you have the PTT set to USB RTS.

All the best,

Andrew

[Kyle]

Hi Andrew, 

Thanks a lot for taking a look at this!

I am using the PTT USB RTS option.

When plugging in the Digirig and Android detects it, I am choosing "WoAD" and the “Just once” option.

Here is the session I am trying to use.

[Andrew Walker]

Hi Kyle,

I tracked this down to a bug in the code as a result of a last minute change I made. I should have a fix out in a day or two. Many thanks for sticking with this.

All the best,

Andrew

[Kyle]

Oh wow. That's great news, Andrew!

Thanks for your work looking into this issue. I'll standby for the update. 

Kyle

[Kyle]

Success! I installed build 1.4.74 and the Digirig is now keying the radio as expected.

Thanks again for taking a look at this Andrew and resolving the issue. I'm very happy to have this up and running now.

Kyle

[Frank Seigler]

I am glad Kyle got this to work but the update has not worked for me.  I am using the same settings that Kyle posted and I was having the exact same results as Kyle.  Now with the update, I can get it to key the radio but it won't unkey,it just keeps transmitting.  I devoted hours to trying to get Woad to work with the digirig mobile and I just can't get it working.  My Mobilinkd works great with Woad but the digirig is another story.

[Sean AI7EQ]

Would you be willing to post your latest settings in WoAD for packet radio via the DigiRig? I'm having a heck of a time getting it to work. My station consists of a FT-5D connected to the DigiRig via their cable and then connected to my Pixel 4a5g phone via a USB C. I have it transmitting a packet signal (verified on a second radio) but I don't get a response from the RMS gateway direct or via a digipeater. If I unplug my phone and plug into my laptop, Winlink Express has no problem making the packet connection.

Any help would be greatly appreciated!

73, Sean, AI7EQ

[Kyle]

Sure! Attached are screen captures and the export of my session settings.

The settings I am currently using are taken from a posting in the Digirig forum by Dan. 

https://forum.digirig.net/t/digirig-support-in-woad/194

I found more consistent/reliable results using these settings vs stock for sending traffic through my local node. 

Have you looked at the WoAD logging at all to see what's going on?

[Kyle]

The session export didn't attach correctly in previous message. Here it is.

[Sean AI7EQ]

Thank you Kyle!!! I got my setup working this evening. Was able to connect to an RMS gateway via a local digipeater and send/receive messages. Much appreciated!

[Andrew Walker]

The following is from the digirig website (https://digirig.net/troubleshooting-digital-modes/), which may help with the problem of the radio refusing to unkey at the end of a transmission:

====

Sticky transmission, Errors on Transmission

If your radio starts transmitting as expected, but then doesn’t return to receive at the end of the TX timeframe or if you get errors during the transmission, but never while receiving then the issue is likely to do with the RF in the shack disrupting Digirig’s communication. The only way to get things back in order is to re-plug the interface and restart the software. Here are few of the methods to diagnose and resolve this issue:

1. reduce the power to a minimum value and/or use a dummy load – if the issue goes away then it is definitely related to the stray RF in the shack
2. lower SWR – tuned antenna is desirable for many reasons, if possible this would be the best solution for eliminating the RF reflected back to the shack
3. use choke balun at the antenna’s feed point – this will block the reflected RF from traveling back to shack even if the antenna is not in perfect tune
4. use ferrite beads on the cables – this will cut the RF from affecting the interface. This could be the only workable solution while using Digirig with HTs which due to the lack of grounding use anything that is connected to their chassis (including the operator btw) as their antenna’s counterpoise.

[Ronny Julian]

That's alot of tech speak for we did not shield the product well and/or we used cheap components.  Don't buy one of these cheap made interfaces. 

--
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 on the web visit https://groups.google.com/d/msgid/woad-support/e3cbc75f-d5e4-495b-9e81-73d46d9c6932n%40googlegroups.com.

[Randy]

I do not believe that is a fair assessment of the Digirig.

I've had one for about a year now and have had minimal issues.  I've used it in my truck with my IC-706MKIIG on HF and most recently with my TH-D74 HT in a portable mode.  I've experienced one occasion of possible RF causing "sticky" transmission in the truck, and have not been able to replicate it since.  RF happens.

(note: this was with a Windows 10 laptop. Next step is to get everything working with WoAD.  It hasn't been a priority since my preferred Winlink mode is VARA. I've primarily used WoAD for VHF Packet Winlink using the TNCs built into my Kenwood radios)

I've been very happy with the DigiRig, the support from the manufacturer, and especially the price performance point compared to a SignaLink.

I have a SignaLink in the shack and it performs well, but a full up DigiRig with cables costs about 1/2 what a basic Signalink runs, and then you have to buy cables.  For mobile use I prefer the simplicity, space saving, and lower monetary risk of having to replace it, of the DigiRig.

No connection to the company except that of a satisfied customer.  IMHO YMMV

73

Randy KA0AZS

On 2/16/2023 16:09, Ronny Julian wrote:

That's alot of tech speak for we did not shield the product well and/or we used cheap components.  Don't buy one of these cheap made interfaces. 

On Thu, Feb 16, 2023 at 2:24 PM Andrew Walker <va7...@gmail.com> wrote:

The following is from the digirig website (https://digirig.net/troubleshooting-digital-modes/), which may help with the problem of the radio refusing to unkey at the end of a transmission:

====

Sticky transmission, Errors on Transmission

If your radio starts transmitting as expected, but then doesn’t return to receive at the end of the TX timeframe or if you get errors during the transmission, but never while receiving then the issue is likely to do with the RF in the shack disrupting Digirig’s communication. The only way to get things back in order is to re-plug the interface and restart the software. Here are few of the methods to diagnose and resolve this issue:

1. reduce the power to a minimum value and/or use a dummy load – if the issue goes away then it is definitely related to the stray RF in the shack
2. lower SWR – tuned antenna is desirable for many reasons, if possible this would be the best solution for eliminating the RF reflected back to the shack
3. use choke balun at the antenna’s feed point – this will block the reflected RF from traveling back to shack even if the antenna is not in perfect tune
4. use ferrite beads on the cables – this will cut the RF from affecting the interface. This could be the only workable solution while using Digirig with HTs which due to the lack of grounding use anything that is connected to their chassis (including the operator btw) as their antenna’s counterpoise.

Virus-free.www.avast.com