[time-nuts] HP 58503A GPS receiver not locking to GPS
Art Sepin
art at synergy-gps.com
Fri Aug 14 06:32:23 UTC 2020
This Motorola Service Bulletin astonished users in the timing community who kept their VP Oncore timing products operating 24/7/365 - Most everyone!
https://synergy-gps.com/wp-content/uploads/2019/06/VP_SERVICE_NOTE.pdf
All of the PVT6, 6 and 8 channel Basic Oncore and 6 and 8 channel VP Oncore OEM GPS receiver boards incorporated a Pendulum Oscillator that was recalibrated every time the boards were power cycled. If the receivers were powered-on for long periods, no calibration occurred so it was possible for the oscillator to drift beyond a point where a board could easily acquire satellites; even if powered off for a short period.
Randy Warner (RIP) authored an App-Note "Startup Times for VP Oncore Receivers" that discusses the details (our web site was hacked and we're still in the process of replenishing content that was deleted. The text of Randy's App-Note is below).
A condition not mentioned in either one of these App-Notes was brought to our attention by our friend, Doug Baker (then at Datum Corp.) sometime in the late nineties. Long term, always on, operation in CDMA cell sites would also suffer from this oscillator drift problem. Anyone with 6 and 8 channel VP Oncore based timing instruments may have noticed this phenomenon too: The longer these VP receivers remained in a powered-on state, the more the oscillator drifted due to no recalibration occurring. The oscillator drift caused the receiver to take longer to acquire satellites as they rose up from the horizon. An attendant effect of not re-calibrating the oscillator was that the longer the receivers were powered on, they appeared to become less sensitive. For example, a receiver installed at a new site that was continuously locking on to 5 to 8 satellites would only be able to see something like 2 to 5 satellites if powered on continuously for more than a year, or so. That's why Motorola generated the VP Oncore Service Note recommending periodic power cycling.
BTW - The 1024 Week Roll-Over for a VP Oncore with v8.8 firmware was 3/22/2016; With v10.0 firmware was 8/13/2017 and with v10.1 firmware was 7/11/2018. These receivers will continue to operate but with incorrect dates. We know of no resource for information about VP Oncore behavior with future Week Roll-Overs, Leap Second, etc.
Apologies for the long-winded explanation!
Art Sepin
START UP TIMES FOR VP RECEIVERS
At first glance, it probably seems a little strange for me to be writing an application note for the Motorola VP OncoreTM series of GPS receivers fully six months after they were phased out due to parts procurement problems, but I am getting enough calls, emails, and receivers returned due to extended Time To First Fix (TTFF) to warrant a quick note.
HISTORY - One result of the impending phase out is that Synergy Systems purchased quantities of VP receivers from other Motorola distributors world-wide in order to support our customers for as long as possible. These receivers included 6 channel B1's and 6/8 channel B3's and B8's. Some of these receivers have been in distributor stock for up to five years after the original date of manufacture. The receivers themselves are in perfect condition, but what can cause problems with many of them is aging of the oscillator components.
Unlike the newer GT+, UT+, and M12 receivers, the VP used a "pendulum oscillator" that was much more complicated to stabilize than the newer units. During the board manufacturing process the oscillator on every board is characterized, and the appropriate oscillator characteristics are stored in EEPROM. The next time the board is powered on (usually by you) the oscillator characteristics are downloaded from EEPROM during initialization and used to set the oscillator output frequency.
THE REAL WORLD - OK, that sounds great. What's the problem? Well, normally this all works fine, but what can slow things down is if the receiver has been sitting around for a while in an un -powered state. In this case, when the receiver is powered up, the stored oscillator characteristics are all wrong, the receiver runs off frequency, and as a result it cannot acquire satellites. [Art - also see Motorola VP Oncore Service Note]
This will continue for some time (an hour or more in some cases) as the receiver tries to lock onto satellite carriers: searching for SVs, adjusting oscillator frequency, etc. Finally, the receiver hits on the right combination and BANG, things ret urn to normal.
This is best illustrated with the following graph. This graph shows the start-up progression of an old 6 channel VP that has been sitting in a box since 1995. The receiver was initialized using our SynTAC control program, which initialized the receiver and loaded in correct time and position at time "0". Note that the receiver variously tracks 0, 1, 2, or 3 SVs for approximately 5000 seconds (over an hour and twenty minutes!) without ever acquiring a fix. We do get three SVs a couple of times at around the 3300 second mark, but the Dilution of Precision (DOP) never gets low enough for the receiver to declare a valid 2D fix.
Note also that the "SVs Visible" trace goes from 0 to 7 at about the 3400 second mark, indicating that a valid almanac has been successfully downloaded. Well, you say, this simply cannot be. It only takes 15 minutes or so to download an almanac. Well, yes, and no. What the graph does not show is that during the time that the receiver was trying to download the almanac, satellites were being acquired and lost with great regularity. Maybe a page of the almanac got through here or there, but it took almost an hour for the entire almanac to be successfully transferred.
Things get even stranger when we look at the period between 3400 and 5000 seconds. Here we have a receiver with time, position, AND a valid almanac, and it still takes almost another half
hour before it starts tracking satellites properly and delivers a valid 3D fix. Note that at the 5000 second mark the number of tracked SVs jumps from 2, to 5, to 6, in a matter of a few seconds. Guess what? The receiver has finally discovered the magic combination of oscillator parameters.
At this point the receiver can be considered "cured", and will operate in a more normal manner. Even so, I usually let the receiver remain powered up for at least another half hour to allow the new oscillator characteristics to be transferred to EEPROM. This is accomplished as a background task by the microprocessor, and as such can take some time. If you disconnect power before this task is complete, you might just get to go through the whole process over again.
Old VP Cold Start
[cid:image003.png at 01D671C9.FCDA04C0]9
8
7
6
[SVs Tracked SVs Visible Fix Type][SVs / Fix Type]5
4
3
2
1
[1 285 569 853 1137 1421 1705 1989 2273 2557 2841 3125 3409 3693 3977 4261 4545 4829 5113 5397 5681 5965 6249 6533]0
Time (sec)
That's about it. Bear in mind that your receiver does not need to be five years old in order for this problem to occur. It all depends upon the oscillator aging characteristics of the specific receiver. This could conceivably happen to a brand new B8 that has been sitting in your stock room for as little as six months. Just don't give up on it too soon. Once things have been recalibrated the start-up times will return to normal.
Randy Warner
Senior Applications Engineer Synergy Systems, LLC randy at synergy-gps.com<mailto:randy at synergy-gps.com>
-----Original Message-----
From: time-nuts <time-nuts-bounces at lists.febo.com> On Behalf Of Eric Garner
Sent: Thursday, August 13, 2020 6:12 PM
To: Discussion of precise time and frequency measurement <time-nuts at lists.febo.com>
Subject: Re: [time-nuts] HP 58503A GPS receiver not locking to GPS
Have you manually set the date/time yet?
Last time I powered mine up. I had to update the current time and date and it locked right up.
-Eric
On Thu, Aug 13, 2020, 1:55 PM Dr. David Kirkby < drkirkby at kirkbymicrowave.co.uk<mailto:drkirkby at kirkbymicrowave.co.uk>> wrote:
> Some time ago my GPS receiver would not lock to GPS. I put this down
> to the fact the antenna had got tilted over quite a bit, and since I
> was not needing the receiver, it got switched off, and I forgot about
> it for some time.
>
> I've since straightened the antenna up, and push it a little higher -
> it is now about 3 m above ground
>
> However, the unit will not lock, despite being on for a couple of
> days. The status shows "attempting to lock", but does not actually
> lock one satellite. I set the and time manually, as well as latitude,
> longitude, and antenna height. I've also set the elevation mask to 10 degrees.
>
> The data below shows some results of :system:status? over a period of
> a little over two hours. I've run self-tests, and they all pass okay.
> The occasional error below, such as E-113, it just where I have
> mis-typed something. If I type *CLS, the display shows scpi>
>
> I'm a bit concerned if the mode of "hold" is correct, but I'm unsure.
>
> Has anyone got any suggestions as to what I can do to get it to lock?
>
> scpi > :system:sy
> E-113> :system:status?
> ------------------------------- Receiver Status
> -------------------------------
>
> SYNCHRONIZATION ........................................... [ Outputs
> Invalid ]
> SmartClock Mode ___________________________ Reference Outputs
> _______________
> Locked TFOM 9
> FFOM 3
> Recovery 1PPS TI --
> Holdover HOLD THR 1.000 us
> >> Power-up: GPS acquisition Holdover Uncertainty
> ____________
> Predict --
>
> ACQUISITION .............................................. [ GPS 1PPS
> Invalid ]
> Tracking: 0 ____ Not Tracking: 12 _______ Time
> ____________________________
> PRN El Az PRN El Az UTC 17:53:34 [?] 13 Aug
> 2020
> * 1 -- --- 7 39 159 GPS 1PPS Invalid: not
> tracking
> 2 46 286 * 8 -- --- ANT DLY 0 ns
> * 3 -- --- 9 77 72 Position
> ________________________
> 4 37 64 *10 -- --- MODE Hold
> 5 17 292 *11 -- ---
> 6 54 214 *30 15 182 LAT N 51:39:04.128
> LON E 0:46:36.375
> ELEV MASK 10 deg *attempting to track HGT +46.29 m
> (MSL)
> HEALTH MONITOR
> ......................................................... [ OK ]
> Self Test: OK Int Pwr: OK Oven Pwr: OK OCXO: OK EFC: OK GPS Rcv:
> OK
> E-113> *CLS
> scpi > :system:status?
> ------------------------------- Receiver Status
> -------------------------------
>
> SYNCHRONIZATION ........................................... [ Outputs
> Invalid ]
> SmartClock Mode ___________________________ Reference Outputs
> _______________
> Locked TFOM 9
> FFOM 3
> Recovery 1PPS TI --
> Holdover HOLD THR 1.000 us
> >> Power-up: GPS acquisition Holdover Uncertainty
> ____________
> Predict --
>
> ACQUISITION .............................................. [ GPS 1PPS
> Invalid ]
> Tracking: 0 ____ Not Tracking: 12 _______ Time
> ____________________________
> PRN El Az PRN El Az UTC 17:54:01 [?] 13 Aug
> 2020
> * 1 -- --- 7 39 159 GPS 1PPS Invalid: not
> tracking
> 2 46 286 * 8 -- --- ANT DLY 0 ns
> * 3 -- --- 9 76 72 Position
> ________________________
> 4 37 64 *10 -- --- MODE Hold
> 5 18 292 *11 -- ---
> 6 54 214 *30 15 182 LAT N 51:39:04.128
> LON E 0:46:36.375
> ELEV MASK 10 deg *attempting to track HGT +46.29 m
> (MSL)
> HEALTH MONITOR
> ......................................................... [ OK ]
> Self Test: OK Int Pwr: OK Oven Pwr: OK OCXO: OK EFC: OK GPS Rcv:
> OK
> scpi > :system:status?
> ------------------------------- Receiver Status
> -------------------------------
>
> SYNCHRONIZATION ........................................... [ Outputs
> Invalid ]
> SmartClock Mode ___________________________ Reference Outputs
> _______________
> Locked TFOM 9
> FFOM 3
> Recovery 1PPS TI --
> Holdover HOLD THR 1.000 us
> >> Power-up: GPS acquisition Holdover Uncertainty
> ____________
> Predict --
>
> ACQUISITION .............................................. [ GPS 1PPS
> Invalid ]
> Tracking: 0 ____ Not Tracking: 12 _______ Time
> ____________________________
> PRN El Az PRN El Az UTC 18:00:50 [?] 13 Aug
> 2020
> 2 47 282 *11 -- --- GPS 1PPS Invalid: not
> tracking
> 4 34 64 *12 -- --- ANT DLY 0 ns
> 5 20 293 *13 -- --- Position
> ________________________
> 6 51 210 *14 -- --- MODE Hold
> 7 42 158 *15 -- ---
> 9 73 70 *16 10 64 LAT N 51:39:04.128
> LON E 0:46:36.375
> ELEV MASK 10 deg *attempting to track HGT +46.29 m
> (MSL)
> HEALTH MONITOR
> ......................................................... [ OK ]
> Self Test: OK Int Pwr: OK Oven Pwr: OK OCXO: OK EFC: OK GPS Rcv:
> OK
> scpi > scpi > :system:status?
> E-113> ------------------------------- Receiver Status
> -------------------------------
> E-121>
> E-121> SYNCHRONIZATION ........................................... [
> Outputs Invalid ]
> E-113> SmartClock Mode ___________________________ Reference Outputs
> _______________
> E-113> Locked TFOM 9
> FFOM 3
> E-113> Recovery 1PPS TI --
> E-113> Holdover HOLD THR 1.000 us
> E-113> >> Power-up: GPS acquisition Holdover Uncertainty
> ____________
> E-101> Predict --
> E-113>
> E-113> ACQUISITION .............................................. [
> E-113> GPS
> 1PPS Invalid ]
> E-113> Tracking: 0 ____ Not Tracking: 12 _______ Time
> ____________________________
> E-113> PRN El Az PRN El Az UTC 18:00:50 [?]
> 13 Aug 2020
> E-113> 2 47 282 *11 -- --- GPS 1PPS Invalid: not
> tracking
> E-103> 4 34 64 *12 -- --- ANT DLY 0 ns
> E-103> 5 20 293 *13 -- --- Position
> ________________________
> E-103> 6 51 210 *14 -- --- MODE Hold
> E-103> 7 42 158 *15 -- ---
> E-103> 9 73 70 *16 10 64 LAT N
> 51:39:04.128
> E-103> LON E
> 0:46:36.375
> E-113> ELEV MASK 10 deg *attempting to track HGT
> +46.29 m (MSL)
> E-113> HEALTH MONITOR
> ......................................................... [ OK ]
> E-113> Self Test: OK Int Pwr: OK Oven Pwr: OK OCXO: OK EFC: OK
> GPS Rcv: OK
> E-113> scpi >
> E-113> scpi > :system:status?
> E-113> ------------------------------- Receiver Status
> -------------------------------
> E-121>
> E-121> SYNCHRONIZATION ........................................... [
> Outputs Invalid ]
> E-113> SmartClock Mode ___________________________ Reference Outputs
> _______________
> E-113> Locked TFOM 9
> FFOM 3
> E-113> Recovery 1PPS TI --
> E-113> Holdover HOLD THR 1.000 us
> E-350> >> Power-up: GPS acquisition Holdover Uncertainty
> ____________
> E-101> Predict --
> E-113>
> E-113> ACQUISITION .............................................. [
> E-113> GPS
> 1PPS Invalid ]
> E-113> Tracking: 0 ____ Not Tracking: 12 _______ Time
> ____________________________
> E-113> PRN El Az PRN El Az UTC 18:00:50 [?]
> 13 Aug 2020
> E-113> 2 47 282 *11 -- --- GPS 1PPS Invalid: not
> tracking
> E-103> 4 34 64 *12 -- --- ANT DLY 0 ns
> E-103> 5 20 293 *13 -- --- Position
> ________________________
> E-103> 6 51 210 *14 -- --- MODE Hold
> E-103> 7 42 158 *15 -- ---
> E-103> 9 73 70 *16 10 64 LAT N
> 51:39:04.128
> E-103> LON E
> 0:46:36.375
> E-113> ELEV MASK 10 deg *attempting to track HGT
> +46.29 m (MSL)
> E-113> HEALTH MONITOR
> ......................................................... [ OK ]
> E-113> Self Test: OK Int Pwr: OK Oven Pwr: OK OCXO: OK EFC: OK
> GPS Rcv: OK
> E-113> scpi >
> E-113> :system:status?
> ------------------------------- Receiver Status
> -------------------------------
>
> SYNCHRONIZATION ........................................... [ Outputs
> Invalid ]
> SmartClock Mode ___________________________ Reference Outputs
> _______________
> Locked TFOM 9
> FFOM 3
> Recovery 1PPS TI --
> Holdover HOLD THR 1.000 us
> >> Power-up: GPS acquisition Holdover Uncertainty
> ____________
> Predict --
>
> ACQUISITION .............................................. [ GPS 1PPS
> Invalid ]
> Tracking: 0 ____ Not Tracking: 12 _______ Time
> ____________________________
> PRN El Az PRN El Az UTC 19:43:25 [?] 13 Aug
> 2020
> 2 27 228 *26 -- --- GPS 1PPS Invalid: not
> tracking
> 5 63 284 *27 -- --- ANT DLY 0 ns
> 7 62 81 *28 -- --- Position
> ________________________
> 9 29 83 *29 -- --- MODE Hold
> 13 29 262 30 65 165
> *25 -- --- *31 -- --- LAT N 51:39:04.128
> LON E 0:46:36.375
> ELEV MASK 10 deg *attempting to track HGT +46.29 m
> (MSL)
> HEALTH MONITOR
> ......................................................... [ OK ]
> Self Test: OK Int Pwr: OK Oven Pwr: OK OCXO: OK EFC: OK GPS Rcv:
> OK
> E-113> ?
> E-103> *CLS
> scpi > :system:status?
> ------------------------------- Receiver Status
> -------------------------------
>
> SYNCHRONIZATION ........................................... [ Outputs
> Invalid ]
> SmartClock Mode ___________________________ Reference Outputs
> _______________
> Locked TFOM 9
> FFOM 3
> Recovery 1PPS TI --
> Holdover HOLD THR 1.000 us
> >> Power-up: GPS acquisition Holdover Uncertainty
> ____________
> Predict --
>
> ACQUISITION .............................................. [ GPS 1PPS
> Invalid ]
> Tracking: 0 ____ Not Tracking: 12 _______ Time
> ____________________________
> PRN El Az PRN El Az UTC 19:56:10 [?] 13 Aug
> 2020
> * 1 -- --- 7 58 72 GPS 1PPS Invalid: not
> tracking
> 2 22 224 * 8 -- --- ANT DLY 0 ns
> * 3 -- --- 9 24 86 Position
> ________________________
> * 4 -- --- *10 -- --- MODE Hold
> 5 68 273 13 34 265
> * 6 -- --- 30 69 155 LAT N 51:39:04.128
> LON E 0:46:36.375
> ELEV MASK 10 deg *attempting to track HGT +46.29 m
> (MSL)
> HEALTH MONITOR
> ......................................................... [ OK ]
> Self Test: OK Int Pwr: OK Oven Pwr: OK OCXO: OK EFC: OK GPS Rcv:
> OK
> scpi > :system:status?
> ------------------------------- Receiver Status
> -------------------------------
>
> SYNCHRONIZATION ........................................... [ Outputs
> Invalid ]
> SmartClock Mode ___________________________ Reference Outputs
> _______________
> Locked TFOM 9
> FFOM 3
> Recovery 1PPS TI --
> Holdover HOLD THR 1.000 us
> >> Power-up: GPS acquisition Holdover Uncertainty
> ____________
> Predict --
>
> ACQUISITION .............................................. [ GPS 1PPS
> Invalid ]
> Tracking: 0 ____ Not Tracking: 12 _______ Time
> ____________________________
> PRN El Az PRN El Az UTC 20:02:13 [?] 13 Aug
> 2020
> 2 19 223 13 36 267 GPS 1PPS Invalid: not
> tracking
> 5 69 267 *14 -- --- ANT DLY 0 ns
> 7 56 69 *15 -- --- Position
> ________________________
> 9 22 88 *16 -- --- MODE Hold
> *11 -- --- *17 -- ---
> *12 -- --- 30 71 148 LAT N 51:39:04.128
> LON E 0:46:36.375
> ELEV MASK 10 deg *attempting to track HGT +46.29 m
> (MSL)
> HEALTH MONITOR
> ......................................................... [ OK ]
> Self Test: OK Int Pwr: OK Oven Pwr: OK OCXO: OK EFC: OK GPS Rcv:
> OK
> scpi >
>
>
>
> Dr David Kirkby Ph.D C.Eng MIET
> Email: drkirkby at kirkbymicrowave.co.uk<mailto:drkirkby at kirkbymicrowave.co.uk> Web:
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> kirkbymicrowave.co.uk%2F&data=01%7C01%7Cart%40synergy-gps.com%7C7f
> 4faab5307946548c4c08d83ff52e9f%7Cc81f9fdec0e04d8c95779afaa0cad9ed%7C1&
> amp;sdata=p39I0KQ65GFbsDxdrcKPQ%2FiC0uoy7vqLEIxjR%2FlupdE%3D&reser
> ved=0 Kirkby Microwave Ltd (Tel 01621-680100 / +44 1621-680100) Stokes
> Hall Lodge, Burnham Rd, Chelmsford, Essex, CM3 6DT.
> _______________________________________________
> time-nuts mailing list -- time-nuts at lists.febo.com<mailto:time-nuts at lists.febo.com> To unsubscribe, go
> to
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists
> .febo.com%2Fmailman%2Flistinfo%2Ftime-nuts_lists.febo.com&data=01%
> 7C01%7Cart%40synergy-gps.com%7C7f4faab5307946548c4c08d83ff52e9f%7Cc81f
> 9fdec0e04d8c95779afaa0cad9ed%7C1&sdata=JEYjiTCOLhabuq80Cp5GGYcjzjW
> wFb38TN7Xfe%2B%2BBJE%3D&reserved=0
> and follow the instructions there.
>
_______________________________________________
time-nuts mailing list -- time-nuts at lists.febo.com<mailto:time-nuts at lists.febo.com> To unsubscribe, go to https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.febo.com%2Fmailman%2Flistinfo%2Ftime-nuts_lists.febo.com&data=01%7C01%7Cart%40synergy-gps.com%7C7f4faab5307946548c4c08d83ff52e9f%7Cc81f9fdec0e04d8c95779afaa0cad9ed%7C1&sdata=JEYjiTCOLhabuq80Cp5GGYcjzjWwFb38TN7Xfe%2B%2BBJE%3D&reserved=0
and follow the instructions there.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 12524 bytes
Desc: image002.png
URL: <http://febo.com/pipermail/time-nuts_lists.febo.com/attachments/20200814/30d5959f/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 21145 bytes
Desc: image003.png
URL: <http://febo.com/pipermail/time-nuts_lists.febo.com/attachments/20200814/30d5959f/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 152 bytes
Desc: image004.png
URL: <http://febo.com/pipermail/time-nuts_lists.febo.com/attachments/20200814/30d5959f/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.emz
Type: application/octet-stream
Size: 2486 bytes
Desc: image005.emz
URL: <http://febo.com/pipermail/time-nuts_lists.febo.com/attachments/20200814/30d5959f/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1040 bytes
Desc: image006.png
URL: <http://febo.com/pipermail/time-nuts_lists.febo.com/attachments/20200814/30d5959f/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.emz
Type: application/octet-stream
Size: 2350 bytes
Desc: image007.emz
URL: <http://febo.com/pipermail/time-nuts_lists.febo.com/attachments/20200814/30d5959f/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.png
Type: image/png
Size: 846 bytes
Desc: image014.png
URL: <http://febo.com/pipermail/time-nuts_lists.febo.com/attachments/20200814/30d5959f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.png
Type: image/png
Size: 156 bytes
Desc: image015.png
URL: <http://febo.com/pipermail/time-nuts_lists.febo.com/attachments/20200814/30d5959f/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image016.png
Type: image/png
Size: 156 bytes
Desc: image016.png
URL: <http://febo.com/pipermail/time-nuts_lists.febo.com/attachments/20200814/30d5959f/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image017.emz
Type: application/octet-stream
Size: 5110 bytes
Desc: image017.emz
URL: <http://febo.com/pipermail/time-nuts_lists.febo.com/attachments/20200814/30d5959f/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image018.png
Type: image/png
Size: 2266 bytes
Desc: image018.png
URL: <http://febo.com/pipermail/time-nuts_lists.febo.com/attachments/20200814/30d5959f/attachment-0007.png>
More information about the Time-nuts_lists.febo.com
mailing list