ELECTRONICS Body Builders BODYBUILDERS WEB SITE DEDICATED TO
ELECTRONICS Body Builders
BODY-BUILDERS WEB SITE DEDICATED TO ELECTRONICS 2
ELECTRIC/ELECTRONICS CONNECTION BETWEEN EURO 6 VEHICLE AND BODY ü In this section we give information and suggestions about the electrical/electronic connection between vehicle and body with the aim to get the best solution in terms of cost, quality and safety. ü A large number of scenarios will be shown, from the simplest one to the more sophisticated, according to the mission need. ü For deeper technical details, you will be: ü addressed to the official IVECO technical documentation ü supported by the BB Market responsible. 3
EURO 6 BB INTERFACE OVERVIEW THREE MAIN CONFIGURATIONS BASE LINE serial BBinterface MID LINE extended BB interface HIGH LINE fully equipped BB interface • no PTO management • basic hardwired interface Strais & Trakker ST 14 A / ST 14 B Euro. Cargo ST 61071 / ST 72071 SEE CONNECTORS • PTO management • • CONNECTORS Extended hardwired interface Incl. <<Vehicle CAN fully operational>> output SEE OPT 4572 SEE CONNECTORS • • • Fully equipped hardwired interface CAN interface (acc. Ci. A 413 Truck-Gateway Std. ) BB-Safety support by Stopped. State feature • EN 1501 support for Rear. Loaded RCV vehicles Aligned to CEN/TC 183 interface for Refuse Collection Vhicles • no OPT to order Remote Halt-Brake support OPT 4572 OPT 0384 OPT 6821 4
CANOPEN – ADVANTAGES Instead to use simple wires from BB connectors, the CANOpen interface offers to BB the complete set of available vehicle information used by the on-board electronic systems. Main advantages: - Considerable number of information and controls - Flexible selection of information and control needed - Flexible Communication setup to match specific application needs - Clearly defined safety aspects - Expandable - Cost efficient Main performances: - Real-time capability - Transmission speed - Reliability & failure tolerance - Electromagnetic capability - Flexibility / configuration - Installation / assembly - Cost effectiveness DETAILS SEE BB CANopen MANUAL High High Low High 5
IVECO CANOPEN FLEXIBLE STRUCTURE If your application needs a «fully equipped body builder interface» (High Line) our system give you the possibility to configure it selecting the following modules: XDC CAN Firewall • Set of signals optimized for a specific mission (concrete mixer, crane, Refuse, etc. ) and • Conditions under which signals/requests are permitted or rejected BB Safety parameters • How to detect BB emergency and what should happen in case of BB emergency In the next steps you will find some guideline to choose the more appropriate XDC, the CAN Firewall as well as BB Safety setting for your application. 6
PROCEDURE TO CONFIGURE CAN INTERFACE Preliminary activities • Configure the CAN interface before placing order • List vehicle interface requirements • Get familiar with BB instruction manuals • Contact MKT reference person if you need support LINK Interface approach • Choose CAN interface approach CAN Firewall XDC • Choose XDC set • Choose CAN Firewall BB Safety • BB Safety parameters Download configuration • Download the selected configuration * If you need a HIGH LINE configuration, but without CAN, follow this different procedure: LINK 7
CAN INTERFACE APPROACH Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration CAN – POSSIBLE COMMUNICATION CONFIGURATION APPROACHES 1. Use «Iveco default CAN communication» aligned to SAE J 1939 protocol (see details about available signals in CANOpen BB Manual) already available from Manufacturing Plant (OPT 0384) ü ü Focused for BB not being familiar with CANOpen No actions needed 2. Use of one of «Public CANOpen communication» pre-defined for a specific mission (see XDC library). Suggested when the mission is in line with pre-defined set of parameters for specific missions ü Focused for BB not being familiar with CANOpen 3. Use of a «Private CANOpen communication» developed by Iveco according to Body-Builder specs. Suggested for an application customized on the mission ü Focused for BB not being familiar with CANOpen 4. Development of a «CANOpen configuration by Body-Builder» using a standard CANOpen configurator tool. Suggested when the Body Builder has the adequate knowledge on the matter. ü Requires BB familiar with CANOpen ü Allows individual CAN configuration by BB in a fully autonomous manner. 8
1. Use «Iveco default CAN communication» aligned to SAE J 1939 protocol (see details about 1 available signals in CANOpen BB Manual) already available from Manufacturing Plant (OPT 0384) ü ü Focused for BB not being familiar with CANopen No actions needed 9
IVECO DEFAULT CAN COMMUNICATION Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration • What it allows to do: 1. Read entire SAE J 1939 CAN Information provided by Vehicle 2. Control Engine RPM, Start&Stop the engine 3. Engage/disengage PTO • Actions: order OPT 0384 available from Plant; no further actions needed. • For the available signals see CANopen IVECO Default: link < EXCEL> / link < VECTOR. DBC>. • • Check if the used default CAN Firewall parameters are in line with your application. Check if the used default BB Safety parameters are in line with your application. GO TO CHECK THE PARAMETERS 10
CAN FIREWALL PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Choose the CAN Firewall parameters for your application. ü The CAN interface offers 72 CAN requests. 11 out of these CAN requests are only permitted under defined conditions. • • Engine start Engine stop Engine starter lockout Request engine rpm • • Rpm upper limit Rpm lower limit Engine torque limit Vehicle speed limit • ASC 2 request msg (ECAS Remote Control) • TSC 1 request msg (Engine Remote Control) • TC 1 request msg (Gearbox Remote Control) ü For each of the 11 CAN request the permitted conditions can be separately selected. The condition to permit / reject the CAN request are: • Various brake & powertrain status information • Vehicle speed status • BB enable input activated 11
CAN FIREWALL PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Actions: 1. Verify if your application use «CAN requests» which are under CAN Firewall control. 2. Verify if the related «Default setting» is in line with your application. If so, there’s no need of further actions. 3. If not, select a suitable set of parameters (var 1, var 2, etc. ). Engine Starter Lockout 0 x 613 D Variant 1… 5 Engine Start 0 x 613 E Variant 1… 5 P A R S A E Engine Stop 0 x 613 F Variant 1… 5 M E T T E S R S Engine High Idle 0 x 6140 Variant 1… 5 Etc. . SEE FIREWALL TABLE Download CAN_Firewall e. g. Starter Lock. Out → Default Engine Start → Var_3 Engine Stop → Default Engine High idle → Var_2 Engine Low idle → Var_4 Engine Trq. Limit → Default Veh Speed. Limit → Default Req. Eng. Speed → Var_3 TSC 1 → Default ASC 2 → Default TC 1 → Default 12
BB-SAFETY PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Choose the BB Safety parameters for your application. ü The Interface is able to detect BB emergency inside the BB application. Select your detection mechanism: • none • Body-Builder CAN timeout monitoring (HB monitoring) • Monitoring of an Hardware input (also for non CAN applications, always enabled) ü The Interface is able to enter autonomously into Stopped. State. Therefore simple and user friendly Pre-setting have been prepared: 1. Select PTO(x) state (engage/disengage), activate Emergency lights, 2. Select requested Engine rpm (800 rpm / 1000 rpm, 1200 rpm, 1400 rpm) 3. Engine rpm & vehicle speed limits (e. g. engine high idle 1500 rpm, Vmax 10 km/h) 4. Remote ECAS request (actually: only Remote control disabled) 5. Remote Gearbox request (actually: all Remote control disabled) ü The Interface offers different “Stopped. State Exit” conditions 1. „Stopped. State Exit“ via CAN 2. „Stopped. State Exit“ via cycling BB enable input ( ST 72072 A / Pin 3) 13
BB-SAFETY PARAMETERS Initialisation Phase • After CANopen Start (K 15/BBena) • Duration ~ 5 sec • Vehicle does not service requests INI Values (set to n. a. ) Preliminary activities • • • Interface approach Operational Phase Entered automatically (Default) Typical operation Status Vehicle service received requests BB sending messages CAN Firewall XDC • • • BB safety Download configuration Stopped State Only for critical situation Entered after EMCY activation Allows client specific actions BB sending messages Stopped. State CANopen Rx Objects Critical signals CANopen Rx Objects Last recieved or INI values serviced CAN Firewall Vehicle CANopen Rx Objects Critical Signals replaced CAN Firewall Appl. Firewall Vehicle 14
BB-SAFETY PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Actions: 1. Verify if your application benefit on <<Stopped. State>> feature 2. Verify if the related «Default setting» is in line with your application. If so, there’s no need of further actions. 3. If not, select a suitable set of parameters (var 1, var 2, etc. ). Hear. Beat Node ID Variant 1… 5 Stooped State PTO’s and Inputs Variant 1… 5 Stopped. State P A Engine Speed Request R A Variant 1… 5 M Stopped. State S E E Engine Limits T T S E R Variant 1… 5 S Stopped State Remote ECAS access SEE Stopped. State TABLE Download Stopped State, e. g. Monitoring & Exit: Monitoring Default Reaction Go 2 Stopped. State: PTO, lights Default Engine Limits Var_2 Engine Speed Var_3 ECAS Default Auto Gearbox Default Stopped. State EXIT : BB enable input Var_3 15
HOW TO REQUEST & DOWNLOAD THE SELECTED CONFIGURATION Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration ü Contact Dealer/Workshop and communicate: a. b. Firewall / Safety set of parameters VIN list ü Go to the Dealer to download the configuration. • The download cost for CAN Firewall / BB Safety is 63 €/VIN END OF PROCESS 16
IVECO DEFAULT COMMUNICATION 1/2 CAN FIREWALL BACK 17
IVECO DEFAULT COMMUNICATION 2/2 BB SAFETY BB Stopped. State BACK 18
2. Use of one of «Public CANOpen communication» pre-defined for a specific mission (see XDC 2 library). Suggested when the mission is in line with pre-defined set of parameters for specific missions ü Focused for BB not being familiar with CANopen 19
PUBLIC CANOPEN COMMUNICATION Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Choose a predefined set of signals according to the specific mission. PN 5801939376 PN 5801692392 PN 5801692376 PN 5801692384 PN TBD REFUSE TRUCKS RCV CEN 2010 REFUSE TRUCKS RCV CEN 2012 REFUSE TRUCKS CEN BENELUX CONCRETE MIXER CRANE/LIGHTING PLATFORMS (PILOT APPLICATION NEEDED) SEE SIGNALS EXCEL SEE SIGNALS *. DBC (PILOT APPLICATION NEEDED) PN 5801692366 PN 5801692390 PN 5801692387 PN 5801939199 PN 5801850655 AUTOMAROCCHI VALCUUM SUGGER FARID HYDROSTATIC DRIVE LINDE SEE SIGNALS EXCEL SEE SIGNALS EXCEL SEE SIGNALS *. DBC AVAILABLE SIGNALS 20
CAN FIREWALL PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Choose the CAN Firewall parameters for your application. ü The CAN interface offers 72 CAN requests. 11 out of these CAN requests are only permitted under defined conditions. • • Engine start Engine stop Engine starter lockout Request engine rpm • • Rpm upper limit Rpm lower limit Engine torque limit Vehicle speed limit • ASC 2 request msg (ECAS Remote Control) • TSC 1 request msg (Engine Remote Control) • TC 1 request msg (Gearbox Remote Control) ü For each of the 11 CAN request the permitted conditions can be separately selected. The condition to permit / reject the CAN request are: • Various brake & powertrain status information • Vehicle speed status • BB enable input activated 21
CAN FIREWALL PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Actions: 1. Verify if your application use «CAN requests» which are under CAN Firewall control. 2. Verify if the related «Default setting» is in line with your application. If so, there’s no need of further actions. 3. If not, select a suitable set of parameters (var 1, var 2, etc. ). Engine Starter Lockout 0 x 613 D Variant 1… 5 Engine Start 0 x 613 E Variant 1… 5 P A R S A E Engine Stop 0 x 613 F Variant 1… 5 M E T T E S R S Engine High Idle 0 x 6140 Variant 1… 5 Etc. . SEE FIREWALL TABLE Download CAN_Firewall e. g. Starter Lock. Out → Default Engine Start → Var_3 Engine Stop → Default Engine High idle → Var_2 Engine Low idle → Var_4 Engine Trq. Limit → Default Veh Speed. Limit → Default Req. Eng. Speed → Var_3 TSC 1 → Default ASC 2 → Default TC 1 → Default 22
BB-SAFETY PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Choose the BB Safety parameters for your application. ü The Interface is able to detect BB emergency inside the BB application. Select your detection mechanism: • none • Body-Builder CAN timeout monitoring (HB monitoring) • Monitoring of an Hardware input (also for none CAN applications, always enabled) ü The Interface is able to enter autonomously into Stopped. State. Therefore simple and user friendly Pre-setting have been prepared: 1. Select PTO(x) state (engage/disengage), activate Emergency lights, 2. Select requested Engine rpm (800 rpm / 1000 rpm, 1200 rpm, 1400 rpm) 3. Engine rpm & vehicle speed limits (e. g. engine high idle 1500 rpm, Vmax 10 km/h) 4. Remote ECAS request (actually: only Remote control disabled) 5. Remote Gearbox request (actually: all Remote control disabled) ü The Interface offers different “Stopped. State Exit” conditions 1. „Stopped. State Exit“ via CAN 2. „Stopped. State Exit“ via cycling BB enable input ( ST 72072 A / Pin 3) 23
BB-SAFETY PARAMETERS Initialisation Phase • After CANopen Start (K 15/BBena) • Duration ~ 5 sec • Vehicle does not service requests INI Values (set to n. a. ) Preliminary activities • • • Interface approach Operational Phase Entered automatically (Default) Typical operation Status Vehicle service received requests BB sending messages CAN Firewall XDC • • • BB safety Download configuration Stopped State Only for critical situation Entered after EMCY activation Allows client specific actions BB sending messages Stopped. State CANopen Rx Objects Critical signals CANopen Rx Objects Last recieved or INI values serviced CAN Firewall Vehicle CANopen Rx Objects Critical Signals replaced CAN Firewall Appl. Firewall Vehicle 24
BB-SAFETY PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Actions: 1. Verify if your application benefit on <<Stopped. State>> feature 2. Verify if the related «Default setting» is in line with your application. If so, there’s no need of further actions. 3. If not, select a suitable set of parameters (var 1, var 2, etc. ). Hear. Beat Node ID Variant 1… 5 Stooped State PTO’s and Inputs Variant 1… 5 Stopped. State P A Engine Speed Request R A Variant 1… 5 M Stopped. State S E E Engine Limits T T S E R Variant 1… 5 S Stopped State Remote ECAS access SEE Stopped. State TABLE Download Stopped State, e. g. Monitoring & Exit: Monitoring Default Reaction Go 2 Stopped. State: PTO, lights Default Engine Limits Var_2 Engine Speed Var_3 ECAS Default Auto Gearbox Default Stopped. State EXIT : BB enable input Var_3 25
HOW TO REQUEST & DOWNLOAD THE SELECTED CONFIGURATION Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration ü Go to IVECO Web Documentation [IWD]. (link) Match the PN of the selected XDC to the VIN number of your vehicle(s). ü Contact Market responsible for support ü Contact Dealer/Workshop and communicate: a. b. c. d. e. User ID IWD PN of XDC CAN Firewall set of parameters BB Safety set of parameters VIN list (for CAN applications only) ü Go to the Dealer to download the configuration. • • The download cost for XDC is 63 €/VIN The download cost for Firewall / Safety is 63 €/VIN END OF PROCESS 26
PUBLIC CANOPEN COMMUNICATION 1/2 CAN FIREWALL BACK 27
PUBLIC CANOPEN COMMUNICATION 2/2 BB SAFETY BB Stopped. State BACK 28
3. Use of a «Private CANOpen communication» developed by Iveco according to Body-Builder 3 specs. Suggested for an application customized on the mission ü Focused for BB not being familiar with CANopen 29
PRIVATE CANOPEN COMMUNICATION (CCM…) Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration 1. Download the form to describe the specs of your mission. SEE BB CANopen MANUAL SEE TEMPLATE BB INTERFACE 30
PRIVATE CANOPEN COMMUNICATION (CCM…) Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration 2. Send the form with specs to your reference person on your market …@iveco. com The MM reference person will support you on this activity. He provide also info about cost&time when new. xdc file is available (new P/N). SEE LIST OF REFERENCE PEOPLE 3. BB to select suitable CAN-Firewall parameter 4. BB to select suitable BB Safety parameter The MM reference person will support you on this activity. BACK CHECK PARAMETER CAN FIREWALL CHECK PARAMETER BB SAFETY 31
CAN FIREWALL PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Choose the CAN Firewall parameters for your application. ü The CAN interface offers 72 CAN requests. 11 out of these CAN requests are only permitted under defined conditions. • • Engine start Engine stop Engine starter lockout Request engine rpm • • Rpm upper limit Rpm lower limit Engine torque limit Vehicle speed limit • ASC 2 request msg (ECAS Remote Control) • TSC 1 request msg (Engine Remote Control) • TC 1 request msg (Gearbox Remote Control) ü For each of the 11 CAN request the permitted conditions can be separately selected. The condition to permit / reject the CAN request are: • Various brake & powertrain status information • Vehicle speed status • BB enable input activated 32
CAN FIREWALL PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Actions: 1. Verify if your application use «CAN requests» which are under CAN Firewall control. 2. Verify if the related «Default setting» is in line with your application. If so, there’s no need of further actions. 3. If not, select a suitable set of parameters (var 1, var 2, etc. ). Engine Starter Lockout 0 x 613 D Variant 1… 5 Engine Start 0 x 613 E Variant 1… 5 P A R S A E Engine Stop 0 x 613 F Variant 1… 5 M E T T E S R S Engine High Idle 0 x 6140 Variant 1… 5 Etc. . SEE FIREWALL TABLE Download CAN_Firewall e. g. Starter Lock. Out → Default Engine Start → Var_3 Engine Stop → Default Engine High idle → Var_2 Engine Low idle → Var_4 Engine Trq. Limit → Default Veh Speed. Limit → Default Req. Eng. Speed → Var_3 TSC 1 → Default ASC 2 → Default TC 1 → Default 33
BB-SAFETY PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Choose the BB Safety parameters for your application. ü The Interface is able to detect BB emergency inside the BB application. Select your detection mechanism: • none • Body-Builder CAN timeout monitoring (HB monitoring) • Monitoring of an Hardware input (also for none CAN applications, always enabled) ü The Interface is able to enter autonomously into Stopped. State. Therefore simple and user friendly Pre-setting have been prepared: 1. Select PTO(x) state (engage/disengage), activate Emergency lights, 2. Select requested Engine rpm (800 rpm / 1000 rpm, 1200 rpm, 1400 rpm) 3. Engine rpm & vehicle speed limits (e. g. engine high idle 1500 rpm, Vmax 10 km/h) 4. Remote ECAS request (actually: only Remote control disabled) 5. Remote Gearbox request (actually: all Remote control disabled) ü The Interface offers different “Stopped. State Exit” conditions 1. „Stopped. State Exit“ via CAN 2. „Stopped. State Exit“ via cycling BB enable input ( ST 72072 A / Pin 3) 34
BB-SAFETY PARAMETERS Initialisation Phase • After CANopen Start (K 15/BBena) • Duration ~ 5 sec • Vehicle does not service requests INI Values (set to n. a. ) Preliminary activities • • • Interface approach Operational Phase Entered automatically (Default) Typical operation Status Vehicle service received requests BB sending messages CAN Firewall XDC • • • BB safety Download configuration Stopped State Only for critical situation Entered after EMCY activation Allows client specific actions BB sending messages Stopped. State CANopen Rx Objects Critical signals CANopen Rx Objects Last recieved or INI values serviced CAN Firewall Vehicle CANopen Rx Objects Critical Signals replaced CAN Firewall Appl. Firewall Vehicle 35
BB-SAFETY PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Actions: 1. Verify if your application benefit on <<Stopped. State>> feature 2. Verify if the related «Default setting» is in line with your application. If so, there’s no need of further actions. 3. If not, select a suitable set of parameters (var 1, var 2, etc. ). Hear. Beat Node ID Variant 1… 5 Stooped State PTO’s and Inputs Variant 1… 5 Stopped. State P A Engine Speed Request R A Variant 1… 5 M Stopped. State S E E Engine Limits T T S E R Variant 1… 5 S Stopped State Remote ECAS access SEE Stopped. State TABLE Download Stopped State, e. g. Monitoring & Exit: Monitoring Default Reaction Go 2 Stopped. State: PTO, lights Default Engine Limits Var_2 Engine Speed Var_3 ECAS Default Auto Gearbox Default Stopped. State EXIT : BB enable input Var_3 36
HOW TO REQUEST & DOWNLOAD THE SELECTED CONFIGURATION Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration ü Go to IVECO Web Documentation [IWD]. (link) Match the PN of the selected XDC to the VIN number of your vehicle(s). ü Contact Market responsible for support ü Identify Interface Customisation requirements ü Contact Dealer/Workshop and communicate: a. b. c. d. e. User ID IWD PN of XDC CAN Firewall set of parameters BB Safety set of parameters VIN list (for CAN applications only) ü Go to the Dealer to download the configuration. • • The download cost for XDC is 63 €/VIN The download cost for Firewall / Safety is 63 €/VIN END OF PROCESS 37
PRIVAT CANOPEN COMMUNICATION 1/2 CAN FIREWALL BACK 38
PRIVAT CANOPEN COMMUNICATION 2/2 BB SAFETY BB Stopped. State BACK 39
4. Development of a «CANOpen configuration by Body-Builder» using a standard CANOpen 4 configurator tool. Suggested when the Body Builder has the adequate knowledge on the matter. ü Requires BB familiar with CANopen ü Allows individual CAN configuration by BB in a fully autonomous manner 40
CANOPEN CONFIGURATION BY BODYBUILDER Same Vehicle configuration as choice 1 ( «Iveco default CAN communication» ) (OPT 0384) Technical reference documentation: • Body Builder CANopen manual: • CANopen signals, • EXCEL Format • CANopen XDD Format <<Link>> <<Link>> *) *) provide all CAN signal details (Resolution, min/max Values, Units, . . ) allows integration inside CANopen simulation environment use of Standard CANopen EDS tool needed also available Free. Of. Charge IVECO use «CANeds» from «VECTOR Informatik Gmb. H» 41
CAN FIREWALL PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Choose the CAN Firewall parameters for your application. ü The CAN interface offers 72 CAN requests. 11 out of these CAN requests are only permitted under defined conditions. • • Engine start Engine stop Engine starter lockout Request engine rpm • • Rpm upper limit Rpm lower limit Engine torque limit Vehicle speed limit • ASC 2 request msg (ECAS Remote Control) • TSC 1 request msg (Engine Remote Control) • TC 1 request msg (Gearbox Remote Control) ü For each of the 11 CAN request the permitted conditions can be separately selected. The condition to permit / reject the CAN request are: • Various brake & powertrain status information • Vehicle speed status • BB enable input activated 42
CAN FIREWALL PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Actions: 1. Verify if your application use «CAN requests» which are under CAN Firewall control. 2. Verify if the related «Default setting» is in line with your application. If so, there’s no need of further actions. 3. If not, select a suitable set of parameters (var 1, var 2, etc. ). Engine Starter Lockout 0 x 613 D Variant 1… 5 Engine Start 0 x 613 E Variant 1… 5 P A R S A E Engine Stop 0 x 613 F Variant 1… 5 M E T T E S R S Engine High Idle 0 x 6140 Variant 1… 5 Etc. . SEE FIREWALL TABLE Download CAN_Firewall e. g. Starter Lock. Out → Default Engine Start → Var_3 Engine Stop → Default Engine High idle → Var_2 Engine Low idle → Var_4 Engine Trq. Limit → Default Veh Speed. Limit → Default Req. Eng. Speed → Var_3 TSC 1 → Default ASC 2 → Default TC 1 → Default 43
BB-SAFETY PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Choose the BB Safety parameters for your application. ü The Interface is able to detect BB emergency inside the BB application. Select your detection mechanism: • none • Body-Builder CAN timeout monitoring (HB monitoring) • Monitoring of an Hardware input (also for none CAN applications, always enabled) ü The Interface is able to enter autonomously into Stopped. State. Therefore simple and user friendly Pre-setting have been prepared: 1. Select PTO(x) state (engage/disengage), activate Emergency lights, 2. Select requested Engine rpm (800 rpm / 1000 rpm, 1200 rpm, 1400 rpm) 3. Engine rpm & vehicle speed limits (e. g. engine high idle 1500 rpm, Vmax 10 km/h) 4. Remote ECAS request (actually: only Remote control disabled) 5. Remote Gearbox request (actually: all Remote control disabled) ü The Interface offers different “Stopped. State Exit” conditions 1. „Stopped. State Exit“ via CAN 2. „Stopped. State Exit“ via cycling BB enable input ( ST 72072 A / Pin 3) 44
BB-SAFETY PARAMETERS Initialisation Phase • After CANopen Start (K 15/BBena) • Duration ~ 5 sec • Vehicle does not service requests INI Values (set to n. a. ) Preliminary activities • • • Interface approach Operational Phase Entered automatically (Default) Typical operation Status Vehicle service received requests BB sending messages CAN Firewall XDC • • • BB safety Download configuration Stopped State Only for critical situation Entered after EMCY activation Allows client specific actions BB sending messages Stopped. State CANopen Rx Objects Critical signals CANopen Rx Objects Last recieved or INI values serviced CAN Firewall Vehicle CANopen Rx Objects Critical Signals replaced CAN Firewall Appl. Firewall Vehicle 45
BB-SAFETY PARAMETERS Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration Actions: 1. Verify if your application benefit on <<Stopped. State>> feature 2. Verify if the related «Default setting» is in line with your application. If so, there’s no need of further actions. 3. If not, select a suitable set of parameters (var 1, var 2, etc. ). Hear. Beat Node ID Variant 1… 5 Stooped State PTO’s and Inputs Variant 1… 5 Stopped. State P A Engine Speed Request R A Variant 1… 5 M Stopped. State S E E Engine Limits T T S E R Variant 1… 5 S Stopped State Remote ECAS access SEE Stopped. State TABLE Download Stopped State, e. g. Monitoring & Exit: Monitoring Default Reaction Go 2 Stopped. State: PTO, lights Default Engine Limits Var_2 Engine Speed Var_3 ECAS Default Auto Gearbox Default Stopped. State EXIT: BB enable input Var_3 46
HOW TO REQUEST & DOWNLOAD THE SELECTED CONFIGURATION Preliminary activities Interface approach XDC CAN Firewall BB safety Download configuration ü Contact Dealer/Workshop and communicate: a. b. Firewall / Safety set of parameters VIN list ü Go to the Dealer to download the configuration. • The download cost for CAN Firewall / BB Safety is 63 €/VIN END OF PROCESS 47
CANOPEN COMMUNICATION BY BODYBUILDER 1/2 CAN FIREWALL BACK 48
CANOPEN COMMUNICATION BY BODYBUILDER 2/2 BB SAFETY BB Stopped. State BACK 49
END OF THE PROCESS 50
END OF THE PROCESS If you want to explore another approach, click here: BACK If not, the process is finished. Private PN @ BB <-> VINs Re Server TLSS qu fo es r. P to riv fc on at e. P fir N m at io n Private PN Confirmation For Private PN IVECO dealer/workshop 51
SLIDES 52
PUBLIC CANOPEN COMMUNICATION 1/2 CAN FIREWALL 53
PUBLIC CANOPEN COMMUNICATION 2/2 BB SAFETY BB Stopped. State 54
IVECO BB INTERFACE – MARKET REFERENCES MARKET REFERENCE CONTACT Italy Mrs. C. Haunschmid France Mr. S. Giguet Spain Mr. A. Rodriguez Germany Mr. P. Klaus, W. Muehläuser Swiss Mr. D. Marti, G. Greco Benelux Mr. R. Van der Hengel UK Mr. D. Harmon, N. Shaw, C. Osborne, Z. D’Ouza, J. Bhagalia CE (Baltic) Mr. D. Kozeniauskas CE (Serbia) Mr. B. Kovacevic CE (Croatia / Slovenia) Mr. M. Postonjki CE (Bulgaria / Ukraine) Mr. N. Yordanov CE (Slovakia) Mr. R. Hanus CE (Romania) Mr. A. Bucur CE (Cekia) Mr. M. Muller BACK 55
IVECO BB INTERFACE – MARKET REFERENCES MARKET REFERENCE CONTACT Italy Mrs. C. Haunschmid France Mr. S. Giguet Spain Mr. A. Rodriguez Germany Mr. P. Klaus, W. Muehlhäuser Swiss Mr. D. Marti, G. Greco Benelux Mr. R. Van der Hengel UK Mr. D. Harmon, N. Shaw, C. Osborne, Z. D’Ouza, J. Bhagalia CE (Baltic) Mr. D. Kozeniauskas CE (Serbia) Mr. B. Kovacevic CE (Croatia / Slovenia) Mr. M. Postonjki CE (Bulgaria / Ukraine) Mr. N. Yordanov CE (Slovakia) Mr. R. Hanus CE (Romania) Mr. A. Bucur CE (Cekia) Mr. M. Muller BACK 56
ABBREVIATIONS PTO ECU EM CAN Ci. A CANopen CAL (CAN Application Layer) Object Dictionary COB (Communication Object) COB-ID (COBIdentifier) NMT (Network Management ) Node-ID (Node identification) Power Take OFF Electonic Control Unit Expansion Module Control Area Network CAN in Automation : International Association of CAN device’s manufacturers and users CANopen application and communication profile Defiend by Ci. A ISO 7 Layer for CAN applications defined by Ci. A, predecessor of CANopen application and communication profile Represents a collection of all data items in a node which are accessible via the network. On CAN bus data is sent as packets so called Communication Objects. A CAN device can send and receive COB’s. Each COB is identified by a unique COBidentifier. Necessary to do initialization, configuration and error processing. PDO (Process Data Object) RPDO TPDO SDO (Service Data Object) SYNC EMCY EDS XDC XDD RR Node ID identifies a device in CANopen net. All devices must have a unique Node ID 0 is reserved and addresses all nodes in the network RS KL 15 CS PDO is used to access Application Objects in real time with no protocol overhead. Received PDO, (comparable to SAE Received Messages) Transmitted PDO, (comparable to SAE Transmitted Messages) SDO ’s provide access to a nodes Data Dictionary. Synchronisation Objects can be used to setup a synchronise nodes in a Network EMCY Objects indicate the occurrence of a node error to the network. An Emergency object is only triggered once at occurrence. Electronic Data Sheet. The EDS file is a image of the CANopen node object dictionary. XML device configuration file, contains the CANopen configuration of the current device XML device description file, extension of a EDS file EM firewall - Request Restriction (on first occurance) EM firewall - Request Shutoff (during Request being active) Ignition Key Iveco Customer Service 57
EURO 6 BB CONNECTOR (LIST OF AVAILABLE SIGNALS FOR BODY-BUILDERS APPLICATION) – 1/2 Junction connector ST 14 A (blue) - for fitters (cab) Pin Function 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Engine start signal input Engine off signal input Brake lights signal for fitters Vehicle stationary signal output Handbrake engaged signal output -Side lights signal for fitters Engine condition (output signal) 0 V engine stopped / 24 V engine running Gearbox in neutral position signal Reverse gear signal Positive +15 Cruise Control SET connection point + Cruise Control SET connection point Cruise Control OFF connection point Cruise Control RESUME connection point Cruise Control setup (interior/exterior selection) Ground PTO command signal connection point 1 PTO command signal connection point 2 PTO command signal connection point 3 Positive +30 Wire colour code 8892 0151 1165 5515 6656 5155 7778 8050 2268 8871 8156 8157 8154 8155 0152 0000 0131 0132 0123 7772 ST 14 A Example Stralis EURO VI Base Line, See details in <<BB connector Euro 6 – Chapter 3. 1>> 58
EURO 6 BB CONNECTOR (LIST OF AVAILABLE SIGNALS FOR BODY-BUILDERS APPLICATION) – 2/2 connector ST 14 B (blue) - for fitters (cab) Pin Function Wire 1 2 3 4 5 6 7 8 0172 Signal for second speed limiter -Clutch status signal Programmable speed (PTS) Hazard lights signal --Engine speed signal 9 Exterior lights signal 9963 5542 1113 5584 3333 ST 14 B Example Stralis EURO VI Base Line, See details in <<BB connector Euro 6 – Chapter 3. 1>> BACK 59
EURO 6 BB CONNECTOR (LIST OF AVAILABLE SIGNALS FOR BODY-BUILDERS APPLICATION) – 2/2 connector ST 72072 A (black) - for fitters (cab) Pin Function 1 2 3 4 5 6 Wire -Neutral Gear requested & engaged Body. Builder Enable Vehicle CAN fully operational --- 6983 0991 -- ST 72072 A Example Stralis EURO VI Mid Line, See details in <<BB connector Euro 6 – Chapter 3. 2>> Junction connector ST 91 - ST 92 - ST 93 ST 91 (black) - PTO 1 (EM) ST 92 (black) - PTO 2 (EM) ST 93 (black) - PTO 3 (EM) Pin Function 1 2 3 4 PTO 1 Power take-off return signal Solenoid valve power supply Enabling signal for PTO Ground PTO 2 6131 9131 0391 0000 PTO 3 6132 9132 0392 0000 6133 9133 0393 0000 Example Stralis EURO VI Mid Line, See details in <<BB connector Euro 6 – Chapter 3. 2>> BACK 60
EURO 6 BB CONNECTOR (LIST OF AVAILABLE SIGNALS FOR BODY-BUILDERS APPLICATION) – 2/2 connector ST 72072 B (black) - for fitters (cab) Pin Function 1 2 3 4 5 6 7 8 Neutral Gear request Body. Builder Stopped. State (EMCY) input External Stopping Brake request Stopping Brake feedback Stepper Switch request Right direction light Left direction light Buzzer output (EN 1501) 9 Keep EM alive 10 EN 1501 Brake Diag lamp ouput 11 Brake output 12 Neutral gear request output 13 Chassis Ready (acc. EN 1501) 14 Accelerator Pedal low idle switch 15 Any PTO engaged output 16 BB Fluid level 17 BB pressure 18 BB Thermal temperature 19 Re. Gen inhibit 20 Re. Gen force Wire 0992 0993 0994 0995 0996 6985 6986 6987 6988 6989 6990 6991 6992 6993 6994 5981 5982 5983 5991 5992 ST 72072 B Example Stralis EURO VI High Line, See details in <<BB connector Euro 6 – Chapter 3. 3>> 61
CANOPEN – CONNECTORS Ci. A–C 413 Cab 9 Pole (High Line) Tyco Code Description 1 -967626 -1 CANOpen Cab connector Ci. A-F 413 Frame 7 Pole (High Line) Tyco Code Description 1 -718230 -1 CANOpen Frame connector* *if you order the connector also order pin’s, sealing and clip cover (90 or straight) Connector Location The connectors are located as shown in the drawing. As you can see the Ci. A-C 413 and Ci. A-F 413 are already connected by IVECO thus the Body Builder has no need to install a CAN wire from the Cab to the Frame. BACK 62
BASE LINE (1/2) Serial Std BB interface (without Expansion Module) - no OPT needed ü Without integrated PTO management ü Only basic hardwired interface, see below the signals available on specific connectors: 63
BODY-BUILDER EQUIPMENT REST of the VEHICLE (ENGINE, TRANMISSION, BRAKING SYSTEM; …) VEHICLE ARCHITECTURE Body-Builder System PTO 1 PTO 2 PTO 3 In-Vehicle analog / digital signals BB CAN Bus REST of the BODY-BUILDERS EQUIPMENTS BASE LINE (2/2) Body-Builders Connectors BACK 64
MID LINE (1/2) Extended BB interface (with Expansion Module) - OPT 4572 Like base-line, in addition: ü With PTO management / PTO predisposition ü With extended hardwired interface, see below additional signals: ü Vehicle CAN fully operational output The “Vehicle CAN fully operational” output indicates, that Vehicle Systems like ECAS, Braking System, Vehicle Computer, MUX System, Tachograph, Gearbox System are communicating without timeouts & the Expansion Module application is running. This Hardware output can be easily integrated inside the BB application technical Safety concept, also for applications not using a CAN interface. 65
BODY-BUILDER EQUIPMENT REST of the VEHICLE (ENGINE, TRANMISSION, BRAKING SYSTEM; …) VEHICLE ARCHITECTURE “Vehicle CAN fully operational” output Vehicle CAN Bus Expansion Module Body-Builder System PTO 1 PTO 2 PTO 3 In-Vehicle analog / digital signals BB CAN Bus REST of the BODY-BUILDERS EQUIPMENTS MID LINE (2/2) Body-Builders Connectors BACK 66
HIGH LINE (1/4) Fully equipped BB interface (with Expansion Module) - OPT 0384 Like base-line, in addition: ü With fully equipped hardwired interface, see below the additional signals available on specific connectors 67
HIGH LINE (2/4) ü With Vehicle Stopped State input In case of an emergency inside the BB application, IVECO offers the activation of the BB Stopped. State input. When that input is activated the vehicle enters - depending on configuration - autonomously in a Vehicle Stopped State. IVECO offers a set of pre-configured Stopped States settings to satisfy BB application specific needs, e. g. force all PTO to disengage, active EMCY light, stop the engine or Request engine speed to 1000 rpm, limit high idle to 1500 rpm, activate Vmax 10 km/h. ü With CAN / CANopen interface ü With CAN Firewall For certain CAN received objects, especially for objects related to engine access, the requests are only permitted under defined conditions. The mechanism which handles the access is called Firewall.
HIGH LINE (3/4) ü With EN 1501 support (only Euro. Cargo & Stralis) OPT 6821 The EN 1501 function is an option for rear loaded refuse collector vehicles equipped with foot plate. In compliance to EN 1501 -1 as soon as the foot plate is occupied the vehicle: • Shall not Reverse • Shall not drive above 30 km/h The function does not prevent the vehicle from rolling backward in uphill conditions. ü With Remote Halt-Brake support (only Euro. Cargo & Stralis) OPT 6821 The Remote Halt-Brake function activates the Vehicle foundation brakes - at vehicle speed smaller than 2 km/h. That Speed can be increased upon explicit Body. Builder request to max 6 km/h via Iveco CS tool. That feature is only supported during K 15 ON phase. It supports the Body. Builder to prevent vehicle from unintended rolling or driving. Note: on Stralis & Trakker Range the EN 1501 (OPT 6821) is incompatible with Hill-Holder (OPT 14861) !
BODY-BUILDER EQUIPMENT REST of the VEHICLE (ENGINE, TRANMISSION, BRAKING SYSTEM; …) VEHICLE ARCHITECTURE “Vehicle CAN fully operational” output “Stopped. State” input Vehicle CAN Bus Expansion Module CANOpen Bus PTO 1 PTO 2 PTO 3 In-Vehicle analog / digital signals Body-Builder System BB CAN Bus REST of the BODY-BUILDERS EQUIPMENTS HIGH LINE (4/4) Body-Builders Connectors BACK 70
PROCEDURE TO CONFIGURE HARDWARE INTERFACE Preliminary activities Interface approach • Configure the CAN interface before placing order • List vehicle interface requirements • Get familiar with BB instruction manuals • Contact MKT reference person if you need support BACK • Choose CAN interface approach XDC • Not needed CAN Firewall • Not needed BB Safety • BB Safety parameters Download configuration • Download the selected configuration 71
- Slides: 71