Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[CA11] RS150 => ST1/E120Classic MFD
04-04-19, 12:50 PM (This post was last modified: 04-08-19 01:32 PM by Chuck - Raymarine - Moderator.)
Post: #1
[CA11] RS150 => ST1/E120Classic MFD
The post here: http://forum.raymarine.com/showthread.php?tid=36 indicates that any RS130/150 should be directly connected to the ST2 port of a E120 Classic, so:

Q1: If the ST2 port on the E120 Classic is occupied by a ST2 Keyboard, can the A06061 adapter cable be inserted into a ST2 block (that shares the ST2 keyboard) with the block connected to the MFD?

Q2: The E22158 user manual (see attached) has a schematic indicating connection of a "SeaTalkng GPS Receiver" (presumed to be a RS150) with the E22158 connecting directly into a ST1 block without the need for the E22158 to be powered.

Is this not correct?

Thanks

JP
Find all posts by this user
Quote this message in a reply
04-04-19, 03:04 PM (This post was last modified: 04-08-19 01:32 PM by Chuck - Raymarine - Moderator.)
Post: #2
RE: [CA11] RS150 => ST1/E120Classic MFD
Welcome to the Raymarine Forum JP,

Q1. The post here: http://forum.raymarine.com/showthread.php?tid=36 indicates that any RS130/150 should be directly connected to the ST2 port of a E120 Classic, so:
A1. This is an incorrect statement. Like most devices supporting CAN bus (SeaTalkng / NMEA 2000) communications the RS30/150 and E-Series Classic MFD are not designed to be directly interfaced to one another. Instead, they are designed to each be interfaced as a spur to a powered and properly terminated SeaTalkng / NMEA 2000 backbone.

Q2: If the ST2 port on the E120 Classic is occupied by a ST2 Keyboard, can the A06061 adapter cable be inserted into a ST2 block (that shares the ST2 keyboard) with the block connected to the MFD?
A2. I would recommend abandoning the SeaTalk2 Junction Block and instead create a backbone from SeaTalkng networking components. This will permit the MFD and RS130/RS150 to be plugged intor a spur socket within the backbone. It would then be recommended that the ST2 Keyboard's cable be spliced to as short SeaTalkng spur cable which in turn would be connected to one of the new backbone's spur sockets.

Q3: The E22158 user manual (see attached) has a schematic indicating connection of a "SeaTalkng GPS Receiver" (presumed to be a RS150) with the E22158 connecting directly into a ST1 block without the need for the E22158 to be powered. Is this not correct?
A3. Unfortunately, the SeaTalk to SeaTalkng Converter Kit's manual has not been updated since is was initially posted. It has since become a best practice to power the SeaTalk bus from the SeaTalk backbone and not vice versa. Please click here to view a FAQ addressing how the system's Data Master MFD and SeaTalk bus(es) should be interfaced to a system's backbone.
Visit this user's website Find all posts by this user
Quote this message in a reply
04-06-19, 09:08 AM (This post was last modified: 04-08-19 01:33 PM by Chuck - Raymarine - Moderator.)
Post: #3
[CA11] RS150 => ST1/E120Classic MFD
Hi Chuck,

Thanks for clarifying that.Thanks for your help!

BR

JP
Find all posts by this user
Quote this message in a reply
04-08-19, 08:59 AM (This post was last modified: 04-08-19 01:33 PM by Chuck - Raymarine - Moderator.)
Post: #4
RE: [CA11] RS150 => ST1/E120Classic MFD
You're welcome.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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

Contact Us