Jerry Royston wrote:
> I seem to remember that a description of the characters displayed by the
> kiwi osd was published somehere.
Hi Jerry,
Try this page, for a description of the various displays:
http://www.geocities.com/kiwi_36_nz/kiwi_osd/example.htm#shots
Also here is the time breakdown:
--------------------------------------------------------------------------
The bottom of the video screen has this format:
HH:MM:SS EEEE OOOO FFFFFF
where:
HH:MM:SS = Hours, Minutes, Seconds UTC time
EEEE = latest Even field Vsync offset to UTC second (in milliseconds).
OOOO = latest Odd field Vsync offset to UTC second (in milliseconds).
FFFFFF = Contiguous field count since initial GPS sync
( 6 digits allow 4.6 hours @ NTSC rate before counter rollover ).
( 6 digits allow 5.5 hours @ PAL rate before counter rollover ).
--------------------------------------------------------------------------
Note the two millisecond displays are not in "time order" but in
"even" and "odd" order. Where "even" is defined by the line structure
of the video field, not whether the millisecond time value is a
mathematical "even" number. This often confuses people.
I hope that helps Jerry.
Regards, Geoff (NZ).
Hello all,
I seem to remember that a description of the characters displayed by the
kiwi osd was published somehere. Could a member be so good as to point me in the
right direction
Thanks, Jerry
You need an RCA x BNC adapter or a cable with the appropriate ends. PFD Systems
sells gold plated adapters. If you build your own cables it would be good to
get the right impedence, 50 or 75 ohm, for the BNC connectors and cable. I
think you want 75 ohms but check the KIWI OSD manual.
bill,
judging from your description, you probably need the KIWI-BNC which is male RCA
to male BNC.
put a request for one via our web page and i'll get one out to you.
http://www.pfdsystems.com/kiwipay.html
regards,
vince
pfd systems
--- In kiwiosd@yahoogroups.com, "Bill Stein" <starman@...> wrote:
>
> I recently purchased one of the last KIWI-OSD video time inserters from PFD
> Systems. Also, I have a Super Circuits PC-164CEX-2 video camera. The video
> output connector from this camera appears to be a female BNC connector.
> However, I cannot connect the camera video output to the KIWI-OSD camera
> input. Can anyone suggest an adaptor for this capability? If so, which PFD
> Systems adaptor would be applicable? Or is there another suggestion?
>
>
>
> Thanks for any help. Bill
>
>
>
> William L. Stein
> Las Cruces, NM 88012
>
I recently purchased one of the last KIWI-OSD video time
inserters from PFD Systems. Also, I have a Super Circuits PC-164CEX-2
video camera. The video output connector from this camera appears to be a
female BNC connector. However, I cannot connect the camera video output
to the KIWI-OSD camera input. Can anyone suggest an adaptor for this
capability? If so, which PFD Systems adaptor would be applicable? Or
is there another suggestion?
Hello Peter,
> You don't need a battery to retain data! There are differing types of
> memory, volatile and non-volatile ....
of course, you are right. But the point of discussion was the internal power
source for the real time clock (RTC) inside the GPS after external power
down. Because every clock circuit needs voltage for operation.
Regards
Gerhard
www.dangl.at
It is sad to say that I am completely out of KIWI-OSDs. The last one was sold
today.
For any of you who have not been keeping up with current events, I direct you to
the following web page:
http://www.pfdsystems.com/sundown.htm
Regards,
Vince
PFD Systems
Sorry but it seems that in my preceding message there was not the link
Hello Gerhard and Geoff
It is perhaps the way
Here is a link to a document from Panasonic
http://www.panasonic.com/industrial/components/pdf/about_gold_capacitors.pdf
where one is able to find a
little calculation for a capacitor of 0.2 Farad, the discharge intensity is
10µA and the leakage current 0.2 µA, the value of the backup time is around
3h8
If the capacitor is 2 Farad ant the discharge intensity 1 µA the time is
then around 380h
For the number of days in the month the time should be or 720 or 744 hours
.To make a better approch w'll know more about the minimum maintain voltage
and the intensity .
Well I'll wait now for 6 months an try again
Best regards
Thomas
----- Original Message -----
From: "thomas.flatres" <thomas.flatres@...>
To: <kiwiosd@yahoogroups.com>
Sent: Saturday, May 02, 2009 7:07 PM
Subject: Re: [kiwiosd] GPS are growing old
>
> Hello Geoff
>
> I've also sent my results to Tim Piercy and here is his answer:
>
> <Hello,
>
> <I didn't think there was an internal battery and to confirm I took one
> apart yesterday and found <there is no battery inside a GPS 18.
>
> that lets me perplexed because I cant' understand how the internal
> memories
> could update time and date without any power source.
>
> If the broken GPS still exists it may be possible to inspect it , to check
> if that assertion is true or false.
>
> Many thanks for photos and text Could I translate it in french to the Gps
> 18LVC users
>
> Regards
>
> Thomas
>
> ---- Original Message -----
>
> From: "Kiwi Geoff" <geoff36@...>
> To: <kiwiosd@yahoogroups.com>
> Sent: Thursday, April 30, 2009 11:05 AM
> Subject: Re: [kiwiosd] GPS are growing old
>
>
>>
>> Thomas Flatres wrote:
>>> The GPS are growing old
>>> It is because the internal battery.
>>
>> Yes I agree Thomas, my oldest Garmin GPS now takes a long time to get
>> a first FIX after being powered OFF for a long time.
>>
>> Perhaps the "take home message" might be - we should allow up to 10
>> minutes for the Garmin 18 LVC to get a FIX after it has been unused
>> for a time. This amount of time will allow for a discharged (or dead)
>> battery inside the Garmin GPS.
>>
>>> Garmin could change it but I've no idea of the cost.
>>
>> I'm not sure they would bother Thomas, the case is a water-proof seal,
>> and if you have a look at the following images:
>>
>> http://geoff36.googlepages.com/insidegarmin18lvcgps
>>
>> the battery will be mounted under the metal shield, and could be
>> difficult to replace.
>>
>> As long as we allow for this "old battery" condition, we can still use
>> the GPS, as long as we wait for 10 minutes for a first FIX (because
>> the GPS has lost all track of time and date).
>>
>> I guess eventually the internal battery in the Garmin 18 could start
>> to leak and so corrode the GPS electronics - and at that point the GPS
>> will fail completely!
>>
>> Regards, Geoff.
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>>
>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>
Hello all -
You don't need a battery to retain data! There are differing types of memory,
volatile and non-volatile. Volatile requires battery back up. Regular EEPROM
does not (Electrically Erasable Programable Read Only Memory) but requires a
specialized writer bosrd and UV eraser. But "flash" memory, such as that used in
common memory sticks you plug into your USB slots, is a special form of EEPROM
that can be freely written over and read out, and is non-volatile. It is widely
used in everything from IPODs to autos - and GPS receivers.
P.S. The KIWI is a wonderfully designed and useful machine, sorry to see it
packing up... but understand the reasoning...
Peter
--- In kiwiosd@yahoogroups.com, "thomas.flatres" <thomas.flatres@...> wrote:
>
> Hello Gerhard and Geoff
>
> It is perhaps the way
> Here is a link to a document from Panasonic where one is able to find a
> little calculation for a capacitor of 0.2 Farad, the discharge intensity is
> 10µA and the leakage current 0.2 µA, the value of the backup time is around
> 3h8
> If the capacitor is 2 Farad ant the discharge intensity 1 µA the time is
> then around 380h
> For the number of days in the month the time should be or 720 or 744 hours
> .To make a better approch w'll know more about the minimum maintain voltage
> and the intensity .
> Well I'll wait now for 6 months an try again
>
> Best regards
> Thomas
> ----- Original Message -----
> From: "Gerhard Dangl" <gerhard@...>
> To: <kiwiosd@yahoogroups.com>
> Sent: Sunday, May 03, 2009 1:00 AM
> Subject: Re: [kiwiosd] GPS are growing old
>
>
> >
> > Hello Thomas and Geoff,
> >
> >> I've also sent my results to Tim Piercy and here is his answer:
> >>
> >> <Hello,
> >>
> >> <I didn't think there was an internal battery and to confirm I took one
> >> apart yesterday and found <there is no battery inside a GPS 18.
> >>
> >> that lets me perplexed because I cant' understand how the internal
> >> memories
> >> could update time and date without any power source.
> >
> > what about the use of a Goldcap?
> >
> > Because up to date RTC technology needs only few microamps I can imagine
> > that a Goldcap could do the supply job for a relative long time after
> > power
> > down. And this part would not have the limited live time like every
> > lithium
> > battery has.
> >
> > Regards
> > Gerhard
> > www.dangl.at
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
>
Hello Gerhard and Geoff
It is perhaps the way
Here is a link to a document from Panasonic where one is able to find a
little calculation for a capacitor of 0.2 Farad, the discharge intensity is
10µA and the leakage current 0.2 µA, the value of the backup time is around
3h8
If the capacitor is 2 Farad ant the discharge intensity 1 µA the time is
then around 380h
For the number of days in the month the time should be or 720 or 744 hours
.To make a better approch w'll know more about the minimum maintain voltage
and the intensity .
Well I'll wait now for 6 months an try again
Best regards
Thomas
----- Original Message -----
From: "Gerhard Dangl" <gerhard@...>
To: <kiwiosd@yahoogroups.com>
Sent: Sunday, May 03, 2009 1:00 AM
Subject: Re: [kiwiosd] GPS are growing old
>
> Hello Thomas and Geoff,
>
>> I've also sent my results to Tim Piercy and here is his answer:
>>
>> <Hello,
>>
>> <I didn't think there was an internal battery and to confirm I took one
>> apart yesterday and found <there is no battery inside a GPS 18.
>>
>> that lets me perplexed because I cant' understand how the internal
>> memories
>> could update time and date without any power source.
>
> what about the use of a Goldcap?
>
> Because up to date RTC technology needs only few microamps I can imagine
> that a Goldcap could do the supply job for a relative long time after
> power
> down. And this part would not have the limited live time like every
> lithium
> battery has.
>
> Regards
> Gerhard
> www.dangl.at
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>
Hello Thomas and Geoff,
> I've also sent my results to Tim Piercy and here is his answer:
>
> <Hello,
>
> <I didn't think there was an internal battery and to confirm I took one
> apart yesterday and found <there is no battery inside a GPS 18.
>
> that lets me perplexed because I cant' understand how the internal
> memories
> could update time and date without any power source.
what about the use of a Goldcap?
Because up to date RTC technology needs only few microamps I can imagine
that a Goldcap could do the supply job for a relative long time after power
down. And this part would not have the limited live time like every lithium
battery has.
Regards
Gerhard
www.dangl.at
Valued Customers,
I have gathered all the leftover components from the last production run and
have put together eight (8) KIWI-OSDs. These OSDs are identical to the units i
was selling before; the only difference is that i had to do the final assembly
myself rather than the assembly house. They all have the recall repair applied
to them and have been tested.
I have (8) Garmin 18X GPSs as well.
I am making them available to the first 8 people who place an order from my
order web page. They are offered at the same pricing as before. One KIWI and one
GPS for $260 USD.
I will only sell them in pairs (1 KIWI-OSD and 1 GPS).
I am also limiting each person to one (1) KIWI-GPS and (1) GPS only.
Place you order here:
http://www.pfdsystems.com/kiwiorder.html
I will not accept email or phone orders since i want everybody to have the same
chance in placing an order. Foreign orders are welcome.
I currently don't have any extension cables but if you really need one, i can
make one up for you; but there will be a delay since i have to order additional
cable.
I also have a few Y-power splitters and a large stock of BNC connectors and
AC/DC adapters.
Please don't email or call me to ask if your order was placed in time. I will
respond to each order individually and let you know.
Regards,
Vince
PFD Systems
Hello Geoff
I've also sent my results to Tim Piercy and here is his answer:
<Hello,
<I didn't think there was an internal battery and to confirm I took one
apart yesterday and found <there is no battery inside a GPS 18.
that lets me perplexed because I cant' understand how the internal memories
could update time and date without any power source.
If the broken GPS still exists it may be possible to inspect it , to check
if that assertion is true or false.
Many thanks for photos and text Could I translate it in french to the Gps
18LVC users
Regards
Thomas
---- Original Message -----
From: "Kiwi Geoff" <geoff36@...>
To: <kiwiosd@yahoogroups.com>
Sent: Thursday, April 30, 2009 11:05 AM
Subject: Re: [kiwiosd] GPS are growing old
>
> Thomas Flatres wrote:
>> The GPS are growing old
>> It is because the internal battery.
>
> Yes I agree Thomas, my oldest Garmin GPS now takes a long time to get
> a first FIX after being powered OFF for a long time.
>
> Perhaps the "take home message" might be - we should allow up to 10
> minutes for the Garmin 18 LVC to get a FIX after it has been unused
> for a time. This amount of time will allow for a discharged (or dead)
> battery inside the Garmin GPS.
>
>> Garmin could change it but I've no idea of the cost.
>
> I'm not sure they would bother Thomas, the case is a water-proof seal,
> and if you have a look at the following images:
>
> http://geoff36.googlepages.com/insidegarmin18lvcgps
>
> the battery will be mounted under the metal shield, and could be
> difficult to replace.
>
> As long as we allow for this "old battery" condition, we can still use
> the GPS, as long as we wait for 10 minutes for a first FIX (because
> the GPS has lost all track of time and date).
>
> I guess eventually the internal battery in the Garmin 18 could start
> to leak and so corrode the GPS electronics - and at that point the GPS
> will fail completely!
>
> Regards, Geoff.
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>
Thomas Flatres wrote:
> The GPS are growing old
> It is because the internal battery.
Yes I agree Thomas, my oldest Garmin GPS now takes a long time to get
a first FIX after being powered OFF for a long time.
Perhaps the "take home message" might be - we should allow up to 10
minutes for the Garmin 18 LVC to get a FIX after it has been unused
for a time. This amount of time will allow for a discharged (or dead)
battery inside the Garmin GPS.
> Garmin could change it but I've no idea of the cost.
I'm not sure they would bother Thomas, the case is a water-proof seal,
and if you have a look at the following images:
http://geoff36.googlepages.com/insidegarmin18lvcgps
the battery will be mounted under the metal shield, and could be
difficult to replace.
As long as we allow for this "old battery" condition, we can still use
the GPS, as long as we wait for 10 minutes for a first FIX (because
the GPS has lost all track of time and date).
I guess eventually the internal battery in the Garmin 18 could start
to leak and so corrode the GPS electronics - and at that point the GPS
will fail completely!
Regards, Geoff.
Here are the test results on two GPS 18LVC One was bougth in 2004 the other in 2007 Process: The GPS has been fed during 24 hours starting on 2009/02/23 Near two months later a test is performed the GPS are shielded in a metalic box Using the sofware SNSRCFG 320 from Garmin,only the sentence $GPRMF is enabled. Then the software TERMINAL is used ,the Startlog is enabled,the shield is removed. When the FIX is reached the Startlog is disabled. It was a foggy day.
Geoff and Hank,
Thanks for the help. After doing the reset on the 18x, everything seems to be
working correctly.
Richard
--- In kiwiosd@yahoogroups.com, Kiwi Geoff <geoff36@...> wrote:
>
> Hank Sielski wrote:
> > I'll bet it was the leapsecond...If the unit you bought in February
> > hadn't been turned on or tested after the first of the year, then
> > the internal data it had at the start to compare GPS time to UTC
> > would have been off by a second...after you download a new almanac
> > etc. and do a re-set, it "heals" itself...
>
> Thanks Hank.
>
> Richard, to carry out what Hank suggests above - please try the following.
>
> Power up the 18x/KIWI combo, once it has a FIX ignore that the time is
> 1 second FAST. Now let the unit run for a "half hour" without
> interruption (with reasonable view of SKY).
>
> At the end of the half hour, the time will still be 1 second fast! Now
> remove the power from the 18x/KIWI combo, wait five seconds then
> re-apply the power. Once it has a FIX, you should now have the time
> correct with USNO etc.
>
> If KIWI is still 1 second fast AFTER the above "self healing" - we
> must assume your 18x has a fault, please contact Vince for help.
>
> Regards, Kiwi Geoff.
>
I am officially out of stock of KIWI-OSDs. I will fulfill orders in the order
they arrived. I am also waiting on 18X GPS units as they are back-ordered from
Garmin. I might not get them till after the 17th of April, according to Garmin.
I have a few GPSs in stock and will send those to the first few customers who
have ordered first.
If i am able to put together a few more OSDs, i will let everybody know though
these forums.
Thank you for your patience.
vince
pfd systems
Hank Sielski wrote:
> I'll bet it was the leapsecond...If the unit you bought in February
> hadn't been turned on or tested after the first of the year, then
> the internal data it had at the start to compare GPS time to UTC
> would have been off by a second...after you download a new almanac
> etc. and do a re-set, it "heals" itself...
Thanks Hank.
Richard, to carry out what Hank suggests above - please try the following.
Power up the 18x/KIWI combo, once it has a FIX ignore that the time is
1 second FAST. Now let the unit run for a "half hour" without
interruption (with reasonable view of SKY).
At the end of the half hour, the time will still be 1 second fast! Now
remove the power from the 18x/KIWI combo, wait five seconds then
re-apply the power. Once it has a FIX, you should now have the time
correct with USNO etc.
If KIWI is still 1 second fast AFTER the above "self healing" - we
must assume your 18x has a fault, please contact Vince for help.
Regards, Kiwi Geoff.
I'll bet it was the leapsecond...If the unit you bought in February hadn't been turned on or tested after the first of the year, then the internal data it had at the start to compare GPS time to UTC would have been off by a second...after you download a new almanac etc. and do a re-set, it "heals" itself...
Maybe Geoff or Vince can comment more authoritatively...
Hank
On Tue, Apr 7, 2009 at 9:10 AM, Richard McKee <r.d.mckee@...> wrote:
I purchased a Garmin 18x around the middle of February 2009. With each use
of the KIWI-OSD, on the first press of the INFO button, I get the error
message saying to use the field count. Prior to the button press, the time
displayed is also off by 1 second when compared to the telephone time from
the US Naval Observatory. Any subsequent press of the INFO button indicates
that the times are OK and the time matches the USNO time. What am I doing
wrong? The only thing I did was to disconnect my Garmin 18 and connect the
Garmin 18x.
I purchased a Garmin 18x around the middle of February 2009. With each use
of the KIWI-OSD, on the first press of the INFO button, I get the error
message saying to use the field count. Prior to the button press, the time
displayed is also off by 1 second when compared to the telephone time from
the US Naval Observatory. Any subsequent press of the INFO button indicates
that the times are OK and the time matches the USNO time. What am I doing
wrong? The only thing I did was to disconnect my Garmin 18 and connect the
Garmin 18x.
Thanks,
Richard McKee
All,
Let me first say that PFD Systems is NOT going out of business. The decision to
stop production of the KIWI was Geoff's and he owns the intellectual property. I
will continue to support the KIWI and also continue to offer the accessories
(GPSs, cables, etc.).
I am also starting design on a replacement unit, but at this time I cannot
provide any further details, especially a time line.
I have about 20 units left and can possibly create another 5 or so from parts on
hand. There will additional information on our website in the future.
I will handle the remaining stock as orders are taken.
Regards,
Vince Sempronio
PFD Systems
Geoff, sorry to see the end of production for the KIWI-OSD. Mine has always
worked perfectly. I don't think I contributed to the support work load at all,
I hope. My second unit just shipped.
Best of luck with all your projects, especially enjoying life.
Geoff,
thank you for your NMEA records and additional infos.
>> But at this moment of leap seconds number change 14/15 in RMF sentence
>> the
>> UTC time output did not change too. The output time was still ahead by
>> one
>> second.
>
> Are you sure that was the case Gerhard ?
No, and I am sorry about because I had forgotten to re-initialize the
KIWI-OSD after almanac was reloaded in the GPS.
A new test today with NMEA recording in a text file showed same result as
recorded by you. The GPS immediately change on the fly to the right UTC
without the need of a startup.
But on my inside measurement place with difficult receiving conditions I am
always astonished about the short time needed until the first fix of the
newer model 18x after power on.
Regards
Gerhard
www.dangl.at
Thomas Flatres wrote:
> Is your SNSRXCFG a recent version or an old one?
> I suppose that the almanacs a inthe soft
I used the "latest" version, the command "Set AutoLocate" is also
available on the SNSRCFG software.
All the command does Thomas is send the ASCII string:
$PGRMI,,,,,,,A <CR> <LF>
to the Garmin sensor. So you can use any (GPS speaking) software to
send the command. The command causes a "cold start", it does not
contain the almanac data itself. So the "old" almanac (that is causing
the 1 second timing error) is contained in the firmware of the 18X
sensor.
It is interesting to note, that the command
$PGRMI,,,,,,,A <CR> <LF>
does not cause the "18" sensor to do anything !
However the "RESET" command:
$PGRMI,,,,,,,R <CR> <LF>
works in "both" the 18 and 18X sensors.
Regards, Geoff.
Geoff,
> Just one issue that I have noticed Gerhard with the 18x - if you use
> the SNSRXCFG (Garmin software program), and issue the command "Set
> Autolocate". It causes the 18X to restart using an "old" almanac. Once
> it has a FIX, it starts showing the time 1 second FAST (using a 14
> second delta between GPS and UTC time). After 12 or so minutes (when
> it has downloaded a new almanac) it inserts a leap second (15 second
> delta between GPS and UTC). So one can "re live" the leap second as
> many times as you like. This is using 18X firmware version 3.00
> (issued 11th Feb 2009) - which should have included the leap second
> change.
I run the same test with the same result. What I could see was that the GPS
18x changed the number of leap seconds from 14 to 15 in the RMF sentence
after receiving the new almanac.
But at this moment of leap seconds number change 14/15 in RMF sentence the
UTC time output did not change too. The output time was still ahead by one
second.
I had to power OFF-ON the GPS device once to get the current right UTC with
15 leap seconds inserted from now on.
Additionally note:
I can easy see if I have the GPS18 or the newer GPS18x connected to the
KIWI-OSD. During power on only the older GPS18 makes a short flash of the
1PPS LED in the KIWI-OSD device. If the newer GPS18x is connected you will
see nothing during power on. There must be a difference in the level
behaviour of the 1PPS outputs during power on.
Of course, with both types after a fix the LED inside starts to flash once
per second.
Regards
Gerhard
www.dangl.at
Please note: Although Gerhard and I have found some minor "issues"
with the 18X sensor, these do not impact on normal use for timing.
These kind of issues are normal for a "new" product of such
complexity.
Gerhard Dangl wrote:
> I run the same test with the same result. What I could see was that the GPS
> 18x changed the number of leap seconds from 14 to 15 in the RMF sentence
> after receiving the new almanac.
Yes, I agree Gerhard.
> But at this moment of leap seconds number change 14/15 in RMF sentence the
> UTC time output did not change too. The output time was still ahead by one
> second.
Are you sure that was the case Gerhard ?
I just repeated the experiment, and logged the serial data from the
GPS, I have edited the logged data to make it easy to see what
happens.
I firstly issued a "Set Autolocate" command to the Garmin 18X, we can
see the GPS received my command because it repeated the command back
to me:
$GPRMC,225137,A (at this stage the UTC time is correct to my other clocks)
$GPGGA,225137,
$PGRMF,500,255112,240309,225137,15, (15 second delta GPS - UTC)
$GPRMC,225138,A
$GPGGA,225138,
$PGRMF,500,255113,240309,225138,15,
$PGRMI,,,,,,,A (this is "my" Set AutoLocate command)
$GPRMC,225138,A (notice the UTC time is the same as previous second)
$GPGGA,225138
$PGRMF,500,255112,240309,225138,14 (14 second delta GPS - UTC)
Notice also the "GPS seconds of week" (255112) has jumped back 2
seconds, I assume this is the GPS using its own clock to get the
initial "approximate" time to start searching for satellites. This
timing error gets corrected as soon as the GPS gets a FIX.
44 seconds later the 18X GPS gets a position FIX
$PGRMF,500,255136,240309,225202,14,
$GPRMC,225203,A,
$GPGGA,225203,,1,00,1.4,6.3,M,9.6
$PGRMF,500,255137,240309,225203,14,
$GPRMC,225204,A,
$GPGGA,225204,,1,04,1.4,6.3,M,9.6 ( FIX with 4 satellites)
$PGRMF,500,255138,240309,225204,14,
$GPRMC,225206,A, (GPS time now jumps 1 second with actual FIX )
$GPGGA,225206,,1,05,2.9,0.2,M,9.6,M,,*6B
$PGRMF,500,255140,240309,225206,14, (UTC still 1 second FAST )
Approximately seven minutes later, the 18X had downloaded a new
almanac and so we see the UTC time changing in the various sentences.
$GPGGA,225839,
$PGRMF,500,255533,240309,225839,14,
$GPRMC,225840,A,
$GPGGA,225840,
$PGRMF,500,255534,240309,225840,14,
$GPRMC,225840,A, (LEAPSECOND - time stamp same as previous second)
$GPGGA,225840,
$PGRMF,500,255535,240309,225840,15, (GPS - UTC now 15 second delta)
$GPRMC,225841,A,
$GPGGA,225841,
$PGRMF,500,255536,240309,225841,15,
$GPRMC,225842,A,
$GPGGA,225842,
Notice in the above sequence, the GPS time remains uniform (255533 to 255536),
it is only the "UTC time" that is shifted back one second.
At this stage, the 18X GPS UTC time, is correct to my other precision clocks.
> I had to power OFF-ON the GPS device once to get the current right UTC with
> 15 leap seconds inserted from now on.
You shouldn't need to do this part Gerhard, the GPS will (eventually)
self correct, however if KIWI OSD was started BEFORE the GPS corrected
itself, KIWI will "remain" 1 second FAST (although at the end of the
timing run, when it does the final integrity check, it will show the
timing error).
Another issue I have found with the 18X Gerhard:
I just tried to download an almanac from the 18x sensor using the command
$PGRMO,GPALM,1
and it doesn't work with the latest firmware version (3.00) of the
18X, yet it works OK with an "18" sensor. I was hoping to find the Toa
(Time of Applicability) of the almanac, but the 18X sensor wont
provide the almanac (although the manual/ data sheet for the 18X says
the command can be used).
> Additionally note:
> I can easy see if I have the GPS18 or the newer GPS18x connected to the
> KIWI-OSD. During power on only the older GPS18 makes a short flash of the
> 1PPS LED in the KIWI-OSD device. If the newer GPS18x is connected you will
> see nothing during power on. There must be a difference in the level
> behaviour of the 1PPS outputs during power on.
Yes, I assume it is just the difference between the "boot" of the two
GPS devices, the "18" appears to flick the 1PPS output as it sets
itself up for work.
Regards, Geoff (New Zealand).
Hello Geoff
----- Original Message -----
From: "Kiwi Geoff" <geoff36@...>
To: <IOTAoccultations@yahoogroups.com>
Cc: "PLANOCCULT" <planoccult@...>; "RASNZ"
<RASNZoccultations@yahoogroups.com>; "KIWI OSD" <kiwiosd@yahoogroups.com>
Sent: Monday, March 23, 2009 11:53 PM
Subject: [kiwiosd] Re: [IOTAoccultations] GPS18x LVC in comparison
>
> Gerhard Dangl wrote:
>> About my present results I have made a bilingual page:
>> http://www.dangl.at/ausruest/gps18lvc_e.htm
>
> An excellent page Gerhard, thank you.
>
> I learned a couple of matters that I had not yet noticed regarding the
> 18x, so your page is a very useful reference.
>
> Just one issue that I have noticed Gerhard with the 18x - if you use
> the SNSRXCFG (Garmin software program), and issue the command "Set
> Autolocate". It causes the 18X to restart using an "old" almanac. Once
> it has a FIX, it starts showing the time 1 second FAST (using a 14
> second delta between GPS and UTC time). After 12 or so minutes (when
> it has downloaded a new almanac) it inserts a leap second (15 second
> delta between GPS and UTC). So one can "re live" the leap second as
> many times as you like. This is using 18X firmware version 3.00
> (issued 11th Feb 2009) - which should have included the leap second
> change.
Is your SNSRXCFG a recent version or an old one?
I suppose that the almanacs a inthe soft
>
> I have been running a new 18X continuously (24/7) for 5 weeks now, in
> a poor reception situation, to see if I can force the sensor to make a
> 1PPS mistake. However KIWI OSD has not latched a single error (by
> flashing X's on the time). I am using "mains" to power the test, but
> using a multi-box that has inbuilt surge protector and low pass filter
> - that provides very clean AC power.
>
> So my testing has convinced me, that the Garmin 18X LVC can be a drop
> in replacement for the Garmin 18 LVC. However it is quite a different
> sensor, and it will be interesting to see how the greater RF
> sensitivity of the 18X will play out over the next few years, as we
> get to know the device better.
There are two ways to improve the sensitivity:
Sharping the channel filters
Using a RF amplifier with a good noise figure( it is perhaps the raison of
the higther consumption of the18X
>
> Regards, Geoff (New Zealand).
>
Regards , Thomas
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>
Gerhard Dangl wrote:
> About my present results I have made a bilingual page:
> http://www.dangl.at/ausruest/gps18lvc_e.htm
An excellent page Gerhard, thank you.
I learned a couple of matters that I had not yet noticed regarding the
18x, so your page is a very useful reference.
Just one issue that I have noticed Gerhard with the 18x - if you use
the SNSRXCFG (Garmin software program), and issue the command "Set
Autolocate". It causes the 18X to restart using an "old" almanac. Once
it has a FIX, it starts showing the time 1 second FAST (using a 14
second delta between GPS and UTC time). After 12 or so minutes (when
it has downloaded a new almanac) it inserts a leap second (15 second
delta between GPS and UTC). So one can "re live" the leap second as
many times as you like. This is using 18X firmware version 3.00
(issued 11th Feb 2009) - which should have included the leap second
change.
I have been running a new 18X continuously (24/7) for 5 weeks now, in
a poor reception situation, to see if I can force the sensor to make a
1PPS mistake. However KIWI OSD has not latched a single error (by
flashing X's on the time). I am using "mains" to power the test, but
using a multi-box that has inbuilt surge protector and low pass filter
- that provides very clean AC power.
So my testing has convinced me, that the Garmin 18X LVC can be a drop
in replacement for the Garmin 18 LVC. However it is quite a different
sensor, and it will be interesting to see how the greater RF
sensitivity of the 18X will play out over the next few years, as we
get to know the device better.
Regards, Geoff (New Zealand).