YACHT DEVICES NMEA2000 Motor Interface / Micro-C / YDEG-04N

You need two gateways for twin engines, one per engine. YDEG-04 can be connected to your engine in two ways: 1) To 6-pin Diagnostic connector "C" using "Yanmar 4JH adaptor cable"; 2) Connection in series with B25/C35/YD25 display using "B25/C35 adapter cable". The second method is preferrable as no need to extend NMEA2000 backbone to the engine room. Please note that YDEG-04 is available in two versions: DeviceNet NMEA2000 Micro Male (YDEG-04N), and Raymarine Seatalk NG (YDEG-04R). Please choose correct version for your network. After the connection, please check LED indication. You should get green-green when the engine and NMEA2000 are ON. If so, both physical connections are OK. Then you will need to reconfigure YDEG units to allow MFD to distinguish engines.

Yes. YDEG-04 should be connected to the Multilink port on MDI box or (preferred) in series with the EVC tachometer. Note that all NMEA 2000 devices should be connected to properly poweren and terminated NMEA 2000 backbone, not to each other directly (even 2 devices). You need to deploy at least a Starter kit. You can get the following data from D1/D2 engines to the NMEA 2000 network: - RPM - Engine (Coolant) temperature - Alternator potential - Engine hours - Engine warnings - Fuel level (optional, only if the fluid level sensor is connected to the MDI)

Dear Zoltan! Do you mean D3-110I-C engine? If so, you should have EVC-C(MC) system. #YDEG-04# is compatible with your engine. YDEG should be connected to X5: Multilink port of the EVC HCU unit, in series with the existing cable. Also check that your chartplotter can display engine data.

Dear Zoltan! I apologize for my mistake. On D3 engines with EVC-MC, YDEG-04 must be connected to the 12-pin "Engine" port on the HIU (Helm Interface Unit) using the "EVC-A MC 12-pin C5:ENGINE cable", in series with the existing cable. I confirm that both MFD can display engine data

Yes, correct, you need 90288 and 90297.

Please state exact engine model to check compatibility. SPX autopilots already have a SeatalkNG interface. However, newer Axiom plotters do not natively support SPX autopilots - this can be solved with the YDNB-07 network bridge.

Dear Padure! Please check YDEG-04 LED indication – it should blink green-green. If first blink is red, check engine connection (in your case YDEG should be connected to any free port of the Multilink hub), is second blink is red – check NMEA2000 connection. Check if you can observe YDEG-04 in NMEA2000 device list. When both connections are OK, YDEG-04 should work plug-and-play with your engine, so you should be able to observe engine data on your MFD. If you have GREEN-GREEN indication, but no engine data on MFD, check that your MFD supports engine data (NMEA2000 PGNs 127488 and 127489). Add engine gauges to your MFD dashboard (if you don`t have it yet), and choose data sources manually. In rare cases, the motor may have a non-standard address on the bus, in which case it must be specified in the gateway configuration file. Check that you have actual firmware version on your YDEG-04, and update it if needed.

If you have RED-GREEN indication (when both engine and NMEA2000 are on), you have issue with engine connection, Please try to connect YDEG into another port of Multilink hub. While you have at least one red blink, configuration file editing is useless.

Dear Padure! Are you sure that you have EVC-D system? Please tell exact engine model/year/specification number. If you have EVC-B system, you can have other issue. CAN buses on EVC-B can be swapped, so you will need to rearrange pins on YDEG-04 connectors.

Dear Padure! Please contact me via email ([email protected]) as it is not possible to attach image here.

Dear Tolga! Our engine gateway YDEG-04 supports only D2-75B/C/F versions with MDI box. If you have it, YDEG-04 can be connected to the "Multilink" connector on the engine's MDI (Mechanical Diesel Interface) box, or in series with the Volvo tachometer.