8 Networks Message Acknowledgement Upon receipt of a message, devices on the network will “Acknowledge” or “Not Acknowledge” that message. If a message is “Not Acknowledged” the sending device will resend the message. The device will respond until 256 failed tries have occurred, after which it will take itself off the bus defined as the “Bus-Off” condition. By taking itself off the network the device avoids excessive network traffic of failed message retries.
In most cases the unit will need to be reset to reestablish its ability to transmit onto the bus (as “Acknowledged” messages are received, the “failed try” count is reduced.) Arbitration When data is to be transmitted on the bus, the device must monitor the bus and any contentions (multiple devices putting data on the bus) will be arbitrated. The message with the higher priority will win and the other device will back off and try again later. The establishment of the message components by the NMEA 2000 ® Committee and its Manufacturer Committee insures that mission critical messages (such as engine control) will have priority over less critical messages such as tank level. 3.
Network Layer A device is identified on the network by an address it claims. This claimed address is contained in the device’s transmitted messages and allow the receiving devices to identify the sender. When first connected to the network (or powered on) a device will first send an address claim message with it’s “Name Information” (every product has a unique name) and the address it wants to claim. Upon receiving the request, a device with the same address will check the name against its name and the name of the requestor. If the device is of a lower priority then the requesting device the claim will be denied the address.
If the requesting device’s name is of higher priority then it will be “bumped” and will need to make a claim of its own for a new address. This method of addressing units on the bus is the basis for the “Plug-N-Play” with no complicated manual settings to be made. See the operation section below for more information on address claims. 4. Application Layer The application layer contains the actual data in the message and a specific message is referred to as a PGN (Parameter Group Number). The PGN is much like an address on an envelope. It defines each element of the message it is carrying. As an example, the fuel level message for the starboard fuel tank would be structured like this.
• Fluid Level The PGN can be used for any type of tank. • Fuel The message is about a fuel tank not a water or waste tank. • Tank Identifier General identifying number called Instance in the protocol. In this case Instance 1 defined as starboard tank (see instance information on page 8:7). • Level The actual level in the tank. Thus a PGN defines all the information for a certain message. In this case the level of the starboard fuel tank is sent out onto the CAN Bus. Any device attached to the CAN Bus that has been designed to read that PGN can see and use the starboard fuel tank level data.
Understanding – To complete any communication on the CAN Bus a device must send a specific PGN and at least one other device on the bus must be able to receive that PGN. If trying to decide if two products will work with each other on a CAN Bus look at the PGN numbers they support. They must both support the same PGN number to send and receive a particular parameter like oil pressure. © 2011 Yanmar Marine International • Rev. 2.0 Yanmar Electronic Control Systems Technical Manual 8:5