开云体育

No, the 9V was a standard Duracell like you'd put in a smoke detector. I wasn't expecting much, just to see if the lower voltage helped or resulted in the same. Ultimately I think it was about the

Randy, I think that was about when the firmware started using all 8 of the LCD data lines. Prior to then it only used 4 of them. One of the 4 others may not be soldered well. Good

At one point, the number of data lines used by the display increased, I think from 4 to 8. Paul -- AI7JR

Ok, I've figured this out. **Firmware versions 19 and earlier work on my QMX — every one of them back to v6 (the earliest one I tried).** Thank goodness for Terminal mode. *Firmware versions 20

Chuck-- If I understand correctly, it's only the QMX+ that gets powered up, firmware loaded, and tested...

Doesn't it say 501?

Hi Randy. I know it seems like updating the firmware caused this but it may have been a coincidence. Gibberish on the screen usually means that one of the data lines to the display has come loose. You

A really good question that you should ask yourself is: Does your radio work when you power it up? They all come with firmware installed for the factory tests of the SMT parts on the board, so if

Did it work before, or is this the initial turn-on? Paul -- AI7JR

I have a factory built unit and your output looks good to me. Very similar. Those that tinker trying to get a little bit more out of theirs write up their sad stories here and ask for help. Don’t

Perhaps that's not enough ... I found that my QMX+ won't really run below about 7.5 VDC.? Below that, it flashes the "flashing battery" icon. Good luck! - Bruce K1FFX

Have you heard about Jeff Moore? He can help.

Unfortunately for me, copy-pasting the file (instead of drag-dropping) made no difference. Still back to gibberish screens. :( Randy K7RAN

Aha, Roger, thank you. I dragged-and-dropped. Using the Terminal app to get back to it, I'll try copy-pasting the file instead. I didn't attempt to delete the old firmware. Will report back. Randy

How are you copying the firmware? Drag and drop has been problematic for some people. Copying/cutting the source file and pasting to the destination is recommended. Also, do not attempt to delete

I'm wondering if the "EEPROM.???" file I see there became corrupted (???) ...

Update... still no solution... but I was able to use the Terminal to enter the QMX's Terminal apps... I tried a factory reset, but it still booted into gibberish... So I then rebooted into the

Just finished QMX build and I can’t get my Mac to recognize the USB so as to upload firmware. ?I am powering with a 7v power supply. ?I am using USB c to usbA and then an adapter. ?Have tried two

I attempted to update the firmware using my MacBook Pro. I followed the manual as follows: * I navigated to the firmware menu choice and clicked "TUNE" * Then I used a USB-C cable to connect to my

I was really hoping for coverage on the prototype? QMX+/- that uses SSB into a DSP with AI? to generate CW from the spoken word and decode? CW back to the spoken word.? Currently it? only