[time-nuts] Re: Lady Heather clock question

2021-07-29 Thread Arnold Tibus

Hi Bill,

I have no knowledge of the interfaces and functions.
I am with you, the problem seem to be with the device from Lucent.
I am running successful the original Trimble Tbolt I got from Tom,TvB,
(thanks again Tom!) now since long years. I am happy so far with it, a
good base as 10 MHz reference for all my measurement eqipment.
On top I do recalibrate my PRS10 with the 1PPS output from time to time.
Recently I made a new survey for the antenna position on top of my roof,
essential for good results. Easy to be done thanks to the unbeatable
tool from Mark Sims!

I wish you good results,
73
Arnold, DK2WT



Am 29.07.2021 um 14:20 schrieb B Riches via time-nuts:

  Hi Arnold,
Loaded V5 on another PC.  Did not load V6 yet.  Lucent not connected.  T and U 
change time correctly to utc.
Connected Lucent - T and U would not change time.
With V5 John sent a link to his working Tbolt. When first opened it has the 
error.  T then U corrects the time.
Looks like Lucent is the problem.  Rebooted it and it made no difference.  I 
have another lucent in the shop I will try.
Strange. I thought that LH told Lucent to change time but now think LH does the 
heavy lifting from time code from Lucent since I can change tme from Johns 
tbolt.
I am going to contact john and see if he has heard of lucent issues.  Thanks 
for your ideas - what GPS are you using?
 On Wednesday, July 28, 2021, 11:44:45 PM EDT, Arnold Tibus 
 wrote:

  Bill,
that does sound a bit strange, for me it looks like the program does not
work correct at all. When I change this way between GPS time and UTC LH
does immediately switch the time these 18 secs and does continue working
without a resetting comment.
Did you install this version 6 (the last is v. 6.14 beta) as described?
You have to have installed v 5 before and then to follow the instruction
for the beta version to install on top. John, KE5FX, does provide this
released v. 5 on his homepage. The readme for the settings is in general
still valid. See http://www.ke5fx.com/heather/readme.htm
I think in your case it will perhaps be a good idea to restart the full
installation with v.5 and then proceeding as in the instruction to
switch to the beta version. Mark Sims wrote:'This is just the .exe To
use it you will need to have v5.0 installed and working (from ke5fx.com)
and replace the v5.0 heather.exe file with this one (backup your old
.exe first).' That should then work properly. I am running Win 10 pro 64
w/o any hazzle with LH 6.14.

Good luck!

73
Arnold, DK2WT



Am 29.07.2021 um 03:30 schrieb B Riches via time-nuts:

   Hi Arnold,
I Tried that - hit t then u - clock program said resetting and will take a bid. 
 Still did not work.  Any other ideas?
73,
Bill
       On Wednesday, July 28, 2021, 07:23:28 PM EDT, Arnold Tibus 
 wrote:

   Bill, it is quite easy:
When running LH type 'T',
you will then see the list 'Reference'
then hit 'U' for UTC-time.
This should resolve the problem.

I had the same effect before
confusing on top left side is
showing 'UTC ofs: 18'
but this is only the information
for the difference GPS/ UTC time I understand.
But LH was still running with GPS-time setting.
Hope this will help you.

kind regards

Arnold, DK2WT


Am 29.07.2021 um 00:04 schrieb B Riches via time-nuts:

How can a make my LH V6.1 clock show time equal to UTC time?  It is 18 seconds 
fast = to 18 second offset.
Set up:
Windoze 10
simple con fig file = /3  /rx  /tz=-4edst
KS24361 - REF0 GPS
UTC time in greenDate, Week, TOW in yellowDate 28 Jul 2021  ro Week 2160UTC 
ofs:18 in white
When programming is running and I enter rxx/17 clock = UTC time but receiver 
has shut down.
What am I doing wrong?
Thanks for any help.
73,
Bill, WA2DVUCape May, NJ
___
time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
email to time-nuts-le...@lists.febo.com
To unsubscribe, go to and follow the instructions there.


___
time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
email to time-nuts-le...@lists.febo.com
To unsubscribe, go to and follow the instructions there.
___
time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
email to time-nuts-le...@lists.febo.com
To unsubscribe, go to and follow the instructions there.


___
time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
email to time-nuts-le...@lists.febo.com
To unsubscribe, go to and follow the instructions there.
___
time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
email to time-nuts-le...@lists.febo.com
To unsubscribe, go to and follow the instructions there.


___
time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
email to 

[time-nuts] Re: Lady Heather clock question

2021-07-29 Thread B Riches via time-nuts
 Hi Arnold,
Loaded V5 on another PC.  Did not load V6 yet.  Lucent not connected.  T and U 
change time correctly to utc.
Connected Lucent - T and U would not change time.  
With V5 John sent a link to his working Tbolt. When first opened it has the 
error.  T then U corrects the time.
Looks like Lucent is the problem.  Rebooted it and it made no difference.  I 
have another lucent in the shop I will try.
Strange. I thought that LH told Lucent to change time but now think LH does the 
heavy lifting from time code from Lucent since I can change tme from Johns 
tbolt.
I am going to contact john and see if he has heard of lucent issues.  Thanks 
for your ideas - what GPS are you using?
On Wednesday, July 28, 2021, 11:44:45 PM EDT, Arnold Tibus 
 wrote:  
 
 Bill,
that does sound a bit strange, for me it looks like the program does not
work correct at all. When I change this way between GPS time and UTC LH
does immediately switch the time these 18 secs and does continue working
without a resetting comment.
Did you install this version 6 (the last is v. 6.14 beta) as described?
You have to have installed v 5 before and then to follow the instruction
for the beta version to install on top. John, KE5FX, does provide this
released v. 5 on his homepage. The readme for the settings is in general
still valid. See http://www.ke5fx.com/heather/readme.htm
I think in your case it will perhaps be a good idea to restart the full
installation with v.5 and then proceeding as in the instruction to
switch to the beta version. Mark Sims wrote:'This is just the .exe To
use it you will need to have v5.0 installed and working (from ke5fx.com)
and replace the v5.0 heather.exe file with this one (backup your old
.exe first).' That should then work properly. I am running Win 10 pro 64
w/o any hazzle with LH 6.14.

Good luck!

73
Arnold, DK2WT



Am 29.07.2021 um 03:30 schrieb B Riches via time-nuts:
>  Hi Arnold,
> I Tried that - hit t then u - clock program said resetting and will take a 
> bid.  Still did not work.  Any other ideas?
> 73,
> Bill
>      On Wednesday, July 28, 2021, 07:23:28 PM EDT, Arnold Tibus 
> wrote:
>
>  Bill, it is quite easy:
> When running LH type 'T',
> you will then see the list 'Reference'
> then hit 'U' for UTC-time.
> This should resolve the problem.
>
> I had the same effect before
> confusing on top left side is
> showing 'UTC ofs: 18'
> but this is only the information
> for the difference GPS/ UTC time I understand.
> But LH was still running with GPS-time setting.
> Hope this will help you.
>
> kind regards
>
> Arnold, DK2WT
>
>
> Am 29.07.2021 um 00:04 schrieb B Riches via time-nuts:
>> How can a make my LH V6.1 clock show time equal to UTC time?  It is 18 
>> seconds fast = to 18 second offset.
>> Set up:
>> Windoze 10
>> simple con fig file = /3  /rx  /tz=-4edst
>> KS24361 - REF0 GPS
>> UTC time in greenDate, Week, TOW in yellowDate 28 Jul 2021  ro Week 2160UTC 
>> ofs:18 in white
>> When programming is running and I enter rxx/17 clock = UTC time but receiver 
>> has shut down.
>> What am I doing wrong?
>> Thanks for any help.
>> 73,
>> Bill, WA2DVUCape May, NJ
>> ___
>> time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
>> email to time-nuts-le...@lists.febo.com
>> To unsubscribe, go to and follow the instructions there.
>>
> ___
> time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
> email to time-nuts-le...@lists.febo.com
> To unsubscribe, go to and follow the instructions there.
> ___
> time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
> email to time-nuts-le...@lists.febo.com
> To unsubscribe, go to and follow the instructions there.
>
___
time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
email to time-nuts-le...@lists.febo.com
To unsubscribe, go to and follow the instructions there.  
___
time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
email to time-nuts-le...@lists.febo.com
To unsubscribe, go to and follow the instructions there.

[time-nuts] Re: Antenna return loss

2021-07-29 Thread Dana Whitlow
Andy,

Good point, up to a point.  But even if the antenna's amplifier itself has
a good return
loss, cheap cables like RG-174 are pure garbage and could be doing just
about
anything along their length.  And if the bottom end connector is put on by
a person
without training and the correct tooling, very bad things can happen there,
too.

Complicating the situation is the mismatch likely to occur when one tries
to power
said antenna through a bias tee or whatever.  Fortunately, if the right
kind of splitter
is used, such mismatches will occur in a "safe" location (downstream of the
splitter).

Nothing's ever simple ...

Dana


On Thu, Jul 29, 2021 at 3:42 AM Andy Talbot  wrote:

> Much talk about source return loss and splitters.
> All active GPS antennas I've met have masses of gain at the top end, 40dB
> or more.   Most of the small puck ones come with several metres of RG174
> thin coax.
>
> This is so lossy at 1.6GHz that that several metres may have perhaps 10 -
> 15dB loss.   So there's your good source impedance for the splitter 20 -
> 30dB RLoss without even considering the head amp itself.
>
> Even several metres of UR43 should have enough loss to constitute a decent
> match.
>
> Andy
> www.g4jnt.com
> ___
> time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send
> an email to time-nuts-le...@lists.febo.com
> To unsubscribe, go to and follow the instructions there.
>
___
time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
email to time-nuts-le...@lists.febo.com
To unsubscribe, go to and follow the instructions there.


[time-nuts] Antenna return loss

2021-07-29 Thread Andy Talbot
Much talk about source return loss and splitters.
All active GPS antennas I've met have masses of gain at the top end, 40dB
or more.   Most of the small puck ones come with several metres of RG174
thin coax.

This is so lossy at 1.6GHz that that several metres may have perhaps 10 -
15dB loss.   So there's your good source impedance for the splitter 20 -
30dB RLoss without even considering the head amp itself.

Even several metres of UR43 should have enough loss to constitute a decent
match.

Andy
www.g4jnt.com
___
time-nuts mailing list -- time-nuts@lists.febo.com -- To unsubscribe send an 
email to time-nuts-le...@lists.febo.com
To unsubscribe, go to and follow the instructions there.


[time-nuts] Re: Trimble GSPDO - ISSUE

2021-07-29 Thread ordnit via time-nuts

Hi there,
thank you for all the information.

I'm using a bullet antenna (don't remember the maker), on top of my 
office. Cable has 50ohm impedance (ultraflex 7) and average quality N 
connectors. Patch from splitter to receiver is 50ohm as well, but still 
using RG58, will upgrade it asap.


Update on my issue:
Yesterday I made some testing, removing the splitter and nothing changed 
(apart the samsung complaining about signal loss :)  ).


I removed the trimble board from its case, I gave a look to it and 
powered up again: well... may be a kind of magic but it works. Now the 
status led is blinking fast and this is the output I get from commands:


UCCM >STATus

   - UCCM Slot STATE-

1-1. #Now ACTIVE STATUS  [Master Manual]
1-2. #Before ACTIVE STATUS - [OCXO Warm]
2-1. #Reference Clock Operation  [Not Used]
2-2. #Current Reference Type --- [GPS]
2-3. #Current Select Reference - [GPS 1PPS]
2-4. #Current Reference Status - [Good Accuracy & Stable]
 #GPS STATUS --- [Available]
 #Priority Level --- [LINK > GPS]
 #ALARM STATUS
 #H/W FAIL [ LINK ]
 #OPERATION ALARM -- [Antenna]
3-1. #PLL STATUS --- [ENABLE]
3-2. #Current PLL MODE - [OFFSET OBSERVATION MODE]

UCCM >SYSTem:STATus?

---
57964-15 serial number  86854165 firmware ver  3.0.0.11-01LINK 
  mode

---
Reference Status __   Reference Outputs 
___

XX Ref 8KHz 0: [LOS]
XX Ref 8KHz 1: [LOS]  TFOM 3FFOM 
 1

XX Ref 8KHz 2: [LOS]  UCCM A Status[ACTIVE]
XX Ref 8KHz 3: [LOS]
>> GPS: [phase:-4.8E-06, settling]
ACQUISITION ...[GPS 1PPS 
Valid]
Tracking: 10 ___   Not Tracking: 0    Time 

PRN  El  Az  C/N   PRN  El  AzGPS  07:35:47 29 
Jul 2021

 26  73 268   45
 31  22 215   37  ANT DLY  0 ns
 16  45 309   42  Position 


 10  11 170   38  MODE Hold
 29  32  77   43
 25   6 141   34  LAT  N  43:35:11.808
 18  79  73   45  LON  E  13:31:1.216
  5  18  45   39  HGT  +228.84 
m (MSL)

 23  31 143   42
 27  19 281   40

UCCM >posstatus

-
 07/29/2021  07:36:06
-
 Position: LAT(N  43:35:11.808) LON(E  13:31:1.216) H( +228.84 m MSL)
-
 Geometry: PDOP(0.0) HDOP(0.0) VDOP(0.0)
 num of visible sats >  10
 num of sats tracked >  10
   Receiver Channel State 
 CH  0 > SateID(26) TrackMode(pos avail) SigValue(46)
 CH  1 > SateID(31) TrackMode(pos avail) SigValue(36)
 CH  2 > SateID(16) TrackMode(pos avail) SigValue(42)
 CH  3 > SateID(10) TrackMode(pos avail) SigValue(37)
 CH  4 > SateID(29) TrackMode(pos avail) SigValue(42)
 CH  5 > SateID(25) TrackMode(pos avail) SigValue(36)
 CH  6 > SateID(18) TrackMode(pos avail) SigValue(45)
 CH  7 > SateID(05) TrackMode(pos avail) SigValue(40)
 CH  8 > SateID(23) TrackMode(pos avail) SigValue(43)
 CH  9 > SateID(27) TrackMode(pos avail) SigValue(38)
 CH  10 > SateID(00) TrackMode(tracking ) SigValue( 0)
 CH  11 > SateID(00) TrackMode(tracking ) SigValue( 0)
-
 Rcvr Status(1):
-
 Antenna Voltage:  5000.00mV   , Antenna Current: 0.00mA


UCCM >DIAGnostic:LOG:READ:ALL?

Log status:  22 entries

L00:21/07/28.06:00:47 Self survey started
L01:21/07/28.06:05:30 Ref Change: GPS
L02:21/07/28.06:09:10 Ref Change: No reference
L03:21/07/28.06:09:25 Ref Change: GPS
L04:21/07/28.06:09:54 Ref Change: No reference
L05:21/07/28.06:10:07 Ref Change: GPS
L06:21/07/28.06:32:45 Ref Change: No reference
L07:21/07/28.06:33:07 Ref Change: GPS
L08:21/07/28.06:34:42 Self survey completed
L09:21/07/28.06:36:13 Ref Change: No reference
L10:21/07/28.06:36:25 Ref Change: GPS
L11:21/07/28.06:58:13 Ref Change: No reference
L12:21/07/28.06:58:25 Ref Change: GPS
L13:21/07/28.07:07:27 Ref Change: No reference
L14:21/07/28.07:07:43 Ref Change: GPS
L15:21/07/28.07:31:43 Ref Change: No reference
L16:21/07/28.07:31:55 Ref Change: GPS
L17:21/07/28.08:35:59 GPS Antenna open
L18:21/07/28.08:36:01 Ref Change: No reference
L19:21/07/28.08:36:30 Ref Change: GPS
L20:21/07/28.12:13:02 Output mode: Active
L21:21/07/28.12:13:02 A/S change: Slave(HIGH)


So far, so good.

PS: I don't belive in magic, so I guess that some glue I used to hold 
the board, added some capacitive side effects.