This article describes a trial of javAPRSSrvr on a Raspberry Pi (RPi) as a headless system (ie without integrated screen and keyboard).
Above is the RPi sitting on a TNC-X KISS TNC connected to the TNC’s USB port. In this case, javAPRSSrvr uses the supplied KISS interface, it does not use Linux kernel support for AX.25. Continue reading Headless javAPRSSrvr
I was handed an Alinco DR-135 + T3-135 to troubleshoot. The reported symptoms were that it “never repeated the owner’s Foxtrak based mobile station”.
The T3-135 is an OT3 tracker/TNC built on a card to fit inside the Alinco DR-135 in the place provided for their own EJ-41U TNC. The rear DE9 port provides data access to the T3-135’s A and B serial data channels.
Continue reading Argent Data T3-135 review
This article documents an open squelch data carrier detect (OSDCD) for TNC-2.
The TNC commonly derives Data Carrier Detect (DCD) from its modem chip (often a broadband energy detector is used in modem chips). DCD is used to enable decoding of incoming Receive Data (RD), and to block transmission whilst the channel is busy. Continue reading Open squelch data carrier detect for TNC-2
A few weeks ago I built up a Foxtrak kit, see Foxtrak build.
During testing, I noted that VK2ZEN-5 occasionally corrupts Foxtrak packets, or more generally MIC-E encoded packets. It is a known problem with aprsd which has not been fixed in more than 10 years.
As a result of the fact that one local digi (OT3) never decoded the Foxtrak (DK7IN firmware), I tried aprstracker0.11 and original TinyTrak(1) firmware.
The aprstracker evaluation is described at Review of APRSTRACKER v0.11 firmware, it was unsuitable.
The TinyTrak(1) firmware didn’t work with the OT3 digi either.
The matter of Foxtrak / OT3 interoperatibility is discussed in more detail at:
A TinyTrak3+ was also evaluated, see TinyTrak3 v1.42 review.
Considering quality, price and performance, the Foxtrack works with most digis types but not OT3s, the DK7IN firmware has more feature than the original TinyTrak, but the combination is nowhere near as capable as the TinyTrack3+ which is less than double the price as landed in Australia.
I ordered a TinyTrack3+ (TT3+) from Byonics (US) website, and it arrived in Australia 8 days later by ordinary mail.
The configuration software worked reliably, but some default settings were not appropriate which led to unnecessary work. Continue reading TinyTrak3 v1.42 review
Further tests have been conducted and observations made of normal on-air traffic.
The question that arises is why everything else I have tried except
OT-USB and OT3 devices reliably decodes the Foxtrak (DK7IN, aprstracker 0.11, TT1), and the OT-USB and OT3 devices reliably
decode everthing else I have tried (including TT3+) except the Foxtrak (DK7IN, aprstracker 0.11, TT1). Continue reading Interoperability of FoxTrak tracker and Argent Data’s OT3 – Part 2
One of my simpler projects, just three electronic components and 140 lines of code… an open squelch DCD (OSDCD) for Paccomm Tiny2 Mk2 . Continue reading Open squelch DCD for Paccomm Tiny2 Mk2
Hams often speak of inline RF wattmeters as being ‘averaging’, but are they? Continue reading Are inline RF wattmeters really averaging
FoxDelta supplies a null modem adapter with their FoxTrak tracker. The null modem is used only during configuration.
The adapter is supplied with hex pillars (jack screws) on both DE9 connectors, which prevents the adapter being plugged directly onto the FoxTrak, or onto a PC USB-RS232 adapter with pillars. Continue reading Revision of FoxDelta null modem adapter
I have observed an apparent interoperability problem between FoxTrak tracker and Argent Data’s OT3.
Tests have revealed that two FoxTrak’s are not decoded by two OT3s. Continue reading Interoperability of FoxTrak tracker and Argent Data’s OT3 – Part 1