Project Deliverable D50 Report on Best Practices ... - ESONET NoE

e: connection e represents the connection between the communication Switch and a
communication Modem. In some cases, Switch block and Modem block could be a single
block.
f: connection f represents the connection between marine node or Junction Box and the shore
station. It can be wired or wireless.
g: connection g represents communication between communication Modem and Main
Controller at Shore Station.
h: connection h represents communication between the Shore Station Controller and a
Memory Buffer. This buffer doesn’t represent a full database or main archive.
i: connection i represents how different clients could be accessed Controller Shore Station
j: connection j represents how an Operator or various Operators communicate with Shore
Station Controller.
L. connection L represents how the controller saves data into a full database or Archive.
k: connection k represent communication between Clients to main Archive.
m&n: connections m and n represents how a timing clock gets the Controllers at Shore or Sea
stations
Proposed and most common standards or initiatives used per connection
Different standards and protocols have been tested with different observatories topologies.
Other are well known and commonly used in nowadays observatories.
Link Standards, Protocols or initiatives to take into account
a Analog
b RS232, RS485, RS422, CAN, 1451.X, PUCK, ETH,USB, SWE, ZeroConf
c Eth, RS485, RS422, CAN, USB, ZeroConf
d Eth, RS232, CAN, USB, RS422, ZeroConf
e
f Eth, RF, Acoustic, Satellite, IEEE1451.0, SWE,ZeroConf
g Eth, RS232,CAN, USB, RS422, ZeroConf
h
i SWE, SOS, DataTurbine, ZeroConf
j SWE, SPS, SAS, ZeroConf
k SWE, SOS
L SWE, ZeroConf
m PPS+NMEA, IEEE1588 PTP
n PPS+NMEA, IEEE1588 PTP
Other standards that may apply
Time synchronization
IEEE1588 PTP and NTP over TCP/IP Network
NMEA over RS232, RS485 and Eth
PPS over TTL, RS232, RS485
<strong>Deliverable</strong> #50 - update October 2010 31