DOCSLIB.ORG

CAN Bus Protocol | User Guide 2 Panelpilotace | CAN Bus Protocol | User Guide | Issue 2 10/2019 Design Studio | CAN Bus Protocol | User Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
CAN Bus Protocol | User Guide 2 Panelpilotace | CAN Bus Protocol | User Guide | Issue 2 10/2019 Design Studio | CAN Bus Protocol | User Guide 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.
Load more

Recommended publications
  • Internationally Standardized As Part of the Train Communication Network (TCN) Applied in Light Rail Vehicles Including Metros, T
    September 2012 CANopen on track Consist network applications and subsystems Internationally standardized as part of the train communication network (TCN) Applied in light rail vehicles including metros, trams, and commuter trains www.can-cia.org International standard for CANopen in rail vehicles IEC 61375 standards In June 2012, the international electro technical commission (IEC) has en- hanced the existing and well-established standard for train communication X IEC 61375-1 systems (TCN; IEC 61375), by the CANopen Consist Network. IEC 61375-3-3 Electronic railway equipment - Train VSHFLÀHVWKHGDWDFRPPXQLFDWLRQEDVHGRQ&$1RSHQLQVLGHDVLQJOHUDLO communication network vehicle or a consist in which several rail vehicles share the same vehicle bus. (TCN) - Part 1: General In general, the lower communication layers as well as the application layer are IEC 61375-3-3 IEC architecture based on the well-proven standards for CAN (ISO 11898-1/-2) and CANopen (1 7KLVDOORZVRQWKHRQHKDQGSURÀWLQJIURPWKHDYDLODEOH&$1 X IEC 61375-2-1 Electronic railway WRROVRQWKHPDUNHW2QWKHRWKHUKDQGLWLVSRVVLEOHWREHQHÀWIURPWKHEURDG equipment - Train UDQJHRIDYDLODEOH&$1RSHQSURWRFROVWDFNV&$1RSHQFRQÀJXUDWLRQDQG communication network diagnostic tools as well as off-the-shelf devices (see CANopen product guide (TCN) - Part 2-1: Wire train DWZZZFLDSURGXFWJXLGHVRUJ :HOOGHÀQHGFRPPXQLFDWLRQLQWHUIDFHVZLOO bus (WTB) therefore simplify system design and maintenance. X IEC 61375-2-2 ,QDGGLWLRQWRHQKDQFHGORZHUOD\HUGHÀQLWLRQV VXFKDVHJ&$1,GHQ- Electronic railway WLÀHUIRUPDWW\SHRIFRQQHFWRUGHIDXOWELWUDWHHWF
    [Show full text]
  • UCC 1 USB-CAN CONVERTER Contents
    Owner’s Manual UCC 1 USB-CAN CONVERTER Contents 1. Description....................................................................................................................... 17 2. Controls and Connections................................................................................................ 18 3. Installation ....................................................................................................................... 19 3.1 Unpacking.................................................................................................................... 19 3.2 Rack-Mounting............................................................................................................ 19 4. Initial Operation............................................................................................................... 20 4.1 PC Connection and CAN Driver Installation .............................................................. 20 4.2 Installing IRIS.............................................................................................................. 20 4.3 CAN-Bus Connection.................................................................................................. 20 4.4 ISOLATED / GROUNDED Switch ............................................................................ 22 5. Monitor Bus..................................................................................................................... 23 6. Technical Information....................................................................................................
    [Show full text]
  • LK9893 Developed for Product Code LK7629 - CAN Bus Systems and Operation
    Page 1 CAN bus systems and operation Copyright 2009 Matrix Technology Solutions Limited Page 2 Contents CAN bus systems and operation Introduction 3 Overview 5 Building Node A 6 Building Node B 7 Building Node C 8 Building Node D 9 Building the Scan/Fuse Node 10 Wiring It All Up 11 Worksheet 1 - The Startup Routine 12 Worksheet 2 - Seeing the Messages 13 Worksheet 3 - Receiving Messages 15 Worksheet 4 - System Monitoring and ‘Pinging’ 16 Worksheet 5 - System Faults 17 Worksheet 6 - Circuit Faults 19 Worksheet 7 - Fault Diagnosis Using Charts 20 Worksheet 8 - Build Your Own Vehicle! 21 Instructor Guide 22 Scheme of Work 26 Message Code Summary 32 Kvaser Analyser Set Up 33 Programming the MIAC 34 System Graphics 35 About this document: Code: LK9893 Developed for product code LK7629 - CAN bus systems and operation Date Release notes Release version 01 01 2010 First version released LK9893-80-1 revision 1 10 06 2010 MIAC programming notes included LK8392-80-1 revision 2 01 10 2012 Programming notes revised LK9893-80-3 25 09 2013 Warning that some faults require reprogramming LK9893-80-4 22 06 2015 Updated sensing resistors and diagrams LK9893-80-5 13 09 2017 Added to introduction and made less car-specific LK9893-80-6 Copyright 2009 Matrix Technology Solutions Limited Page 3 Introduction CAN bus systems and operation What is this all about? protocol to be used ‘on top’ of the basic CAN The ‘CAN’ in CAN bus stands for ‘Controller Area bus protocol to give additional functionality Network’ and ‘bus’ a bundle of wires.
    [Show full text]
  • CAN-To-Flexray Gateways and Configuration Tools
    CAN-to-Flexray gateways Device and confi guration tools lexray and CAN net- Listing bus data traffic toring channels it is possi- power management func- Fworks will coexists in (tracing) ble to compare timing rela- tionality offers configurable the next generation or pas- Graphic and text displays tionships and identify timing sleep, wake-up conditions, senger cars. Flexray orig- of signal values problems. and hold times. The data inally designed for x-by- Interactive sending of GTI has developed a manipulation functionality wire applications gains mar- pre-defined PDUs und gateway, which provides has been extended in or- ket acceptance particular- frames two CAN and two Flexray der to enable the user to ap- ly in driver assistance sys- Statistics on nodes and ports. It is based on the ply a specific manipulation tems. Nevertheless, Flexray messages with the Clus- MPC5554 micro-controller. function several times. Also applications need informa- ter Monitor The gateway is intended to available for TTXConnexion tion already available in ex- Logging messages for be used for diagnostic pur- is the PC tool TTXAnalyze, isting CAN in-vehicle net- later replay or offline poses, generating start-up/ which allows simultaneous works. Therefore, CAN-to- evaluation sync frames, and it can be viewing of traffic, carried on Flexray gateways are nec- Display of cycle multi- used with existing software the various bus systems. essary. Besides deeply em- plexing, in-cycle rep- tools. The Flexray/CAN bedded micro-controller etition and PDUs in the The TTXConnexion by gateway by Ixxat is a with CAN and Flexray inter- analysis windows TTControl is a gateway tool configurable PC application faces, there is also a need Agilent also provides an combining data manipula- allowing Flexray messag- for gateway devices as in- analyzing tool for Flexray tion, on-line viewing, and es and signals to be trans- terface modules for system and CAN.
    [Show full text]
  • LIN (LOCAL INTERCONNECT NETWORK) SOLUTIONS by Microcontroller Division Applications
    AN1278 APPLICATION NOTE LIN (LOCAL INTERCONNECT NETWORK) SOLUTIONS by Microcontroller Division Applications INTRODUCTION Many mechanical components in the automotive sector have been replaced or are now being replaced by intelligent mechatronical systems. A lot of wires are needed to connect these components. To reduce the amount of wires and to handle communications between these systems, many car manufacturers have created different bus systems that are incompatible with each other. In order to have a standard sub-bus, car manufacturers in Europe have formed a consortium to define a new communications standard for the automotive sector. The new bus, called LIN bus, was invented to be used in simple switching applications like car seats, door locks, sun roofs, rain sensors, mirrors and so on. The LIN bus is a sub-bus system based on a serial communications protocol. The bus is a single master / multiple slave bus that uses a single wire to transmit data. To reduce costs, components can be driven without crystal or ceramic resonators. Time syn- chronization permits the correct transmission and reception of data. The system is based on a UART / SCI hardware interface that is common to most microcontrollers. The bus detects defective nodes in the network. Data checksum and parity check guarantee safety and error detection. As a long-standing partner to the automotive industry, STMicroelectronics offers a complete range of LIN silicon products: slave and master LIN microcontrollers covering the protocol handler part and LIN transceivers for the physical line interface. For a quick start with LIN, STMicroelectronics supports you with LIN software enabling you to rapidly set up your first LIN communication and focus on your specific application requirements.
    [Show full text]
  • CAN / RS485 Interface Adapter for SHP Series
    Technical Reference Note CAN / RS485 Interface Adapter For SHP Series Total Power: < 1 Watts Input Voltage: 5V Internal Outputs: CAN, RS485, USB, I2C Special Features Product Description The new SHP Extension adapter enables both USB and Controller Area Network (CAN) or RS485 Bus connectivity, providing a complete interface between the • Input Protocols: SHP device and the I2C bus with a simple command set which enables the 1) RS485 using Modbus highest levels of configuration flexibility. 2) CAN using modified Modbus The CAN/RS485 to I2C interface adapter modules connect with CAN Bus • Output Protocol: architectures through CaseRx/CaseTx interfaces found on the SHP case. The I2C with SMBus Support modules communicate with on-board I2C Bus via MODbus Protocol for RS485 Bus and modified MODbus for CANbus. The new adapters now enable the SHP to be used in a host of new ruggedized applications including automotive networks, industrial networks, medical equipment and building automation systems. The RS485/CAN-to-I2C uses 2 Input Protocols and 1 Output Protocol. The Input Protocols used are: RS485 using Modbus (Command Index: 0x01), and CAN using modified Modus (Command Index: 0x02). The Output Protocol use is: I2C with SMBus support (Command Index: 0x80). www.solahd.com [email protected] Technical Reference Note Table of Contents 1. Model Number ………………………….………………………………………………………………. 4 2. General Description ……………………………………………………………………………………. 5 3. Electrical Specifications ……………………………………………………………………………..… 6 4. Mechanical Specification …………………………………………………….….…………………….. 9 5. Hardware Interfaces ………………………………………………………….……………………..... 12 6. Software Interfaces ……………………………………………………………................................ 13 6.1 Adapter Protocol Overview ……………………………………………………………………… 13 6.2 Protocol Transaction …………………………………………………………………………….. 13 6.3 Adapter Command and Response Packets …………………………………………….…..… 14 6.4 Adapter Control Commands ……………………………………………………………..……..
    [Show full text]
  • EN CAN-RS-485 BUS Gateway
    MTGW Installation Guide EN CAN-RS-485 BUS Gateway MTGW | Installation Instructions | 1.0 Overview CAN bus wiring requirements are as follows: Trademarks • CAN Bus Interface: Connect the CAN bus to the Microsoft® Windows® 98/2000/XP are registered MTR Communication Receiver with at least trademarks of Microsoft Corporation in the United 1.5 mm (16 AWG) shielded twisted-pair wire; States and other countries. maximum length: 2000 m (6500 ft). • RS-485 Buses 1-3: Use at least 1.0 mm (20 AWG) 1.0 Overview shielded twisted-pair wire for the RS-485 bus; maximum length: 1200 m (3900 ft). RS-485 bus 1.1 Multi-Tenant System (MTS) Overview wiring status is supervised. MTS is a distributed security system for monitoring 1.2 MTS Device Address and controlling a large number of small sites. You must assign an address to each device in the Examples include apartment and condominium system. The address consists of at least four segments. complexes, retail plazas, office buildings, and For example: educational and hospital campuses. 1.2.5.3.6 A typical MTS installation consists of the following components: • 1: This segment identifies the number assigned to the MTR central receiver (1 to 99). • MTSW Security Station Software: MTSW is an ® ® • 2: This segment identifies the CAN bus number application based on Microsoft Windows , occupied by the MTGW (1 or 2). installed on a PC and monitored by guard station • personnel. 5 : This segment identifies the MTGW’s CAN bus address (1 to 100). • MTR Communication Receiver: The MTR • receives and handles alarm events from devices 3 : This segment identifies the device’s RS-485 connected to the CAN RS-485 bus.
    [Show full text]
  • Local Interconnect Network Bus Application in Vehicle Presented By- Prashant M
    International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 2 Issue 2, February- 2013 Local Interconnect Network Bus Application In Vehicle Presented By- Prashant M. Ambure Guided By- Prof. Mrs. Aditi V. Vedalankar (MGM College of Engineering, Nanded) (Dept. Electronics and Telecommunication Engineering) Abstract busse interconnected between them as shown in the Local Interconnect Network bus was particularly figure below. This is a major difference with other low- designed for low-cost communication between smart cost busses as K-line which was intended to link all the sensors in automotive applications. It is used when ECUs to an external analyse tool for diagnosis purpose high bitrates communications as CAN bus are not The design consist of a central "Airbag needed. The LIN master initiates communication by control unit"(ACU) (a specific type of ECU) monitors a sending the “Header”. The “Data fields” are send by number of related sensors within the vehicle, including LIN master or a LIN slave. Only one slave will respond accelerometers, impact sensors, wheel speed sensors, to a given header. An airbag is part of a vehicle's gyroscopes, brake pressure sensors, and seat occupancy safety system, a flexible envelope designed for rapid sensors. When the requisite 'threshold' has been reached inflation in an automobile collision, to prevent vehicle or exceeded, the airbag control unit will trigger the occupants from striking hard interior objects such as ignition of a gas generator propellant to rapidly inflate a steering wheels. It is considered a "passive" safety nylon fabric bag. The inflated airbag reduces the component not requiring any input or action from the deceleration experienced by the passenger during the user, rather than an "active" component such as a seatIJERT IJERTcrash through the process of venting gas out of small belt, which requires fastening.
    [Show full text]
  • Technical Note TN 156 What Is CAN? Version 1.0
    Technical Note TN_156 What is CAN? Version 1.0 Issue Date: 2015-03-23 The purpose of this technical note is to explain the basics of CAN (Controller Area Network) which are a feature of FTDI’s MCUs. Use of FTDI devices in life support and/or safety applications is entirely at the user’s risk, and the user agrees to defend, indemnify and hold FTDI harmless from any and all damages, claims, suits or expense resulting from such use. Future Technology Devices International Limited (FTDI) Unit 1, 2 Seaward Place, Glasgow G41 1HH, United Kingdom Tel.: +44 (0) 141 429 2777 Fax: + 44 (0) 141 429 2758 Web Site: http://ftdichip.com Copyright © 2015 Future Technology Devices International Limited Technical Note TN_156 What is CAN? Version 1.0 Document Reference No.: FT_001079 Clearance No.: FTDI# 441 Table of Contents 1 Introduction .................................................................................................................................... 2 2 CAN Bus ........................................................................................................................................... 3 2.1 Signals ..................................................................................................................................... 4 2.1.1 MCU Signals .................................................................................................................... 4 2.1.2 PHY Signals ...................................................................................................................... 4 2.2 Typical interconnect
    [Show full text]
  • Communication Protocol Reference Guide
    Communication Protocol Reference Guide 2018-10-08, Rev. 2.0 © Copyright 2018, Nuvation Energy Table of Contents 1. Introduction . 1 1.1. About this Guide. 1 2. Modbus Protocol Support . 2 2.1. Overview . 2 2.1.1. Modbus RTU. 2 2.1.2. Modbus TCP . 2 2.2. Implemented MESA Models . 2 2.2.1. Common Model . 3 2.2.2. S801. 3 2.2.3. S802. 3 2.2.4. S803. 3 2.2.5. End Model . 3 2.3. MESA Model Structure and Nomenclature . 3 2.3.1. Points . 3 2.3.2. Fixed/Repeating Blocks . 3 2.3.3. Unimplemented Points . 4 2.3.4. Scale Factors . 5 2.4. Operational Cases for MESA . 5 2.4.1. External Controller Communicating Over MESA Interface . 5 2.4.2. External Nuvation BMS Monitoring Over MESA Interface . 6 2.5. Accessing MESA Models . 8 3. CAN Bus Protocol Support . 10 3.1. Overview . 10 3.2. CAN Reporting and Commands . 10 3.3. Data Format . 10 Communication Protocol Reference Guide - 2018-10-08, Rev. 2.0 1. Introduction Thank you for choosing Nuvation BMS™ Nuvation BMS™ is an enterprise-grade battery management system with support for various external communication protocols like Modbus RTU, Modbus TCP, and CANBus. Nuvation BMS is conformant with the MESA-Device/Sunspec Energy Storage Model (Draft 3). MESA (mesastandards.org) conformant products share a common communications interface that exposes all the data and control points required for operating an energy storage system. This enables Nuvation BMS to be integrated with other MESA-conformant energy storage hardware or software without the need for custom middleware.
    [Show full text]
  • Common High Speed Physical Layer Problems Version 1.0
    Common High Speed Physical Layer Problems Version 1.0 Application Note AN-ANI-1-115 Restrictions Public Document Abstract This application notes discusses three commonly encountered high speed CAN physical layer problems - bus termination, signal levels, and ground. Table of Contents 1 Overview ............................................................................................................................................................... 1 1.1 CAN Implementations ........................................................................................................................................ 1 2 Common High-Speed CAN Bus Physical Problems............................................................................................. 2 2.1 Bus Termination ................................................................................................................................................. 2 2.1.1 Termination Resistor Location......................................................................................................................... 3 2.1.2 Checking Termination Resistance................................................................................................................... 4 2.1.3 Tool-Related Termination Problems................................................................................................................ 4 2.2 CAN Bus DC and AC Voltages .......................................................................................................................... 5 2.2.1
    [Show full text]
  • Implementation of Controller Area Network (Can) Bus in an Autonomnous All-Terrain Vehicle
    IMPLEMENTATION OF CONTROLLER AREA NETWORK (CAN) BUS IN AN AUTONOMNOUS ALL-TERRAIN VEHICLE by Sunil Kumar Reddy Gurram A thesis submitted to the faculty of The University of North Carolina at Charlotte in partial fulfillment of the requirements for the degree of Master of Science in Electrical Engineering Charlotte 2011 Approved by: ______________________________ Dr. James M. Conrad ______________________________ Dr. Ronald Sass ______________________________ Dr. Yogendra Kakad ii ©2011 Sunil Kumar Reddy Gurram ALL RIGHTS RESERVED iii ABSTRACT SUNIL KUMAR REDDY GURRAM. Implementation of controller area network (CAN) bus in an autonomous all-terrain vehicle. (Under the direction of DR. JAMES M. CONRAD) The University of North Carolina Charlotte is provided with a Honda Four Trax Ranch ATV by Zapata Engineering (a small business firm located in Charlotte, NC) which is intended to tow a trailer of ground sensing equipment. The mechanical control system of the all-terrain vehicle (ATV) is converted to an electronic control system and is interfaced to a wireless radio system. The control system of the ATV is designed to run autonomously with the help of LIDAR, GPS and camera and can also be controlled over the wireless radio system. In order to improve the control system design and reduce the wiring, a Controller Area Network (CAN) control system has been implemented which is very flexible and reliable. A CAN control system contains electronic control units (ECU) which communicate over CAN protocol. CAN protocol is a serial communication protocol which is internationally standardized by ISO and it creates a two line differential bus for communication. It is a widely used real time communication protocol designed mainly for in vehicle networking but also gained popularity in many embedded applications.
    [Show full text]