?

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
> >
> >
> >
> >
>

?

Hans,

From your spreadsheet, I see that the average number of shipping days to the US is 6.6.? I ordered my kit on April 20, and it still has not arrived.? If it was one of the first 200, my data will cause a considerable skew to your statistics.

Could you tell me whether the kit has been shipped yet?

Best regards,
Michael? KD4SGN

Hi all

I finally got round to typing all my order details into a big spreadsheet and doing some statistics. From time to time I'll update the charts.

1) The number of LPF kits that have been ordered so far, total 637. Remember, not all of these have been sent out - there are 48 Ultimate2 orders currently pending since the first set of 200 sold out and I am getting the new set together. So the numbers in the chart includes the sent and the unsent orders.

2) The shipping information. Thank you to everybody who wrote to told me when their kit arrived, I have compiled all this information and arranged it into a table, by country - so that you can see the minimum, average, and maximum shipping times to your country.

See?

73 Hans G0UPL

?

Thanks Hans.

I wasn't worried, because I know how dedicated you are to supporting these kits Hans. They are brilliant fun for what they cost. I need a new AVR anyway, being a complete arse, I stupidly shorted the 5v/9v PA pins while it was powered up..... The screen went blank and the chip now sits there getting quite warm. I'm hoping the DDS is OK, I can hear a faint 125mhz signal and an even more feint 20hhz one, so maybe it is OK. Maybe I'm too senile to be messing about with things like this.... I certainly called myself some names.

:)))

Tony BZB

?

Good news Barry. Delighted your new GPS works with the new kit.?

However, there is nothing wrong with the EM-406A. I've had one working with the UQRSS1 for about ten months, day in day out 24/7. It is working now with all GPS functions working correctly as designed. However, it behaves just like yours did on the UQ2.

The issue with the UQRSS2 is being caused by some different way the software in this kit works. It's a shame really, but I won't be spending another ?17 to replace a GPS that is not faulty.

Best regards

Tony G0BZB

On 31 May 2013 12:18, Barry Chambers <b.chambers@...> wrote:

Afternoon All

For several weeks, I've been struggling to get my U2 kit working with a
EM-406A GPS module. The problem seems to be with the 1pps signal. as the
NEMA data is read correctly.

Today, I got through the post a Fastrax (Reyax) ?UP501 GPS module (from
Taiwan via E-Bay, ?17, about 10 days delivery time). Hans lists this
module on the U2 kit web pages. It requires a 3.3v supply and the modem
setting is 09600,10,1,8. Hey presto! ?It works! I found that the "Inv
GPS" setting needs to be "On". The clock keeps perfect time (as compared
against my wireless clock), the Locator is set correctly and the DDS
125MHz oscillator frequency is corrected (mine is now slightly lower
than 125 MHz). At present I have "Start" set at 02 and "Frame" at 04 and
the U2 is on soak test on 20m WSPR with a "loop" made from two pieces of
wire about 15cm long, joined by a 47R resistor.

73

Barry, G8AGN


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
? ?

<*> Your email settings:
? ? Individual Email | Traditional

<*> To change settings online go to:
? ?
? ? (Yahoo! ID required)

<*> To change settings via email:
? ? QRPLabs-digest@...
? ? QRPLabs-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
? ? QRPLabs-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
? ?

Afternoon All

For several weeks, I've been struggling to get my U2 kit working with a
EM-406A GPS module. The problem seems to be with the 1pps signal. as the
NEMA data is read correctly.

Today, I got through the post a Fastrax (Reyax) ?UP501 GPS module (from
Taiwan via E-Bay, ?17, about 10 days delivery time). Hans lists this
module on the U2 kit web pages. It requires a 3.3v supply and the modem
setting is 09600,10,1,8. Hey presto! ?It works! I found that the "Inv
GPS" setting needs to be "On". The clock keeps perfect time (as compared
against my wireless clock), the Locator is set correctly and the DDS
125MHz oscillator frequency is corrected (mine is now slightly lower
than 125 MHz). At present I have "Start" set at 02 and "Frame" at 04 and
the U2 is on soak test on 20m WSPR with a "loop" made from two pieces of
wire about 15cm long, joined by a 47R resistor.

73

Barry, G8AGN


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
? ?

<*> Your email settings:
? ? Individual Email | Traditional

<*> To change settings online go to:
? ?
? ? (Yahoo! ID required)

<*> To change settings via email:
? ? QRPLabs-digest@...
? ? QRPLabs-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
? ? QRPLabs-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
? ?

?

Thanks Hans.

It seems that although my new boxed unit is very pretty, it's rubbish as an oven as it drifted all over the place last night as the shack cooled down.

73 Keith.

On 30 May 2013, at 23:30, Hans Summers <hans.summers@...> wrote:

?

Hi Keith

I'll check it ASAP!

The weekend is coming up! Just one more day! Means being able to stop wasting time in the office, and spend it worthily in the radio room (and with XYL).?

73 Hans G0UPL

On Thu, May 30, 2013 at 11:09 PM, Keith Maton <nentecular@...> wrote:

?

All (specifically Hans),

I've found what I think is a problem with the frequency stabilisation routine in the U2.

The manual says:

"When using the connected GPS module for frequency stabilisation, you must choose a non-zero Frame parameter. This is because the frequency stabilisation must take place when there is no transmission from the kit, i.e. during a pause between transmissions. The frequency stabilisation takes 12 seconds and occurs just before the start of a transmission. Therefore you need to ensure that the Frame parameter is sufficiently large that there is a minimum gap of 12 seconds between the completion of your message transmission and the start of the next one."

This is all great in WSPR because there is a period of non transmission between each frame but it's not possible to do this when running FSKCW (and probably other QRSS modes, I've not checked them all).

I have my kit all working well and when I first start it, the frequency is absolutely spot on because it's calibrated. However, when starting from cold, there's always an initial drift as it all warms up.

My callsign takes 9 minutes and 40 seconds to send, leaving a period of 20 seconds or so before the next frame starts but the kit continues to transmit the lower tone for those 20 seconds and so it doesn't calibrate.

With the kit built into a box which works well as an oven, I've just watched it start transmitting on the correct frequency and then drift 20Hz upwards. When the next frame started, it carried on drifting so I simply cycled through all the menus and after the next frame had completed, I pushed the right button and when it started transmitting a few seconds later, it had run the stabilisation and was back on the correct frequency. It still hadn't reached the stable temperature in the box so it continued to drift upwards.

So as it stands, when running FSKCW (and possibly other modes), there's no stabilisation apart from the initial routine, no matter how long the callsign is because there isn't a pause between transmissions.

I don't think the transmitter should be switched off between frames because that will cause a temperature change of the overall unit, especially if it's built into a sealed enclosure and it will drift again once the transmitter comes back on.

I think a fix would be to force the transmitter off automatically for fifteen seconds prior to the end of the frame to allow stabilisation to take place.

Has anyone else noticed this?

I've uploaded a screenshot of what happens when I cycle through the menus at the end of the frame here - You can see that it's dropped back down to the correct frequency but I'll need to do it again at the end of this cycle as it's still not quite warmed up fully yet.

The automatic stabilisation routine is fantastic but it needs to work every frame to be worthwhile.

Or have I got something wrong in the menus that's stopping this from working? I have my frame length set to 10 and the start set to 1.

73, Keith.