[CA] [CA11] I50 and I60 compatible with my present hardware?

[Chuck - Raymarine - Moderator]

udo,

Q1. NMEA 2000 backbone that is not the SeaTalkng backbone not work, right?
A1. Incorrect. SeaTalkng is an extension of the NMEA 2000 communications messaging protocol. They are not mutually exclusive and these messaging protocols may essentially be considered to be the same. Like other marine electronics manufacturers, Raymarine produces its own NMEA 2000 Networking components and these components feature Raymarine's time proven SeaTalkng plugs and sockets. As many marine electronics manufacturers and manufacturers of NMEA 2000 networking component have chosen to utilize DeviceNet plugs and sockets within their networking components, Raymarine offers spur adapters and spur adapter cables to support interfacing devices featuring DeviceNet plugs or sockets to a NMEA 2000 backbone which has been constructed from SeaTalkng networking components. As specified within the FAQ found here, it is considered to be a best installation practice that a backbone be constructed from the networking components of a single manufacturer to ensure maximum performance and reliability of a system. As indicated within this same FAQ, third party field installable DeviceNet connectors are available to permit a backbone which has been constructed from SeaTalkng networking components to be joined to a backbone which has been constructed from third party NMEA 2000 networking components. Please click here to view a FAQ addressing how additional spur sockets may be added to a NMEA 2000 network which has been constructed from SeaTalkng networking components. Please click here to view a FAQ addressing best SeaTalkng / NMEA 2000 installation practices for binnacle mounted Raymarine electronics.

Q2. According to the E7 MDF manual it is not and therefore it does not make sense to connect them to a NMEA 2000 backbone since I mentioned I use the SeaTalkng backbone.
A2. This is an incorrect statement. See the response to Q1.

Q3. and: You cannot have 2 backbones connected together.
A3. This is an incorrect statement. See the response to Q1.

Q4. But I can connect NMEA 2000 devices to my SeaTalkng backbone on a spur.
A4. This is a correct statement

Q5. But it seems that the I50 and I60 are also Sea Talkng devices which can be directly connected using Seatalkng cables to connect to the SeaTalk backbone right?
A5. This is a correct statement.

Q6. If I want the transducers to connect to my existing SeaTalkng backbone, according to the manual from my E7, I need an ITC-5 connector. (see manual E7 page 41 for a typical SeaTalkng system). Is that the only way to connect them to my system?
A6. Compatible Smart NMEA 2000 transducers (ex. DT800, DST800, P79S, etc.), like other NMEA 2000 devices are designed to be interfaced to a spur socket within a backbone. Compatible analog transducers must be interfaced directly to the instrument (ex. i50, i60, i40, etc.) or to an iTC-5 Analog Instrument Converter. If Smart transducers or an iTC-5 is installed, then an i70S or i70(legacy) MFID must be installed. Please note that Raymarine offers the A06081 SeaTalkng Right Angle Spur
- STng Straight Plug (1m), which can effectively reduce the mounting depth normally associated with a straight SeaTalkng Spur Cable.

Q7. According to the manuals from Raymarine I can not have both NMEA 2000 and SeaTalkng at the same time, so than we stay with SeaTalkng right?
A7. That is an incorrect statement. Please see the response to Q1.

Q8. because the I60 and I50 plug directly into the SeaTalkng network?
A8. Please refer to my initial response regarding how these instruments may be interfaced to the system. Within a system featuring a NMEA 2000 network which has been constructed from SeaTalkng networking components, it would be recommended that these instruments each be interfaced to the backbone via an appropriate length of SeaTalkng Spur Cable.

Q9. The package (here in Sweden) is supplied with:
DT800-12 Plastic Transducer for Depth, speed, temperature
No need for an ST70 transducer pod or ITC-5.
direct connect to SeaTalkng backbone
A9. I assume that you are referring to the E70153 i50 / i60 Depth, Speed and Wind Systems Pack. If so, while the instruments will be interfaced to the system as specified within the response to Q8, the transducers will need to be directly connected to the transducer terminals of the i50 and i60 instruments ... unless an iTC-5 and an i70S MFID will additionally be installed.

Q10. So this data becomes available to all my devices on the SeaTalkng backbone?
A10. If interfaced to the current system in the manner which I have specified, then depth, speed, and wind data will indeed be available throughout the system.

Q11. But on the website from Raymarine I also find:
Compatible Models
ST70 & i70

Not the I50 and I60? I do not understand! Why is this sensor supplied in this package?
A11. Raymarine offers both analog and Smart versions of the DT800 and DST800. The analog versions of these transducers are included within the E70153 i50 / i60 Depth, Speed and Wind Systems Pack.

Q12.
The I50/I60 packages also includes:
P319 200KHZ Transducer (ANALOG)
This one fits on the back of the I50?
or use a pod or ITC-5 converter connect to the SeaTalkng backbone?
A12. Correct. However, if interfaced to an iTC-5, then an i70S MFID must be added to the system.

Q13. But when it is plugged in to the back of the I50, will this data be available for the other devices on the SeaTalkng network?
A13. Yes.

Q14. The supplied windsensor (E22078 - VINDGIVARE MED 30M KABEL) plugs in directly into the back of the I60?
A14. Correct.

Q15. When the windsensor is plugged in on the back of the I60, will this data be available on my SeaTalkng nertwork, for example my EV-100 autopilot?
A15. Yes.

Q16a. I70 system package wind, speed, depth: I70 connect only to the SeaTalkng backbone?
Q16a. Correct

Q16b. and for the sensors being able to communicate with the I70 we need to connect the sensors to the SeaTalkng backbone using ITC-5 converter, right?
A16b. Correct.