So I came across this gem whilst watching a youtube video. I promptly ordered one and set it up yesterday after much head banging due to not finding a clear cut tutorial on how to run it on android exclusively. I am able to tune my HT to the frequency of the closest node but am unable to send emails over winlink via packet. In the session info section, I have the status indicates that it is Running but I also have an extended status of “unconnected” I am new to digital modes and this is the first one I have bothered with attempting to learn. I have reached out to the most active clubs in my region and have yet to have someone reply and spent several hours yesterday trying to help myself by watching videos and attempting to troubleshoot. Is it possible that even though the closest packet server is too far away and the unconnected message is showing because I simply do not have enough power to reach it? Hardware is as follows: Phone: Google Pixel 6, HT: Anytone 878+, Interface: Digirig Lite with Baofeng adapter, antenna: Nagoya 24J. Thanks and 73
Yes, you might not be able to reach it. Do you have a monitor radio available to listen to the exchange? Do you have the ability to get an antenna higher up and away from the handset?
There are other posts here about WoAD:
Latest software-woad topics - Digirig Forum
73 Constrainted
lot of ‘things’ going on for this project.
as stated, there are quite a few discussions here about winlink email via WoAD so hopefully you’ll find enough bits to make a byte.
the running notice means woad is sending connection requests.
i don’t remember offhand how many attempts is the default but 10 retries is normal for the winlink express (the official windows program for winlink)
woad will send a connection packet (very short burst of noise) then wait. then retry, then wait, etc until retries are exhausted or connection is made.
so, unconnected will show during this time.
as far as connection possibility, i have a 3 element yagi at 60’ and 70 miles is pushing it for most packet nodes.
most winlink gateway owners in my area are like me, self funded.
so 200’ towers with commercial antennae are not common like you find on ham club voice repeaters.
so coverage is much smaller due to equipment used PLUS the fact that vhf+ packet/digital modes DO NOT perform like the digital modes used on hf sideband.
next, your packet audio is generated by woad and fed to the digirig, which then feeds into your radio.
at each step, too much or too little audio reduces your chance of being decoded on the other end.
as suggested, another radio to simply listen in on your attempts could help you get the audio ‘just right’.
to start, while sending those connection attempts, manipulate the volume control on your android device.
for me, 2/3 scale is about right. right at the point android warns about high volume with headsets.
good luck
kb0wlf
Thank you for taking the time to respond. 
I have a roll up ladder line that I am going to try next and I do have a backup HT I can use to monitor. If that fails, I will attempt to get closer to the node I am targeting and will also use an amp though I would rather play around with the antenna and its config and check my connections as that is what one of my Elmer’s taught me. I will try those suggestions.
Thank you for taking the time to respond. I have heard that initial audio burst you mentioned. I was not sure of what that was and I do remember seeing something in the individual session settings about retries and time between retries. I do also remember the audio levels on each component from the more useful explanatory videos I watched yesterday on YT. Most of the videos I could find centered around the mobilnkd and some bluetooth pieces of kit. I appreciate your insight and I will continue tinkering with it until I am successful. Thank you again for taking the time to share your insight.
gotcha.
the mobilinkd is a great bit of kit.
i have/use one also.
it is an actual TNC rather than a soundcard like the digirig.
so the mobilinkd does all the ‘heavy lifting’ for a packet connection and simply communicates with a program via serial data (comport via bluetooth for mobilinkd)
now, packet, using any method, has a txd or tx delay setting.
this is the time that your station will ‘key up’ BEFORE the data payload is sent.
if you can hear the nearest gateway but can’t connect, try raising the txd to 50 or 500 depending on what the program asks for.
(note what value is there an just change the first digit. 20 becomes 50 or 200 becomes 500)
this will ‘get the attention’ of the receiving radio before actual data is sent.
if you do get connects, then back this value down until you don’t, then go up ‘1’.
last thing to consider;
i don’t have your radio but one of the important things for packet or any winlink ‘mode’ is tx/rx ‘turn around time’ or ptt switching time.
this is also true for APRS operation, which is also packet (the most used anyway)
how long does it take from releasing the ptt button before the radio is ready to receive.
many slow switching radios are still holding ptt when the remote radio is sending a reply. resulting in no connection.
again, good luck.
kb0wlf