[time-nuts] Z3805, Port 2

BD Systems Inc. bdsysco at yahoo.com
Thu Apr 4 17:35:24 EDT 2013


See below:Broadcast (Continuous Output) Mode:
The Serial Port (Port 2) interface is used by 
the GPS Receiverto broadcast 
the time of day and abbreviated status once every two seconds on the even 
second.  The length of the transmission is 16 bytes and is partially decoded 
below (The data is shown in Hex):
               00  09  01 07  03 
 01 04  04  00  02  03  01 03  00  00  0D
All numerical data is transmitted as a single 
byte per digit, i.e. digit 9 is transmitted as 09 Hex.
Bytes 1-2 are two least significant digits of 
the Year (00 09) 2009.
Bytes 3-5 are the numerical Day of the Year 
(01 07 03) or day 173 (June 22).
Bytes 6-7 are the Hour (01 04), hour 14 or 2 
PM.
Bytes 8-9 are the Minute (04 00), minute 
40.
Bytes 10-11 are the Second (02 03), second 
23.
Bytes 12-13 are the Accumulated Leap Seconds 
(01 03), 13 leap seconds.
Bytes 14-15 SmartClock Mode or 
Status:
01 00: Power-Up Mode
10 00 Holdover Mode
00 00 GPS Lock Mode
Byte 16 is a Carriage Return (0D).
Under the example above, the Date and Time is 
June 22, 2009 (day 173) at 14:40:23,  and no Holdover.
On the Port 
2serial interface, the serial port parameters are 
fixed at 9600, N, 8, 1and 
cannot be changed.  Although the Port 2connector is wired for Receive Data (pin 
3) it does not appear that the GPS Receiverwill accept any commands. 
 All commands must be issued over the Port 
1serial interface connector.
 
Chuck Zabilski
BD Systems, Inc.
 

________________________________
 From: "time-nuts-request at febo.com" <time-nuts-request at febo.com>
To: time-nuts at febo.com 
Sent: Thursday, April 4, 2013 10:00 AM
Subject: time-nuts Digest, Vol 105, Issue 10
  
Send time-nuts mailing list submissions to
    time-nuts at febo.com

To subscribe or unsubscribe via the World Wide Web, visit
    https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
or, via email, send a message with subject or body 'help' to
    time-nuts-request at febo.com

You can reach the person managing the list at
    time-nuts-owner at febo.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of time-nuts digest..."


Today's Topics:

   1. Re: Z3805A Port 2. (Herbert Poetzl)
   2. Re: Z3805A Port 2. (Jim Lux)


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

Message: 1
Date: Thu, 4 Apr 2013 16:52:14 +0200
From: Herbert Poetzl <herbert at 13thfloor.at>
To: Discussion of precise time and frequency measurement
    <time-nuts at febo.com>
Subject: Re: [time-nuts] Z3805A Port 2.
Message-ID: <20130404145214.GD8336 at MAIL.13thfloor.at>
Content-Type: text/plain; charset=us-ascii

On Thu, Apr 04, 2013 at 02:32:09PM +0000, Mark C. Stephens wrote:
> I wanted to have a look at what the Z3805A puts out on Port 2.

> I can see the LEDS flickering on the BOB so its saying something.
> I connected up a terminal program set to 96008N1 and it seems there is nothing.
> So I plugged the cable into port one to check the settings:
> scpi > syst:comm:ser2:pace?
> NONE
> scpi > syst:comm:ser2:baud?
> +9600
> scpi > syst:comm:ser2:parity?
> NONE
> scpi > syst:comm:ser2:bits?
> +8
> scpi > syst:comm:ser2:sbits?
> +1
> So Serial 2 is definitely 96008N1.

> Nothing displays on the terminal program so I used a serial
> port monitor program and I see this recurring data:

> 01 03 00 09 04 01 04 02 08 02 06 01 06 00 00 0D
> 01 03 00 09 04 01 04 02 08 02 08 01 06 00 00 0D
> 01 03 00 09 04 01 04 02 08 03 00 01 06 00 00 0D
> 01 03 00 09 04 01 04 02 08 03 02 01 06 00 00 0D
> 01 03 00 09 04 01 04 02 08 03 04 01 06 00 00 0D
> 01 03 00 09 04 01 04 02 08 03 06 01 06 00 00 0D
> 01 03 00 09 04 01 04 02 08 03 08 01 06 00 00 0D
> 01 03 00 09 04 01 04 02 08 04 00 01 06 00 00 0D
> 01 03 00 09 04 01 04 02 08 04 02 01 06 00 00 0D
> 01 03 00 09 04 01 04 02 08 04 04 01 06 00 00 0D

   1  3  0  9  4  1  4  2  8  4  4  = 1309412844

> I can see its transmitting the even second time but what format
> is this and how can I use it?

$ date +"%s" # unix time (seconds since Jan, 1st, 1970)
1365086814

so, my guess is, it is seconds since some point in
time in decimal.

HTH,
Herbert


> Mark
> Vk2hmc
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.


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

Message: 2
Date: Thu, 04 Apr 2013 08:28:58 -0700
From: Jim Lux <jimlux at earthlink.net>
To: time-nuts at febo.com
Subject: Re: [time-nuts] Z3805A Port 2.
Message-ID: <515D9C3A.6040907 at earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 4/4/13 7:52 AM, Herbert Poetzl wrote:
> On Thu, Apr 04, 2013 at 02:32:09PM +0000, Mark C. Stephens wrote:
>> I wanted to have a look at what the Z3805A puts out on Port 2.
>
>> I can see the LEDS flickering on the BOB so its saying something.
>> I connected up a terminal program set to 96008N1 and it seems there is nothing.
>> So I plugged the cable into port one to check the settings:
>> scpi > syst:comm:ser2:pace?
>> NONE
>> scpi > syst:comm:ser2:baud?
>> +9600
>> scpi > syst:comm:ser2:parity?
>> NONE
>> scpi > syst:comm:ser2:bits?
>> +8
>> scpi > syst:comm:ser2:sbits?
>> +1
>> So Serial 2 is definitely 96008N1.
>
>> Nothing displays on the terminal program so I used a serial
>> port monitor program and I see this recurring data:
>
>> 01 03 00 09 04 01 04 02 08 02 06 01 06 00 00 0D
>> 01 03 00 09 04 01 04 02 08 02 08 01 06 00 00 0D
>> 01 03 00 09 04 01 04 02 08 03 00 01 06 00 00 0D
>> 01 03 00 09 04 01 04 02 08 03 02 01 06 00 00 0D
>> 01 03 00 09 04 01 04 02 08 03 04 01 06 00 00 0D
>> 01 03 00 09 04 01 04 02 08 03 06 01 06 00 00 0D
>> 01 03 00 09 04 01 04 02 08 03 08 01 06 00 00 0D
>> 01 03 00 09 04 01 04 02 08 04 00 01 06 00 00 0D
>> 01 03 00 09 04 01 04 02 08 04 02 01 06 00 00 0D
>> 01 03 00 09 04 01 04 02 08 04 04 01 06 00 00 0D
>
>     1  3  0  9  4  1  4  2  8  4  4  = 1309412844
>
>> I can see its transmitting the even second time but what format
>> is this and how can I use it?
>
> $ date +"%s" # unix time (seconds since Jan, 1st, 1970)
> 1365086814
>
> so, my guess is, it is seconds since some point in
> time in decimal.
>

perhaps since week 0  (6 Jan 1980)




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

_______________________________________________
time-nuts mailing list
time-nuts at febo.com
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

End of time-nuts Digest, Vol 105, Issue 10
******************************************


More information about the time-nuts mailing list