search

mobilinkd / tnc3-firmware

Firmware for the Mobilinkd TNC3. STM32L433-based Bluetooth/LE KISS TNC.
GNU General Public License v3.0
36 stars 13 forks source link

Not "well" documented mode? #13

Open dx9s opened 3 years ago

dx9s commented 3 years ago

Not really an issue but a comment?!

(I am NOT asking for Ubuntu support on how to create a bluetooth serial port work)

Just got my TNC3 today, connected to phone no problems there. TRIED to connect to my computer via Bluetooth and it claims there is a serial port created and I can even open the port ( cat /dev/rfcommX ), but it either doesn't stay connected or only works once or not sure. I am in dialout group so the file permissions appear to be fine. Been trying to connect YAAC to it and no luck via a well supported USB Bluetooth dongle I have.

I randomly plugged into a USB hub that has 3 power only ports and 7 data ports and got a data port and /dev/ttyACM0 showed up).

I pointed the 'SerialTNC' type port at it (ttyACM0) and things started showing up in the map (currently have transmit disabled) and packets getting received?! I obviously glanced over the http://www.mobilinkd.com/wp-content/files/MobilinkdTNC3.pdf user guide and didn't see this option as showing up. The ONLY mention I see going back is a blurb "or via USB CDC (serial port emulation)."

I think this is something I fully missed upon initially reading up on this device. Thanks for putting that into the firmware!

You can graciously accept my gratitude and close this issue, just wanted to give a thumbs up for direct serial port support.

--Douglas 'dx9s' Marsh

dx9s commented 3 years ago

FWIW.. I got connected over BT from desktop Ubuntu.. it was a combination of

For whatever reason, my TNC3 stopped receiving packets (both over bluetooth and direct USB CDC connection) and attempted to transmit packets (assuming garbled transmissions) but nothing showed up online until after a reset.

Assuming the TNC3 got some buffer/memory corrupted switching between wired/wireless modes. Doesn't hurt to reset device before making changes between serial connections.

I've seen recommendation to perform a "sudo sdptool add SP" (or modify the systemd/dbus script to do this during BT adapter enumeration/startup) to add a "Serial Port Service" to the stack, but it seems optional.

mobilinkd commented 3 years ago

What version of the firmware are you running?

On Wed, Sep 23, 2020 at 12:37 PM dx9s notifications@github.com wrote:

FWIW.. I got connected over BT from desktop Ubuntu.. it was a combination of

  • pressing the reset button
  • BT pair (via GUI or command line)
  • opening command line: "sudo rfcomm bind 0 TNC-Mac-Addr 6" (bind X = /dev/rfcommX)
  • "sudo rfcomm release 0 TNC-Mac-Addr" to release the serial binding.

For whatever reason, my TNC3 stopped receiving packets (both over bluetooth and direct USB CDC connection) and attempted to transmit packets (assuming garbled transmissions) but nothing showed up online until after a reset.

Assuming the TNC3 got some buffer/memory corrupted switching between wired/wireless modes. Doesn't hurt to reset device before making changes between serial connections.

I've seen recommendation to perform a "sudo sdptool add SP" (or modify the systemd/dbus script to do this during BT adapter enumeration/startup) to add a "Serial Port Service" to the stack, but it seems optional.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mobilinkd/tnc3-firmware/issues/13#issuecomment-697761218, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABD64DFMVK3HKRVJAHBGKETSHIW4VANCNFSM4RVFI2JQ .

dx9s commented 3 years ago

according to the Android configuration app, the latest 2.0.1 as of what I can see.

mobilinkd commented 3 years ago

I will have to see what could possibly cause such behavior.  I frequently switch between USB & BT when testing (mostly done on Linux, but lots of Android and iOS BLE as well) and have yet to encounter such behavior.