开云体育

Hey Mike - that would be an amazing set of bands when I'm out portable.? Nice balance between antenna size and usable bands both locally and DX when hiking. 73/72 Jeff - VE3CW / VA3JFF

My QMX went up in smoke at my initial power up.? One of the voltage regulators on the buck power board blew. Prior to that, I was able to download the firmware using a 9v smoke detector battery for

The row of boxes on the display is likely the "Contrast" pot setting (R47 I believe)....the manual doesn't tell you to turn/set it fully CCW for an initial setting.....i.e. Having boxes showing is

I was able to load the firmware with a 9v smoke detector battery as a power source. And I put electrical tape over the back of the power socket to keep it from shorting against the rotary controller.

Does your computer recognize Progrock when plugged in with usb cable. I was working on a different kit but had a communication problem on the usb connector on the kit causing issue. Once i fixed that

Congrats on the FW progress! My feedback is that the FW update completed and the QMX rebooted and displayed 1_00_0004 on the screen. But the QMX was in a "hang" state and could? not be powered off

FWIW, my Mac would not recognize my QMX at initial power up. however, my PC did recognize it and I was able to load the firmware. I was using a 9v smoke detector battery for power.

Can someone please help me step up Putty to talk to my ProgRock2 I got the screen and port selected but cannot type or connect to the progrock... Thanks Dave

It also works in WSJT-X. However, you can't select it, you have to type the whole string. 73, Uli DF7SC

"I can even initiate a serial connection (with Putty, for example), and the acts like the port is fine. However, there is no response to manually entered CAT commands, and the QDX doesn't go into

Also, to reiterate the timeline: the QDX worked great on-air for the first couple days after I built it. But after I put it into Terminal Mode (to run some of its internal tests), and shut it down

Hi Paul, Thanks for the reply. I'm loading the firmware by just dragging and dropping files in the File Manager. Since I'm a Raspberry Pi, not Windows, I don't have that same Device Manager, but by

Hans, Thank you! That is a LOT of work done in quick time on top of all the rest that you have going on. I really appreciate the frequent updates. That said, yes, you do have a few more things going

I can confirm a new problem with FW 004 and fldigi. If using TxID the QMX reverts to receive in a second or two. The QMX has had an issue with Olivia mode with firmware 003 and before, but this is a

When you say you loaded the firmware in bootloader mode, you mean from the PC to the QDX using the DFU tool? That probably says the MPU and USB /connections/ are working correctly. If you go into

Observing the same thing here with 004. 73 de K9ID

Upgraded from 002 to 004 and now wsjtx will not tune for more than a second and transmit will not work for more than a second. Reverting back to 002 and tx works normally.? did a factory reset in 004

Hans sent me a factory EEPROM file, and it loaded onto the QDX in bootloader mode, but unfortunately the serial port is still non-functional. Is it documented anywhere what the 5 header pads are at

I have a two-channel LeoBodnar GPS clock box. I am trying to time both a QDX lo and KIWI SDR. I worked with Bodnar support for a few days. The time shift slowed the communications. We started with the

Yes that R48 resistor is the feed to the display backlight LED.? Depending on what supply you are using, there is 10V or more across the 270 ohm resistor which will dissipate around 0.4W (depending