Got radio cable, Tracker 4 beacons, but...

#1
I've had the Tracker4 for a while, and the cable for the DE-9 to 6 pin Mini-DIN arrived. I hooked it up to my Yaesu FT-857d and the Tracker4 is beaconing.
Interestingly my Kenwood TH-D74a receives the beacon with the status line "APRS-IS for Win32". I can't see where I'd even set that!
Where would I set it?

Also, the digipeater is on, but beaconing from the Kenwood doesn't result in it "being heard", nor, therefore digipeating.
cmd:show digi_mycall
digi_mycall=true

cmd:show rx1_level
rx1_level=1000

That status line shows
Ch 1:99 ######## TX [ ] RX [*] D [ ] Ch 2:00 -------- TX [ ] RX [ ] D []

The Yaesu FT-857d is certainly hearing the packets.

Ideas?

Thanks! KH6CP
 
#3
I understand about being a "one man show". It's difficult. Yeah, I'd rather be coding, too!
In any case, when I used a Yaesu FT-2DR to watch the beacons the status line came up empty. So the Kenwood
probably chose what it had last heard from the call sign as its status.

We know beaconing is working, so the connections for the audio out to the "1200 baud data in" is proper.
I took a VOM to the pins on each connector and find:

DE-9 male pin Mini-DIn 6 male pin
1 2
2 6
3 3
4
5 4
6 2
7
8
9

The male Mini-DIN 6 pin-out I find on the web doesn't match the pin-outs above, but does make some sense
for the female Mini-DIN 6 pin-out.
Hmmmm....
 
#4
I just received a cable and connected my Yaesu FT 991a - like you, I could beacon out but can't receive anything. I fiddled with a number of the obvious control settings on the radio but haven't found the right combination yet...please let me know if you have.
 

Ian ZL1VFO

Moderator
Staff member
#5
Might this webpage help?
http://www.wa8lmf.net/6-Pin-MiniDin-Data-Connector/index.htm
The audio (Rx) from the radio to the opentracker should be on DE-9 pin 5
The audio (Tx) going back to the radio should come from DE-9 pin 1
and the PTT line should be coming from DE-9 pin 3
Ground is on DE-9 pin 6, and don't worry about any of the others.
I suspect identifying which mini-DIN pin is which might be the problem, so hopefully the positions indicated in the link above might help fix that.
73,
Ian ZL1VFO
 
#6
Thanks Ian - at least in my case, I purchased the cable from Argentdata - so I hope it is correct. As I said, transmit works fine - I can beacon - but receive doesn't.

73,

dan KG5SCN
 

Scott Miller

Administrator
Staff member
#7
Hi all,

Pardon the duplication, but I'm going to try to hit every open thread.

Please consider this forum to be strictly peer-to-peer discussion for now. For anything that needs an official response, please contact support@argentdata.com. We're tracking all tickets through Zendesk there. I won't guarantee that everything will get handled immediately, but we can at least see and keep track of it all.

There are just two of us working on the radio side of things for now and that's not likely to change while Covid is still a thing. We've at least reached something like a steady state, even if it's still exhausting. Macrofab in Texas is now handling some of our assembly so that's taken some load off, but the holiday season is likely to have us scrambling again.

For any software issues, try the 'update' command first if that's working for you. If it's not or if it's not connected to the internet, you can grab the latest files (as of 11/19/2020) here:

https://www.dropbox.com/s/suawyisd15cywy6/t4.bin?dl=0
https://www.dropbox.com/s/d3dl2zsofaav4wz/t4-wgm.bin?dl=0

Copy them both to the tracker. From the console, run:

Code:
wifi load t4-wgm.bin
loadfw t4.bin
If whatever problem you're having persists, please email support@argentdata.com. I'll try to check back here as time permits.

73,

Scott
N1VG