|
|
Re: QMX Build Completed but seems to be some issues
Hi Ron,
I have as yet to receive my QMX, so the following is from the multiple QDX connections that I have made using PuTTy:
The important settings are the Serial Line and the Serial radial button.? The speed should be irrelevant.?
The Serial Line?will be the name from Device Manager if you are using Windows.? It would be a TTY in a Linux OS.? I have not tried with Mac OS, so I do not know the port nomenclature for that OS.
Once you have set the values, I recommend saving as I did to either the default or label it as QMX, then press the save button.?
If you do not save the settings as default, you must select and load the saved settings each time you want to connect to the QMX.
73
Evan
AC9TU
|
Re: UK supplier for ZK-4KX buck module and enclosure.
#supply
Thanks. Any US suppliers? Googling hasn’t been fruitful so far.
|
Re: QMX Build Completed but seems to be some issues
Hans – Thank you for that – very informative and will have to read several times to absorb it all. In my case I can power it on, get LCD Panel backlighting, and the PC sees the device as a USB COM Port. I can hear white noise in the headset that increases when I connect an antenna and the noise can be adjusted with the volume control. With that it seems that I can ASSUME that the power supplies are working, and that the main board seems to be okay. At this point I get no text displayed on the LCD panel and contrast adjustment makes no difference from max to min. The display flickers occasionally and when I try to connect to the COM Port using PuTTY, the "Open" doesn’t seem to do anything. Then again, I've never used PuTTY to open a COM Port - only a web server. For now, I'll assume the problem is in the control or display board (maybe both) and go over both very closely. The USB connections seem to be okay also. We all appreciate your support and advice. 72, Ron AC2C From: [email protected] [mailto: [email protected]] On Behalf Of Hans Summers Sent: Thursday, June 1, 2023 8:56 AM To: [email protected]Subject: Re: [QRPLabs] QMX Build Completed but seems to be some issues Hi all A little word about what goes on in the firmware should aid understanding and debugging. Firstly if you are in firmware update mode, the buck converters are NOT being used. This means there is no 5V rail at all, and the 3.3V rail is supplied by the 78M33 linear voltage regulator. Secondly when you are in the main QMX application mode, the program goes through a whole step by step initialization procedure. The bootloader is ALWAYS run, but if there is no flag set in the EEPROM to indicate the user wants to do firmware update, and if the application firmware is present, then it will jump into the application program very soon after power up. The initialization procedure of QMX goes through many stages. It's important to understand the sequence. 1. Initialize the Flash memory, reset peripherals, configure the system clock, configure the I/O pins 2. Initialize the DMA (Direct Memory Access interface) 3. Initialize the ADC (Analog to Digital Converter) of the CPU; we use 10 channels for monitoring supply voltage, 3.3V, 5V and Bias buck converter outputs, Fwd/Rev power from the SWR bridge etc; all continuously read via the ADC and stored in memory using DMA 4. SMPS (Switched Mode Power Supplies) initialization - this means the little plug-in buck converter boards. 5. DIsplay init - which initializes the LCD module, switches on the backlight (depending on if you configured that to be on in the configuration menu), and writes the Splash screen text (QMX, firmware version, QRP Labs 2023). 6. Blah blah loads and loads of other things - including eventually, the USB initialization... 7. Eventually, audio system initialization (the I2S 48ksps stereo ADC chip and corresponding stereo DAC chip Eventually once all initializations are done (I say eventually but this is all over in less than half a second) - the main process handling runs for the rest of the duration of the radio being powered up, doing all the various functions - one of which is handling a serial terminal login via USB Virtual COM port (PuTTY etc). The SMPS initialization actually WAITS until both the 3.3V and 5V buck converters are spun up and producing the correct voltages, and the system has switched over to using the buck converter boards. The 3.3V rail is first, followed by the 5V rail. In that order. The program has GOT to wait because subsequent initializations require the 5V rail to be ready. This includes the LCD module which is powered from the 5V rail, and the 48ksps stereo I2S ADC and DAC chips. What I'm saying ladies and gentlemen is that if you are able to log in to your QMX using PuTTY then the program has already gone through its entire initialization successfully. The buck converters have both been powered up and are in use producing the 3.3V and 5V rails. It's already gone past initialization of the ADC/DAC chips which also require the 5V rail. So if you have PuTTY log in but nothing on your LCD screen - don't think the problem is the power supplies, it cannot be. The problem can only be some kind of connection problem to the LCD itself. Or perhaps the contrast adjustment needs doing. It should be noted that currently, in common with all other QRP Labs kits, the processor talks AT the LCD, it does not ever try to read anything back from it. If the LCD wasn't even plugged in, the processor would still run through the initialization and tell stuff to the LCD. I suggest checking all the connections to the LCD module. Which are the 2x5-pin header at the top left of the board and the 2x2 pin header at the top right. Note also that the baud rate, start/stop bits etc configuration of PuTTY etc are irrelevant to a Virtual COM Port serial device such as QMX. They are ignored. Not used. 73 Hans G0UPL On Thu, Jun 1, 2023 at 3:17?PM Conrad Trautmann - N2YCH via groups.io <conradtrautmann@...> wrote: I hope it's okay that I join this thread...I'm at about the same point. I copied the firmware file in, powered down and powered back up and now it appears as a port in my device manager, however, I have no display. I tried adjusting the LCD trimmer and nothing. I putty'd in (serial mode, 19200) got to the menu and did a firmware update and copied the file in a second time and waited...it rebooted on its own, but I still have no display. I read on another thread that the display is dependent on the power supplies which are dependent on the firmware. The microprocessor seems to be acting like it should, so do you think I may have a power supply issue to troubleshoot?
|
The capacitors are in the same orientation as they were when I first opened the kit.
|
Re: QMX - strokes of genius?
#qmx
When dealing with transistors and possible damage, i have elected to build in a moderate amount of loss to buffer the finals.? I'd suggest, for your consideration, leaving space on the PCB to accommodate a few non-inductive resistors. If I remember correctly I used 560 ohms (non-inductive) from the PA output to ground and about 2.7-3.3 ohms in series.? ?These could be builder option.? The series resistor could be a jumper & the parallel omitted at the owners option.? ?I did this at high levels (100W) for my IC-7000 years ago after a discussion with Icom technicians about the use of auto-tuners (other than the AH-4) and finals being damaged.? Used the LDG Z100 & never a hint of trouble. autotunerI used the resistors and never missed the 1/2 to 1dB of signal.? ?73,? Tom K1TWH (formerly WB1FPA)??
|
Hi Devan,
As people have indicated, the polarity of the Tantalum capacitor is critical. Note: On the tantalum capacitor, as opposed to a more common electrolytic capacitor,? the marked terminal is the Positive terminal. On a traditional electrolytic capacitor the marked terminal is the negative terminal. You symptoms certainly sound like reverse polarity.
|
John
You prompted to see how well the ProgRock2 would work if the 1PPS signal was removed once the oscillator was stable. ?So I left my GPSDO for a few hours to stabilise whilst connected to the same rig as the other experiments - ie as the 36MHz clock source for my VNWA with my 5MHz Rb oscillator as the S21 input. ?I removed the 1PPS signal and then started a zero frequency scan for 4000 seconds. ?I got the following graph - the red line is the change in frequency at 0.04Hz/div. ?You will see it is pretty stable!
For comparison, here is a similar graph when the 1PPS is on
Not a huge difference! ?So it remarkably stable once it has got lock and has stayed there for a while.
Just before I removed the 1PPS, the adjustment was 4222/3560. ?I turned the 1PPS back on after nearly 1.5 hours, the adjustment drifted down to about 4183/3560
73
Paul
|
UK supplier for ZK-4KX buck module and enclosure.
#supply
Hi,
Just purchased this great enclosure for the Z4-KX buck module which is popular with QRP stations & makes a great supply for qrp labs units.
USB 3.0 PD and XT-60 connector inputs.
Great supplier, Cheaper than Chinese vendors. Standard post is ?1.90 goods usually arrive next day.
The buck module itself is also linked on page below.
|
Re: QMX Build Completed but seems to be some issues
Hi all
A little word about what goes on in the firmware should aid understanding and debugging.?
Firstly if you are in firmware update mode, the buck converters are NOT being used. This means there is no 5V rail at all, and the 3.3V rail is supplied by the 78M33 linear voltage regulator.?
Secondly when you are in the main QMX application mode, the program goes through a whole step by step initialization procedure. The bootloader is ALWAYS run, but if there is no flag set in the EEPROM to indicate the user wants to do firmware update, and if the application firmware is present, then it will jump into the application?program very soon after power up. The initialization procedure?of QMX goes through many stages. It's important?to understand the sequence.? - Initialize the Flash memory, reset peripherals, configure the system clock, configure the I/O pins
- Initialize the DMA (Direct Memory Access interface)?
- Initialize the ADC (Analog to Digital Converter) of the CPU; we use 10 channels for monitoring supply voltage, 3.3V, 5V and Bias buck converter outputs, Fwd/Rev power from the SWR bridge etc; all continuously read via the ADC and stored in memory using DMA
- SMPS (Switched Mode Power Supplies) initialization - this means the little plug-in buck converter boards.?
- DIsplay init - which initializes the LCD module, switches on the backlight (depending on if you configured that to be on in the configuration menu), and writes the Splash screen text (QMX, firmware version, QRP Labs 2023).?
- Blah blah loads and loads of other things - including eventually, the USB initialization...?
- Eventually, audio system initialization (the I2S 48ksps stereo ADC chip and corresponding stereo DAC chip
Eventually once all initializations are done (I say eventually but this is all over in less than half a second) - the main process handling runs for the rest of the duration of the radio being powered up, doing all the various functions - one of which is handling a serial terminal login via USB Virtual COM port (PuTTY etc).?
The SMPS initialization actually WAITS until both the 3.3V and 5V buck converters are spun up and producing the correct voltages, and the system has switched over to using the buck converter boards. The 3.3V rail is first, followed by the 5V rail. In that order. The program has GOT to wait because subsequent initializations require the 5V rail to be ready. This includes the LCD module which is powered from the 5V rail, and the 48ksps stereo I2S ADC and DAC chips.?
What I'm saying ladies and gentlemen is that if you are able to log in to your QMX using PuTTY then the program has already gone through its entire initialization successfully. The buck converters have both been powered up and are in use producing the 3.3V and 5V rails. It's already gone past initialization of the ADC/DAC chips which also require the 5V rail.?
So if you have PuTTY log in but nothing on your LCD screen - don't think the problem is the power supplies, it cannot be. The problem can only be some kind of connection problem to the LCD itself. Or perhaps the contrast adjustment needs doing. It should be noted that currently, in common with all other QRP Labs kits, the processor talks AT the LCD, it does not ever try to read anything back from it. If the LCD wasn't even plugged in, the processor would still run through the initialization and tell stuff to the LCD.
I suggest checking all the connections to the LCD module. Which are the 2x5-pin header at the top left of the board and the 2x2 pin header at the top right.?
Note also that the baud rate, start/stop bits etc configuration of PuTTY etc are irrelevant to a Virtual COM Port serial device such as QMX. They are ignored. Not used.?
73 Hans G0UPL
On Thu, Jun 1, 2023 at 3:17?PM Conrad Trautmann - N2YCH via <conradtrautmann= [email protected]> wrote:
I hope it's okay that I join this thread...I'm at about the same point. I copied the firmware file in, powered down and powered back up and now it appears as a port in my device manager, however, I have no display. I tried adjusting the LCD trimmer and nothing. I putty'd in (serial mode, 19200) got to the menu and did a firmware update and copied the file in a second time and waited...it rebooted on its own, but I still have no display.
I read on another thread that the display is dependent on the power supplies which are dependent on the firmware. The microprocessor seems to be acting like it should, so do you think I may have a power supply issue to troubleshoot?
|
Hi Devan. I assume you are absolutely sure the tantalums are mounted with the correct polarity???
-Steve K1RF
------ Original Message ------
Date 6/1/2023 8:05:11 AM
Subject [QRPLabs] Burned Up QMX #dummy #qmx #smoke
Well, I had a friend pick me up a brand new QMX at Dayton. I waited for the build instructions, and then built the rig (I've built many kits over the years and a couple of QRP Labs kits more recently.). I spent what felt like an eternity checking all solder joints with a lighted magnifier as well as a digital microscope, found a couple small issues and promptly repaired them. Then I applied power with a non current limited 12v supply (mistake No.1). Nothing happened, so I held the rotary encoder, nothing happened. I had missed the line that nothing would happen on the display without firmware (mistake No.2). I set the unit down to go grab a USB? cable and as I sat it down something arced, and a tantalum capacitor had exploded on one of the power supply boards.
I ordered new tantalum capacitors over the Memorial Day weekend and they arrived a day later, I waited until Tuesday to replace the capacitor. Once I had replaced it, I spent another hour or more under the scope looking for what went wrong and anything else I missed. I found nothing. So I tried it again. This time when I pressed the rotary encoder, I had already plugged in the USB cable. as second or two later, the USB device was recognized, and I was ready for firmware (still not available a that time). I unplugged everything and set it all aside to wait for firmware. Well, firmware was released last night..... I could hardly sleep!!! That takes us to today.
I downloaded the firmware, read the updated build manual, checked all the spots that need checked, double and triple checked the spots outlined by Hans in the revised manual. I then plugged in my USB cable, applied power, and pushed the rotary encoder. All is well, a second or two in and the pc dink-donks and the "USB Drive" shows up in my devices. I copy the firmware file over and as soon as the copy completes, crack, smoke, fire. The large tantalum capacitor on the other power supply board had exploded. I scrambled to unplug and disconnect everything.... off to the solder bench to replace another capacitor and have another look under the scope. after some searching, I found what looked like a solder bridge that I had missed, I made the repair, replaced my capacitor and back to my test bench I went. As soon as I applied power again the same capacitor blew up and caught fire again.
Suffice it to say, I am tired of looking and my office/test bench smells terrible. I calmly reassembled the unit, and logged into QRP Labs to order another QMX. If someone wants to attempt to repair this QMX I have, I am more than willing to ship it to you to play with. I'm not against further testing, and repair attempts, but I don't really want it totally destroyed, I would rather have it as a desk ornament/conversation piece than a ball of charred PCB. Hopefully the new shipment of boards comes in super fast and I can get my replacement in short order. (hopes aren't too high). I would like to thank Hans for a very well written and detailed build manual and also for all the effort he puts into all of these kits for us to enjoy! I want the QMX to use for FT8 as well as CW when I learn it. (currently learning) Rest assured, I will continue to buy and build his kits as long as they are available. My goal is to build them all but i need to learn CW before I go too much further.
May the smoke stay ever in your radio!!!
'73 Devan KD8MST
|
Re: QMX Build Completed but seems to be some issues
I hope it's okay that I join this thread...I'm at about the same point. I copied the firmware file in, powered down and powered back up and now it appears as a port in my device manager, however, I have no display. I tried adjusting the LCD trimmer and nothing. I putty'd in (serial mode, 19200) got to the menu and did a firmware update and copied the file in a second time and waited...it rebooted on its own, but I still have no display.
I read on another thread that the display is dependent on the power supplies which are dependent on the firmware. The microprocessor seems to be acting like it should, so do you think I may have a power supply issue to troubleshoot?
|
As KJ4A ?said, my first thought was it really sounds like the polarity of your tantalum capacitors is backwards, they tend to explode when reverse polarized.
73, Willie N1JBJ
toggle quoted message
Show quoted text
On Jun 1, 2023, at 8:05 AM, Devan Phillis <devan@...> wrote:
Well, I had a friend pick me up a brand new QMX at Dayton. I waited for the build instructions, and then built the rig (I've built many kits over the years and a couple of QRP Labs kits more recently.). I spent what felt like an eternity checking all solder joints with a lighted magnifier as well as a digital microscope, found a couple small issues and promptly repaired them. Then I applied power with a non current limited 12v supply (mistake No.1). Nothing happened, so I held the rotary encoder, nothing happened. I had missed the line that nothing would happen on the display without firmware (mistake No.2). I set the unit down to go grab a USB? cable and as I sat it down something arced, and a tantalum capacitor had exploded on one of the power supply boards.
I ordered new tantalum capacitors over the Memorial Day weekend and they arrived a day later, I waited until Tuesday to replace the capacitor. Once I had replaced it, I spent another hour or more under the scope looking for what went wrong and anything else I missed. I found nothing. So I tried it again. This time when I pressed the rotary encoder, I had already plugged in the USB cable. as second or two later, the USB device was recognized, and I was ready for firmware (still not available a that time). I unplugged everything and set it all aside to wait for firmware. Well, firmware was released last night..... I could hardly sleep!!! That takes us to today.
I downloaded the firmware, read the updated build manual, checked all the spots that need checked, double and triple checked the spots outlined by Hans in the revised manual. I then plugged in my USB cable, applied power, and pushed the rotary encoder. All is well, a second or two in and the pc dink-donks and the "USB Drive" shows up in my devices. I copy the firmware file over and as soon as the copy completes, crack, smoke, fire. The large tantalum capacitor on the other power supply board had exploded. I scrambled to unplug and disconnect everything.... off to the solder bench to replace another capacitor and have another look under the scope. after some searching, I found what looked like a solder bridge that I had missed, I made the repair, replaced my capacitor and back to my test bench I went. As soon as I applied power again the same capacitor blew up and caught fire again.
Suffice it to say, I am tired of looking and my office/test bench smells terrible. I calmly reassembled the unit, and logged into QRP Labs to order another QMX. If someone wants to attempt to repair this QMX I have, I am more than willing to ship it to you to play with. I'm not against further testing, and repair attempts, but I don't really want it totally destroyed, I would rather have it as a desk ornament/conversation piece than a ball of charred PCB. Hopefully the new shipment of boards comes in super fast and I can get my replacement in short order. (hopes aren't too high). I would like to thank Hans for a very well written and detailed build manual and also for all the effort he puts into all of these kits for us to enjoy! I want the QMX to use for FT8 as well as CW when I learn it. (currently learning) Rest assured, I will continue to buy and build his kits as long as they are available. My goal is to build them all but i need to learn CW before I go too much further.
May the smoke stay ever in your radio!!!
'73 Devan KD8MST
|
Devan, Double check the polarity of the tantalum capacitors. If installed reversed they go off like a firecracker.
JZ KJ4A?
On Thu, Jun 1, 2023, 8:05 AM Devan Phillis < devan@...> wrote: Well, I had a friend pick me up a brand new QMX at Dayton. I waited for the build instructions, and then built the rig (I've built many kits over the years and a couple of QRP Labs kits more recently.). I spent what felt like an eternity checking all solder joints with a lighted magnifier as well as a digital microscope, found a couple small issues and promptly repaired them. Then I applied power with a non current limited 12v supply (mistake No.1). Nothing happened, so I held the rotary encoder, nothing happened. I had missed the line that nothing would happen on the display without firmware (mistake No.2). I set the unit down to go grab a USB? cable and as I sat it down something arced, and a tantalum capacitor had exploded on one of the power supply boards.
I ordered new tantalum capacitors over the Memorial Day weekend and they arrived a day later, I waited until Tuesday to replace the capacitor. Once I had replaced it, I spent another hour or more under the scope looking for what went wrong and anything else I missed. I found nothing. So I tried it again. This time when I pressed the rotary encoder, I had already plugged in the USB cable. as second or two later, the USB device was recognized, and I was ready for firmware (still not available a that time). I unplugged everything and set it all aside to wait for firmware. Well, firmware was released last night..... I could hardly sleep!!! That takes us to today.
I downloaded the firmware, read the updated build manual, checked all the spots that need checked, double and triple checked the spots outlined by Hans in the revised manual. I then plugged in my USB cable, applied power, and pushed the rotary encoder. All is well, a second or two in and the pc dink-donks and the "USB Drive" shows up in my devices. I copy the firmware file over and as soon as the copy completes, crack, smoke, fire. The large tantalum capacitor on the other power supply board had exploded. I scrambled to unplug and disconnect everything.... off to the solder bench to replace another capacitor and have another look under the scope. after some searching, I found what looked like a solder bridge that I had missed, I made the repair, replaced my capacitor and back to my test bench I went. As soon as I applied power again the same capacitor blew up and caught fire again.
Suffice it to say, I am tired of looking and my office/test bench smells terrible. I calmly reassembled the unit, and logged into QRP Labs to order another QMX. If someone wants to attempt to repair this QMX I have, I am more than willing to ship it to you to play with. I'm not against further testing, and repair attempts, but I don't really want it totally destroyed, I would rather have it as a desk ornament/conversation piece than a ball of charred PCB. Hopefully the new shipment of boards comes in super fast and I can get my replacement in short order. (hopes aren't too high). I would like to thank Hans for a very well written and detailed build manual and also for all the effort he puts into all of these kits for us to enjoy! I want the QMX to use for FT8 as well as CW when I learn it. (currently learning) Rest assured, I will continue to buy and build his kits as long as they are available. My goal is to build them all but i need to learn CW before I go too much further.
May the smoke stay ever in your radio!!!
'73 Devan KD8MST
|
Well, I had a friend pick me up a brand new QMX at Dayton. I waited for the build instructions, and then built the rig (I've built many kits over the years and a couple of QRP Labs kits more recently.). I spent what felt like an eternity checking all solder joints with a lighted magnifier as well as a digital microscope, found a couple small issues and promptly repaired them. Then I applied power with a non current limited 12v supply (mistake No.1). Nothing happened, so I held the rotary encoder, nothing happened. I had missed the line that nothing would happen on the display without firmware (mistake No.2). I set the unit down to go grab a USB? cable and as I sat it down something arced, and a tantalum capacitor had exploded on one of the power supply boards.
I ordered new tantalum capacitors over the Memorial Day weekend and they arrived a day later, I waited until Tuesday to replace the capacitor. Once I had replaced it, I spent another hour or more under the scope looking for what went wrong and anything else I missed. I found nothing. So I tried it again. This time when I pressed the rotary encoder, I had already plugged in the USB cable. as second or two later, the USB device was recognized, and I was ready for firmware (still not available a that time). I unplugged everything and set it all aside to wait for firmware. Well, firmware was released last night..... I could hardly sleep!!! That takes us to today.
I downloaded the firmware, read the updated build manual, checked all the spots that need checked, double and triple checked the spots outlined by Hans in the revised manual. I then plugged in my USB cable, applied power, and pushed the rotary encoder. All is well, a second or two in and the pc dink-donks and the "USB Drive" shows up in my devices. I copy the firmware file over and as soon as the copy completes, crack, smoke, fire. The large tantalum capacitor on the other power supply board had exploded. I scrambled to unplug and disconnect everything.... off to the solder bench to replace another capacitor and have another look under the scope. after some searching, I found what looked like a solder bridge that I had missed, I made the repair, replaced my capacitor and back to my test bench I went. As soon as I applied power again the same capacitor blew up and caught fire again.
Suffice it to say, I am tired of looking and my office/test bench smells terrible. I calmly reassembled the unit, and logged into QRP Labs to order another QMX. If someone wants to attempt to repair this QMX I have, I am more than willing to ship it to you to play with. I'm not against further testing, and repair attempts, but I don't really want it totally destroyed, I would rather have it as a desk ornament/conversation piece than a ball of charred PCB. Hopefully the new shipment of boards comes in super fast and I can get my replacement in short order. (hopes aren't too high). I would like to thank Hans for a very well written and detailed build manual and also for all the effort he puts into all of these kits for us to enjoy! I want the QMX to use for FT8 as well as CW when I learn it. (currently learning) Rest assured, I will continue to buy and build his kits as long as they are available. My goal is to build them all but i need to learn CW before I go too much further.
May the smoke stay ever in your radio!!!
'73 Devan KD8MST
|
Re: QMX Build Completed but seems to be some issues
Okay, Willie, I’ll keep working on it. At this point the problem is that plugging in the USB causes the PC to display "USB Device is not recognized". As it stands now, the ON/OFF push always works to turn on but not always to turn off. The backlight also seems to flicker at times. Pressing the left encoder once seems to change mode since the background noise level changes. It also appears to be changing bands. The noise level increases when I plug in an antenna so it seems as if the receiver is working. Since I have another QMX kit that I picked up at Hamvention, I'm considering building the second one and then I can use parts from the two to try to narrow it done a bit - at least to the which board. Ron From: [email protected] [mailto: [email protected]] On Behalf Of William Smith Sent: Thursday, June 1, 2023 7:13 AM To: [email protected]Subject: Re: [QRPLabs] QMX Build Completed but seems to be some issues It’s either: 1) In firmware update mode it looks like a USB disk drive, copy files onto it and it’ll reboot running the new firmware. OR 2) In normal operations mode it looks like COM ports and audio interfaces. Connect Putty to one of the COM ports and <I don’t remember the details off the top of my head, you should Read The Fine Manual> 73, Willie N1JBJ On Jun 1, 2023, at 7:08 AM, Ron AC2C <AC2C@...> wrote: Curt – I have cycled the power a few times now and the PC no longer recognizes it when I plug in the USB. I ASSUME that the QMX is no longer recognized because it is no longer in firmware update mode. Is that a safe assumption ? I am slightly familiar with PuTTY as I use it to access our club's web server. If the QMX is no longer recognized by the PC, then how cold I connect to it using PuTTY ? I appreciate your advice but am a bit lost as to how to proceed. Ron From: [email protected] [mailto: [email protected]] On Behalf Of Curt M. Sent: Wednesday, May 31, 2023 10:12 PM To: [email protected]Subject: Re: [QRPLabs] QMX Build Completed but seems to be some issues Once you send the firmware into it cycle the power and connect to it with Putty and select upgrade firmware. After that cycle the power and double check the contrast on the display again. Curt WU3U
|
Re: QMX Build Completed but seems to be some issues
GM Sandy -
Yes, the unit is not in the container and the trimmer pot has no effect from one extreme to the other.
Ron
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] [mailto: [email protected]] On Behalf Of Sandy Sent: Wednesday, May 31, 2023 7:27 PM To: [email protected]Subject: Re: [QRPLabs] QMX Build Completed but seems to be some issues Hey Ron - You must first adjust the contrast of the display with the kit outside of the container. Plug it in and turn the 20K trimmer potentiometer R47 until you see visible print. 73, Sandy On 5/31/23 19:03, Ron AC2C wrote: I completed a build of the QMX this afternoon. Before I knew that a firmware
load was available I tried connecting power with headphones plugged in and
noticed a pop when I applied power and the LCD display was off - no text, no
backlight. I plugged the USB into my PC an the PC immediately saw a USB
Drive.
At that point the main thing I had noticed was that the On/Off encoder
button did not seem to have any effect.
With the initial version of firmware available, I downloaded it, unzipped
the file and tried following the firmware installation instructions. I got
lost pretty quickly:
"Note: you have to switch on QMX by pressing the left rotary encoder shaft
button! In
firmware update mode, the LCD is blank and the backlight is off."
Okay, mine seems to always ON and the LCD is blank and not backlit.
"QMX provides four possible ways to enter firmware update mode:
1. The first time you power up your QMX, there is no firmware on the QMX. It
will
automatically enter firmware update mode and stay in firmware update mode
until you have
successfully installed the firmware.
2. Select the "Update firmware" option in the QMX in the "Other" sub-menu of
the
configuration menu system on the QMX itself."
Okay but I have no display - the LCD is blank. How can I select anything
from a menu ?
So I figure since the QMX was pretending to be a USB Drive, I could just
drag/drop the 1_00_001.QDX file from the zip file to the QMX USB. That took
a few seconds but nothing happened after the transfer was complete. So I
powered down - I still can only power ON/OFF by disconnecting the battery.
When I reconnected power, the LCD was backlit but still blank. I can hear
what sounds like white noise in the headphones and the volume control seems
to adjust the volume of the noise.
I'm not sure what to do next but will disassemble and do some very thorough
inspections.
Any suggestions where to look ?
Ron, AC2C
|
Re: QMX Build Completed but seems to be some issues
It’s either:
1) In firmware update mode it looks like a USB disk drive, copy files onto it and it’ll reboot running the new firmware.
OR
2) In normal operations mode it looks like COM ports and audio interfaces. ?Connect Putty to one of the COM ports and <I don’t remember the details off the top of my head, you should Read The Fine Manual>
73, Willie N1JBJ
toggle quoted message
Show quoted text
On Jun 1, 2023, at 7:08 AM, Ron AC2C <AC2C@...> wrote:
Curt –I have cycled the power a few times now and the PC no longer recognizes it when I plug in the USB.I ASSUME that the QMX is no longer recognized because it is no longer in firmware update mode. Is that a safe assumption ?I am slightly familiar with PuTTY as I use it to access our club's web server. If the QMX is no longer recognized by the PC, then how cold I connect to it using PuTTY ?I appreciate your advice but am a bit lost as to how to proceed.RonFrom:?[email protected]?[mailto:[email protected]] On Behalf Of Curt M.Sent: Wednesday, May 31, 2023 10:12 PMTo:?[email protected]Subject: Re: [QRPLabs] QMX Build Completed but seems to be some issuesOnce you send the firmware into it cycle the power and connect to it with Putty and select upgrade firmware. After that cycle the power and double check the contrast on the display again.?CurtWU3U
|
Re: QMX Build Completed but seems to be some issues
Curt – I have cycled the power a few times now and the PC no longer recognizes it when I plug in the USB. I ASSUME that the QMX is no longer recognized because it is no longer in firmware update mode. Is that a safe assumption ? I am slightly familiar with PuTTY as I use it to access our club's web server. If the QMX is no longer recognized by the PC, then how cold I connect to it using PuTTY ? I appreciate your advice but am a bit lost as to how to proceed. Ron From: [email protected] [mailto: [email protected]] On Behalf Of Curt M. Sent: Wednesday, May 31, 2023 10:12 PM To: [email protected]Subject: Re: [QRPLabs] QMX Build Completed but seems to be some issues Once you send the firmware into it cycle the power and connect to it with Putty and select upgrade firmware. After that cycle the power and double check the contrast on the display again. Curt WU3U
|
On Wed, May 31, 2023 at 08:50 PM, Paul Wilton wrote:
I have recently packaged up a QLG2 plus a ProRock 2 into an enclosure to give me a GPSDO for the workbench. ?I also happen to have an uncalibrated 5MHz TEMEX LPRS-01 Rb source so I thought it would be interesting to see if I could measure the Allan Deviation using my DG8SAQ VNWA 3E as a precision frequency source. ?
I too have used a Progrock2 for similar purposes, although my implementation was a bit more inelegant!.? Mine is mounted vertically on a piece of stripboard (same size as a Progrock1 by the way).? I wanted to try screening the Progrock2 to reduce radiation of spurious harmonics into the 1575MHz GPS area.? So initially, I wrapped the board in insulating tape, with a short flexible wire tacked to one of the ground pins.? I then carefully wrapped a strip of aluminium foil around the board to help screen it, with the wire taped to it for grounding contact.? Finally, the whole is wrapped in a piece of plastic foam as thermal insulation, held in place with a couple of zip ties.?? The Progrock2 settles after a period into the 3/3650Hz? correction as does Paul's unit.? ?It provides a highly suitable 24MHz frequency reference for my SDRplay receiver and this is significantly better than the Progrock1 unit that it replaces. incidentally, not shown in the picture is the USB cable into the Progrock2.? I used a short fly lead fitted with a micro USB at one end and a Type B USB panel mounting socket at the other.? This allows me to use a Type B lead, which is similar to my Arduino Uno etc and which is far more suitable for repeated connections compared to a micro USB.? The other thing is that I cut the red +5V wire in this cable so that the computer's 5V does not attempt to power the Progrock2.? This is because I put a 22 ohm dropper resistor into the +V feed (which reduces the supply to 3.9V or so).? The power dissipation in the LDO regulator is thereby reduced - possibly important if I was going to wrap the board in thermal insulation! ? -- Peter Lee G3SPL
|
EI9ILB
Ron AC2C
WS1M - bammi
Conrad Trautmann - N2YCH