Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Evo 100 Networking Problem
06-14-17, 01:46 PM
Post: #2
RE: Evo 100 Networking Problem
Barry,

In the system specified there would be no need to specify Data Sources, as the system only features one source for each type of data. Communications with each of the devices within the network may be verified via the autopilot control head (MENU->SET-UP->DIAGNOSTICS->ABOUT SYSTEM). Should each of the system's devices be listed, then nothing more need typically be done.

A SeaTalk to SeaTalkng Cable would be used to support replacing a ST60 instrument with an i60 or i50 instrument. As the only devices listed have a SeaTalkng communications interface, the supplied SeaTalk to SeaTalkng Cable would not be used and should be disconnected from the instrument to avoid any potential confusion for someone servicing the system. No more than three SeaTalkng devices should be installed within a single spur. The total length of the spur created by daisy chaining the i50 and i60 instruments and then connecting them to a spur socket within the backbone cannot exceed 6m ... please verify.

The SeaTalkng backbone will need to be powered via a SeaTalkng Power Cable installed within a spur socket positioned at the approximate midpoint of the backbone's LEN load.

Finally, one blue SeaTalkng Termination Plug each must be installed within the backbone socket located at the backbone's two opposite end nodes.

Should you be having some other problem with the product and have interfaced the equipment in the manner described, then please describe the problem and attach a diagram of the system (a photo of a hand drawn diagram will suffice).
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Evo 100 Networking Problem - lenobleb - 06-12-17, 08:49 PM
RE: Evo 100 Networking Problem - Chuck - Raymarine - Moderator - 06-14-17 01:46 PM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)