Time synchronization for APR64 / APR64M

Transcription

1 03/21/2013 Edition Time synchronization for APR64 / APR64M dfv Technologie Z.A. Ravennes-les-Francs 2 avenue Henri Poincaré BP BONDUES CEDEX FRANCE Tel : 33 (0) Fax : 33 (0) contact@dfv.fr Site Web :

2 SOMMARY Généralités...3 Traitement des erreurs et des pertes de synchronisation horaire...4 Protocole STET...5 Protocole IRIG-J17 (Standard )...6 Protocole IRIG-J "STRING-A"...7 Protocole IRIG-J "STRING-C"...8 Protocole NMEA 0183 (Récepteur GARMIN + top pps)...9 Protocole NTP...10 Tiroir IRIG-B (APR64)...11 Connexion sur APR64M

3 General Measurements of the APR64 can be synchronized either by internal clock or external clock (Satellite ). APR64 deals with the following norms : - STET clock(from SCLE or ACEB receivers) Software option STET - Analog IRIG-B signal (IRIG-B Rack + Software) not possible on APR64M - pps signal and IRIG-J message I/O rack is necessary on APR64 - pps signal alone I/O rack is necessary on APR64 - APR64 can also be synchronized by externals signals (10min, 60min or 24H) I/O rack is necessary on APR64 - Synchronization by Ethernet in NTP (Software option) - Synchronization by pps signal and with NMEA 0183 (Message " GPRMC") with a GARMIN receiver I/O rack is necessary on APR64-3-

4 Errors on loss of time synchronization 1) If no external synchronization is programmed, "Ext time status" led if OFF and APR64 is synchronized by internal clock (time is set by APRWIN64) 2) If a pps time synchronization is programmed, "Ext time status" led blinks when receiving pps. If pps signal is lost "Ext time status" led stay ON. In case of loss of pps, APR64 uses internal clock. When pps is back, if internal clock is not synchronized with external clock, measures stops and restart. An error message is written in APR64 log file. 3) If synchronization is done by 10 min, 24 hour top, then the "Ext time status" led is ON if a top has been lost. 4) If time synchronization is done by pps signal and RS232 message (IRIG-J or NMEA GARMIN), then the "Ext time status" led blinks when receiving pps. "Ext time status" led is ON if pps is lost. 5) If time synchronization is done with STET RS232 protocol, "Ext time status" led is ON if no message has been received withing 1min10sec. 6) If time synchronization is done by NTP, "Ext time status" led is ON if NTP server doesn't answer. Note : Sometimes NTP servers have problems. In case of error wait a little Internal "system states" for time synchronization are available on APR64. They can be used in OR,AND formulas, and for relays State : Loss of time message (1 if message is not received) State : Loss of pps (1 when pps is lost)) State : Desynchronization (1 when pp sis lost and internal time is not good) State : Loss of RTC time (1 when RTC backuped time has been lost) State : Invalide time (1 when time is incorrect) -4-

5 STET protocol Message send as text 1200bauds / 8 bits even parity / 2 stop bits Message : $FF $01 aa $02 js j m An h mn s $03 $16 aa : Status (8 bits) : 0 0 F G1 G0 R D1 D0 F=1 férié G1 G0 = 10 summer time G1 G0 = 01 winter time R = 0 : correct receive (status Bit) 1 : bad receive D1 D0 = 00 conformity to TUC at about 3ms D1 D0= 01 conformity to TUC is garantied under reserve any TUC correction has occured since the 1 state has been leaved Js : day of the week (BCD) coded 1=Monday 7=Sunday J : day (BCD coded ) from 1 to 31 M : month (BCD coded ) from 1 to 12 An : year (BCD coded) from 0 to 99 H : Time (BCD coded) from 0 to 23 Mn : minute (BCD coded) from 0 to 59 S : second (BCD coded) from 0 to 59 Note : Message is send every minute by SCLE / ACEB clock Cable to be used to connect SCLE (RH2002) clock must be wired as following scheme : DB9 Male connector DB9 Female connector (serial #3) SCLE clock side APR64 side DCD 1 4 DTR DSR 6 1 DCD DTR 4 6 DSR RTS 7 8 CTS CTS 8 7 RTS TXD 6 2 RXD Schield GNDmeca 3 3 TXD GND 1 5 GND Cable length must be maximum 10 meters -5-

6 IRIG-J17 protocol (Standard ) ASCII message is send every second Start bit of the 1 st character indicated the change of the second. Messages send in format 9600 bauds, 7-bits ASCII, even parity Message : 1 SOH (start of header) $01 2 hundred's of day (1-366) $30-$33 3 tens of the day (1-366) $30-$39 4 unit's of the day (1-366) $30-$39 5 : ASCII colon $3A 6 tens of hours $30-$32 7 hours $30-$39 8 : ASCII $3A 9 tens of minutes $30-$35 10 minutes $30-$39 11 : ASCII $3A 12 tens of seconds $30-$36 13 seconds $30-$39 14 CR (Carriage return) $0D 15 LF (line feed) $0A Example: <SOH>112:12:34:36<CR><LF> Is decoded as : 112th day of the year, hour, minute, seconds 12:34:36 RS232 pps Serial #3 of APR64 pps input of APR64-6-

7 IRIG-J protocol "STRING-A" This protocol is very similar to IRIG-J17, there are only 2 bytes for year. ASCII message is send every second Start bit of the 1st character of the message indicates the change of the second. Message is 9600 bauds, 8-bits ASCII, without parity Message : 1 SOH (start of header) $01 2 hundreds of day of year $30-$33 3 Tens' of day of year $30-$39 4 unit of day of year $30-$39 5 : ASCII colon $3A 6 tens of hours $30-$32 7 hours $30-$39 8 : ASCII $3A 9 tens of minutes $30-$35 10 minutes $30-$39 11 : ASCII $3A 12 tens of seonds $30-$36 13 seconds $30-$39 15 tens of year $30-$39 Modification / IRIG-J17 16 year $30-$39 17 CR (carriage return) $0D 18 LF (line feed) $0A Example: <SOH>112:12:34:36:10<CR><LF> Is decoded as : 112th day of the year, hour/minut/second 12:34:36 year 2010 RS232 pps serial #3 of APR64 pps input of APR64-7-

8 IRIG-J protocol "STRING-C" This protocol is very similar to IRIG-J17, there are only 2 bytes for year and a quality indicator. ASCII message is send every second Start bit of the 1st character of the message indicates the change of the second. Message is 9600 bauds, 8-bits ASCII, without parity Message <CR><LF>Q YY DDD hh mm ss.000 Contenu de la trame : <CR><LF> HEX 0D,0A Q Quality indicator: = synchronized? = desynchronized "E"= Error, invalid time "T"= Top Minute (In this case message is zero : T :00:00.000) HEX 20 Space Or ":" YY Year: tens of year and year DDD day of the year hh time: mm minute: ss seconds: ASCII.000 Example : <CR><LF>? :34: Is decoded as : Desynchronized (?), Year (20)02, 112th day of the year, hour/minutes/seconds: 12:34:36 RS232 pps Serial #3 of the APR64 pps input of APR64-8-

9 NMEA 0183 protocol (GARMIN receiver )+ top pps ASCII Message is send every second Start bit of the 1st character of the message indicates the change of the second. Message is 4800 bauds, 8-bits ASCII, without parity Message : $GPRMC,HHMMSS,A,latt,N,long,W,000.0,xxx,JJMMAA,yyy,E*69 Example : $GPRMC,125008,A, ,N, ,E,000.0,181.9,281010,001.3,W*66 Is decoded as : 28/10/2010 à 12H50Mn08sec Pps input of APR64 Pps led +12V APR64 GPS / APR64 interface RS232 n 3 APR64-9-

10 NTP protocol This time synchronization protocol is an option of the APR64. It allows to setup time of the APR64 from Ethernet/Internet Network. The setup of the parameters is done by APRWIN64 software. Name or IP address of the NTP server, interval of synchronization must be set. Note : if using a name for the NTP server, DNS server address must be set. Example of configuration -10-

11 IRIG-B Rack (APR64) This rack receives the IRIG-B signal (AFNOR NFS87-500) and decodes it in IRIG-J protocol Blinks every second when receiving a correct IRIG-B signal IRIG-B input BNC (insulated) 1pps output (BNC) 5V To be connected to the I/O synchro rack RS232 Output (DB9) to be connected to serial #3 IRIG-J17 protocol in input Serial link is connected on serial #3 of the APR64 with an RS232 crosswired cable and pps output is connected to pps input of the I/O synchro rack with a BNC 50Ohms shielded cable. Note : IRIG-B protocol don't contains year. Year must be setted with the APRWIN64 Software. IRIG-B Rack I/O Synchro rack I/O rack IRIG-B signal -11-

12 Connection on APR64M pps synchronization input 0 to 24V DC Insulated 12V output 450mA (allows to power GARMIN receiver) Note : APR64M can't be synchronized by IRIG-B protocol -12-