开云体育

Hi all,

I have an APRS Voyager and a TH-D74 and I would like to connect their internal Bluetooth TNCS to YACC.
I have managed to pair my APRS Voyager to Linux OK but I can find how to make YAAC see this modem! Which port do I use in settings?
Any idea on how to go on about it?
I use LinuXmint 20.3 Una

73 de Demetre M0SUY

You should be able to bind the Bluetooth serial ports (SPP protocol) to your Linux laptop. The devices should then appear as /dev/rfcommN files which the YAAC Serial_TNC port driver should be able to open. Note that you will need to put the APRS Voyager in KISS mode to work with YAAC.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Demetre - M0SUY/SV1UY <demetre.sv1uy@...>
Sent: Thursday, September 29, 2022 5:02 PM
To: [email protected]
Subject: [yaac-users] Bluetooth TNC support?

Hi all,

I have an APRS Voyager and a TH-D74 and I would like to connect their internal Bluetooth TNCS to YACC.
I have managed to pair my APRS Voyager to Linux OK but I can find how to make YAAC see this modem! Which port do I use in settings?
Any idea on how to go on about it?
I use LinuXmint 20.3 Una

73 de Demetre M0SUY

Hi Andrew,

Thanks for quick reply OM.

Unfortunatelly Linuxmint cannot see any /dev/rfcomm0 or rfcomm1 or any other rfcomm devices because they are not created in /dev/ directory.
I have paired my APRS Voyager succesfully as far as I can see. Do I need a plugin of some sort?

73 de Demetre M0SUY

Did you bind your Bluetooth devices to your computer? Until you do that, the /dev/rfcomm devices won't appear.

Andrew, KA2DDO

________________________________________
From: [email protected] <[email protected]> on behalf of Demetre - M0SUY/SV1UY <demetre.sv1uy@...>
Sent: Thursday, September 29, 2022 5:33 PM
To: [email protected]
Subject: Re: [yaac-users] Bluetooth TNC support?

Hi Andrew,

Thanks for quick reply OM.

Unfortunatelly Linuxmint cannot see any /dev/rfcomm0 or rfcomm1 or any other rfcomm devices because they are not created in /dev/ directory.
I have paired my APRS Voyager succesfully as far as I can see. Do I need a plugin of some sort?

73 de Demetre M0SUY

Hi Anrew,

I have paired my device(s) to my computer but I still can't see any rfcomm devices in /dev directory. I will try them both again today and see what happens!

BTW the same devices work flawlessly in my Windows 10 computers when I use APRSIS32 and they are recognised as Bluetooth devices not as Serial Devices by the OS.
So I can fo APRS using APRSIS32 just fine.

YACC on the other hand expects to see a COMport and each one of these devices create 2 COMports in Windows 10. No matter which one of the two I try to use, YACC cannot see this COMport.

73 de M0SUY

On Fri, Sep 30, 2022 at 03:50 AM, Demetre - M0SUY/SV1UY wrote:

Hi Anrew,

I have paired my device(s) to my computer but I still can't see any rfcomm devices in /dev directory. I will try them both again today and see what happens!

BTW the same devices work flawlessly in my Windows 10 computers when I use APRSIS32 and they are recognised as Bluetooth devices not as Serial Devices by the OS.
So I can fo APRS using APRSIS32 just fine.

YACC on the other hand expects to see a COMport and each one of these devices create 2 COMports in Windows 10. No matter which one of the two I try to use, YACC cannot see this COMport.

After you have paired the radio with the Mint computer try running:
hcitool scan
which should show you the mac address of the controller in the radio. Next run:
sudo rfcomm connect /dev/rfcomm1 <MAC_ADDR>
Now you should be able to see rfcomm1 when you list the /dev directory. Use /dev/rfcomm1 in YAAC.

I don't have a D74 to test with with but this is the method used with the Mobilinkd TNC which is also Bluetooth.

73, de KM4ACK

Hi there,

I just did this and now there is a device rfcomm1 created in /dev directory. Any idea How do we make this persistent at every startup?
Now I see my APRS Voyager being connected when I click at the Bluetooth Devices icon.

But unfortunatelly YAAC beta version 178 still cannot open /dev/rfcomm1.
When I try to enable /dev/rfcomm1, I get a message saying "java.io.IOException: unable to open Serial_TNC connection /dev/rfcomm1"

I hope now Andrew can help with this one!

73 de Demetre M0SUY

The RF comm device can't be persistent because you don't have the device up 24/7 connected to your Linux system. Every time the Bluetooth device (or the laptop) powers off, you will lose the connection and have to rebind it. Now, whether your Linux distro supports remembering previous bindings and rebinding them again automatically is another issue, but not a YAAC issue.

Regarding the IOException, can you send me the entire error message (including the stack trace)? Easiest way would be to email me the YAAC.out file from your YAAC log directory. However, my suspicions include your user account not being a member of the group that owns the /dev/rfcomm1 file (such as dialout), which is a typical problem for Linux users not being able to open serial port devices. Alternatively, it could be an issue with trying to set attributes that may not exist on the Bluetooth device (such as baud rate). Either way, I need to see the complete stack trace to determine where it is failing.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Demetre - M0SUY/SV1UY <demetre.sv1uy@...>
Sent: Friday, September 30, 2022 10:43 AM
To: [email protected]
Subject: Re: [yaac-users] Bluetooth TNC support?

Hi there,

I just did this and now there is a device rfcomm1 created in /dev directory. Any idea How do we make this persistent at every startup?
Now I see my APRS Voyager being connected when I click at the Bluetooth Devices icon.

But unfortunatelly YAAC beta version 178 still cannot open /dev/rfcomm1.
When I try to enable /dev/rfcomm1, I get a message saying "java.io.IOException: unable to open Serial_TNC connection /dev/rfcomm1"

I hope now Andrew can help with this one!

73 de Demetre M0SUY

Hi Andrew,

Thanks a lot for your help. I had forgotten about the group dialout. Once I included myself to this group now YAAC works in my LinuxMint Desktop FB FB FB!

Now to find a way for the Bluetooth connection to be persistent across restarts, maybe put the command in Crontab?

BTW we have used YAAC to install an APRS DIGI & IGATE on a Raspberry Pi 3B which replaced our local IGATE's PC that was power thirsty 24/7/365 and we are very happy with the way YACC works!

73 de Demetre M0SUY

You probably need to start YAAC, "AFTER" connecting/pairing/binding the device to the computer, and verifying what ports the system creates and makes available.

At least, with Linux Mint, that's what happens here with other Bluetooth devices.? If the virtual devices do not exist when a program starts, it cannot see them, no matter how many times you re-plug stuff.?? Some software can re-scan for available devices/ports, not sure if YAAC can do that.

73.
Dave G8KBV

--
Created on and sent from a Unix like PC running and using free and open source software:

Hi Dave,

Thanks for reply OM, I fixed it after Andrew reminded me about th e dialout group. I hadn't used LINUX for a long time and I had forgotten!
Now it works FB!

73 de Demetre M0SUY