WoAD - Mobilinkd - Winlink string issue?

[David Hepner]

Hello all, looking for some help. With my Mobilinkd TNC version 1, the radio transmits and packets are sent, but It will not bring up my local winlink node. Same radio works with my pc. 

The only difference I notice is the packets sent to connect to the node.  The characters at the end of the string are different. I assume this is the issue, however I don't know how to correct it to make WoAD work. 

Packets from pc read - 

1:Fm KB3HWM To K3ARS-10 <SABM C P> [19:19:42T]

 Vs Packets from Mobilinkd -

1:Fm KB3HWM To K3ARS-10 <SABM C P> [19:31:26R] [+++]

73

Dave

[Andrew Walker]

Hi Dave,

The packets look the same to me. Are you monitoring the traffic with soundmodem? The first value in the square brackets is a timestamp, which is being added by your monitoring program as the AX.25 packet doesn't have an associated timestamp. I'm not sure what the difference is between the T (first packet) and R (second packet) at the end of the timestamp. Similarly with the [+++], absent in the first packet but present in the second. I did a bit of googling but was no further enlightened. Perhaps someone with more knowledge of soundmodem could provide a better answer.

It might be worth checking the various TNC settings on both devices and check for any differences (such as Tx delay, Tx tail, etc).

It might be useful to send the WoAD log file to help further debug the problem.

All the best,

Andrew

VA7YAA 

--
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/3a49eff8-3f3a-48f3-bd52-c83a7bcbbf0cn%40googlegroups.com.

[David Hepner]

The big thing I noticed about the T & R at the end of the string along with the [+++], is when I make the connection via my pc and sound modem, the return from the node has them at the end. With the WoAD string sending that to the node to connect, I'm curious if it has something to do with the initializing command to connect to the node vs the return, which would explain why it doesn't bring up the node. Ill attach the Woad Log. I couldn't find anything via google either.

Thanks 73

Dave

[Andrew Walker]

Naively one could guess that T=Transmit and R=Receive with the [+++] an indication of the incoming signal quality.

Am I right in thinking that on the pc you're using Winlink and soundmodem?

When you're running on WoAD and mobilinkd are you using soundmodem simply to monitor the over-the-air traffic, which would imply you have a second radio?

 

If so the soundmodem log would make sense as in the first scenario (pc) the SABM packet is being transmitted, while in the second (WoAD) it is being received.

Of course that doesn't help work out why the remote node isn't responding to WoAD + mobilinkd.

At this point its really a fishing expedition. Some things to investigate would be:

* mobilinkd settings

* does a peer-to-peer session work

* can you hear the outgoing and incoming packets and they are just not being processed

* etc.

Hope that helps,

Andrew

VA7YAA

[David Hepner]

Yes, you are correct, I am running winlink + soundmodem for the PC. Those were my exact assumptions of what the packets meant. 

My end goal is to be able to use the mobilinkd and my Anytone HT for portable winlink. I have used the same radio that I used soundmodem with the mobilinkd with no success also. I have confirmed that the packets are going out when both radios are used with the mobilinkd. 

I have not tried p2p, I need to find someone close enough to try it, or use an ssid and connect to myself. 

The only thing that still sticks in my mind is the possibility that that command string is like you said sending a reply vs a transmit message. I have read in other discussions on this forum that the Mobilinkd 3 does better with winlink. maybe there is something updated that will work better with that. Just a shame they are not available at the moment.

Thanks for helping attempt to diagnose this by the way! 

Dave