Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Es127
07-20-16, 04:41 PM
Post: #1
Es127
What is the cable that is needed to run from a es127 to the hs it is a conversion cable from device net it looks like. So I can run a cp370 to the es127. I will be running 1 es127 and 1 es128 along to a cp370 to a vhf260 along with a vhf70 with ais, also a sr150 and linking into a vv7 along with a acu200 and a p70r. Autopilot. Just having trouble figuring all the cables with STng. And help would be a welcomed sight. Thank you.
Find all posts by this user
Quote this message in a reply
07-21-16, 10:48 AM
Post: #2
RE: Es127
Welcome to the Raymarine Forum Wildride1,

Of the products which you have listed , only four feature an Ethernet communications interface: eS127, eS128, SR150, and CP370. Each of the MFDs feature two Ethernet Network sockets. These will be used to interface the MFDs to one another. The remaining Ethernet Network socket of one of the MFDs will be interfaced to the Ethernet Network socket of the SR150, and the remaining Ethernet Network socket of other MFD will be interfaced to the Ethernet Network socket of the CP370. Appropriate lengths of RayNet (F) to RayNet (F) Cable will be used to network these products to one another.

One of the MFDs (to be designated as the system's Data Master), EV-1 Sensor Core, ACU200, p70R, Ray70, and VV7's (assumed to support NMEA 2000 via its NMEA 2000 socket ... check with Mercury Marine) will each be interfaced as spurs to a powered and properly terminated SeaTalkng backbone. Raymarine offers SeaTalkng Spur to DeviceNet (F) and SeaTalkng Spur to DeviceNet (M) adapter cables to support interfacing third party NMEA 2000 products (ex. VV7) as spurs to a SeaTalkng backbone.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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