FieldbusAccess v.1.0.0

Transcription

1 FieldbusAccess v Release Notes

2 Contents Revision history...3 Glossary Brief Introduction Components LinX Fieldbus Access Configuration Tool Fieldbus Access Runtime Data Engine Library SocketCan Features New features One CAN controller Address claiming ECU naming Receive filter Transmission Modes On change Cyclic SAE J standard Library Updated features Coming features Multi CAN controllers Address list Transmission Modes Request message Scaling Large data messages ( > 8 data bytes ) Diagnostic CANopen Package (Installed files) LinX Fieldbus Access Configuration Tool /opt/qt-5.4.0/tools/qtcreator/lib/qtcreator/plugins/ Fieldbus Access Runtime /opt/bin Data Engine /opt/bin /opt/lib /opt/mtcc/include Library SocketCan /usr/local/lib Callback Object /home/ccs/qt/qtobserver ARM... Error! Bookmark not defined /opt/xa/lib /opt/xa/include... Error! Bookmark not defined /opt/xa/usr/bin /opt/xa/usr/lib... Error! Bookmark not defined.

3 Revision history Rev Date Author Comments Daniel N-G First Version Daniel N-G Updated for Pre Release Glossary Word/Abrevation CA CAN DE ECU FA RTE VM Explanation Controller Application Controller Area Network Data Engine Electronic Control Unit FieldbusAccess Runtime Environment Virtual Machine 1. Brief Introduction Fieldbus Access is a communication bridge containing the implementation of the most widely used vehicle fieldbuses (incl. J1939 and CANopen) and enables all other LinX Software Suite modules to use them with an easy-to-use interface. The Fieldbus Access UX configuration tool provides an easy interface to manage fieldbuses and which signals to use in your application. 2. Components 2.1. LinX Fieldbus Access Configuration Tool A QtCreator plugin, User Interface, managing the setup and configuration of CAN/DE Signals of the system. Aside from generating configuration files for fieldbus layer, this configuration tool can auto generate the communication layer between your Qt application and Data Engine, exposing your configured signals to QML and widgets with a single mouse click Fieldbus Access Runtime RTE running software of the most used fieldbuses such as J1939 and CANopen stack. The runtime is responsible of initialization and communication between CAN fieldbuses and LinX Software Suite modules such as Data Engine.

4 2.3. Data Engine Updated to version with support for unsigned datatypes. Unsigned char, unsigned short and unsigned integer is now supported. Added BLOB data type with BinaryArray with support for up to 4085 bytes Library SocketCan Application interface needed by the FA RTE for communication with the CAN bus. 3. Features 3.1. New features One CAN controller Support of one can controller interface Address claiming At initialization of FieldbusAccess an address claim of the preferred address is sent to the SAE J1939 network Address list List of arbitrary addresses for address claiming ECU naming Name (64 bit) on hex format Receive filter Filters are used to assure only relevant messages are received/accepted Transmission Modes On change Forward messages between DE and FA upon incoming message Cyclic Data of the message is transmitted/received cyclically. Intervals is configured by the configuration tool, either from standard library or by custom assigned value Scaling Utilize Gain and Offset parameters from PGN/SPN library. (Today only raw data is supported) Large data messages ( > 8 data bytes ) Default up to 8 bytes of data is supported. Larger data messages requires a Transport functionality protocol.

5 Diagnostic Support for DM1 and DM2 messages. Active and Previously Active Diagnostic Trouble Code Module SAE J standard Library Standard SAE J specification with PGN/SPN information needed by configuration tool Updated features 3.3. Coming features Multi CAN controllers Support for up to four CAN controllers configurable from the configuration tool Transmission Modes Request message The request message provides the capability to request data globally (from all CAs in the network) CANopen Support for transmission of CANopen messages. 4. Package Develop Environment The patch (Patch_fieldbusAccess_1.0.0_LinX_Software_Suite_Develop_Envionment_v2.0.2.run) consists of one.run file which self-extracts and installs needed files upon execution within the VM (LinX Software Suite Development Environment v2.0.2). The patch may be installed from any location/folder in the VM. Download patch to your development VM Add execution rights to the file. # chmod +x Patch_fieldbusAccess_1.0.0_LinX_Software_Suite_Develop_Envionment_v2.0.2.run If you are prompted to use a password, type default. Install package Patch_fieldbusAccess_1.0.0_LinX_Software_Suite_Develop_Envionment_v2.0.2.run 4.1. LinX Fieldbus Access Configuration Tool /opt/qt-5.4.0/tools/qtcreator/lib/qtcreator/plugins/ libpc_configtool.so LinX Configuration Tool (Qt-plugin)

6 4.2. Fieldbus Access Runtime /opt/bin fieldbusaccess_x86 New Fieldbus Access RTE FieldbusAccess_ConfigFile.json Default configuration file 4.3. Data Engine /opt/bin dataengineserverapp New DataEngine RTE /opt/lib libadmincore.so DE admin-interface library libsapcore.so DE user-interface library Links to libraries Additional soft links created /opt/mtcc/include admincore.h DE header files used for development PUIProtocol.h PUISignalString.h sapcore.h 4.4. Library SocketCan /usr/local/lib libsocketcan.so API to socketcan layer Links to library Additional soft links 4.5. Callback Object The callback object qtobserver is used by applications to received updated values from Data Engine. This observer class should be used by all new applications. Linked projects with the configuration tool will receive updated objects automatically /home/ccs/qt/qtobserver qtobserver.cpp Updated class needed by DE qtobserver.h Updated header needed by DE

7 5. Package - CCPilot Required files for develop and deployment of projects using Fieldbus Access and updated Data Engine v Files needed on target device ARM (CCpilot XA, XS, VC, VA) and x86 (CCpilot XM2) can be installed with runtime installation package LinX-Base_XX_device_2.1.0.run Download required packages to your development VM. Transfer device installation file to target (CCpilot) # scp LinX-Base_**_device_2.1.0.run root@<ipaddress>:/opt Login to target # ssh root@<ipaddress> Add execution rights to installation package # chmod +x /opt/linx-base_**_device_2.1.0.run Install package # /opt/linx-base_**_device_2.1.0.run Reboot the device # reboot /opt/lib libsocketcan.so API to socketcan layer Links to library Additional soft links libsapcore.so DataEngine User API libadmincore.so DataEngine Admin API /opt/bin fieldbusaccess New Fieldbus Access RTE o o Deplosy to /opt/bin on your ARM device Adds auto-start script in /opt/etc/init.d