I‘m so happy with my (tr)usdx. The best and most useful rf trx (for my needs) I’ve experienced - especially when being on journey. And I really appreciate the concept of audio-via-cat, which reduces the cable mess significant
And I like the idea of an open, well documented, trx design, combined with a user community!I like to write about two topics.
I use the latest beta firmware 2.00x
1. Android ft8cn app (used via usb) looses connection after some time running. I faced with two problems:
- 1. ft8cn does not automatically reconnect (their fault)
- 2. Restarting the app and / or re-plugging the usb-cable does sometimes not resolve the issue: (tr)usdx needs to be restarted (by disconnecting the external power AND also the usb cable). I miss an easy-accessible reboot-button
I don‘t know if it‘s a problem in the trx of the usb-serial chip (wich is solved due to power cycle), or if the cat-protocol in the trx stops working or is in a state where it does not get it right that the android device does not respond / is disconnected. I argue the trx still thinks the android-device is available, because the speaker keeps still muted.
2. The other topic:
————————
I own this cool device for IT-nerds: getconsole
https://www.get-console.com/shop/en/air ... ingle.html
My idea was:
getconsole speaks usb-serial to tr-usdx.
And either
a) waits for bluetooth connect from the android device
or
b) waits for tcp-session (tcp2serial) via wifi from android
Cool thing about this:
- getconsole has a battery and can power (tr)usdx via usb
- Getconsole hardware is near the trx (short usb cable -> lesser rf impact) and you operate cable-free with your android (or notebook) )
b) failed, because ft8cn says, rig „(tr)usdx (audio over cat)“ is not supported via network (error message: „Now only the FlexRadio or ICom series is supported!“). -> ft8cn concept problem
a) fails - and I think it may be some timing issue. I tested with ft8cn „connection type: bluetooth“, and on connect, (tr)usdx switches off the speaker (as normal for cat control) - but one second later, speaker switches on again and ft8cn says it lost the connection to (tr)usdx.
I‘m not sure if it has to do with dtr/dsr or if the cat init-command comes too late.
I need to investigate more time on this, but I write it here in case other readers of this group have success-stories in connecting (tr)usdx usb-serial to Bluetooth.
vy 73,
- Thomas dl9sau