On Thu, Apr 04, 2013 at 08:28:58AM -0700, Jim Lux wrote: > 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) difference is roughly 55Ms (depending on the time the sample was taken) which is roughly 1.75 years, so the start date should be somewhere around October 1971, which seems a little odd to me ... but maybe it counts in half seconds since mid 1992, in which case the increment by two would happen every second. GPS time should start at Jan,6th 1980, so that doesn't really match anything here, OTOH, RTC clocks use decimal coding as well, so each byte could simply be the current RTC entry/register ... hard to say without the exact time when the sample was taken. best, Herbert > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
