When I connected to my Mobilink TNC3 via bluetooth, I had an issue wherein /dev/rfcomm0 could not be opened. The YAAC application threw a 'permission denied' error. I am running Linux Mint v21.2 on a fresh install on an old HP Elitebook laptop. The problem was that my user was not a member of the 'dialout' group. I added my user to the 'dialout' group then rebooted the PC. I am able to move on from this point. I found a similar error for people trying to open serial ports going back more than 10 years ago. Hope this helps someone else!
Great video, Jason. I've been participating in "APRS Thursday", run by KC8OWL, but do not have any local APRS infrastructure in my area, so I deployed an RF-only fill-in at the house. I opted not to deploy an IGate just to challenge myself. My setup is using a directional antenna (Arrow II Yagi) at 15' pointed at Phoenix (20 miles south); a 5 watt HT connected via the DigiRig mobile, and Dire Wolf. This solution is nice as I can walk around the house and the surrounding area with my VX-8DR using this fill-in. Keep up the good work and thanks for putting this out there. FYI: YAAC is my go-to APRS application.
One note - if you don't need the GUI of YAAC - APRSd is a simple command line digipeater/igate software that works really well - as I remember it, the Mobilinkd is a simple KISS TNC, so APRSd can support it directly, or also by means of the Linux AX.25 networking stack. I used to run a fill-in digi/i-gate here locally with an old Pi-1B, a TNC-Pi, and APRSd.
Which do you prefer? This digipeater using a mobilinkd TNC or the one in your other video with a Pi Zero 2W where you use direwolf as your TNC? I want to tinker with one of these, haven't decided which route to go and if either has an advantage over the other. Which would be easier to also implement as an i-gate??? Love your educational videos.
Love your videos! now you gave me a reason to use my Mobilinkd 3 again. If you ever get a chance it would be awesome if you could show us in another video how to create a crontab -e script to use with the Raspberry Pi so the Bluetooth connection and Yaac start automatically. I just followed this video and got it to work perfectly fine on my Raspberry Pi3 still running Bullseye with external GPS and your Build-A-Pi app installed.
It's not simple to start the TNC connection but it can be done. You can see how I did it in this script github.com/km4ack/patmenu2/blob/master/mobilink Personally, I would write a script to do the work and then call the script from crontab at boot.
Would you mind sharing the clock widget/application you have on your desktop? Waiting for my digirig and TNC 4 to come in the mail, but I have been working on setting up Winlink. The time zone widget seems super useful.
Jason: Although you had me at APRS Digipeater, I was wondering if the same concepts apply to DigiRig, as I looked on mobilink's site, and Amazon, and was unable to locate a mobilinkd 3 device, looks like they are going with the V4 device going forward. I do have a DigiRig 1.9 thatt I've successfully set up with Direwolf, on a Baofeng HT but am always looking for other ways to go...
Correct. V4 is the only Mobilinkd available now. I have one and it works great. The only difference will be the rfcomm command shown in the video where I point out the differences.
Let's just say I won't be going back to the Pi for a field computer :-) I still love the Pi for single use application though. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-cj5xFwTXbbU.html
I can't get my maps to come up on YAAC program, what could I be missing ? I had it come up when was in Ohio but now that I'm back in Florida no maps. and I live in Florida. BTW I'm running the Linux Mint
I am getting "Can't connect RFCOMM socket: Connection timed out" when attempting to connect rfcomm0 with my Mobilink MAC address. When you first execute the connect command a "TNC3 Mibillinkd Connected" message flashes on the screen, but a few moments later this time out message appears in the terminal.
What is strange is that I can successfully connect to the TNC3 via the Bluetooth manager GUI, and set it up as a serial device that YAAC can use. I cannot do this within terminal.
@@KM4ACK I am in the dialup group, as confirmed when attempting to re-add. However, terminal access to connect to rfcomm0 fails, while doing so in the Bluetooth Manager works. Strange indeed.
