Tuesday, 10 December 2024

KD0TLS: Using the Microsat TNC with an APRS client

  As I previously mentioned, I recently bought a Microsat WX3in1 Plus 2.0 TNC, and I love it. I'm writing a separate post about the device itself, but I thought it would be useful to discuss how to use it with an actual APRS client. 

 The Microsat TNC (which is how I will refer to it, rather than the unwieldy "WX3in1 Plus 2.0" name) is self-contained. It needs no additional APRS client to gate packets, operate as a digipeater, send bulletins, announcements, and objects at regular intervals, or transmit beacon and STATUS messages. You just configure it, and let it run. 

 And that's great, but it has no display and no way to interact with the device beyond configuration. Unlike an actual client (APRSDroid, YAAC, APRSIS32, UI-View, etc.), you can't see the actual traffic passing through your station. You also can't send (or read) messages, or see the activity displayed on a map. Instead, the Microsat TNC has lights that flicker to indicate what it's doing: receiving/transmitting packets, accessing the -IS servers, or judging a received packet to be properly formatted. 

 Even if you want to use the Microsat TNC as a tracker in your vehicle, you would probably want it to connect your phone/tablet to use the GPS on the phone/tablet and be notified of messages. If you are using it as remote digipeater, you probably wouldn't care if it has GPS and you wouldn't be around to watch a display. If you are using it as a home gateway/digipeater, as I do, then you might find it useful to connect this TNC to a client. 

 How to connect 

 The easiest way is to buy the Bluetooth module from Microsat. Pretty much everything has BT these days, but iOS (Apple) devices need special BLE connections -- and the Microsat BT module won't do that. Windows, Android, and Linux will all work, though.  

 Pairing is unusually tricky, however, regardless of the OS used. This normally simple effort requires a PIN code to pair. That PIN is non-standard, and is found on the label of the Microsat BT module cable where it connects to the TNC. Entering that special four-digit number is the key to making the whole thing work.

 If you have an Android phone/tablet running APRSDroid, you just pair the BT module (BT/MICROSAT_0052) and select that as the device under Connection Preferences (TNC KISS, Bluetooth SPP) and then under TNC Bluetooth Device. Be aware that whatever SSID you had configured before will become the new SSID of the Microsat device. Things like comment text, frequency, icon will simply be added on to whatever you configured the Microsat TNC for originally. You may want to create a specific profile (three dots under APRSDroid Preferences) that you can load when you are using the Microsat TNC, as opposed to your normal operation. Set everything up using the SSID you configured the Microsat TNC for, including the icon. 

 Windows (e.g. APRSIS32 or UI-View) is similar. For APRSIS32, you will need to create a new port (Configure Ports/New Port) and choose KISS -- NOT "SimplyKISS". Select the paired device from the drop-down. Again, whatever icon and beacon text (etc.) you had before will be added on to the Microsat TNC settings. 

 The best advice I can offer is to remove all previous SSID/beacons/icons/STATUS text etc. and use whatever is on the Microsat TNC. 

 The result 

 Once the client (phone, laptop, tablet, etc.) is set up properly, you will see whatever packets are being heard by the Microsat TNC. The client will map the received stations, show the raw packet data, and any received messages. 

 You can use the client to create and maintain bulletins, announcements, and objects -- though APRSDroid will not maintain any of this. It will send it once, and objects are probably too tricky to send using APRSDroid. Fortunately, there's a nice work-around to send objects at regular intervals using the Microsat TNC, instead. 

 Any of these options will allow you to send messages, and participate in things like #APRSTHURSDAY using the Microsat TNC. 

 If you want to add a special STATUS text (e.g. Happy Holidays, Go Vikes!, Blizzard coming, TX down etc.) you can use the client to add this on top of your regular beacon activity. 

 Summary 

  If you order the Microsat TNC, you should probably order the cabling and BT module at the same time to save on shipping. Shipping from Poland is about two weeks. HRO has the TNC, but only limited cable options and no BT module.

 If you can't find the proper cabling for your rig, check out hammadeparts.com. I did this to get the cable between my Leixen VV-898 and the Microsat TNC. 

 The Microsat TNC is a great option, and it will do its thing without any client 24/7 on a rock-solid basis. The BT module allows you to connect to it for messaging, nets, and EmComm. 

No comments:

Post a Comment