Design Studio | CAN bus Protocol | User Guide 2 PanelPilotACE | CAN bus Protocol | Userwww.lascarelectronics.com Guide | Issue 2 10/2019 Design Studio | CAN bus Protocol | User Guide Contents Page No. 1. Introduction 4 1.1 SAE J1939 CAN bus Standards 4 2. Getting Started with CAN bus 5 2.1 Installing the S70-CAN Adapter 5 3. Design Studio Elements for CAN bus 7 4. CAN bus Device Hardware Element Properties 8 5. The CAN Variable 9 6. CAN Frame Builder 11 7. Runtime & Error Handling 12 7.1 Active State 12 7.2 Comms Error Handler 12 7.3 Resolve Connection Action 12 8. Address Limitations 13 9. Tutorial: Basic Data Transfer 13 9.1 Send PDU1 type data frame to bus 13 9.2 Create a CAN bus device in the Design Studio 13 9.3 Add a CAN bus Variable to a project 14 9.4 Add a CAN Frame Builder to a project 15 9.5 Link to a button 16 9.6 Examine the results with a CAN bus analyser 16 9.7 Examine the results with another PanelPilotACE device 16 9.8 Auto reply “Request PGN” 17 9.9 Acknowledge Supported Feature 18 9.10 Encode/Decode CAN Frame with String Type Data 19 Change the linked project variable default value in 9.11 20 different values 10. Tutorial: Transport Data 21 Contact us for more 10.1 Transport Data with BAM 21 PanelPilotACE products, 10.2 RTS/CTS: Request to Send/Clear to Send 22 services and support: 11. Tutorial: Non-reconfigurable Address Claim 24 UK & Europe 11.1 Address Claim with contention 24 www.lascarelectronics.com [email protected] 11.2 Address Claim with contention 25 +44(0)1794 884567 12. Tutorial: Reconfigurable Address Claim 26 Americas 13. Tutorial: Error Handling 27 www.lascarelectronics.com 13.1 Using Communication Error Element 27 [email protected] (814) 835 621 13.2 Disable Error Dialog for a specific error 27 Asia www.lascarelectronics.com [email protected] (814) 835 621 PanelPilotACE | CAN bus Protocol | User Guide | Issue 2 10/2019 3 The CAN bus Protocol has SAE Standards J1939-73 Application PanelPilotACE been added to the SGD 70-A layer “Diagnostics” and J1939-74 PanelPilotACE colour capacitive Application Configurable Messaging Design Studio touch display. are NOT supported by the PanelPilotACE CAN bus. CAN bus The set-up and control of PanelPilotACE devices with CAN bus Standard J1939 defines a device Protocol added is implemented through the connected and operated via CAN PanelPilotACE Design Studio. bus as an Electronic Control Unit User Guide (ECU) or node. The CAN bus Protocol has been added to Design Studio software J1939-21 uses Parameter Group version 4.0.1.4050 onwards. Numbers (PGN) and Suspect 1. Introduction This and many other PanelPilotACE Parameter Numbers (SPN). Each SPN resources can be downloaded specifies the properties of a single A CAN bus (Controller Area Network) free from: parameter such as data length, is a message-based communications resolution, offset, range and unit. protocol. It was originally used www.lascarelectronics.com/ PGN specifies which SPNs belong within the automotive industries. panelpilotace-university to it. J1939-21 also provides a CAN bus allows microcontrollers user defined PGN range named and devices to communicate with 1.1 SAE J1939 CAN bus “Proprietary A”, “Proprietary A2” and each other without the need for a Standards “Proprietary B” host PC. The PanelPilotACE CAN bus adapter has been created to comply with the J1939-71 specifies that all PGN and As well as the Automotive industry, Society of Automotive Engineers SPNs can be used in a vehicle. CAN bus can be used in many other (SAE) set of standards, specifically PanelPilotACE CAN bus J1939 areas including Aviation, Industrial SAE J1939 and the following: Automation and Mechanical Control, Elements provide a flexible way to Building Automation and Medical i) J1939-21 Data Link Layer create SPNs and PGNs. Users can Equipment. ii) J1939-71 Vehicle Application create any PGN or SPN covered by Layer J1939-71 and J1939-75 (Application Layer - Generator Sets and iii) J1939-81 Network Management Industrial) or Proprietary PGN. 4 PanelPilotACE | CAN bus Protocol | User Guide | Issue 2 10/2019 Design Studio | CAN bus Protocol | User Guide Data can be regularly reported by The PanelPilotACE J1939 CAN bus 1. Make sure the SGD 70-A is an ECU or by a Request PGN from Element also provides the ability to powered-off. another ECU. reconfigure it’s address according to 2. Plug the S70-CAN Adapter into a “Commanding Address” message. the SK2 Pin Header on the Commanding ECUs can also send However, note that it is not able to reverse of the SGD 70-A device queries to other ECUs to check the issue this message. (see Figure 1). support feature. Users can create PGNs by using the PanelPilotACE Each PGN contains 8 bytes. A PGN The CAN bus adapter can be wired CAN Frame Builder in Design Studio. with a data length of more than 8 point to point or by multi-drop This will automatically setup the bytes will be carried by a transport wiring. response of the Request PGN and protocol message as defined by acknowledge available features. J1939-21. Both Broadcast and An example of wiring an S70-CAN RTS/CTS transport protocols are to a DB9-F connector can be seen in Each ECU has its own 8 bit address supported. Figure 3. and a 64 bit ECU Name. Public, preferred addresses for ECUs can be Figure 2 shows a multi-drop found in the J1939 Appendix that is wiring to system with multiple ECUs available to view at www.sae.org. 2. Getting Started or SGD-70-A. The preferred address is the default with CAN bus one used by ECUs on a network however, conflicts can occur. 2.1 Installing the S70-CAN Standard J1939-81, includes a Adapter procedure to resolve these conflicts The S70-CAN adapter is available (view the tutorials in section 11 as an Add-on board for the & 12). PanelPilotACE SGD 70-A model. The following are the instructions for installing the adapter. The PanelPilotACE SGD 70-A with S70-CAN Adapter. PanelPilotACE | CAN bus Protocol | User Guide | Issue 2 10/2019 5 S70-CAN Adapter Figure 1. Plugging in the S70-CAN Adapter. GND CANL CANH S70-CAN Terminal Block ECU ECU ECU S70-CAN Terminal Block Figure 2. Multiple ECU connections diagram. CAN bus DB9-F GND Optional GND Wire 1 CANL CANH 5 Twisted Pair Signal Wires S70-CAN Terminal Block Figure 3. S70-CAN to DB9-F wiring diagram. 6 PanelPilotACE | CAN bus Protocol | User Guide | Issue 2 10/2019 Design Studio | CAN bus Protocol | User Guide 3. Design Studio Elements for CAN bus The PanelPilotACE Design Studio contains two Elements and one Project Variable for a user to enable the CAN bus Protocol. 1. CAN bus Device Hardware Element This Hardware Element includes properties to control the S70-CAN hardware port and setup the ECU information. 2. CAN Frame Builder Function Element This Function Element provides the construct service. It can create J1939 CAN frame data encode, data decode and mapping to other Design Studio resources such as Project Variables or Element Properties. Figure 4. The Properties Editor showing CAN bus Device Properties. 3. CAN Project Variable This Variable provides a flexible way to construct CAN frame data in terms of PGNs and SPNs. It can be used to create a simulated ECU (Provide Service) or to remote control another ECU (Request Service). Figure 5. The ECU Construct Name dialogue box. PanelPilotACE | CAN bus Protocol | User Guide | Issue 2 10/2019 7 4. CAN bus Device Property Name Description Name Element Name Hardware Channel S70-CAN includes a signal CAN bus port. This is always Channel 1 Element The Frame Rate can be set as 125, 256, 512 or 1 Mbits. All devices Properties using CAN bus use the same frame rate. The configurable properties of the Frame Rate Note: Do not connect a PanelPilotACE device to an active CAN bus CAN bus Device Element can be with an unknown frame rate. Mismatched frame rates may cause found in the Properties Editor within network nodes to switch to passive or bus-off mode. the Design Studio. The Properties This allows selection of the version of the CAN bus Protocol to be used. Editor is located in the top right- CAN Network hand side of the Design Studio Type Note: Only CAN J1939 Protocol is functional at this time. Open CAN workspace (see Figure 4). Table 1 and Native mode are reserved for future expansion. describes which of the values and Every ECU controller connected to a CAN bus will process all data fields within the Properties Editior frames on the bus and de-assert the ACK bit if any controller is that can be configured. found with errors on a data frame. The original controller will resend data frames until the accumulated error count exceeds the Listen Only threshold that activates “Passive” or “Bus-off’ mode. Mode A user can configure the controller to operate in “Listen Only Mode”. It does not de-assert the ACK bit if an ECU is just used as a monitor or to display an SPN parameter (i.e. read only). Each ECU on a network will have at least one 64 bit Name and one address assigned to it. A complex ECU can have multiple addresses and names. The Device Address, PGN and Message Priority form the CAN ID. This affects the message priority. Addresses can be allocated statically or dynamically using the “Address Claim” arbitration process.