EGON FAMILY - Naviop Manual Rel... · The EGON responds with message ID 0x01, which indicates if...

EGON FAMILYPROGRAMMING NOTES

REV. January 2013

Naviop EGON Series - Programming Notes

NAVIOPTM - NAVIOP S.R.L.2

UK

WelcomeThank you for choosing NAVIOP EGON Series products. We invite you to read this manual in full before proceeding to use the product.

The purpose of this manualThis manual describes only the operating or installation instructions regarding the NAVIOP EGON product. We invite you to store this manual with care and keep it in a place that is known and easily accessible to all staff authorised to use the product.

Conventional symbolsThis manual contains conventional symbols in order to highlight information of particular importance.The meanings of such conventional symbols are described below:

Note

This symbol draws attention to important technical guidelines and recommendations.

Warranty exclusionThe manufacturer provides no guarantee on the outcome of the use of information contained in this documentation. The user is liable for any use made of this documentation and information contained herein. The producer has taken utmost care and attention in producing this documentation however, it may contain inaccuracies or typographical errors. The producer reserves the right to modify and/or improve its products at any time and without prior notice so as to continuously enhance product quality. Therefore, future editions of this manual may be subject to revisions or changes.

Brand namesNAVIOP EGON, EGON+ and EGON+ POWER are registered trademarks owned by NAVIOP S.R.L. Other brands and product names mentioned in this documentation are acknowledged as registered trademarks and are proprietary of their respective owners.

CopyrightIt is forbidden to reproduce this documentation, even partially, without explicit written authorisation being given by NAVIOP S.R.L.

Copyright © 2012 NAVIOP S.R.L.All rights reserved.

Attention!This symbol draws attention to important guidelines concerning the safety of the user and proper maintenance of the system.


NAVIOPTM - NAVIOP S.R.L. 3

UK

Table of Contents

�1. Programming the EGON (Using J1939 Messages to Set, Control, and Monitor the EGON) ................................................................6

1.1. CAN Software Settings ............................................................................................ 6

1.1.1. Proprietary A Messages ................................................................................. 6

1.1.2. CAN Source Address ..................................................................................... 6

1.1.2.1. Viewing the Source Address Base and Source Address Offset ........71.1.2.2. Changing the Source Address Base ..................................................71.1.2.3. Changing the Source Address Offset ...............................................7

1.1.3. Parameter Group Number (PGN) Base for Proprietary B Messages ........... 8

1.1.3.1. Viewing the PGN Base Value ........................................................... 81.1.3.2. Changing the PGN Base Value ........................................................ 8

1.1.4. Population Table ........................................................................................... 9

1.1.4.1. Viewing the Population Table ......................................................... 91.1.4.2. Changing the Population Table ....................................................... 9

1.1.5. Default Relay States .....................................................................................10

1.1.5.1. Viewing the Default Relay States ....................................................101.1.5.2. Changing the Default Relay States .................................................10

1.1.6. Start-up Delay Time .....................................................................................10

1.1.6.1. Viewing the Start-up Delay Time ...................................................101.1.6.2. Changing the Start-up Delay Time ................................................10

1.1.7. CAN Message Count Threshold ................................................................... 11

1.1.7.1. Viewing the CAN Message Count Threshold .................................. 111.1.7.2. Changing the CAN Message Count Threshold ............................... 11

1.1.8. Software Version Number ........................................................................... 11

1.1.8.1. Viewing the Software Version Number .......................................... 11

1.1.9. Controlling Relays........................................................................................12

1.1.9.1. Viewing Relay States .......................................................................121.1.9.2. Changing Relay States ....................................................................121.1.9.3. Changing Relay States Using Message ID 0x80 ............................121.1.9.4. Changing Relay States Using Message ID 0x88 ............................12

1.2. Monitoring Fuse, Relay, and System Fault States ................................................12

1.2.1. Proprietary B Messages ...............................................................................13

1.2.2. Fuse Status Messages ..................................................................................13

1.2.3. Relay Status Messages .................................................................................13



UK

1.2.4. System Error Status Messages ....................................................................14

1.3. CAN Message Definitions ......................................................................................14

1.3.1. Proprietary A Messages ...............................................................................14

1.3.1.1. Command Messages .......................................................................141.3.1.1.1. Message ID 0x12 (Command) ........................................................... 15

1.3.1.1.2. Message ID 0x80 (Command) ......................................................... 15



1.3.1.1.5. Message ID 0x92 (Command) .......................................................... 17

1.3.1.1.6. Message ID 0x94 (Command).......................................................... 17




1.3.1.1.10. Message ID 0x98 (Command) ....................................................... 20

1.3.1.1.11. Message ID 0x99 (Command) ....................................................... 20

1.3.1.2. Reply Messages ............................................................................. 201.3.1.2.1. Message ID 0x01 (Reply) .................................................................. 21

1.3.1.2.2. Message ID 0x13 (Reply) ................................................................. 21

1.3.1.2.3. Message ID 0x94 (Reply) .................................................................22



1.3.2. Proprietary B Messages .............................................................................. 24

1.3.2.1. Fuse Status .................................................................................... 241.3.2.2. Relay Status................................................................................... 261.3.2.3. System Error Status .......................................................................27



UK



UK

1. Programming the EGON (Using J1939 Messages to Set, Con-trol, and Monitor the EGON)

1.1. CAN Software SettingsA number of EGON software settings can be viewed and changed using J1939 Proprietary A messages(refer to section 1.1.1. Proprietary A Messages).The software settings that can be changed include the following:

• CAN Source Address• Parameter Group Number (PGN) for Proprietary B messages• Population Table• Default Relay states• Startup delay• CAN message count threshold and source address

Note

It is recommended that the EGON be set-up in a stand-alone environment when working withsoftware settings.

1.1.1. Proprietary A MessagesProprietary A messages (PGN EF00) are used for viewing and changing various EGON software settings.These messages allow you to define which module in a system is going to receive the message.

• Proprietary A messages sent to the EGON from external devices are called command messages.• Proprietary A messages sent from the EGON in response to command messages are called reply messages.

When the EGON receives a Proprietary A command message, it responds with a Proprietary A reply message. The reply is sent to the CAN node that sent the command message. The first data byte of a Proprietary A message is the message ID. For messages that have less than 8 bytes, the unused bytes can be filled in with 0x00 or 0xFF without interfering with EGON performance.The second data byte of a Proprietary A message may be used as a grid address if the message is grid specific. The parameter called grid address identifies a particular grid within the EGON (for EGONs with more than one grid). An EGON with one 8x8 grid would use 0x00 as its grid address.For a summary of all Proprietary A messages, refer to section 1.3.1. Proprietary A Messages.

1.1.2. CAN Source AddressIf multiple EGONs are being used in a vehicle, each must have a unique CAN source address so thatother modules can identify which EGON is sending and receiving messages.The source address on an EGON is determined with the following equation:CAN Source Address = Source Address Base + Source Address Offset

Note

The default value for the source address base is 0xB0 (176 DEC).

If your system uses 8 EGONs or less, you can assign CAN source addresses using one of thefollowing methods:• Method 1 - Give each EGON in your vehicle a unique source address base by changing the source address base value in software, and leave the source address offset (harness address pins) the same for each. Refer to section 1.1.2.2. Changing the Source Address Base for more information.



UK

• Method 2 - Give each EGON in your vehicle a unique source address offset by configuring the CAN harness address pins in the CAN connector, and leave the source address base the same for each. Refer to section 1.1.2.3. Changing the Source Address Offset for more information.

If your system uses more than 8 EGONs, you can combine different source address bases withdifferent source address offsets to create more than 8 unique CAN source addresses.

1.1.2.1. Viewing the Source Address Base and Source Address OffsetTo view an EGON’s source address base and source address offset

• Send message ID 0x97 to the EGON. See Message ID 0x97 (Command) for more details about the message.

The EGON responds with message ID 0x97, which displays the current values for the EGONs source address offset in byte 2.0 and source address base in byte 3.0. See Message ID 0x97 (Reply).

1.1.2.2. Changing the Source Address Base• To set the source address base, set the desired source address base value in byte 1.0 of message ID 0x90, and send the message to the EGON. See Message ID 0x90 (Command).

The EGON responds with message ID 0x01, which indicates if the change was a success or failure in byte 2.0. See Message ID 0x01 (Reply).

Changes made to the source address base will not take effect until the ignition power to the EGON is cycled.

Note

Byte 2.0 in message ID 0x90 is the PGN base value. If you wish to leave the PGNbase value as is, then use 0xFF.

1.1.2.3. Changing the Source Address OffsetThe EGON’s source address offset is assigned by configuring the CAN harness address pins (called ADDR_0, ADDR_1 and ADDR_2) in the EGON’s CAN connector. Refer to section 5.1.6.CAN Connection for more information about connecting and configuring the CAN harness address pins.

Up to 8 different source address offsets can be created using different combinations of CAN harness address pin states. There are two CAN harness address pin states: open andGND_REF.

• GND_REF indicates the CAN harness address pin is connected to the GND_REF pin on the CAN connector.• Open indicates the CAN harness address pin is open circuit (not connected).

Changes made to the source address offset when the EGON is powered will not take effect until the ignition power to the EGON is cycled.The following table shows all the possible address pin states and the resulting offsets they produce:



UK

Table 1. CAN Harness Address Pin States and OffsetsADDR_2 ADDR_1 ADDR_0 OffsetOpen Open Open 0Open Open GND_REF 1Open GND_REF Open 2Open GND_REF GND_REF 3GND_REF Open Open 4GND_REF Open GND_REF 5GND_REF GND_REF Open 6GND_REF GND_REF GND_REF 7

1.1.3. Parameter Group Number (PGN) Base for Proprietary B MessagesThe PGN Base identifies which type of Proprietary B message is being sent by the EGON. The EGON uses Proprietary B messages to send three types of information: fuse status, relay status, and error status.It may be necessary to change the PGN Base for Proprietary B messages to avoid conflicts with

Proprietary B messages from other modules. The Proprietary B PGN has an upper byte and a lower byte.• The upper byte of the PGN is always 0xFF• The lower byte of the PGN is determined by adding the PGN base value and PGN offset value.

The PGN base value defaults to 0xA0 (160 DEC). To change the PGN you must change the PGN base value. The PGN base can be set to any value between 0x00 and 0xF1.The PGN offset values are not configurable, and are set as follows:

• Fuse status offset – 0x00• Relay status offset – 0x01• Error status offset – 0x02

For example, if you are using the default PGN base value of 0xA0, the PGN values would be 0xFFA0 (fuse status), 0xFFA1 (relay status), and 0xFFA2 (error status).

1.1.3.1. Viewing the PGN Base ValueTo view an EGON’s PGN base value

• Send message ID 0x97 to the EGON. See Message ID 0x97 (Command) for more details about the message.•

The EGON responds with message ID 0x97, which displays the current value for the PGN base in byte 1.0. See Message ID 0x97 (Reply).

1.1.3.2. Changing the PGN Base ValueTo change the status PGN base value

• Set the desired PGN base value in byte 2.0 of message ID 0x90, and send the message to the EGON. See Message ID 0x90 (Command) for more details about the message.

The EGON responds with message ID 0x01, which indicates if the change was a success or failure in byte 2.0. See Message ID 0x01 (Reply).

Note

TheByte 1.0 in message ID 0x90 is the source address base value. If you wish to leave the source address base value as is, then use 0xFF.



UK

1.1.4. Population TableThe hardware configuration of your EGON defines which components belong on the EGON’s electrical grid, and where each component must be connected. For the EGON to work properly, all components configured to be connected to the electrical grid must actually be connected.

Note

The term “connected” in this section refers to physically plugging a component into the topof the EGON’s electrical grid.

A population table (stored in Flash memory) indicates whether or not the components are actually connected to the electrical grid. If a component is not connected (but should be according to the population table), the EGON will generate an error in the corresponding status message, indicating the component is missing (refer to section 1.2. Monitoring Fuse, Relay, and System Fault Status for more details about status messages).

To avoid errors from a missing component, you must send the EGON a message telling it to stop controlling or monitoring the component, which is done through the population table using message ID 0x94.

1.1.4.1. Viewing the Population TableTo view the population table

• Send message ID 0x92 to the EGON. See Message ID 0x92 (Command) for more details about the message. The EGON responds with message ID 0x94, which diplays the current population values for each component:

• 0 indicates the component is not controlled and monitored.• 1 indicates the component is controlled and monitored.

See Message ID 0x94 (Reply).

Note

If the grid address you are trying to view is invalid, the EGON responds with message ID 0x01, and displays a value of 0 (failure) in byte 2.0.

1.1.4.2. Changing the Population TableTo change the population table setting for a component

• Set the desired population value(s) in the appropriate byte(s) of message ID 0x94, and send the message to the EGON. See Message ID 0x94 (Command) for more details about the message.• The following population values can be used:

• 0 indicates the component is not populated and does not need to be controlled and monitored• 1 indicates the component is populated and must be controlled and monitored.

The EGON responds with message ID 0x01, which indicates if the operation was a success or failure in byte 2.0. See Message ID 0x01 (Reply).

Note

You cannot ‘populate’ a device that was not in the original factory configuration. You may only alter the population settings of factory-installed devices.



UK

1.1.5. Default Relay StatesThe default relay states are the “safe” relay states the EGON assumes when it powers-up, and when the CAN message count threshold is breached. When the EGON is shipped, all of the default relay states are set to “off” (0). The following sections show how to view and change the default relay states.

1.1.5.1. Viewing the Default Relay StatesTo view the default relay states of the EGON

• Send the message ID 0x96 to the EGON. See Message ID 0x96 (Command) for more details about the message.If the grid address is valid, the EGON responds with message ID 0x96, which shows the default relay states in byte 4.0 to byte 5.4. See Message ID 0x96 (Reply).If the grid address is invalid, the EGON responds with message ID 0x01, and displays a value of 0 (failure) in byte 2.0. See Message ID 0x01 (Reply).

1.1.5.2. Changing the Default Relay StatesTo change the default relay states

• Set the desired default relay states in the appropriate bytes of message ID 0x95, and send the message to the EGON. See Message ID 0x95 (Command) for more details about the message.• The following default relay state values can be used:

• 0 sets the default state to “off”• 1 sets the default state to “on”The EGON responds with the message ID 0x01, which indicates if the operation was a success or failure in byte 2.0. See Message ID 0x01 (Reply).

1.1.6. Start-up Delay TimeThe start-up delay is the number of milliseconds the EGON waits after start-up before receiving commands, or sending messages.The start-up delay range is 0 milliseconds to 65,534 milliseconds (65.5 seconds), which is 0x0000 to 0xFFFE.

Note

The default start-up delay time is 1,000 ms (1 second).

1.1.6.1. Viewing the Start-up Delay TimeTo view the current start-up delay time

• Send message ID 0x96 to the EGON, see Message ID 0x96 (Command) for more details about the message. If the grid address is valid, the EGON responds with message ID 0x96, which shows the values for the start up delay in bytes 6.0 and 7.0. See Message ID 0x96 (Reply). If the grid address is invalid, the EGON responds with message ID 0x01, and displays a value of 0 (failure) in byte 2.0. See Message ID 0x01 (Reply).

1.1.6.2. Changing the Start-up Delay TimeTo set the delay time

• Set the desired start-up delay time values in byte 1.0 and 2.0 of message ID 0x99, and send the message to the EGON. See Message ID 0x99 (Command) for more details about the message.The EGON responds with message ID 0x01, which indicates success or failure in byte 2.0.See Message ID 0x01 (Reply).



UK

1.1.7. CAN Message Count ThresholdThe CAN message count threshold refers to the minimum number of messages that must be received by the EGON every two seconds. If the EGON does not receive enough messages over two seconds, it switches all relays to their default state. The relays will remain in the default state until the EGON receives a message ID 0x80 or message ID 0x88 with different relay state information, or until ignition power is cycled (for more details on default relay states, see 1.4.2. Relay Status).

There are two ways you can use the CAN message count threshold:• The same CAN message count threshold can be applied to all modules communicating with the EGON by not setting a specific CAN timeout source address.• A specific CAN message count threshold can be applied to one module communicating with the EGON by using a specific CAN timeout source address. If this is used, the EGON will only count messages from the indicated module.

1.1.7.1. Viewing the CAN Message Count ThresholdTo view the CAN message count threshold

• Send message ID 0x97 to the EGON. See Message ID 0x97 (Command) for more details about the message.

The EGON responds with message ID 0x97, which displays the values for the CAN message count threshold in byte 4.0 (LSB) and byte 5.0 (MSB), and the CAN timeout source address in byte 6.0. See Message ID 0x97 (Reply).

1.1.7.2. Changing the CAN Message Count ThresholdTo change the CAN message count threshold

• Set the desired CAN message count threshold in byte 1.0 (LSB) and byte 2.0 (MSB), and CAN timeout source address in byte 3.0 of message ID 0x98, and send the message to the EGON, see Message ID 0x98 (Command) for more details about the message.

The following are things to consider when setting the CAN message count threshold:• Setting the CAN message count threshold to a value of “0” will disable the CAN timeout feature. Any value other than “0” will be the actual CAN message count threshold.• Setting the CAN timeout source address to 0xFF will apply the same CAN message count threshold to all modules communicating with the EGON. If you only want the EGON to count messages received from one module, you must provide the CAN timeout source address for that specific module.

The EGON responds with message ID 0x01, which indicates success or failure in byte 2.0.See Message ID 0x01 (Reply).

1.1.8. Software Version NumberIt may be necessary to indicate the software version number for your EGON when corresponding with NAVIOP S.R.L..

1.1.8.1. Viewing the Software Version NumberTo determine the EGON’s software version number

• Send the message message ID 0x12 to the EGON. See Message ID 0x12 (Command) for more details about the message.• The EGON responds with the message message ID 0x13. See Message ID 0x13 (Reply). The values that are returned depend on the operating mode of the EGON. The operating mode is indicated in byte 1.0 of message ID 0x13.



UK

• If the operating mode is 0 (Run), the software version number will be shown in byte 2.0 and 3.0, and the bootloader version number will be shown in byte 4.0 and 5.0.• Operating mode is 1 is reserved.• If the operating mode is 2 (Test Mode), the software version number will be the same as that in mode 0 (Run).

1.1.9. Controlling RelaysThe EGON’s relays are controlled by CAN messages received from external devices that tell the EGON to turn the relays “on” or “off”. The following sections describe how to view and change the state of a relay.

1.1.9.1. Viewing Relay StatesTo determine the state of the EGON’s relays

• Send message ID 0x96 to the EGON. See Message ID 0x96 (Command) for more detail about the message.If the grid address is valid, the EGON responds with message ID 0x96, which shows the state of the EGONs relays (and high-side drive, if installed) in bytes 2.0 to 3.4. See Message ID 0x96 (Reply). If the grid address is invalid, the EGON responds with message ID 0x01, and displays a value of 0 (failure) in byte 2.0. See Message ID 0x01 (Reply).

1.1.9.2. Changing Relay StatesThere are two messages that can be used when changing the state of a relay, as follows:• Message ID 0x80 - does not provide a diagnostic reply message from the EGON indicating if the message was a success or failure.• Message ID 0x88 – does provide a diagnostic reply message from the EGON indicating if the message was a success or failure.

1.1.9.3. Changing Relay States Using Message ID 0x80To change the state of a relay and not receive a diagnostic reply, set the desired relay states in the appropriate bytes of message ID 0x80, and send the message to the EGON, see Message ID 0x80 (Command) for more details about the message. Each relay state value will have one of the bit settings described in Table 3 listed for message ID 0x80. See Message ID 0x80 (Command) for more details about the message.If the message fails because it is too short, contains an invalid grid address, or is trying to control a relay that is not in a controlled and monitored component location, message ID 0x80 will be ignored.

1.1.9.4. Changing Relay States Using Message ID 0x88To change the state of a relay and receive a diagnostic reply set the desired relay states in the appropriate bytes of message ID 0x88, and send the message to the EGON, see Message ID 0x88 (Command) for more details about the messageEach relay state value will have one of the bit settings described in Table 3 listed for message ID 0x80, see Message ID 0x80 (Command) for more details about the message.The EGON responds with message ID 0x01, which indicates success or failure in byte 2.0, see Message ID 0x01 (Reply).If the message fails because it is short, contains an invalid grid address, or is trying to control a relay that is not in a controlled and monitored location on the grid, message ID 0x01 will have additional bytes explaining the failure, as detailed in the description for Message ID 0x01 (Reply).

1.2. Monitoring Fuse, Relay, and System Fault StatesFuses, relays and errors are monitored by the EGON, and the state of each is communicated periodically



UK

to other modules on the CAN bus using Proprietary B status messages.

1.2.1. Proprietary B MessagesAll Proprietary B messages start at PGN FF00. These messages do not allow you to define which module receives the message; they are broadcast to all modules on the CAN bus at the same time. The EGON uses Proprietary B messages to communicate three types of information: fuse status, relay status, and error status. These messages are sent by the EGON once every 1000 ms, or every time the status of a relay or fuse is changed (up to once every 25 ms).

Note

Error messages are only sent when the EGON experiences an error, or when there is aspecific J1939 request from another module to obtain error information (they are not sent once every 1000 ms). Once an error is detected, the error message is sent once every 1000 ms until it is corrected.

Each type of Proprietary B message is identified by a Parameter Group Number (PGN) that may need to be changed to avoid message conflicts with other modules. Refer to section 1.3.2. Proprietary BMessages for more information on changing the PGN Base for Proprietary B messages.

1.2.2. Fuse Status MessagesThe EGON automatically sends Proprietary B message 0xFF00 + PGN base (defaults to 0xFFAO) indicating the fault state of its fuses once every 1000 ms, or every time the state of a fuse is changed (up to once every 25 ms). Refer to section 1.3.2.1. Fuse Status for more details about this message.

• The state of each fuse on the EGON is represented by a two-bit value. See Table 20.

Note

You have the option of disabling the “Not Powered” fuse fault. Doing so will prevent fuses downstream from a relay from generating error messages when the relay is “off” (because they are not receiving power). Disabling the “Not Powered” fuse fault must be done during production at the factory, and cannot be implemented once the product is shipped.

1.2.3. Relay Status MessagesThe EGON automatically sends Proprietary B message 0xFF01 + PGN base (defaults to 0xFFA1)indicating the fault state of its relays once every 1000 ms, or every time the state of a relay is changed(no more than once every 25 ms). Refer to section 1.3.2.2. Relay Status for more information about thismessage.

• The state of each relay on the EGON is represented by a four-bit value. See Table 23.• Some of the faults shown in the table can be disabled at the factory during production. These cannot be disabled after your EGON is shipped.

Note

If multiple faults occur on the same relay at the same time, only the first fault that isdetected will be reported by the EGON.



UK

Note

If a shorted relay coil is detected when a relay is switched “on”, the EGON turns that relay coil driver “off” to protect the circuit and reports the “coil shorted” error. The relay will remain “off” until the EGON receives a command to turn it “off” and then back “on”.

1.2.4. System Error Status MessagesSystem error messages are Proprietary B messages; however, they are not sent by the EGON on a regular basis like other Proprietary B messages. Instead, they are sent every time a system error occurs, or when there is a specific J1939 Request message from an external module to obtain System Error Status information.

When a system error occurs, the message 0xFF02 + PGN base (defaults to 0xFFA2) is transmitted once every 1000 ms until either the power is cycled, or CAN communication is restored, see 1.3.2.3. System Error Status for more details about the message.

Note

The EGON will send an error message at least once after CAN communication is restored.

1.3. CAN Message DefinitionsThe EGON uses two kinds of messages when communicating with other modules:

• Proprietary A• Proprietary B

The sections that follow show the settings and values for the various Proprietary A and Proprietary B messages.

• Settings enclosed by round brackets (xxx) are actual values.• Settings enclosed by square brackets [xxx] are default values.

1.3.1. Proprietary A MessagesWhen the EGON receives a Proprietary A message from an external device, it sends a reply message back to that device using a Proprietary A message.

• Messages sent from the external device to the EGON are called command messages.• Messages sent from the EGON back to the external device are called reply messages.

1.3.1.1. Command MessagesCommand messages are sent to the EGON by external modules. The EGON replies to every command message except message ID 0x80. All command messages have the following message format:

pgn61184 – Proprietary ATransmission Repetition Rate: N/A, received message onlyData Length: As defined below, no more than 8 bytesData Page: 0PDU Format: 239PDU Specific: Destination Address (EGON CAN Source Address)Default Priority: 6Parameter Group Number: 61184 ( 00EF00 16 )

The data bytes of each command message are formatted as described in the following sections.



UK

1.3.1.1.1. Message ID 0x12 (Command)Message ID 0x12 is used for viewing the EGON’s software version number. The EGON responds to this message with reply message ID 0x13.The following table shows the format of the data bytes of message ID 0x12:

Table 2. Message ID 0x12 (Command)Byte Description Value

0 Message ID Message ID (0x12)

1-7 Reserved

1.3.1.1.2. Message ID 0x80 (Command)Message ID 0x80 is used to change the state of relays or the high-side drive (if installed).The EGON does not respond to this message. Refer to section 1.3.2.2. Relay Status for the different relay state values.The following table shows the format of the data bytes of message ID 0x80:

Table 3. Message ID 0x80 (Command)Byte Size (bits) Meaning

0.0 8 Message ID (0x80)

1.0 8 Grid address (0x00)

2.0 2 Relay 1 state

2.2 2 Relay 2 state

2.4 2 Relay 3 state

2.6 2 Relay 4 state

3.0 2 Relay 5 state

3.2 2 Relay 6 state

3.4 2 Relay 7 state

3.6 2 Relay 8 state

4.0 2 Relay 9 state

4.2 2 Relay 10 state



5.0 2 High-side output state

5.2 6 Reserved

Total: 6 bytes

Each relay state value will have one of the following bit settings:

Table 4. Relay State ValuesBit Value Hex Value Action

00 0 Turn relay off

01 1 Turn relay on

10 2 Do not change relay state



UK

Bit Value Hex Value Action

11 3 Do not change relay stateThe “Do not change” values shown above are used when multiple modules are controlling the same EGON to enable you to leave the state of some relays unchanged while changing the state of others with the same message.

1.3.1.1.3. Message ID 0x88 (Command)Message ID 0x88 is used to change the active state of relays or the high-side drive (if installed). The EGON responds to this message with reply message ID 0x01. Refer to section 1.3.2.2. Relay Status for the different relay state values.

The following table shows the format of the data bytes of message ID 0x88:




2.0 2 Relay 1 state

2.2 2 Relay 2 state

2.4 2 Relay 3 state

2.6 2 Relay 4 state

3.0 2 Relay 5 state

3.2 2 Relay 6 state

3.4 2 Relay 7 state

3.6 2 Relay 8 state

4.0 2 Relay 9 state





5.2 6 Reserved

Total: 6 bytes

Each relay state value will have one of the bit settings described in Table 4. Relay State Values listed for message ID 0x80.

1.3.1.1.4. Message ID 0x90 (Command)Message ID 0x90 is used to set:

• the CAN source address base value• the PGN base value

The EGON responds to this message with reply message ID 0x01. The new setting for the CAN source address takes effect on the next power cycle. The new setting for the PGN base value takes



UK

effect immediately.The following table shows the format of the data bytes of message ID 0x90:

Table 6. Message ID 0x90 (Command)Byte Size (Bits) Value


1.0 8 Source address base. Use 0xFFto indicate no change.

2.0 8 Status PGN base. Use 0xFF to indicate no change

Total: 3 bytes

1.3.1.1.5. Message ID 0x92 (Command)Message ID 0x92 is used to view the population table. The EGON responds to this message with reply message ID 0x94 (or reply message ID 0x01 if the grid address is invalid).



0 1 Message ID (0x92)

1 1 Grid address (0x00)

Total: 2 bytes

1.3.1.1.6. Message ID 0x94 (Command)Message ID 0x94 is used to change the population table settings.The EGON responds to this message with reply message ID 0x01.The following table shows the format of the data bytes of message ID 0x94:

Note

A value of 1 = populated and 0 = unpopulated.




2.0 1 Fuse 1 populated











UK

Byte Size (bits) Meaning
















5.0 8 Reserved

6.0 1 Relay 1 populated












1.4 1 High-side output

1.5 3 Reserved

Total: 8 bytes

1.3.1.1.7. Message ID 0x95 (Command)Message ID 0x95 is used to change the default relay states. The EGON responds to this message with reply message ID 0x01.


Note

A default state value of 1 = on and 0 = off.



UK




2.0 1 Relay 1 default state









3.1 1 Relay 10 s default tate




3.5 3 Reserved

Total: 4 bytes

1.3.1.1.8. Message ID 0x96 (Command)Message ID 0x96 is used to view:

• The start-up delay time• The default relay states• The current relay states

The EGON responds to this message with reply message ID 0x96 (or reply message ID 0x01 if the grid address is invalid).The following table shows the format of the data bytes of message ID 0x96 (command):

Table 10. Message ID 0x96 (Command)Byte Size (Bits) Meaning


1 1 Grid address (0x00)

Total: 2 bytes

1.3.1.1.9. Message ID 0x97 (Command)Message ID 0x97 is used to view:

• The mapping board configuration• The CAN source address offset• The CAN source address base• The PGN base value• The CAN message count threshold• The CAN timeout source address



UK

The EGON responds to this message with reply message ID 0x91.The following table shows the format of the data bytes of message ID 0x97 (command):



Total: 1 byte

1.3.1.1.10. Message ID 0x98 (Command)Message ID 0x98 is used to change:

• The CAN message count threshold (set both bytes to zero to disable)• The CAN timeout source address

The EGON responds to this message with reply message ID 0x01.The following table shows the format of the data bytes of message ID 0x98 (command):



1.0 8 CAN message count threshold (LSB)

2.0 8 CAN message count threshold (MSB)

3.0 8 CAN timeout source address [0xFF = count all messages from all addresses]

Total: 4 bytes Do not change relay state

1.3.1.1.11. Message ID 0x99 (Command)Message ID 0x99 is used for setting the start-up delay time. The EGON responds to this message with reply message ID 0x01.The following shows the format of the data bytes of message ID 0x99:



1.0 8 Start-up delay (LSB)

2.0 8 Start-up delay (MSB)

Total: 3 bytes

1.3.1.2. Reply MessagesReply messages are sent by the EGON after it receives command messages from external modules.All reply messages have the following message format:

pgn61184 – Proprietary ATransmission Repetition Rate: As required, in response to command messagesData Length: 8 bytesData Page: 0PDU Format: 239PDU Specific: Destination Address (address of node that sent command)Default Priority: 6Parameter Group Number: 61184 ( 00EF00 16 )



UK

The data bytes of the reply messages are formatted as described in the following sections.

1.3.1.2.1. Message ID 0x01 (Reply)Message ID 0x01 is a diagnostic message that indicates success or failure.The following table shows the format of the data bytes of message ID 0x01:

Table 14. Message ID 0x01 (Reply)Byte Size (Bits) Value


1.0 8 Message ID being responded to

2.0 8 0 = failure1 = success

3.0-1.0 8 Reserved

If the diagnostic reply message is in response to a Message ID 0x88, and that message failed because it was short, contained an invalid grid address, or was trying to control a relay that is not in a controlled and monitored location on the grid, message ID 0x01 will have additional bytes explaining the failure, as detailed in the following table:

Table 15. Relay State Change Failure MessageByte Size (bits) Meaning

3.0 8 Default: Grid Address requestedOr0xE0 = Message is too short0xE1 = Invalid offset

4.0 1 Relay 1 unable to change state as requested












5.4 1 High-Side Output unable to change state as requested

5.5 1 Reserved

6.0-1.0 8 Reserved

Total: 8 bytes

1.3.1.2.2. Message ID 0x13 (Reply)Message ID 0x13 is sent by the EGON after receiving the command message ID 0x12.The following table shows the format of the data bytes of message ID 0x13:



UK

Table 16. Message ID 0x13 (Reply)Byte Description Value

0 Response Message ID (0x13)

1 Operating Mode 0 = Run (application)1 = Reserved2 = Test Mode (bootloader)

2-3 SoftwareVersion SoftwareVersion

4-5 Alternate Version Bootloader version.

6-7 Reserved

1.3.1.2.3. Message ID 0x94 (Reply)Message ID 0x94 is sent by the EGON after receiving command message ID 0x92.The following table shows the format of the data bytes of message ID 0x94:

Table 17. Message ID 0x94 (Reply)Byte Size (bits) Meaning



























UK




5.0 8 Reserved













1.4 1 High-side output

1.5 3 Reserved

Total: 8 bytes














3.1 1 Relay 10 s default tate




3.5 3 Reserved



UK














5.4 1 High-side output default state

5.5 3 Reserved

6.0 8 Start-up delay (LSB)

1.0 8 Start-up delay (MSB)

Total: 8 bytes




1.0 8 Deacted circuit board configuration (Read from mapping board)

2.0 8 CAN source address offset (cable select)

3.0 8 CAN source address base

4.0 8 CAN message count threshold (LSB)

5.0 8 CAN message count threshold (MSB)

6.0 8 CAN timeout source address

1.0 8 Status PGN base

Total: 8 bytes

1.3.2. Proprietary B MessagesProprietary B messages are sent by the EGON (to every module in the system) once every 1000 ms, orevery time the state of a relay, fuse, or error is changed (up to once every 25 ms).1.3.2.1. Fuse Status

The status of the EGON’s fuses is transmitted in message 0xFF00 + PGN base (defaults to 0xFFAO).

pgn65283 – Proprietary B – Fuse Status –Transmission Repetition Rate: 1000ms



UK

Data Length: 8 bytesData Page: 0PDU Format: 255PDU Specific: 0Default Priority: 6Parameter Group Number: 65280 ( 00FF00 16 ) (depends on PGN Base setting)

The following table shows the format of the data bytes of Fuse Status message:

Table 20. Fuse Status MessageByte Size (bits) Meaning


1.0 2 Fuse 1 status

1.2 2 Fuse 2 status

1.4 2 Fuse 3 status

1.6 2 Fuse 4 status

2.0 2 Fuse 5 status

2.2 2 Fuse 6 status

2.4 2 Fuse 7 status

2.6 2 Fuse 8 status

3.0 2 Fuse 9 status

3.2 2 Fuse 10 status















1.0 8 Reserved

Total: 8 bytes

Each fuse status value will have one of the following bit settings:

Table 21. Fuse Status ValuesBit Value Hex Value Meaning Option to Disable?

00 0 No Fault No

01 1 Blown No



UK

Bit Value Hex Value Meaning Option to Disable?

10 2 Not Powered Yes

11 3 Not Used No

1.3.2.2. Relay StatusThe status of the EGON’s relays is transmitted in message 0xFF01 + PGN base (defaults to 0xFFA1).

pgn65283 – Proprietary B – Relay Status –Transmission Repetition Rate: 1000msData Length: 8 bytesData Page: 0PDU Format: 255PDU Specific: 1Default Priority: 6Parameter Group Number: 65281 ( 00FF01 16 ) (depends on PGN Base setting)

The following table shows the format of the data bytes of Relay Status message:

Table 22. Relay Status MessageByte Size (bits) Meaning


1.0 4 Relay 1 status












1.0 4 High-side output status

1.4 4 Reserved

Total: 4 bytes

Each relay status value will have one of the following bit settings:

Table 23. Relay Status ValuesBit Value Hex

ValueMeaning Option to Disable

0000 0 Okay No

0001 1 Relay coil open or relay not present No

0010 2 Coil shorted or failed relay driver No



UK

Bit Value Hex Value

Meaning Option to Disable

0011 3 Normally Open (N.O) contact is open (when a N.O contact is not connected to the Common (C) terminal, but should be).

No

0100 4 Normally Closed (N.C) contact is open (when a N.C contact is not connected to the Common (C) terminal, but should be).

No

0101 5 The coil is not receiving power Yes

0110 6 Normally Open (N.O) contact is shorted (when a N.O contact is connected to the Common (C) terminal, but should not be).

Yes

0111 7 Normally Closed (N.C) contact is shorted (when a N.C contact is connected to the Common (C) terminal, but should not be)

Yes

1000 8 Reserved No

1001 9 Reserved No

1010 A Reserved No

1011 B High-side driver is reporting a fault condition No

1100 C High-side driver has an open-load No

1101 D High-side driver is over voltage No

1110 E Reserved No

1111 F Relay location not used No

1.3.2.3. System Error StatusSystem error status messages are sent in message 0xFF02 + PGN base (defaults to 0xFFA2).

pgn65283 – Proprietary B – System Error Status –Transmission Repetition Rate: 1000msData Length: 8 bytesData Page: 0PDU Format: 255PDU Specific: 2Default Priority: 6Parameter Group Number: 65282 ( 00FF02 16 ) (depends on PGN Base setting)

The following table shows the format of the data bytes of System Error Status message:

Table 24. Error MessagesByte S i z e

(bits)Meaning Corrective Action


1.0 1 EGON contains invalidconfiguration information.

EGON must be re-configured by NAVIOP S.R.L..

1.1 1 Internal electrical grid identifier values have changed since power-up.Note: Initial error may have no effect, but functionality may change on next power-up.

EGON must be serviced by NAVIOP S.R.L..



UK

Byte S i z e (bits)

Meaning Corrective Action

1.2 1 CAN Harness address input pinvalues have changed duringoperation.

Check harness connections. Ifno result, contact NAVIOP S.R.L..

1.3 1 CAN Rx communication error. This happens when the EGON receives an insufficient number of messages.

Adjust CAN message countthreshold.Check module harnesses in thesystem that are sending theEGON messages.

1.4 1 CAN Tx communication error. This happens when a message sent by the EGON is not received by an external module.

Cycle vehicle power.Check terminators in the harness.If no result, contact NAVIOP S.R.L.

1.5 1 Unexpected reset, or watchdogtimer reset.

Check power and groundconnections on the CANconnector. Refer to Section 11.Troubleshootingfor more details.

1.6 1 Over voltage Batt+ is greater than about 43v.Reduce input voltage.

1.7 1 SPI error Internal error.

2.0 1 Short message received Erase Region command incomplete. Check host application.

2.1 1 Bad FLASH address Invalid address specified for Erase Region or Write Memory command.

2.2 1 Invalid length Invalid data length specified for Write Memory command.

2.3 1 Checksum failure Invalid checksum for received data for Write Memory command.

2.4 1 FLASH miscompare FLASH data doesn’t match received data after Write Memory command.

2.5 1 Reserved

2.6 1 Reserved

2.7 1 Reserved

3.0-1.0 8 Reserved



UK

EGON FAMILY - Naviop Manual Rel... · The EGON responds with message ID 0x01, which indicates if...

Documents

Transcript of EGON FAMILY - Naviop Manual Rel... · The EGON responds with message ID 0x01, which indicates if...