Product Manual CANcockpitTU00-0726-5111102 Technische Änderungen vorbehalten 0609 Technical details subject to change 5.2 - 7The reproduction, distribution and utilization of this document as well as the communication of its contents to others without expressauthorization is prohibited. Offenders will be held liable for the payment of damages. All right reserved in the event of the grant of a patent,utility model or design .CANopen-Specification for CANcockpitMinimum CapabilitiesTo enable devices, which do not support the complete DBT- (Distributor) and NMT (Network Management) Slave functionality,to co-operate with full capability devices, the following minimal capabilities are required:Module-ID,Object dictionary, depending on the device functionality,One SDO, supporting the mandatory entries (read only),Support of the following services as NMT Slave:Reset_Node,Enter_Pre-Operational_State,Start_Remote_Node,Stop_Remote_Node,Reset_CommunicationDefault profile ID-allocation schemeMinimum capability devices enter the Pre-Operational state directly after finishing the device initialisation. ID-allocation is viaWINgauge. Then the nodes can be switched directly into the Operational state. By switching a device into the stopped state itis forced to stop the communication altogether (except node guarding, if active). Furthermore, this state can be used toachieve certain application behaviour. The definition of this behaviour falls into the scope of device profiles.EEPROM Option for transition from pre-operational to operational state after KL.15on.It is possible to enable an option via EEPROM configuration, which lets CANcockpit move from pre-operational state tooperational state automatically after KL.15 is turned on. Also, if CANcockpit performs a reset, the operational state will beentered without requiring an NMT-command. A reset for example can be caused by a low voltage condition or a watchdogtrigger.However when an NMT-command is received to move from operational to another state, CANcockpit will perform therequested transition without automatically re-entering the operational mode.If the pre-operational state is entered, because of an error condition requiring this, then CANcockpit will remain in the pre-operational state without automatically moving to operational state again.Static allocation of the communication object identifiers (COB-ID's)Static distribution means that the identifiers are fixed by the module suppliers and may be changed by the system integratorthrough module specific means such as configuration with WINgauge.Restore DefaultsIf parameters in EEPROM can be changed via CANopen interface, then this option should be implemented.