Business Model for J1939 Stack Solution
We offer this industry-wide proven and stable SAE J1939 software solution under a one-time licensing fee model.
In this business model, you (as the customer) own the IP rights and the source code of the software stack. This enables you to integrate the J1939 stack across multiple projects and/or product lines.
Our SAE J1939 Protocol Stack, for commercial vehicles, has been designed as a low power & memory footprints solution. This ready-to-deploy J1939 Protocol Stack comprises of configurable J1939 PGN and SPN list
J1939 Stack Integration, Configuration and Testing Services
J1939 Datalink + Transport layer (J1939/21) and Network Management layer (J1939/81) are pre-tested and pre-packaged as per the SAE J1939 protocol standard. These layers are ‘re-usable’ for any automotive ECU and/or automotive tooling applications
 |
End-user Application analysis
|
 |
J1939/73 diagnostics layer services
|
 |
J1939/71 application layer services
|
 |
J1939-82 conformance testing services
|
 |
J1939 bootloader development services
|
 |
J1939 diagnostic tester
|
Meet Our Automotive Leaders
SAE J1939 Software Stack Factsheet:
This is a quick-reference guide to know all the details about our J1939 solution for commercial and light passenger vehicles.
Download this J1939 PDF to get following information:
- J1939 license fee, engagement model and overview
- Benefits of IP rights and access to J1939 source code
- J1939 software features, OS compatibility, memory requirements
- J1939 protocol stack integration, testing and maintenance services (pre and post production)
Refer to the J1939 FAQ sections for more details.
Ans. J1939 protocol is a standard (set of embedded software specifications) defined by SAE (Society of Automotive Engineers). The SAE J1939 protocol specifications are defined for CAN bus, and J1939 stack is an embedded software code with layered architecture and is compliant with J1939 standard.
The J1939 protocol stack is best suited for automotive ECU and tooling applications in commercial vehicles.
Ans. Our J1939 software stack consists of validated and verified software layer services.
Following are the software specifications of the included layers:
| ISO-OSI model layer | Embedded software specification |
|---|---|
| Data link / Transport Layer | J1939/21 |
| Network Management Layer | J1939/81 |
| Diagnostics Layer | J1939/73 |
| Application Layer | J1939/71 and 73 |
Ans. As part of the SLA, our software team will work closely with your team to analyze the end-user application.
Based on your business requirement, we provide customization and integration of the J1939 stack with your hardware platform and software application.
To summarize, we will partner with your team to deliver following services along with the stack:
- Integration of the J1939 stack to your hardware platform
- Integration of J1939 solution with target application
- Development of bootloader software based on J1939 standard
- Development of driver modules like CAN, UART and more
- Verification &validation (testing services)of your target application after integration
Ans. The modules that support the bootloader functionality are already included in the software stack. We also provide additional integration support for ECU reprogramming.
This includes segregating the memory as boot and application area, implementing boot loader logic in both boot and application, CRC checks, Flash driver and more.
Ans. No, our J1939 software solution is hardware independent. We also provide CAN drivers as a part of software package. These are designed to ensure hardware abstraction.
Ans. The J1939 software stack is complaint with ISO J1939 standard. The software source code is developed using embedded C in compliance with MISRA-C standard.
At an organization level, we also follow all the software development best practices as per CMMI level 3 standards.
Q7. Have you integrated the J1939 protocol software stack solution before for any of your customers?
Ans. We have more than 10 years of experience and domain expertise in partnering with global automotive OEMs’ and Suppliers
We have a team of expert automotive software engineers, who have delivered key solutions for integration, end-of-line testing and support for the implementation J1939 protocol software stack across multiple platforms
Ans. We have a well-defined support and maintenance process for your post-production requirements.
As per your project requirements and partnership expectations, post-production support will be part of the SLA at the onset of the J1939 stack integration project
Ans. Our business module enables one-time licensing which provides the customer with IP rights and source code for the software stack.
The IP rights help your business to reuse the software code across multiple projects.
However the business model can be re-framed according to the business needs of the customer and project specifications.
J1939 Customer Success Stories:
Advanced EPS system – Code optimization, J1939 Stack Integration, Onsite Support and In-Vehicle Testing
- Business Challenge – Our customer (Automotive Tier-I Supplier of steering and driveline components) encountered a major roadblock during software porting.Due to limited on-chip memory (RAM and ROM) of DsPIC 30F4011 platform, it became imperative for the customer to port highly-optimized embedded software to the EPS system.
- Embitel Solution – After several engineering workshops with the customer for understanding and analyzing the EPS system, Team Embitel was able to overcome the hurdle with the help of following solution:
- A light-weight and re-usable SAE J1939 compliant stack best suited for commercial vehicles was integrated with the system
- The entire code was optimized around J1939 stack and since the stack has layered architecture, the optimized software was successfully ported thus overcoming the memory issue
For more details, please refer to the J1939 stack integration with EPS
Android based Infotainment system – J1939 stack integration for ECU communication and vehicle data collection
- Business Challenge – Infotainment application communicates with several ECUs to fetch various vehicle parameters. Embitel’s infotainment software development team needed an off-the-shelf communication layer that can be configured easily. This would ensure reduced development time and add value to the bottom-line of the project costs.
- Embitel Solution – The team decided to integrate the J1939 stack, designed in-house for CAN communication, to save time and costs. Hence our cross-functional expertise in Embedded and Automotive technology added value to our client’s product roadmap.
For more details, please refer to the J1939 stack integration with Infotainment system
Related Posts : Learn More About SAE J1939 Software Stack
- What is J1939 software stack? Learn about the layered architecture and diagnostic trouble codes (DTC)
- How to Integrate J1939 Software Stack with an Automotive ECU: A Step-by-Step Tutorial
- What is ELD Mandate and its Dec 2017 Deadline for the Fleet Management Companies in USA
- ELD Implementation for fleets in US: Learn About the System Design & J1939/OBD2 Stack Integration
- How to Test Quality of J1939 Software Source Code
- What is J1939/21 Transport Protocol? Learn How It Supports More Than 8 Bytes Data Over CAN
J1939 Stack – Details of the Layered Architecture
We have designed and developed a J1939 stack, that can be integrated with your automotive ECU and/or tooling applications, to fast-track your product development process.
The J1939 stack is implemented in ANSI-C and is independent of the CAN controller, CPU and operating system.
The layered architecture consists of:
| ISO-OSI model layer | Embedded software specification |
|---|---|
| Data link/Transport Layer | J1939/21 |
| Network Management Layer | J1939/81 |
| Diagnostics Layer | J1939/73 |
| Application Layer | J1939/71 and 73 |
Features of the Reusable J1939 Stack:
- enables in-vehicle network communications (ECU communications)
- supports vehicle diagnostics services and fault-code memory
- J1939 bootloader supports in-vehicle ECU reprogramming
- The embedded software code of the Stack is MISRA-C complaint.
Why Partner with us for J1939 Stack Integration Project:
- Leverage our automotive domain expertise and project experience in J1939 integration to reduce time-to-market and application development costs
- We are a CMMi Level 3 and ISO 9001:2008 & ISO 27001:2013 certified organization
- Robust project management processes based on EmbiQ – an engagement model. This model is built on three critical pillars – People, Process and Technology
