Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buttons do not function after write #327

Open
bwanamaker opened this issue Apr 10, 2023 · 11 comments
Open

Buttons do not function after write #327

bwanamaker opened this issue Apr 10, 2023 · 11 comments

Comments

@bwanamaker
Copy link

After writing to my TYT MD-UV390 (non-GPS), the PTT is the only button that is working. I've experimented with the extension section of qDMR, attempting to assign ScanToggle to the various buttons but none seem to toggle scan.

Buttons that no longer function after write:

  • Side top - above the PTT
  • Side bottom - below the PTT
  • Green/Menu - front, top left corner
  • Red/Mute - front, top right
  • Up arrow
  • Down arrow
  • Number keys also do not seem to have any function
@hmatuschek
Copy link
Owner

Ok, this is bad. This actually looks like a keyboard lock. Is the lock enabled? It may be a codeplug issue too, maybe I accidentally activate the keyboard lock somehow.

@bwanamaker
Copy link
Author

I cannot see that the lock is enabled. To recover, I found that writing from TYT's CPS software would restore functionality. But something seems to be missing from the YAML that the TYT CPS writes to the radio. I looked through the YAML file to see if there was an obvious keyboard lock being set, but I didn't see anything.

@hmatuschek
Copy link
Owner

Just updated my RT3S (actually identical to the UV390) to the newest FW version (P19.20) and I cannot reproduce this issue. Which firmware version are you running?

@bwanamaker
Copy link
Author

@hmatuschek My UV390 is showing the firmware version as D019.005.

@hmatuschek
Copy link
Owner

Got an email, stating, that this issue is intermittent. If that is the case, this might be a communication issue. That is, the radio stops receiving the codeplug and thus an incomplete codeplug is written. This may cause a lot of issues. Does qdmr report any problems? Does it work reliably, if the command-line-tool is used?

@andrewschott
Copy link

andrewschott commented Feb 6, 2024

Any updates here?

I recently purchased a TYT MD-UV380, and am running into the same issue. Qdmr did not state that there were any issues, just the fact the radio was a micron from being a brick. As aforementioned, the Tytera CPS will %100 restore functionality by writing an empty codeplug. Qdmr has never restored functionality of the radio for me. I have an old habit, used even in chirp of every time I use the tool, read, save, edit, save another copy, write. None of my iterations will restore functionality, just the TYT CPS. Once functionality has been restored with the TYT CPS, I can re-upload any one of the army of codeplugs to the radio just fine.

TY.

@hmatuschek
Copy link
Owner

This appears to be a firmware version issue. Unfortunately the radio does not report any version info to the CPS. So I cannot check, whether qdmr is compatible with that particular version.

@andrewschott
Copy link

Is there firmware versions that are known to work or not to work?

@hmatuschek
Copy link
Owner

Usually, I try to support the latest version, but I may have missed one. It works for me running P19.20.

@andrewschott
Copy link

Out of curiousity, you know where I can get the firmware? I was over on the tyt888.com site and couldnt find any firmware files.

Thanks.

@bmatticus
Copy link

I just had the same issue with my new uv390. I think I got it mostly back by doing a download off the device, checking extensions in settings, deleting any extensions settings in settings and the extensions tab, unchecking everything but ignore verification warnings under settings and then doing an upload to the device.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants