#qcx Firmware 1.06 release #qcx


Richard Clemens
 

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! :-). 


kb8aob



Ronald Taylor
 

Hans answered this in this post.   https://groups.io/g/QRPLabs/topic/78013491#55111 

Ron

On Sun, Nov 8, 2020 at 3:09 PM Shane Justice <justshane@...> wrote:
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




On Nov 8, 2020 at 14:44, Z32ZZZ <zj0369@...> wrote:

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




On Nov 8, 2020 at 14:44, Z32ZZZ <zj0369@...> wrote:

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


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


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 


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
 


Steven Dick, K1RF
 

OK on Low Fuse changed to D7. I found the original post - message
#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

Steven


I believe the fuse settings should be:
Extended fuse: 0xFC or equivalently 0x04
Low Fuse: 0xF7
High fuse: 0xD1 (adds 65mS start up delay). Was 0xF7.
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





--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


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 


Al Holt
 

Michael Greene,
It's working in v.106. no lowercase letters, but a good way to tag it.
--Al


Michael N6QP
 

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
 

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


Daniel Conklin
 

I flashed my 40 meter QCX with no issues. I'm looking forward to the LCD mini circuit. 
--
73, Dan - W2DLC


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


Alan G4ZFQ
 

Steven

I believe the fuse settings should be:
Extended fuse: 0xFC or equivalently 0x04
Low Fuse: 0xF7
High fuse: 0xD1 (adds 65mS start up delay). Was 0xF7.
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


Steven Dick, K1RF
 

While were at it, what are the current recommended fuse settings to go along with version 1.06? I know I can leave them unchanged and it worked fine for me before.

I believe the fuse settings should be:
Extended fuse: 0xFC or equivalently 0x04
Low Fuse: 0xF7
High fuse: 0xD1 (adds 65mS start up delay). Was 0xF7.

I got these from message # 24845, 6/25/18 (original definition)  and 40743, 12/03/19 (change for 65mS startup delay for 50 watt amp).

I seem to recall there was one more change having to do with faster bootup but I couldn't find the message.  Thanks,

-Steve K1RF

------ Original Message ------
From: "Hans Summers" <hans.summers@...>
Sent: 10/30/2020 11:05:30 AM
Subject: [QRPLabs] #qcx Firmware 1.06 release

Hi all

This is to notify you of the release of firmware version 1.06:
This version is compatible with all models: QCX, QCX+ and the imminent QCX-mini; it was originally intended to support the backlight control feature in the QCX-mini but as you can see below, the scope expanded considerably!
If any anomalies are noticed please let me know As Soon As Possible!

If you want to buy the chip, you can get it here: http://shop.qrp-labs.com/firmware/qcxchip

From this moment forward, all kits and chips will be shipped with this firmware version.

I have now also split out the firmware operating manual from the main QCX manuals into its own Operating manual, since this firmware applies to all three models QCX, QCX+ and QCX-mini and I don't want to have to update all three which will get very confusing for everyone. You can download the operating manual from the manuals section of the QCX+ page http://qrp-labs.com/qcxp and I will also add it to the QCX and QCX-mini pages. Or click here to read it: http://qrp-labs.com/images/qcxp/firmware/1.06/OpMan106.pdf

There are 20 changes in all, which are listed below. But I want to draw your attention to the following main things:

a) There are quite a few improvements to the CAT interface (computer control). Some of these are bug fixes and should make the operation more reliable, there were some issues with the circular text buffers used, and I have resolved these as well as improved some aspects of the timing, and changed some of the command responses. 

b) This version will work on 6m (using standard 25MHz TCXO or 27MHz crystal). We can supply a LPF for any of the bands 6, 10, 12, 15 which the QCX is not normally supplied with. You can expect that as you go higher in frequency, the transmit power output will decrease and the receiver sensitivity will decrease. 

c) This version will work on 160m, IF you use a 12MHz crystal instead of the supplied 27MHz crystal. It won't work with the 25MHz TCXO option or the supplied 27MHz crystal. You will also need to modify the T1 and other components. This should be considered experimental. 

d) This version has support for prosigns AR, KN and SK (VA). On CW decode, they appear on the display as AR, KN and SK. There is a new menu entry "5.7 VA" which if set to ON, shows VA not SK. This allows you to have your preference (there was a long and inconclusive debate on this point, some months back). You can also use prosigns in stored messages in which case you prefix the two prosign letters with a _ character; that will actually let you string together ANY two characters, not just the three supported by the decoder. 

e) Sidetone is now enabled during CW beacon operation. 

f) The annoying "backwave" (attenuated low transmit power) in between transmitted symbols, when using semi-QSK mode, has been resolved. Now no milliwatts are transmitted between your keydowns. 

g) Sidetone volume now beeps every time you change it in the menu (e.g. by rotating the rotary encoder while setting it) to give you an audible feedback of what it will sound like. 

h) The GPS Info menu display option has been removed, and I have made improvements to the handling of the 8.11 and 8.12 calibration menu options, to make them more robust against incorrect calibration (for example of satellite lock is lost during calibration). It also resolves the long-standing GPS checksum bug which caused some GPS (non QLG1) not to work properly, manifested as display of -- in the GPS Info screen (which is now no longer included anyway). 

i) There is a new menu item 7.11 to control the backlight of the QCX-mini, it can also be toggled temporarily by double-pressing the rotary shaft encoder button - this does not save in EEPROM, so is not remembered on power up. The 7.11 menu setting IS saved in EEPROM and remembered on power up. This function has no effect in QCX and QCX+; it is only applicable to the QCX-mini which has the backlight control. 

Full list of changes:
  1. CAT: OM command response shortened to OMQC;
  2. CAT: KY command set text is now a circular buffer; if full, it returns ?;
  3. CAT: KY command get is KYn; where n = 0 if buffer < 75% full, 1 if buffer > 75% full, 2 if buffer empty and previous sending is complete
  4. CAT: Sent message via KY is immediately decoded on screen at message completion, without delay or corruption by receive signals
  5. CAT: TB command get, the 3rd response character is now number of remaining characters to be sent;
  6. CAT: QU command set now clears the unsoliticted update event flags
  7. Experimental modification for better output signal on 6m band
  8. Enable sidetone during CW beacon operation
  9. Removed GPS Data menu, and now Cal menus show "Waiting" while waiting for GPS lock, protect against from missed 1pps
  10. Sidetone volume now beeps every time it is changed while in the menu
  11. New menu item 7.11 controls Backlight (QCX-mini only)
  12. Double-click rotary encoder toggles backlight temporarily (not saved to EEPROM)
  13. Experimental support for 160m operation; this requires a 12MHz reference crystal for the Si5351A
  14. Eliminate low power "backwave" during key-up in Semi-QSK mode
  15. Added Morse prosigns AR, KN and SK/VA. New menu "5.7 VA" if set to ON selects VA, otherwise SK
  16. Bug fix: When beacon enabled, started on ref freq at power up, until you went into a sub-menu and exited
  17. Bug fix: CAT: Corrected bug command circular buffer that corrupted commands sometimes
  18. Bug fix: CAT: Increased reliability of comms by increasing wait timeout for incoming characters
  19. Bug fix: CAT: If the command buffer overflows, truncate the current CAT command to prevent the overflow
  20. Bug fix: CAT: Updating keyer speed can no longer cause occasional display corruption
73 Hans G0UPL
http://qrp-labs.com

Virus-free. www.avast.com


Evan Hand
 

Thank you all!

I have the new version now and will try flashing my current QCX+ after I get the new chip (I do not want to flash without a backup :-).

73
Evan
AC9TU


Hans Summers
 

Hi Dean

I mentioned it only because it doesn't seem intuitive. After pressing select as the manual states. I assumed that was all that was needed, 
 Now its mentioned, yes as previous versions. You need to reach for the encoder to start the magic :))
Observation not a moan!
Got it going, so I'm one happy camper.

Thanks for the observation! I agree it isn't intuitive, I don't like it. I need to find out what's causing it as it isn't supposed to be like that. But it isn't a show-stopper either. I'll make a note in the manual on how to do it. So even though it has always been this way and isn't a new issue, I think the new changes in 1.06 perhaps make it more irritating. 

Evan, Ted

The 1.06 firmware is here:

I don't consider it beta. Several people gave already tested beta versions extensively. The only reason I haven't posted the link in the group files section and haven't updated the firmware page version history, is that I ran out of time on Friday evening. 

I released it on Friday afternoon so that if the wider audience found any major issues I have some opportunity to fix them before the chips start getting sent out on Monday. So far, everything seems good. The one peculiar one (#1) was resolved by re-flashing the chips. The other GPS calibration weirdness (#2) is an ever-existing behaviour not new, and anyway easily worked around. 

The other thing I will do on Monday is post the QCX-mini circuit here so that anyone can, if they wish, add the backlight control circuit to a QCX or QCX+. The blue LCD module isn't really readable without the backlight. But:

a) it may be of interest to people who have modified their QCX/QCX+ to use a yellow/green type display that IS viewable without backlight

b) people who have the standard blue backlight LCD module could actually use this circuit to have say, a bright backlight and a dim backlight mode (rather than on, off). That might be cool too.

Many thanks all, for the feedback so far! 

73 Hans G0UPL 


Phil N6WKZ
 

Evan,

http://qrp-labs.com/images/qcxp/firmware/1.06/T106.zip

73 Phil N6WKZ

On 10/31/2020 4:04 PM, Evan Hand wrote:

Hans,

Where is the 1.06 firmware file?  It is not on the files section as far as I can tell.  We are getting ready for a group build and want all of us on the same version.

73
Evan
AC9TU


Ted 2E0THH
 

Evan
There is a link at the very top of this page.
I guess it still is in Beta so won't be in the full release file page until Hans is happy   

73s Ted
2E0THH


Evan Hand
 

Hans,

Where is the 1.06 firmware file?  It is not on the files section as far as I can tell.  We are getting ready for a group build and want all of us on the same version.

73
Evan
AC9TU