Date
21 - 34 of 34
#qcx Firmware 1.06 release #qcx
|
Alan G4ZFQ
Steven
I believe the fuse settings should be:Yes, except the Low fuse changed to D7, was it to remove delay? But not really any point in changing, it's just theoretically correct. High must be D1 and has never changed. 73 Alan G4ZFQ |
|
|
|
chmims <chmims@...>
I have flashed a 40M QCX. It seemed to go well with one minor change.
With 1.05 when booting up I got the initial message '5W CW Tcvr 1.05'. Now all I get is '1.06'. Initially it seems to be working well. However, since I have 'bricked' a QRX in the past with upgrades of the firmware I am hesitating to upgrade my QCX+. Do have any reason to worry. Charles KG5ZLH |
|
|
|
I flashed my 40 meter QCX with no issues. I'm looking forward to the LCD mini circuit.
-- 73, Dan - W2DLC |
|
|
|
Al Holt
The '1-06' display at startup seems to be normal. I get it on all QCX's I have, two of which are QCX+ models.
Wasn't there something posted here about doing your own 'splash screen?' --Al |
|
|
|
Pg 130 of manual, setting 7.8 is used to enable the splash screen. 2 lines which can be stored in messages 11 and 12 in settings section 2.
Not sure about version 1.06, but works nicely in 1.05 |
|
|
|
Al Holt
Michael Greene,
It's working in v.106. no lowercase letters, but a good way to tag it. --Al |
|
|
|
Hans Summers
Hi all No significant issues were found with 1.06. Today we started programming and shipping 1.06 chips. The shortened splash screen message is just an oversight of mine. I uploaded a new 1.06 file where I corrected this: I didn't even bother to call it 1.06a since it is such a trivial thing. I tested and adjusted three different assembled QCX+ kit orders today. Two had 1.05 chips which I upgraded. One had a fresh 1.06 chip. All three worked perfectly. I couldn't even see the long-standing minor issue of needing to rotate the rotary encoder one click if the calibration (menus 8.12 and 8.13) gets stuck, because none of mine got stuck. I have updated the website pages with the needed changes, including the firmware history page. 73 Hans G0UPL |
|
|
|
Steven Dick, K1RF
OK on Low Fuse changed to D7. I found the original post - message
toggle quoted message
Show quoted text
#40742, 12/03/19. in it Hans stated: "Note that from now on we will supply QCX chips with low fuse 0xD7 not 0xF7. The new recommendation will be 0xD7. The old F7 has a 65ms delay on start-up for slowly rising power line but this is NOT required when you are using a Brownout Detector bit since the brownout logic will hold the reset anyway until the power line comes up (ATmega328 datasheet). D7 removes the 65ms startup delay." ------ Original Message ------
From: "Alan G4ZFQ" <alan4alan@...> To: QRPLabs@groups.io Sent: 11/1/2020 7:55:32 AM Subject: Re: [QRPLabs] #qcx Firmware 1.06 release StevenYes, except the Low fuse changed to D7, was it to remove delay? But not really any point in changing, it's just theoretically correct. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus |
|
|
|
Tim Keene
I also have been having basically the same problems with my QCX 40, I just have not made time to work on it yet. I got it few months ago....just before the QCX+ came out. My processor tag says T1.04. The rig works fine and normal until I connect the QLG1. When connected it starts acting weird. I have a hard time setting parameters in the menu for example setting the keyer. I have to keep turning the encoder back and forth to finally select what I want. Some of the menus come up with settings that should not be there like the frame rate will come up as DM64, my grid square. When trying to calibrate the system or Cal ref oscillators I freezes up until I turn the encoder again between them until it finally works. The QLG1 work perfectly with my other 2 QCX's.
Is it my rig or do I need to get a new processor? Or I guess I could swap out one of the other chips from one of the other QCX's. Let me know what you folks think. Tim - K5DEZ |
|
|
|
Hans Summers
Hi Tim I also have been having basically the same problems with my QCX 40, I just have not made time to work on it yet. I got it few months ago....just before the QCX+ came out. My processor tag says T1.04. The rig works fine and normal until I connect the QLG1. When connected it starts acting weird. I have a hard time setting parameters in the menu for example setting the keyer. I have to keep turning the encoder back and forth to finally select what I want. Some of the menus come up with settings that should not be there like the frame rate will come up as DM64, my grid square. You aren't supposed to connect the GPS while you are editing menus! You are only supposed to connect the GPS during calibration (menus 8.11, 8.12 and 8.13) and when the beacon is switched on. The GPS RxD and 1pps are using the same pins as the paddle. So when the GPS signals change, it is the same as closing the paddle. The manual does say all this. However, several people didn't read that part of the manual, evidently, and then their GPS was keying the radio with 100% duty cycle, and perhaps into mismatched or absent load, and people reported PA transistors destroyed. Therefore in version 1.03 (03-Dec-2019) I added some code to automatically detect serial data on the paddle inputs, rather than real keying, and if detected, protect the QCX before any damage can occur, by putting it temporarily into "Practice mode" automatically (no RF output is generated). BUT, it is still the case that it is WRONG to connect the GPS except during calibration or beacon operation. If you have the GPS connected while you are trying to edit menu parameters, then yes, it will corrupt things. When trying to calibrate the system or Cal ref oscillators I freezes up until I turn the encoder again between them until it finally works. This is a minor thing which has always been present in all versions of the firmware. Not new... I do need to figure out the cause. Strangely, I can't reproduce it here! The QLG1 work perfectly with my other 2 QCX's. Most probably there is some difference in configuration parameters setting between them. For example in the CW decoder menu, whether the decoder is on or off for editing. Is it my rig or do I need to get a new processor? Or I guess I could swap out one of the other chips from one of the other QCX's. None of the above! Let me know what you folks think. I think everything is normal :-) No new chip needed, no QLG1 problem, no QCX problem... frankly, just an op problem :-) as is written in the manual - don't connect the GPS except in 8.11, 8.12, 8.13 or when Beacon is switched to ON! 73 Hans G0UPL http://qrp-labs.com |
|
|
|
Z32ZZZ
Hi Hans,
GPS Info menu 8.13 was a neat feature, quite informative, interesting, I used a lot, checking how GPS behaves. Is there strong reason removing it? 73 Zoran |
|
|
|
Shane Justice <justshane@...>
I, too, will miss having the GPS status screen. I suspect the reason it was removed was to provide more memory for new, higher-value functions. 73, Shane KE7TR Hi Hans, |
|
|
|
On Sun, Nov 8, 2020 at 3:09 PM Shane Justice <justshane@...> wrote:
|
|
|
|
Dusted off my QCX (last update 1.00f) and flashed 1.06. Had some errors on Win10 20H2 until I ran new arduino install as administrator then presto! Wow great firmware and great work!!! New fun with eyes fixed (cataracts). I am so impressed I ordered another unit (different band) built w/case! :-).
|
|
|