Software Products

SAE J1939 Diagnostic Stack
Fault Manager software component

SAE J1939 Diagnostic stack

sae1.jpg
sae2.png
Specifications
  • Complete end-to-end ECU side stack comprising of
  • SAE J1939-21 Rev 2016-03: Data Link layer (includes Transport protocol)
  • SAE J1939-73 Rev 2017-05: Application Diagnostics (DM Services)
  • SAE J1939-81: Network Layer
Benefits
  • MISRA-C compliant.
  • Tested with Vector tool set (third party).
  • Tested under SIL (Software-In-Loop) environment.
  • DMx for Boot Block and Application – Total fourteen (14) DM services are supported.
  • Support for additional DM services will be given on need basis.
  • Lower foot print (depends on the MCU architecture)
  • Code size in order of 10KB to 15KB.
  • Data size in order of 1KB to 2KB.
  • Stack is portable on 8/16/32bit MCUs
Deliverables
  • Complete source code, Test plan & test report.
  • Integration support document.

SAE J1939 based Vehicle Programming

sae1.jpg
Features
  • Developed Bootloader on ECU side according to
  • SAE J1939 protocol standard
  • Developed Flash Programming Tool on PC side (C# .NET tech)
  • The Flash programming tool supports following hardware interfaces between PC & ECU
  • Vector CANCASE-XL
  • SCANUSB (Sloki’s proprietary hardware)
  • VCAN232 (proprietary CAN to RS232 hardware)

SAE J1939 Protocol Simulator

sae4.jpg
sae5.jpg
Features
  • PC based simulator to act as Vehicle ECU
  • Best suited to simulate J1939 messages for engine parameters
  • Can also generate DM1 (Diagnostic Message) to simulate Fault codes

UDS (ISO14229) Stack Solutions – Ready to Integrate with ECU Software

uds.png
Specifications
  • Complete end-to-end ECU side stack comprising of
  • ISO 14229 UDS stack for application diagnostics
  • ISO 15031-5 for EOBD – On Board Diag services
  • ISO 15765 – underneath network layer protocol support diagnostics over CAN
Benefits
  • Tested with Vector tool set (third party)
  • Tested under SIL (Software-In-Loop) environment
  • Tested OBD diagnostic services relevant for Diesel Engines.
  • Support for additional UDS/EOBD services will be given on need basis.
  • Lower foot print (depends on the MCU architecture).
  • Stack is portable on 8/16/32bit MCUs
  • CAPL scripts shall be provided along with stack for testing purpose.
Deliverables
  • Complete source code (MISRA-C compliant), Test plan & test report.
  • Integration support document.

UDS (ISO 14229) based Vehicle Programming Tool

uds2.png
Features
  • Developed Bootloader on ECU side according to
  • UDS ISO 14229 protocol standard
  • Developed Flash Programming Tool on PC side
  • Memory blocks are configurable using XML configuration file
  • The Flash programming tool supports following hardware interfaces between PC & ECU
  • Vector CANCASE-XL
  • SCANUSB (Sloki’ s proprietary hardware)
  • VCAN232 (proprietary CAN to RS232 hardware)
  • MQTT (Over the air updates)

ISO 14229 – UDS Services

UDS Services for BSW(Boot loader) Project
CAN driver initialisation and integration of 15765
14229 integration with network layer and implementing the scheduled processes
14229 SERV10(Start Diagnostic Section)
14229 SERV11(ECU Reset)
14229 SERV27(Security access)
14229 SERV31(Routine control)
14229 SERV34(Request download)
14229 SERV36(Transfer date)
14229 SERV37(Request Transfer Exit)
14229 SERV3E(Tester present)
14229 SERV83(Access timing parameters)
UDS Services for ASW(Application SW) Project
CAN driver initialisation and integration of 15765
CAN driver initialisation and integration of 15765
14229 integration with network layer and implementing the scheduled processes
14229 SERV10(Start Diagnostic Section)
14229 SERV11(ECU Reset)
14229 SERV27(Security access)
14229 SERV3E(Tester present)
14229 SERV83(Access timing parameters)
14229 SERV85(Control DTC settings)
14229 SERV86(Response on envent)
14229 SERV22(Read data by ID)
14229 SERV2E(Write data by ID)
14229 SERV19(Read DTC information)
14229 SERV14(Clear diagnostic information)
14229 SERV2F(I/O control by ID)
14229 SERV23(Read memory by address)
14229 SERV24(Read scaling data by ID)
14229 SERV2A(Read data by periodic ID)
14229 SERV2C(Dynamically defined data id)
14229 SERV3D(Write meomry by address)

Fault Management (OBD2, J1939 and UDS compliant)

software image
Features
  • Our FM stack is suitable for Engine Management System for OBD2 ISO-15031, SAE J1939 and UDS ISO-14229 protocol.
  • This will be modified to support for UDS requirements.
  • The FM would require around 50 bytes of NVM per faults.
  • Complete fault life cycle handling is taken care by the FM.
  • This stack is useful for supporting ISO 14229 UDS Service-14 and Service-19.
  • The FM handles different states of a fault, such as "POTENTIAL / ACTIVE", "CONFIRMED", "HEALING", "DELETING"...etc.