1. In-Vehicle Networking for Heavy Duty Systems Review of CAN / SAE J1939/ ISO 11783 Network Management ISO 11783 Part 5 J1939-81 Network Management ISO 11783 Part 5 J1939-81

2. How do we create new messages? – Is there a block of identifiers/addresses/messages set aside for experimental use? If so, how do we get information about them? Use proprietary if you must be compliant Use proprietary if you must be compliant OEM reserved address available OEM reserved address available – If we make a controller which will remain on the vehicle, how do we get it added to the standard? How long does it take to get something added? Controller needs a NAME defined, can use self- configuring addressing Controller needs a NAME defined, can use self- configuring addressing Should take ~3 mo to add a new name or message Should take ~3 mo to add a new name or message – Is there a block of identifiers/addresses/messages set aside for experimental use? If so, how do we get information about them? Use proprietary if you must be compliant Use proprietary if you must be compliant OEM reserved address available OEM reserved address available – If we make a controller which will remain on the vehicle, how do we get it added to the standard? How long does it take to get something added? Controller needs a NAME defined, can use self- configuring addressing Controller needs a NAME defined, can use self- configuring addressing Should take ~3 mo to add a new name or message Should take ~3 mo to add a new name or message FAQFAQ

3. Tools / Emergencies? – What kind of diagnostic/programming software tools are available? http://www.noregon.com/caninterface.html http://www.noregon.com/caninterface.html http://www.vector-cantech.com/ http://www.vector-cantech.com/ – Is there some kind of provision or protocol for when a controller, etc. can't talk to the micro, etc.? i.e., is there a 911/411 for figuring out what's wrong? Need a good PC based tool and a test network Need a good PC based tool and a test network – What kind of diagnostic/programming software tools are available? http://www.noregon.com/caninterface.html http://www.noregon.com/caninterface.html http://www.vector-cantech.com/ http://www.vector-cantech.com/ – Is there some kind of provision or protocol for when a controller, etc. can't talk to the micro, etc.? i.e., is there a 911/411 for figuring out what's wrong? Need a good PC based tool and a test network Need a good PC based tool and a test network FAQFAQ

4. FAQFAQ Network initialization / module naming? – How are ECUs identified? – Are there rules for initialization? – Are there requirements if power supply drops out briefly? – How are ECUs identified? – Are there rules for initialization? – Are there requirements if power supply drops out briefly?

5. Purpose of Network Management Describes –the management of source addresses and the association of those addresses with the actual functional identification of a device –the detection and reporting of network related errors. –initialisation processes –requirements for reaction to brief power outages –minimum requirements for network connected electronic control units. Provides methods for distributed management of addresses and identity (no master). Describes –the management of source addresses and the association of those addresses with the actual functional identification of a device –the detection and reporting of network related errors. –initialisation processes –requirements for reaction to brief power outages –minimum requirements for network connected electronic control units. Provides methods for distributed management of addresses and identity (no master).

6. Defines NAMEs for ECUsDefines NAMEs for ECUs –Provides hierarchical naming structure Three Hierarchical LevelsThree Hierarchical Levels –Device Class -> function-> ECU –Provides instance count for each level –Provides identification of manufacturer of ECU –Provides type IDs for Class and Function Defines address configuration typesDefines address configuration types –ECU Address configuration –Configurable Address –Service Configurable Address –Command Configurable Address –Self-Configurable Address ECU –(J1939) Arbitrary address capable Defines NAMEs for ECUsDefines NAMEs for ECUs –Provides hierarchical naming structure Three Hierarchical LevelsThree Hierarchical Levels –Device Class -> function-> ECU –Provides instance count for each level –Provides identification of manufacturer of ECU –Provides type IDs for Class and Function Defines address configuration typesDefines address configuration types –ECU Address configuration –Configurable Address –Service Configurable Address –Command Configurable Address –Self-Configurable Address ECU –(J1939) Arbitrary address capable Network Management Functions

7. Defines ECU typesDefines ECU types –Standard –Diagnostic/Development Tool –Network Interconnection Defines address initialisation processDefines address initialisation process Defines address commanding processDefines address commanding process Defines power continuity requirementsDefines power continuity requirements –ISO and J1939 are different Defines ECU typesDefines ECU types –Standard –Diagnostic/Development Tool –Network Interconnection Defines address initialisation processDefines address initialisation process Defines address commanding processDefines address commanding process Defines power continuity requirementsDefines power continuity requirements –ISO and J1939 are different Network Management Functions

8. Messages defined for Network Management Request for Address Claim Request for Address Claim – Normal Request Message of the Address Claim PGN Address Claim Address Claim Commanded Address Commanded Address Cannot Claim Cannot Claim – Address Claim of the Null Address (254) Request for Address Claim Request for Address Claim – Normal Request Message of the Address Claim PGN Address Claim Address Claim Commanded Address Commanded Address Cannot Claim Cannot Claim – Address Claim of the Null Address (254)

9. Always sent to Global!

11. ECUs have a NAME and address (numeric ID)ECUs have a NAME and address (numeric ID) – Address Provides unique identity within a sessionProvides unique identity within a session Included in every message to provide message uniquenessIncluded in every message to provide message uniqueness – NAME Provides high probability of a unique identifier within a connected systemProvides high probability of a unique identifier within a connected system Provides some functional identification of ECUsProvides some functional identification of ECUs Used to arbitrate in the case of an address selection conflictUsed to arbitrate in the case of an address selection conflict ECUs have a NAME and address (numeric ID)ECUs have a NAME and address (numeric ID) – Address Provides unique identity within a sessionProvides unique identity within a session Included in every message to provide message uniquenessIncluded in every message to provide message uniqueness – NAME Provides high probability of a unique identifier within a connected systemProvides high probability of a unique identifier within a connected system Provides some functional identification of ECUsProvides some functional identification of ECUs Used to arbitrate in the case of an address selection conflictUsed to arbitrate in the case of an address selection conflict NAMEing - ECU Identity within the network

12. NAME Structure

13. NAME Hierarchy

14. NAME Example – Second ECU of a Rate Control unit on third Planter Self-Configuring - True = 1 Self-Configuring - True = 1 Industry Group - Agriculture and Forestry = 2 Industry Group - Agriculture and Forestry = 2 Device Class - Planter/Seeders = 4 Device Class - Planter/Seeders = 4 Device Class Instance - Third Planter = 2 Device Class Instance - Third Planter = 2 Function - Rate Control (undefined) = 255 Function - Rate Control (undefined) = 255 Function Instance - First undefined = 0 Function Instance - First undefined = 0 ECU Instance - Second ECU = 1 ECU Instance - Second ECU = 1 – Second ECU of a Rate Control unit on third Planter Self-Configuring - True = 1 Self-Configuring - True = 1 Industry Group - Agriculture and Forestry = 2 Industry Group - Agriculture and Forestry = 2 Device Class - Planter/Seeders = 4 Device Class - Planter/Seeders = 4 Device Class Instance - Third Planter = 2 Device Class Instance - Third Planter = 2 Function - Rate Control (undefined) = 255 Function - Rate Control (undefined) = 255 Function Instance - First undefined = 0 Function Instance - First undefined = 0 ECU Instance - Second ECU = 1 ECU Instance - Second ECU = 1

15. Initialization Process Given in the text of the document Given in the text of the document – Following figures Provides distributed methods for ECUs to secure the use of an address Provides distributed methods for ECUs to secure the use of an address Provides processes for both self and non-self configuring ECUs Provides processes for both self and non-self configuring ECUs Given in the text of the document Given in the text of the document – Following figures Provides distributed methods for ECUs to secure the use of an address Provides distributed methods for ECUs to secure the use of an address Provides processes for both self and non-self configuring ECUs Provides processes for both self and non-self configuring ECUs

16. State Transitions for self-configuring ECUs

17. State Transitions for Non Self-configuringECUs

18. NAME-Address Table Maintenance – Addresses of ECUs may change May occur on initialization (initial address conflict) May occur on initialization (initial address conflict) – New ECUs are added since last power-up Could occur during operation Could occur during operation – New ECUs are powered during operation Self-Configuring ECUs lose conflicts with non-Self- Configuring ECUs Self-Configuring ECUs lose conflicts with non-Self- Configuring ECUs – Self-Configuring bit in NAME gives non-self-configuring ECUs priority – Change of Addresses of ECUs rare ECUs retain successfully claimed address for next power-up ECUs retain successfully claimed address for next power-up Changes occur on re-configuration Changes occur on re-configuration – Addresses of ECUs may change May occur on initialization (initial address conflict) May occur on initialization (initial address conflict) – New ECUs are added since last power-up Could occur during operation Could occur during operation – New ECUs are powered during operation Self-Configuring ECUs lose conflicts with non-Self- Configuring ECUs Self-Configuring ECUs lose conflicts with non-Self- Configuring ECUs – Self-Configuring bit in NAME gives non-self-configuring ECUs priority – Change of Addresses of ECUs rare ECUs retain successfully claimed address for next power-up ECUs retain successfully claimed address for next power-up Changes occur on re-configuration Changes occur on re-configuration

19. NAME-Address Table Maintenance Must maintain current “NAME to Address” relationship Must maintain current “NAME to Address” relationship – For ECUs to which destination specific messages are sent Commands, Requests Commands, Requests May need current “NAME to Address” relationship May need current “NAME to Address” relationship – For ECUs that are Listened to If the information is sender dependent If the information is sender dependent – Procedure Listen to address claims Listen to address claims Update table for those of interest Update table for those of interest Maintain across power disruptions Maintain across power disruptions Must maintain current “NAME to Address” relationship Must maintain current “NAME to Address” relationship – For ECUs to which destination specific messages are sent Commands, Requests Commands, Requests May need current “NAME to Address” relationship May need current “NAME to Address” relationship – For ECUs that are Listened to If the information is sender dependent If the information is sender dependent – Procedure Listen to address claims Listen to address claims Update table for those of interest Update table for those of interest Maintain across power disruptions Maintain across power disruptions

20. – < 10 ms, interruptions spaced by at least 100 ms: NO Loss of normal network communications nor loss of in-process messages.NO Loss of normal network communications nor loss of in-process messages. NO Processor reset.NO Processor reset. NO Loss of data in volatile memory, including network configuration information and/or messages in progress over the network.NO Loss of data in volatile memory, including network configuration information and/or messages in progress over the network. – > 1s Power is not restored within 1 second then the ECU must reset and complete a Power On Self Test (POST).Power is not restored within 1 second then the ECU must reset and complete a Power On Self Test (POST). – Between 10ms and 1s Internal requirements determine if a reset is required.Internal requirements determine if a reset is required. – < 10 ms, interruptions spaced by at least 100 ms: NO Loss of normal network communications nor loss of in-process messages.NO Loss of normal network communications nor loss of in-process messages. NO Processor reset.NO Processor reset. NO Loss of data in volatile memory, including network configuration information and/or messages in progress over the network.NO Loss of data in volatile memory, including network configuration information and/or messages in progress over the network. – > 1s Power is not restored within 1 second then the ECU must reset and complete a Power On Self Test (POST).Power is not restored within 1 second then the ECU must reset and complete a Power On Self Test (POST). – Between 10ms and 1s Internal requirements determine if a reset is required.Internal requirements determine if a reset is required. Reaction to Power Supply Voltage Disturbances and Interruptions