UV380 + DM-1701 Beta 2023 04 04

[ct1esj]

The firmware loaded fine only many RT3S

Did you select the correct radio type?

Yes, of course I chose it, my RT3S is from the first versions, it has never rejected an update except this one.

So you can still load the previous version.

Error message indicates radio is not in DFU mode. Check the windows device manager

You are right Roger, the problem was in the windows driver. Fixed and already installed.
This Windows bullshit every now and then gives this, it must have lost the DFU driver in yesterday's update.
Thanks mate for the suggestion.

[VK3KYY]

Yes, of course I chose it, my RT3S is from the first versions, it has never rejected an update except this one.

So you can still load the previous version.

Error message indicates radio is not in DFU mode. Check the windows device manager

You are right Roger, the problem was in the windows driver. Fixed and already installed.
This Windows bullshit every now and then gives this, it must have lost the DFU driver in yesterday's update.
Thanks mate for the suggestion.

We don't install this driver. Windows does it automatically. Probably you plugged into a different USB socket on your computer and Windows installed the wrong driver onto that port.

[ct1esj]

So you can still load the previous version.

Error message indicates radio is not in DFU mode. Check the windows device manager

You are right Roger, the problem was in the windows driver. Fixed and already installed.
This Windows bullshit every now and then gives this, it must have lost the DFU driver in yesterday's update.
Thanks mate for the suggestion.

We don't install this driver. Windows does it automatically. Probably you plugged into a different USB socket on your computer and Windows installed the wrong driver onto that port.

No, I have always used the same one with usb, the driver update I did through windows update and it stayed as it was. Big THANK YOU. It's time to go to sleep, there's more tomorrow, hehehe.

[EU1AEQ]

Oh, last heard is now full screen in RT3S! I wonder what else has changed?
Thanks. Great.
Are you planning to increase the scanning speed like the 1801?

[Ik0nwg]

the firmware on my rt3s works very well... now on the last heard screen the last 7 transmitted calls are shown (previously they were only 3).... thanks
Ciao

[KC7RBW]

On mine it no longer displays the boot image. Are there plans to support one that fits the display better?

Loving the more sane key mapping. Thank you for that!

[SA0BUX]

I noticed some quirk that seems to be a bug in the 20230404 build on both RT3S and RT84 (DM-1701)

When you have used 1750 Hz and DTMF a while on a channel it latches either 1750 or a DTMF tone that is heard in background when you press PTT.
It can be a bit random to activate the bug , last time I had to play around with long press on PTT+Fn (1750) combined with a lot of DTMF.
When the bug is active, microphone is blocked and you only hear the tone when transmitting.
It's possible to activate another tone by doing some more long press on keys.
A restart of the radio clears it.

[SA0BUX]

I noticed some quirk that seems to be a bug in the 20230404 build on both RT3S and RT84 (DM-1701)

When you have used 1750 Hz and DTMF a while on a channel it latches either 1750 or a DTMF tone that is heard in background when you press PTT.
It can be a bit random to activate the bug , last time I had to play around with long press on PTT+Fn (1750) combined with a lot of DTMF.
When the bug is active, microphone is blocked and you only hear the tone when transmitting.
It's possible to activate another tone by doing some more long press on keys.
A restart of the radio clears it.

I tested my other RT3S which is running 20230311 and it seemed even easier to activate the bug on that radio, only needed some 1750 burst
to trigger it.
I don't use 1750 or DTMF so much so I haven't noticed it before and you will not notice it unless you monitor your own TX.

[SA0BUX]

I noticed some quirk that seems to be a bug in the 20230404 build on both RT3S and RT84 (DM-1701)

When you have used 1750 Hz and DTMF a while on a channel it latches either 1750 or a DTMF tone that is heard in background when you press PTT.
It can be a bit random to activate the bug , last time I had to play around with long press on PTT+Fn (1750) combined with a lot of DTMF.
When the bug is active, microphone is blocked and you only hear the tone when transmitting.
It's possible to activate another tone by doing some more long press on keys.
A restart of the radio clears it.

I tested my other RT3S which is running 20230311 and it seemed even easier to activate the bug on that radio, only needed some 1750 burst
to trigger it.
I don't use 1750 or DTMF so much so I haven't noticed it before and you will not notice it unless you monitor your own TX.

I rolled back to some older versions, the bug with latched 1750/DTMF occurs from build 20230227-201014.
I haven't been able to trigger it in 20230225-075614 or 20230213-163105.

[G4EML]

The reported DTMF and 1750Hz latching bug occurs if you release the PTT while you are sending a DTMF or 1750Hz tone. The code then doesn't correctly terminate the tone.

I have created a fix for this which will be included in the next release.


Colin G4EML