|
All
Just to let you know, I worked on the v2.02 firmware over the last week and have completed it, I am now testing. On Monday I am planning to have a few sent to some people who can also do some testing. I have managed to incorporate ALL requests, and fix ALL reported issues. I made careful notes since the launch of the U2 kit and I don't think I have missed any requests that I agreed to include, or bug fixes for any issues.
However code space is extremely tight and I had to do some space-saving modifications, including removal of a few unnecessary features! To be precise, the code currently occupies 99.9% of the available space, there are just 14 bytes of 16,384 spare!
List of changes:
1) GPS: I put the GPS back to as close as I could, to how it was done in the U1, since that seemed to work well. The existing U2 method in v2.01 worked with some GPS modules but apparently was much more fussy than the U1 kit. Note that there is no longer an "Inv. GPS" menu item, since the U1 will trigger off the correct edge by itself.?
2) DDS resolution on high frequencies: I have corrected the precision issue in the arithmetic, so now you get full accuracy shift steps at any operating frequency.?
3) Removed the upper frequency limit of approx 42.5MHz, so you can now use the full range available from the DDS
4) New mode WSPR-15 is now supported, for experimental use on LF bands (8 times slower WSPR tones, 8 times closer together). Note that I will also be providing Low Pass Filter kits for 135kHz and 475kHz (600m) bands.
5) New mode "FSK" which is a fast FSK mode for 10m beaconing, where the speed setting is interpreted in words per minute. The "FSK (Hz)" setting is now 3 digits (default "004" i.e. 4Hz) so that shift can be up to 999Hz. Note that I removed the "Inv. FSK" parameter, because I had never heard of anyone using it, and I needed desperately to create some code space.?
6) Added an indication on the display when the kit is GPS locked. Of all the enhancements and bug fixes, this one took the longest to do!
7) Added 1 digit to the baud rate setting, so that it can now handle 115kbps (this was a request for support of a particular GPS module). At the same time I removed the number of bits in the data word setting, which is the right-most digit of the "GPS Baud" parameter. I haven't heard of a GPS which uses other than 8 bit data words, so it seemed superfluous. Getting rid of it saved me some code space which I could use for other requested features. The default "GPS Baud" setting is now "009600,01,1".
8) Removed the DDS "reset" every time the frequency was updated, which caused the frequency to briefly go to zero before being updated to the new frequency. This should improve the spectral purity of the output.?
9) Put a "stop" on the cycling through characters when you are editing the Message (and other text) parameters, by holding down the right button. The character cycling now stops at Z, 9 and the Enter symbol. In order to continue cycling through, you have to release the right button and start pressing it again. This will make it easier to program the text parameters e.g. Message.
10) Moved the "Time" parameter menu to the start of the menu, when the kit is in WSPR mode. This is because the Time parameter is what you would most commonly want to adjust, when operating in WSPR mode, if you did not have a GPS to regulate it. In other modes, "Time" still comes right at the end of the menu.
11) CW, FSKCW, DFCW, QRSS and FSK modes can now contain the '/' character in the message
12) Bug fix (cosmetic only): When setting the time, the 10 minutes digit incorrectly allowed numbers >= 6. So it was possible to set a time such as 15:89.?
13) Bug fix (cosmetic only): If you went back in to the time parameter to edit it a second time immediately after finishing the first edit, the display was overwritten incorrectly, with the system clock frequency display.
14) Bug fix (cosmetic only): If using FSKCW mode an 10 second dit speed (for example), in the interval between frames the LCD display did not have space to show the seconds digit of the clock. I have now changed the "Waiting" screen so that it does not show the mode etc., it now only shows the time and the minutes to wait until. E.g. "15:43:21 >50" means 3:43pm and 21 seconds, and the kit is waiting for minute 50 to start the next frame. The "Waiting" screen also shows the GPS heartbeat if a GPS is connected and GPS lock is successful.
15) Bug fix: In FSKCW mode, the GPS frequency stabilisation operating in the waiting period between messages, only worked the first time after cycling through the menu. Subsequent waiting periods did not perform the calibration because the kit was always in key-down (transmitting the low tone between messages).?
16) I changed the default speed setting to 006 for no other reason than that I think 6 second dits are more common and useful than 3 second dits, so make a better default.
17) I have removed the mode message "CW Ident" when transmitting the CW callsign identifier, and replaced it with just the text "CW". This was purely a space-saving measure - sacrificing something unnecessary for the sake of gaining more space to include important features and fixes.?
73 Hans G0UPL
|
Hi Hans (and group),
That's fantastic, I'm sure I speak on behalf of the whole group when I say 'Thank You' for that update and all the work you've put in providing enhancements and fixes.
73 Keith, G6NHU
toggle quoted message
Show quoted text
?
All
Just to let you know, I worked on the v2.02 firmware over the last week and have completed it, I am now testing. On Monday I am planning to have a few sent to some people who can also do some testing. I have managed to incorporate ALL requests, and fix ALL reported issues. I made careful notes since the launch of the U2 kit and I don't think I have missed any requests that I agreed to include, or bug fixes for any issues.
However code space is extremely tight and I had to do some space-saving modifications, including removal of a few unnecessary features! To be precise, the code currently occupies 99.9% of the available space, there are just 14 bytes of 16,384 spare!
List of changes:
1) GPS: I put the GPS back to as close as I could, to how it was done in the U1, since that seemed to work well. The existing U2 method in v2.01 worked with some GPS modules but apparently was much more fussy than the U1 kit. Note that there is no longer an "Inv. GPS" menu item, since the U1 will trigger off the correct edge by itself.?
2) DDS resolution on high frequencies: I have corrected the precision issue in the arithmetic, so now you get full accuracy shift steps at any operating frequency.?
3) Removed the upper frequency limit of approx 42.5MHz, so you can now use the full range available from the DDS
4) New mode WSPR-15 is now supported, for experimental use on LF bands (8 times slower WSPR tones, 8 times closer together). Note that I will also be providing Low Pass Filter kits for 135kHz and 475kHz (600m) bands.
5) New mode "FSK" which is a fast FSK mode for 10m beaconing, where the speed setting is interpreted in words per minute. The "FSK (Hz)" setting is now 3 digits (default "004" i.e. 4Hz) so that shift can be up to 999Hz. Note that I removed the "Inv. FSK" parameter, because I had never heard of anyone using it, and I needed desperately to create some code space.?
6) Added an indication on the display when the kit is GPS locked. Of all the enhancements and bug fixes, this one took the longest to do!
7) Added 1 digit to the baud rate setting, so that it can now handle 115kbps (this was a request for support of a particular GPS module). At the same time I removed the number of bits in the data word setting, which is the right-most digit of the "GPS Baud" parameter. I haven't heard of a GPS which uses other than 8 bit data words, so it seemed superfluous. Getting rid of it saved me some code space which I could use for other requested features. The default "GPS Baud" setting is now "009600,01,1".
8) Removed the DDS "reset" every time the frequency was updated, which caused the frequency to briefly go to zero before being updated to the new frequency. This should improve the spectral purity of the output.?
9) Put a "stop" on the cycling through characters when you are editing the Message (and other text) parameters, by holding down the right button. The character cycling now stops at Z, 9 and the Enter symbol. In order to continue cycling through, you have to release the right button and start pressing it again. This will make it easier to program the text parameters e.g. Message.
10) Moved the "Time" parameter menu to the start of the menu, when the kit is in WSPR mode. This is because the Time parameter is what you would most commonly want to adjust, when operating in WSPR mode, if you did not have a GPS to regulate it. In other modes, "Time" still comes right at the end of the menu.
11) CW, FSKCW, DFCW, QRSS and FSK modes can now contain the '/' character in the message
12) Bug fix (cosmetic only): When setting the time, the 10 minutes digit incorrectly allowed numbers >= 6. So it was possible to set a time such as 15:89.?
13) Bug fix (cosmetic only): If you went back in to the time parameter to edit it a second time immediately after finishing the first edit, the display was overwritten incorrectly, with the system clock frequency display.
14) Bug fix (cosmetic only): If using FSKCW mode an 10 second dit speed (for example), in the interval between frames the LCD display did not have space to show the seconds digit of the clock. I have now changed the "Waiting" screen so that it does not show the mode etc., it now only shows the time and the minutes to wait until. E.g. "15:43:21 >50" means 3:43pm and 21 seconds, and the kit is waiting for minute 50 to start the next frame. The "Waiting" screen also shows the GPS heartbeat if a GPS is connected and GPS lock is successful.
15) Bug fix: In FSKCW mode, the GPS frequency stabilisation operating in the waiting period between messages, only worked the first time after cycling through the menu. Subsequent waiting periods did not perform the calibration because the kit was always in key-down (transmitting the low tone between messages).?
16) I changed the default speed setting to 006 for no other reason than that I think 6 second dits are more common and useful than 3 second dits, so make a better default.
17) I have removed the mode message "CW Ident" when transmitting the CW callsign identifier, and replaced it with just the text "CW". This was purely a space-saving measure - sacrificing something unnecessary for the sake of gaining more space to include important features and fixes.?
73 Hans G0UPL
|
Yes indeed....
Above and beyond the call of duty..
Well done Hans
Philip G4JVF
toggle quoted message
Show quoted text
--- In QRPLabs@..., Keith Maton <nentecular@...> wrote:
Hi Hans (and group),
That's fantastic, I'm sure I speak on behalf of the whole group when I say 'Thank You' for that update and all the work you've put in providing enhancements and fixes.
73 Keith, G6NHU
On 1 Jun 2013, at 16:05, Hans Summers <hans.summers@...> wrote:
All
Just to let you know, I worked on the v2.02 firmware over the last week and have completed it, I am now testing. On Monday I am planning to have a few sent to some people who can also do some testing. I have managed to incorporate ALL requests, and fix ALL reported issues. I made careful notes since the launch of the U2 kit and I don't think I have missed any requests that I agreed to include, or bug fixes for any issues.
However code space is extremely tight and I had to do some space-saving modifications, including removal of a few unnecessary features! To be precise, the code currently occupies 99.9% of the available space, there are just 14 bytes of 16,384 spare!
List of changes:
1) GPS: I put the GPS back to as close as I could, to how it was done in the U1, since that seemed to work well. The existing U2 method in v2.01 worked with some GPS modules but apparently was much more fussy than the U1 kit. Note that there is no longer an "Inv. GPS" menu item, since the U1 will trigger off the correct edge by itself.
2) DDS resolution on high frequencies: I have corrected the precision issue in the arithmetic, so now you get full accuracy shift steps at any operating frequency.
3) Removed the upper frequency limit of approx 42.5MHz, so you can now use the full range available from the DDS
4) New mode WSPR-15 is now supported, for experimental use on LF bands (8 times slower WSPR tones, 8 times closer together). Note that I will also be providing Low Pass Filter kits for 135kHz and 475kHz (600m) bands.
5) New mode "FSK" which is a fast FSK mode for 10m beaconing, where the speed setting is interpreted in words per minute. The "FSK (Hz)" setting is now 3 digits (default "004" i.e. 4Hz) so that shift can be up to 999Hz. Note that I removed the "Inv. FSK" parameter, because I had never heard of anyone using it, and I needed desperately to create some code space.
6) Added an indication on the display when the kit is GPS locked. Of all the enhancements and bug fixes, this one took the longest to do!
7) Added 1 digit to the baud rate setting, so that it can now handle 115kbps (this was a request for support of a particular GPS module). At the same time I removed the number of bits in the data word setting, which is the right-most digit of the "GPS Baud" parameter. I haven't heard of a GPS which uses other than 8 bit data words, so it seemed superfluous. Getting rid of it saved me some code space which I could use for other requested features. The default "GPS Baud" setting is now "009600,01,1".
8) Removed the DDS "reset" every time the frequency was updated, which caused the frequency to briefly go to zero before being updated to the new frequency. This should improve the spectral purity of the output.
9) Put a "stop" on the cycling through characters when you are editing the Message (and other text) parameters, by holding down the right button. The character cycling now stops at Z, 9 and the Enter symbol. In order to continue cycling through, you have to release the right button and start pressing it again. This will make it easier to program the text parameters e.g. Message.
10) Moved the "Time" parameter menu to the start of the menu, when the kit is in WSPR mode. This is because the Time parameter is what you would most commonly want to adjust, when operating in WSPR mode, if you did not have a GPS to regulate it. In other modes, "Time" still comes right at the end of the menu.
11) CW, FSKCW, DFCW, QRSS and FSK modes can now contain the '/' character in the message
12) Bug fix (cosmetic only): When setting the time, the 10 minutes digit incorrectly allowed numbers >= 6. So it was possible to set a time such as 15:89.
13) Bug fix (cosmetic only): If you went back in to the time parameter to edit it a second time immediately after finishing the first edit, the display was overwritten incorrectly, with the system clock frequency display.
14) Bug fix (cosmetic only): If using FSKCW mode an 10 second dit speed (for example), in the interval between frames the LCD display did not have space to show the seconds digit of the clock. I have now changed the "Waiting" screen so that it does not show the mode etc., it now only shows the time and the minutes to wait until. E.g. "15:43:21 >50" means 3:43pm and 21 seconds, and the kit is waiting for minute 50 to start the next frame. The "Waiting" screen also shows the GPS heartbeat if a GPS is connected and GPS lock is successful.
15) Bug fix: In FSKCW mode, the GPS frequency stabilisation operating in the waiting period between messages, only worked the first time after cycling through the menu. Subsequent waiting periods did not perform the calibration because the kit was always in key-down (transmitting the low tone between messages).
16) I changed the default speed setting to 006 for no other reason than that I think 6 second dits are more common and useful than 3 second dits, so make a better default.
17) I have removed the mode message "CW Ident" when transmitting the CW callsign identifier, and replaced it with just the text "CW". This was purely a space-saving measure - sacrificing something unnecessary for the sake of gaining more space to include important features and fixes.
73 Hans G0UPL
|
Sounds perfect - well done !!!!
73 de Andy G0FTD (currently running a U2 nicely on 28,000,825 FSK)
|
" Yes indeed....Above and beyond the call of duty..
Well done Hans?
Philip G4JVF"
Here here!
Great news.?
Three cheers for Hans!
Bzb Tony
On 1 June 2013 17:57, Philip <pcteee@...> wrote:
?
Yes indeed....
Above and beyond the call of duty..
Well done Hans
Philip G4JVF
--- In QRPLabs@..., Keith Maton
>
> Hi Hans (and group),
>
> That's fantastic, I'm sure I speak on behalf of the whole group when I say 'Thank You' for that update and all the work you've put in providing enhancements and fixes.
>
> 73 Keith, G6NHU
>
>
> On 1 Jun 2013, at 16:05, Hans Summers wrote:
>
> >
> >
> > All
> >
> > Just to let you know, I worked on the v2.02 firmware over the last week and have completed it, I am now testing. On Monday I am planning to have a few sent to some people who can also do some testing. I have managed to incorporate ALL requests, and fix ALL reported issues. I made careful notes since the launch of the U2 kit and I don't think I have missed any requests that I agreed to include, or bug fixes for any issues.
> >
> > However code space is extremely tight and I had to do some space-saving modifications, including removal of a few unnecessary features! To be precise, the code currently occupies 99.9% of the available space, there are just 14 bytes of 16,384 spare!
> >
> > List of changes:
> >
> > 1) GPS: I put the GPS back to as close as I could, to how it was done in the U1, since that seemed to work well. The existing U2 method in v2.01 worked with some GPS modules but apparently was much more fussy than the U1 kit. Note that there is no longer an "Inv. GPS" menu item, since the U1 will trigger off the correct edge by itself.
> >
> > 2) DDS resolution on high frequencies: I have corrected the precision issue in the arithmetic, so now you get full accuracy shift steps at any operating frequency.
> >
> > 3) Removed the upper frequency limit of approx 42.5MHz, so you can now use the full range available from the DDS
> >
> > 4) New mode WSPR-15 is now supported, for experimental use on LF bands (8 times slower WSPR tones, 8 times closer together). Note that I will also be providing Low Pass Filter kits for 135kHz and 475kHz (600m) bands.
> >
> > 5) New mode "FSK" which is a fast FSK mode for 10m beaconing, where the speed setting is interpreted in words per minute. The "FSK (Hz)" setting is now 3 digits (default "004" i.e. 4Hz) so that shift can be up to 999Hz. Note that I removed the "Inv. FSK" parameter, because I had never heard of anyone using it, and I needed desperately to create some code space.
> >
> > 6) Added an indication on the display when the kit is GPS locked. Of all the enhancements and bug fixes, this one took the longest to do!
> >
> > 7) Added 1 digit to the baud rate setting, so that it can now handle 115kbps (this was a request for support of a particular GPS module). At the same time I removed the number of bits in the data word setting, which is the right-most digit of the "GPS Baud" parameter. I haven't heard of a GPS which uses other than 8 bit data words, so it seemed superfluous. Getting rid of it saved me some code space which I could use for other requested features. The default "GPS Baud" setting is now "009600,01,1".
> >
> > 8) Removed the DDS "reset" every time the frequency was updated, which caused the frequency to briefly go to zero before being updated to the new frequency. This should improve the spectral purity of the output.
> >
> > 9) Put a "stop" on the cycling through characters when you are editing the Message (and other text) parameters, by holding down the right button. The character cycling now stops at Z, 9 and the Enter symbol. In order to continue cycling through, you have to release the right button and start pressing it again. This will make it easier to program the text parameters e.g. Message.
> >
> > 10) Moved the "Time" parameter menu to the start of the menu, when the kit is in WSPR mode. This is because the Time parameter is what you would most commonly want to adjust, when operating in WSPR mode, if you did not have a GPS to regulate it. In other modes, "Time" still comes right at the end of the menu.
> >
> > 11) CW, FSKCW, DFCW, QRSS and FSK modes can now contain the '/' character in the message
> >
> > 12) Bug fix (cosmetic only): When setting the time, the 10 minutes digit incorrectly allowed numbers >= 6. So it was possible to set a time such as 15:89.
> >
> > 13) Bug fix (cosmetic only): If you went back in to the time parameter to edit it a second time immediately after finishing the first edit, the display was overwritten incorrectly, with the system clock frequency display.
> >
> > 14) Bug fix (cosmetic only): If using FSKCW mode an 10 second dit speed (for example), in the interval between frames the LCD display did not have space to show the seconds digit of the clock. I have now changed the "Waiting" screen so that it does not show the mode etc., it now only shows the time and the minutes to wait until. E.g. "15:43:21 >50" means 3:43pm and 21 seconds, and the kit is waiting for minute 50 to start the next frame. The "Waiting" screen also shows the GPS heartbeat if a GPS is connected and GPS lock is successful.
> >
> > 15) Bug fix: In FSKCW mode, the GPS frequency stabilisation operating in the waiting period between messages, only worked the first time after cycling through the menu. Subsequent waiting periods did not perform the calibration because the kit was always in key-down (transmitting the low tone between messages).
> >
> > 16) I changed the default speed setting to 006 for no other reason than that I think 6 second dits are more common and useful than 3 second dits, so make a better default.
> >
> > 17) I have removed the mode message "CW Ident" when transmitting the CW callsign identifier, and replaced it with just the text "CW". This was purely a space-saving measure - sacrificing something unnecessary for the sake of gaining more space to include important features and fixes.
> >
> > 73 Hans G0UPL
> >
> >
> >
> >
>
|
I second that!
------------------------------
toggle quoted message
Show quoted text
On Sat, Jun 1, 2013 9:57 AM PDT Philip wrote: Yes indeed....
Above and beyond the call of duty..
Well done Hans
Philip G4JVF
--- In QRPLabs@..., Keith Maton <nentecular@...> wrote:
Hi Hans (and group),
That's fantastic, I'm sure I speak on behalf of the whole group when I say 'Thank You' for that update and all the work you've put in providing enhancements and fixes.
73 Keith, G6NHU
On 1 Jun 2013, at 16:05, Hans Summers <hans.summers@...> wrote:
All
Just to let you know, I worked on the v2.02 firmware over the last week and have completed it, I am now testing. On Monday I am planning to have a few sent to some people who can also do some testing. I have managed to incorporate ALL requests, and fix ALL reported issues. I made careful notes since the launch of the U2 kit and I don't think I have missed any requests that I agreed to include, or bug fixes for any issues.
However code space is extremely tight and I had to do some space-saving modifications, including removal of a few unnecessary features! To be precise, the code currently occupies 99.9% of the available space, there are just 14 bytes of 16,384 spare!
List of changes:
1) GPS: I put the GPS back to as close as I could, to how it was done in the U1, since that seemed to work well. The existing U2 method in v2.01 worked with some GPS modules but apparently was much more fussy than the U1 kit. Note that there is no longer an "Inv. GPS" menu item, since the U1 will trigger off the correct edge by itself.
2) DDS resolution on high frequencies: I have corrected the precision issue in the arithmetic, so now you get full accuracy shift steps at any operating frequency.
3) Removed the upper frequency limit of approx 42.5MHz, so you can now use the full range available from the DDS
4) New mode WSPR-15 is now supported, for experimental use on LF bands (8 times slower WSPR tones, 8 times closer together). Note that I will also be providing Low Pass Filter kits for 135kHz and 475kHz (600m) bands.
5) New mode "FSK" which is a fast FSK mode for 10m beaconing, where the speed setting is interpreted in words per minute. The "FSK (Hz)" setting is now 3 digits (default "004" i.e. 4Hz) so that shift can be up to 999Hz. Note that I removed the "Inv. FSK" parameter, because I had never heard of anyone using it, and I needed desperately to create some code space.
6) Added an indication on the display when the kit is GPS locked. Of all the enhancements and bug fixes, this one took the longest to do!
7) Added 1 digit to the baud rate setting, so that it can now handle 115kbps (this was a request for support of a particular GPS module). At the same time I removed the number of bits in the data word setting, which is the right-most digit of the "GPS Baud" parameter. I haven't heard of a GPS which uses other than 8 bit data words, so it seemed superfluous. Getting rid of it saved me some code space which I could use for other requested features. The default "GPS Baud" setting is now "009600,01,1".
8) Removed the DDS "reset" every time the frequency was updated, which caused the frequency to briefly go to zero before being updated to the new frequency. This should improve the spectral purity of the output.
9) Put a "stop" on the cycling through characters when you are editing the Message (and other text) parameters, by holding down the right button. The character cycling now stops at Z, 9 and the Enter symbol. In order to continue cycling through, you have to release the right button and start pressing it again. This will make it easier to program the text parameters e.g. Message.
10) Moved the "Time" parameter menu to the start of the menu, when the kit is in WSPR mode. This is because the Time parameter is what you would most commonly want to adjust, when operating in WSPR mode, if you did not have a GPS to regulate it. In other modes, "Time" still comes right at the end of the menu.
11) CW, FSKCW, DFCW, QRSS and FSK modes can now contain the '/' character in the message
12) Bug fix (cosmetic only): When setting the time, the 10 minutes digit incorrectly allowed numbers >= 6. So it was possible to set a time such as 15:89.
13) Bug fix (cosmetic only): If you went back in to the time parameter to edit it a second time immediately after finishing the first edit, the display was overwritten incorrectly, with the system clock frequency display.
14) Bug fix (cosmetic only): If using FSKCW mode an 10 second dit speed (for example), in the interval between frames the LCD display did not have space to show the seconds digit of the clock. I have now changed the "Waiting" screen so that it does not show the mode etc., it now only shows the time and the minutes to wait until. E.g. "15:43:21 >50" means 3:43pm and 21 seconds, and the kit is waiting for minute 50 to start the next frame. The "Waiting" screen also shows the GPS heartbeat if a GPS is connected and GPS lock is successful.
15) Bug fix: In FSKCW mode, the GPS frequency stabilisation operating in the waiting period between messages, only worked the first time after cycling through the menu. Subsequent waiting periods did not perform the calibration because the kit was always in key-down (transmitting the low tone between messages).
16) I changed the default speed setting to 006 for no other reason than that I think 6 second dits are more common and useful than 3 second dits, so make a better default.
17) I have removed the mode message "CW Ident" when transmitting the CW callsign identifier, and replaced it with just the text "CW". This was purely a space-saving measure - sacrificing something unnecessary for the sake of gaining more space to include important features and fixes.
73 Hans G0UPL
|
Great News Hans !!
We all enjoy the fruits of your labor and more especially the
passion which you perform the tasks with .
You bring many of us , the world over , untold hours of great joy ,
building , using , learning from , and enjoying your always great
projects .
Thank you.
Best 73 ,
Charlie , W5COV
toggle quoted message
Show quoted text
?
All
Just to let you know, I worked on the v2.02 firmware
over the last week and have completed it, I am now
testing. On Monday I am planning to have a few sent to
some people who can also do some testing. I have managed
to incorporate ALL requests, and fix ALL reported
issues. I made careful notes since the launch of the U2
kit and I don't think I have missed any requests that I
agreed to include, or bug fixes for any issues.
However code space is extremely tight and I had to do
some space-saving modifications, including removal of a
few unnecessary features! To be precise, the code
currently occupies 99.9% of the available space, there
are just 14 bytes of 16,384 spare!
List of changes:
1) GPS: I put the GPS back to as close as I could, to
how it was done in the U1, since that seemed to work
well. The existing U2 method in v2.01 worked with some
GPS modules but apparently was much more fussy than the
U1 kit. Note that there is no longer an "Inv. GPS" menu
item, since the U1 will trigger off the correct edge by
itself.?
2) DDS resolution on high frequencies: I have
corrected the precision issue in the arithmetic, so now
you get full accuracy shift steps at any operating
frequency.?
3) Removed the upper frequency limit of approx
42.5MHz, so you can now use the full range available
from the DDS
4) New mode WSPR-15 is now supported, for
experimental use on LF bands (8 times slower WSPR tones,
8 times closer together). Note that I will also be
providing Low Pass Filter kits for 135kHz and 475kHz
(600m) bands.
5) New mode "FSK" which is a fast FSK mode for 10m
beaconing, where the speed setting is interpreted in
words per minute. The "FSK (Hz)" setting is now 3 digits
(default "004" i.e. 4Hz) so that shift can be up to
999Hz. Note that I removed the "Inv. FSK" parameter,
because I had never heard of anyone using it, and I
needed desperately to create some code space.?
6) Added an indication on the display when the kit is
GPS locked. Of all the enhancements and bug fixes, this
one took the longest to do!
7) Added 1 digit to the baud rate setting, so that it
can now handle 115kbps (this was a request for support
of a particular GPS module). At the same time I removed
the number of bits in the data word setting, which is
the right-most digit of the "GPS Baud" parameter. I
haven't heard of a GPS which uses other than 8 bit data
words, so it seemed superfluous. Getting rid of it saved
me some code space which I could use for other requested
features. The default "GPS Baud" setting is now
"009600,01,1".
8) Removed the DDS "reset" every time the frequency
was updated, which caused the frequency to briefly go to
zero before being updated to the new frequency. This
should improve the spectral purity of the output.?
9) Put a "stop" on the cycling through characters
when you are editing the Message (and other text)
parameters, by holding down the right button. The
character cycling now stops at Z, 9 and the Enter
symbol. In order to continue cycling through, you have
to release the right button and start pressing it again.
This will make it easier to program the text parameters
e.g. Message.
10) Moved the "Time" parameter menu to the start of
the menu, when the kit is in WSPR mode. This is because
the Time parameter is what you would most commonly want
to adjust, when operating in WSPR mode, if you did not
have a GPS to regulate it. In other modes, "Time" still
comes right at the end of the menu.
11) CW, FSKCW, DFCW, QRSS and FSK modes can now
contain the '/' character in the message
12) Bug fix (cosmetic only): When setting the time,
the 10 minutes digit incorrectly allowed numbers >=
6. So it was possible to set a time such as 15:89.?
13) Bug fix (cosmetic only): If you went back in to
the time parameter to edit it a second time immediately
after finishing the first edit, the display was
overwritten incorrectly, with the system clock frequency
display.
14) Bug fix (cosmetic only): If using FSKCW mode an
10 second dit speed (for example), in the interval
between frames the LCD display did not have space to
show the seconds digit of the clock. I have now changed
the "Waiting" screen so that it does not show the mode
etc., it now only shows the time and the minutes to wait
until. E.g. "15:43:21 >50" means 3:43pm and 21
seconds, and the kit is waiting for minute 50 to start
the next frame. The "Waiting" screen also shows the GPS
heartbeat if a GPS is connected and GPS lock is
successful.
15) Bug fix: In FSKCW mode, the GPS frequency
stabilisation operating in the waiting period between
messages, only worked the first time after cycling
through the menu. Subsequent waiting periods did not
perform the calibration because the kit was always in
key-down (transmitting the low tone between messages).?
16) I changed the default speed setting to 006 for no
other reason than that I think 6 second dits are more
common and useful than 3 second dits, so make a better
default.
17) I have removed the mode message "CW Ident" when
transmitting the CW callsign identifier, and replaced it
with just the text "CW". This was purely a space-saving
measure - sacrificing something unnecessary for the sake
of gaining more space to include important features and
fixes.?
73 Hans G0UPL
|
As always: Well Done! BUT:
Don't forget your wife ... otherwise you and afterwards the community will get into trouble ;-)
72 de Hajo DL1SDZ
On Sat, Jun 1, 2013 at 7:31 PM, Charlie , W5COV <cvest@...> wrote:
Great News Hans !!
We all enjoy the fruits of your labor and more especially the
passion which you perform the tasks with .
You bring many of us , the world over , untold hours of great joy ,
building , using , learning from , and enjoying your always great
projects .
Thank you.
Best 73 ,
Charlie , W5COV
?
All
Just to let you know, I worked on the v2.02 firmware
over the last week and have completed it, I am now
testing. On Monday I am planning to have a few sent to
some people who can also do some testing. I have managed
to incorporate ALL requests, and fix ALL reported
issues. I made careful notes since the launch of the U2
kit and I don't think I have missed any requests that I
agreed to include, or bug fixes for any issues.
However code space is extremely tight and I had to do
some space-saving modifications, including removal of a
few unnecessary features! To be precise, the code
currently occupies 99.9% of the available space, there
are just 14 bytes of 16,384 spare!
List of changes:
1) GPS: I put the GPS back to as close as I could, to
how it was done in the U1, since that seemed to work
well. The existing U2 method in v2.01 worked with some
GPS modules but apparently was much more fussy than the
U1 kit. Note that there is no longer an "Inv. GPS" menu
item, since the U1 will trigger off the correct edge by
itself.?
2) DDS resolution on high frequencies: I have
corrected the precision issue in the arithmetic, so now
you get full accuracy shift steps at any operating
frequency.?
3) Removed the upper frequency limit of approx
42.5MHz, so you can now use the full range available
from the DDS
4) New mode WSPR-15 is now supported, for
experimental use on LF bands (8 times slower WSPR tones,
8 times closer together). Note that I will also be
providing Low Pass Filter kits for 135kHz and 475kHz
(600m) bands.
5) New mode "FSK" which is a fast FSK mode for 10m
beaconing, where the speed setting is interpreted in
words per minute. The "FSK (Hz)" setting is now 3 digits
(default "004" i.e. 4Hz) so that shift can be up to
999Hz. Note that I removed the "Inv. FSK" parameter,
because I had never heard of anyone using it, and I
needed desperately to create some code space.?
6) Added an indication on the display when the kit is
GPS locked. Of all the enhancements and bug fixes, this
one took the longest to do!
7) Added 1 digit to the baud rate setting, so that it
can now handle 115kbps (this was a request for support
of a particular GPS module). At the same time I removed
the number of bits in the data word setting, which is
the right-most digit of the "GPS Baud" parameter. I
haven't heard of a GPS which uses other than 8 bit data
words, so it seemed superfluous. Getting rid of it saved
me some code space which I could use for other requested
features. The default "GPS Baud" setting is now
"009600,01,1".
8) Removed the DDS "reset" every time the frequency
was updated, which caused the frequency to briefly go to
zero before being updated to the new frequency. This
should improve the spectral purity of the output.?
9) Put a "stop" on the cycling through characters
when you are editing the Message (and other text)
parameters, by holding down the right button. The
character cycling now stops at Z, 9 and the Enter
symbol. In order to continue cycling through, you have
to release the right button and start pressing it again.
This will make it easier to program the text parameters
e.g. Message.
10) Moved the "Time" parameter menu to the start of
the menu, when the kit is in WSPR mode. This is because
the Time parameter is what you would most commonly want
to adjust, when operating in WSPR mode, if you did not
have a GPS to regulate it. In other modes, "Time" still
comes right at the end of the menu.
11) CW, FSKCW, DFCW, QRSS and FSK modes can now
contain the '/' character in the message
12) Bug fix (cosmetic only): When setting the time,
the 10 minutes digit incorrectly allowed numbers >=
6. So it was possible to set a time such as 15:89.?
13) Bug fix (cosmetic only): If you went back in to
the time parameter to edit it a second time immediately
after finishing the first edit, the display was
overwritten incorrectly, with the system clock frequency
display.
14) Bug fix (cosmetic only): If using FSKCW mode an
10 second dit speed (for example), in the interval
between frames the LCD display did not have space to
show the seconds digit of the clock. I have now changed
the "Waiting" screen so that it does not show the mode
etc., it now only shows the time and the minutes to wait
until. E.g. "15:43:21 >50" means 3:43pm and 21
seconds, and the kit is waiting for minute 50 to start
the next frame. The "Waiting" screen also shows the GPS
heartbeat if a GPS is connected and GPS lock is
successful.
15) Bug fix: In FSKCW mode, the GPS frequency
stabilisation operating in the waiting period between
messages, only worked the first time after cycling
through the menu. Subsequent waiting periods did not
perform the calibration because the kit was always in
key-down (transmitting the low tone between messages).?
16) I changed the default speed setting to 006 for no
other reason than that I think 6 second dits are more
common and useful than 3 second dits, so make a better
default.
17) I have removed the mode message "CW Ident" when
transmitting the CW callsign identifier, and replaced it
with just the text "CW". This was purely a space-saving
measure - sacrificing something unnecessary for the sake
of gaining more space to include important features and
fixes.?
73 Hans G0UPL
|
On 01/06/2013 16:05, Hans Summers wrote: Just to let you know, I worked on the v2.02 firmware over the last week and have completed it, I am now testing. Yet another post but can't resist it. Great stuff Hans, thanks, can't wait to give it a try. Surely you can do summut in them 14 bytes. :-) 73 Eddie G3ZJO
|
Hans, and the Group,
I was going to stay out of the 'Me too' postings, even
though I am just as excited by the prospect of putting my U2 to some serious
beaconing as any one else. But I wasn't part of the U1 user-group, so I am
curious to know how the dissemination of updates works. I've never programmed a
micro-controller. Even if I had the kit to do it, I would need some detailed
guidance if the code were available. So, will I send back my old chip for
modification/replacement, will I find an Elmer who can talk me through doing it
myself, or is there another process that is followed? I'm not looking for a free
lunch -- I am happy to bear the costs -- but I'm curious to know. And I really
am looking forward to applying the changes and improvements.
Perhaps you could use those 14 bytes to write a game we
can play while the U2 is between WSPR transmissions ;-))
?
Thanks, and Best Wishes
?
David G8XBZ
All
Just to let you know, I worked on the v2.02 firmware over the last week and
have completed it, I am now testing. On Monday I am planning to have a few sent
to some people who can also do some testing. I have managed to incorporate ALL
requests, and fix ALL reported issues. I made careful notes since the launch of
the U2 kit and I don't think I have missed any requests that I agreed to
include, or bug fixes for any issues.
|
Hi David
They way I was thinking it would work is, there would be two ways to get the v2.02 upgrade:
1) I'll put the v2.02 upgrade in the online shop as I used to do for the "Ultimate" (a.k.a. U1) upgrade, price ?3 + shipping (same as in the U1 kits).
2) People who feel they should be entitled to a free upgrade can email me, I'm not difficult to convince!
73 Hans G0UPL
?
Hans, and the Group,
I was going to stay out of the 'Me too' postings, even
though I am just as excited by the prospect of putting my U2 to some serious
beaconing as any one else. But I wasn't part of the U1 user-group, so I am
curious to know how the dissemination of updates works. I've never programmed a
micro-controller. Even if I had the kit to do it, I would need some detailed
guidance if the code were available. So, will I send back my old chip for
modification/replacement, will I find an Elmer who can talk me through doing it
myself, or is there another process that is followed? I'm not looking for a free
lunch -- I am happy to bear the costs -- but I'm curious to know. And I really
am looking forward to applying the changes and improvements.
Perhaps you could use those 14 bytes to write a game we
can play while the U2 is between WSPR transmissions ;-))
?
Thanks, and Best Wishes
?
David G8XBZ
All
Just to let you know, I worked on the v2.02 firmware over the last week and
have completed it, I am now testing. On Monday I am planning to have a few sent
to some people who can also do some testing. I have managed to incorporate ALL
requests, and fix ALL reported issues. I made careful notes since the launch of
the U2 kit and I don't think I have missed any requests that I agreed to
include, or bug fixes for any issues.
|
How about offering people a
free upgrade with their next order?
?
?
73, Colin
M0XSD.
toggle quoted message
Show quoted text
Sent: Sunday, June 2, 2013 1:39 PM
Subject: Re: [QRPLabs] v2.02 firmware version coming
soon...
?
?
?
Hi David
?
They way I was thinking it would work is, there would be two ways to get
the v2.02 upgrade:
?
1) I'll put the v2.02 upgrade in the online shop as I used to do for the
"Ultimate" (a.k.a. U1) upgrade, price ?3 + shipping (same as in the U1
kits).
?
2) People who feel they should be entitled to a free upgrade can email me,
I'm not difficult to convince!
?
73 Hans G0UPL
|
Would the upgrade be useful to anyone planning on deploying their kits as either a QRSS beacon sans GPS or CW beacon?
73
John
|
Hi John
The upgrade is mainly useful for people wanting to use GPS, because v2.01 is evidently much too fussy about GPS modules it supports. It is also useful for people wanting accurate frequency shifts on the higher bands, which is mainly of use for people wanting to use WSPR.
You wouldn't need v2.02 for QRSS/CW, without GPS.
73 Hans G0UPL
?
Would the upgrade be useful to anyone planning on deploying their kits as
either a QRSS beacon sans GPS or CW beacon?
73
John
|
Thank you Hans.... I wish everyone supported their products as well as you do!
73
John K5MO
toggle quoted message
Show quoted text
At 11:20 AM 6/2/2013, you wrote: Hi John
The upgrade is mainly useful for people wanting to use GPS, because v2.01
is evidently much too fussy about GPS modules it supports. It is also
useful for people wanting accurate frequency shifts on the higher bands,
which is mainly of use for people wanting to use WSPR.
You wouldn't need v2.02 for QRSS/CW, without GPS.
73 Hans G0UPL
On Sun, Jun 2, 2013 at 3:52 PM, john <johnmb@...> wrote:
**
WARNING: The remainder of this message has not been transferred.
The estimated size of this message is 10323 bytes.
Click on the Retrieve From Server icon above and check mail again to get the whole thing. (If you're reading this in the preview pane, you'll need to open the message to see the icon.) If the Retrieve From Server icon is not showing, then this message is no longer on the server.
|
Sorry to disagree with the designer Hans, but I would say that the
upgrade is essential for all U2's.
U2's on QRSS can be identified on air by the LF and HF spikes which
are still clearly visible at 1000Km on 7MHz (capture available) and
hopefully will be eliminated by your sterling work.??? Who for the
sake of ???3 + post or possibly pay post both ways for an exchange
would not want their signal to be perfected.
Again apologies but it is there, and I cannot ignore it.
73 Eddie G3ZJO
???
On 02/06/2013 16:20, Hans Summers wrote:
toggle quoted message
Show quoted text
???
Hi John
The upgrade is mainly useful for people wanting to
use GPS, because v2.01 is evidently much too fussy about
GPS modules it supports. It is also useful for people
wanting accurate frequency shifts on the higher bands,
which is mainly of use for people wanting to use WSPR.
You wouldn't need v2.02 for QRSS/CW, without GPS.
73 Hans G0UPL
|
Hi Eddie
John was asking about QRSS and CW. The issue you're referring to is the one where the DDS output in v2.01 is very briefly set to 0 before being set to its new frequency. But that is only an issue if you are actually changing the frequency, i.e. using a Frequency Shift Keying (FSK) mode. QRSS or CW, being just on/off keyed, aren't affected by that issue!
But yes, you are right for anyone using any FSK mode, the v2.02 should provide benefit (we hope) because it should greatly reduce the transients at the point of the frequency switch.?
73 Hans G0UPL
On Sun, Jun 2, 2013 at 6:51 PM, g3zjo <g3zjo@...> wrote:
?
Sorry to disagree with the designer Hans, but I would say that the
upgrade is essential for all U2's.
U2's on QRSS can be identified on air by the LF and HF spikes which
are still clearly visible at 1000Km on 7MHz (capture available) and
hopefully will be eliminated by your sterling work.? Who for the
sake of ?3 + post or possibly pay post both ways for an exchange
would not want their signal to be perfected.
Again apologies but it is there, and I cannot ignore it.
73 Eddie G3ZJO
?
On 02/06/2013 16:20, Hans Summers wrote:
?
Hi John
The upgrade is mainly useful for people wanting to
use GPS, because v2.01 is evidently much too fussy about
GPS modules it supports. It is also useful for people
wanting accurate frequency shifts on the higher bands,
which is mainly of use for people wanting to use WSPR.
You wouldn't need v2.02 for QRSS/CW, without GPS.
73 Hans G0UPL
|
