Mecel Picea Mecel Betula Mecel Populus

 

Autolan SDK

The Autosoft - Autolan SDK gives the application developer a set of components that provide the basic communication mechanisms needed when one or more CAN-systems are connected to the ECU. By providing tools for configuration, adaptation and verification, the customer has full support through the different development stages.

CAN communication has existed in the automotive and commercial vehicle world since 1985. Mecel has been involved in both specification and software development work since the start. The experience gained over the years has been captured and formalised into the Autosoft - Autolan SDK.

 

Autolan SDK Overview

 

TECHNICAL SPECIFICATION

Autosoft - Autolan consists of the following software components:

  • CAN Data Link Layer
  • Network/Transport Protocol
  • Signal Interaction Layer
  • Network Management

 

CAN Data Link Layer

This component serves two purposes where the first is to provide optimal code for the specific CAN controller used in the ECU. The second is to provide a standardized interface for the common services needed for other software components. This includes:

  • Initialization of CAN controller
  • Reception of CAN messages
  • Provide Message Filtering
  • Transmission of CAN messages
  • Wake-up functionality
  • Error handling

Our DLL component has been integrated into several CAN-controllers and C-compiler combinations. To get the latest list of implementations, send us a request via Contact information. We are continuously updating our list of supported CAN-controllers and c-compilers. New CAN-controllers and/or c-compiler combinations can also be supported via our engineering services provided.

Network/Transport Protocol

The Transport Protocol component provides the ability to send and receive segmented messages according to the ISO 15765-2 specification. Typical usage of this is diagnostic communication services or other protocols where message length exceeds the CAN data frame size, i.e. 8 bytes. Autolan supports multi-channel transport service.

Signal Interaction Layer

The Signal Interaction Layer is the abstraction layer between application and low-level CAN communication services. By this the application software will typically use engineering units e.g. Engine Speed instead of managing CAN frames.

The Signal Interaction Layer in Autolan handles the mapping of signals into CAN frames as well as the distribution of the CAN frames. The definition of the signals and corresponding CAN frame are stored in a MessageMap and code is configured using Autolan Configuration Tool.

Network Management

Autolan Network Management is using the master-slave paradigm and ensures a controlled start-up and shutdown of the CAN Network communication. This includes bus wake-up, supervision of the ECU´s communication and controls CAN re-initializations in case a bus communication failure is detected.

FEATURES
Components are configurable self-contained units. They are exchangeable to simplify integration with customer code-base/requirements.

  • Multi-instance support of components
  • Software CAN filtering support
  • Support for automatic code generation
  • Adhere to MISRA/C rules&recommendations
  • Robust
  • Resource Efficient
  • Flexible, easy to adapt to HW/SW platforms

 

DELIVERABLES

  • Source Code
  • User manual
  • Autolan Configuration Tool
  • Autolan Integration Verification Tool
  • Sample programs

Optional Deliverables

  • Autolan Specification Tool
  • Gateway Applications (CAN-CAN, CAN-Bluetooth, CAN-MOST)
  • SNAP - Serial Number Arbitration Protocol
  • GMLAN Communication Protocol
  • J1939 Protocol Layers
  • CCP - CAN Calibration Protocol

 

SUPPLEMENTAL SERVICES

  • SW integration & configuration services
  • CAN Communication expert consultation