Feedback thread for Firmware 2.00v/w/x BETA

[diskilly40]

Hello Manuel, Guido, all,
I would like to download latest firmware but when clicking on link provided, I only got a blank page? Is there a problem with the website or anything else?

Thanks for any information!

73

Didier - F4ISC

[diskilly40]

Hi all,

ok, fine now, disregard my previous post I managed to download latest FW as the related page has been reached!

thks!

73 Didier

[Neily]

I noticed that when the spectrum view is used the call sign does not get re displayed in the main screen. It however does get re displayed if you TX.
I think the AGC is working different, still looking at this.
Great incremental update though Guido, many thanks. 73

[Neily]

As others have noticed the SWR meter does not function in Iambic A or B mode, only straight key mode. Also if I send a long series of dits the SWR Meter does appear in the display and thereafter will only appear with dits only (not dahs) but shows an incorrect power reading.

[aa6st]

A silly ask. But how does one get any of the firmware after 2.00i. On the download page there is no links to any other place. Just serial number call sign a download.

I tried that and I get the latest which on that page is 2.00i. How do I get the cool features of audio over usb and the spectrum scope.

I am using this page.
New Beta Firmware available here:
https://dl2man.de/wp-content/uploads/20 ... /beta.html


Thanks
AA6ST

[DL2MAN]

https://dl2man.de/wp-content/uploads/20 ... /beta.html

[aa6st]

Sorry to bother you again, but that page does not let me cherry pick a specific version.
Is there a place where I can pick a specific beta version?

Thanks,
AA6ST

[w2hsj]

Hi,
I was going to upgrade to Beta, but was looking to download a previous version if that does not work.
even as far as my original 2.00i
Is there a link to previous version .hex file library I can use to 'rollback' ?

Hank
W2HSJ

[KK0NIG]

Engaging VOX lock up the menu and radio.

I reinstalled the firmware and the problem comes back after a few power cycles.

Any ideas? Really want to use this rig for SOTA FT8 using iFTx.

KK0NIG

[pe1nnz]

Hi KK0NIG,
Try to increase the "Noise Gate" level by a lot.
If this value is too low, the TX is triggered by noise, and this may explain the lockup.
If you are unable to change setting, use factory reset (holding rotary on startup).

[lu9mdh]

Hi... Daniel, LU9MDH from Argentina: CW key selection

In the next beta, and about the selection of straight or iambic key, it would be good to implement that if when turning on the transceiver a mono jack is connected, take it as straight, and with a stereo as iambic...

73!!

[pe1nnz]

Hi Daniel, and welcome.

I think this is a good idea: once detected that dash and dot lines are connected it automatically goes in straight mode, else in iambic.

I wonder only if all straight keys in the world in practice are connected to a mono plug (both dash and dot connected).

Guido

[DL2MAN]

No, I don´t think so, but you can implement it vice versa:
If straight is selected in menu, it should just read sleeve and tip and igrnore the middle one.

73 Manuel; DL2MAN

[KN6LOE]

Firmware: 2.00x

Bug Report

Symptoms:
- Check ptt/key alert comes on boot.
- Pressing PTT causes rapid fluctuation, if continued to hold a long continuous tone finally triggers after a few seconds.
- Tapping on the board or microphone causes PTT to trigger.

Steps To Reproduce:
- Switch Keyer to Iambic A
- Insert External Key (possibly optional)
- Remove External Key
- Turn off TruSDX
- Turn on TruSDX

Steps to Fix:
- Changing the keyer back to straight key

Fixes all issues including the microphone PTT triggering sensitivity (almost seems like VOX is triggered, but it was not set in menu.) The 'fluctuation' is in fact the onboard PTT button acting like an Iambic (dit) paddle. Confirmed by changing the WPM and triggering the issue again with fluctuations reflecting the WPM speed setting.

Hope this helps.

Just built my first TruSDX last night and have been having fun!

73 de KN6LOE

[kk1zz]

I'm keen to try the audio driver on linux, but I can't seem to access https://github.com/threeme3/trusdx-audio. I found what appear to be some forks, but wanted to try the latest version. I searched the forum a bit but couldn't find anything. New to trusdx, but excited to try it out!

[pe1nnz]

Hi kk1zz,
Curious where you saw that old link to GitHub page.
The CAT driver can be downloaded from this page: https://dl2man.de/4-trusdx-manual/
73

[kk1zz]

Hi kk1zz,
Curious where you saw that old link to GitHub page.
The CAT driver can be downloaded from this page: https://dl2man.de/4-trusdx-manual/
73

Thank you for the reply! Now I feel very stupid, it was right under my nose the entire time. I found the reference to the github first on this post: https://n1ugk.com/2023/06/trusdx-ft8-wi ... io-cables/ and also on various posts here by searching 'github' and 'audio driver'. I've already emailed N1UGK to let him know he should update the link!

73 KK1ZZ

[Matěj OK2MTB]

Hi Carlo,

No, the procedure should be the same.

Make sure you are in CW mode, then in menu point on CW Message and press left button, then it should start sending.

Does that help?

I will be on travel for a few days but can have a look at it somewhere next week.

73, Guido

Dear Guido,
I’m reporting the same issue with FW 2.00x. When switching the transceiver to CW and setting the menu to item 4.2 (or 4.3), pressing the left button only exits the menu, but the message does not start transmitting.

I’ve already performed a factory reset, but it didn’t resolve the issue.

[PP2PB]

Firmware: 2.00x

Bug Report

Symptoms:
- Check ptt/key alert comes on boot.
- Pressing PTT causes rapid fluctuation, if continued to hold a long continuous tone finally triggers after a few seconds.
- Tapping on the board or microphone causes PTT to trigger.

Steps To Reproduce:
- Switch Keyer to Iambic A
- Insert External Key (possibly optional)
- Remove External Key
- Turn off TruSDX
- Turn on TruSDX

Steps to Fix:
- Changing the keyer back to straight key

Fixes all issues including the microphone PTT triggering sensitivity (almost seems like VOX is triggered, but it was not set in menu.) The 'fluctuation' is in fact the onboard PTT button acting like an Iambic (dit) paddle. Confirmed by changing the WPM and triggering the issue again with fluctuations reflecting the WPM speed setting.

Hope this helps.

Just built my first TruSDX last night and have been having fun!

73 de KN6LOE

I've been having the very same issue here, including the ppt triggering while just handling the board, just like you've pointed out.
I hope it gets addressed on the next update.
It is still amazing what's was made with the available hardware! Hats off to the developers!

73 DE PP2PB

[Miss_Sissy_KM4QLB]

Is there a memory corruption bug in 2.00x?

After leaving my (tr)uSDX running overnight (with 12V power) in receive-only mode, I often come back the next day and find that the transmit wattage, as measured by my ATU-10 antenna tuner, only reaches 0.1W to 0.9W when I reenable transmit in WSJT-X-Improved v2.7.1. Everything else looks normal. Reception is still working, the waterfall looks fine, and FT8 is still being decoded properly. The (tr)uSDX responds to USB serial port commands as well as the buttons and knob.

Powering the (tr)uSDX down and back up (by removing both the 12V and USB plugs and reinstalling them) seems to be the only reliable way to fix it. Things that do not fix it include:

• Changing bands in WSJT-X.

• Shutting down and restarting WSJT-X.

• Reselecting the serial port and pressing the Test CAT and Test PTT buttons (both of which pass).

• Reselecting the input and output audio devices in WSJT-X.

• Connecting to and commanding the (tr)uSDX with FLRIG.

• Pressing the physical PTT button.

I'm running out of things to blame it on other than firmware. I will also note that I reported an issue where, under 2.00x, the (tr)uSDX would turn itself back on after being turned off via the volume knob, a behavior not present under 2.00i. In summary, I wrote:

Since the behavior was not present in v2.00i, but exists in v2.00x, it looks like a firmware issue. It doesn't need to be fixed, but it should be understood lest it turn out to be something like a bounds issue, corrupted pointer, timer with interrupt inadvertently left active, etc.

If there's a way to dump RAM when this happens, I'd be happy to do that in order to provide debug information.

[Hiker-1 KG4ZGW]

Problems upgrading to 2.00x from 2.00i firmware.

1. Installed CH341SER.EXE Drivers.
2. Turned on the (Tr)uSDX with battery power.
3. Attached usb cable to radio then other end of usb cable to computer USB port.
4. Windows made a sound and saying it recognized the device.
5. Device Manager shows software and TR-uSDX installed (no issues) on com port 3
see photo https://drive.google.com/file/d/1jd7mSy ... sp=sharing

6. Initialized AVRDUDESS-2.18-setup.exe
7. Ran AVRDUDESS
8. Changed parameters as per Forum Settings.
9 Hit Program but got this error message
see photo https://drive.google.com/file/d/1ilDepo ... sp=sharing

Any idea why upgrade firmware not working?

Hiker-1 KG4ZGW

[KE0QQQ]

Hello,

Can you offer a picture showing your Device Manager with hidden devices showing under View.

My guess with windows is there is conflict. Windows 11? It might show com 3, but past the reach of the device manager is a mess of entanglement involving how software sees hardware. Lots of tech-no lingo that my old mind has forgotten.

You will find threads I posted here talking of the use of USB connection for command control for windows 11

Google > virtual com ports windows 11 You may have to fuss with regedit, or get a tool,
Google > nirsoft usbdeview to help you see what is passing within the pipes

built in BT , remote video , on top of all the legacy uses of com ports have blurred the paths of software getting to hardware within Windows 11

I had to disable my built in BT to get the flow going in the right direction.

[VE3RRD]

Was the baud rate set to 115200 ? In the picture it looks like 11520

[Hiker-1 KG4ZGW]

I Flashed my (tr)uSDX successfully !!!!

OPERATOR ERROR !! My Baud rate was 11500 should have been 115000.

Can't wait to get it on the air.

Hugo

[KD6FLM]

For what it is worth, I upgraded to x and it broke CAT control on Linux. The radio will click twice after launching JS8Call and then pop up the Rig Control Error dialog box. Back to i and it is working correctly.

A buddy of mine is runing x, problems on Linux too. He switched to Windows as he wanted to get audio working through USB. He mentioned switching back to Linux and working on the issues.

Aaron KD6FLM