I’m currently setting up this community forum to create a place where engineers, developers, and J1939 enthusiasts can ask questions, exchange ideas, share experiences, and discuss everything related to SAE J1939, embedded development, the JCOM1939 Monitor software, and the upcoming J1939 Development for Embedded Systems book.
The forum is still a work in progress, so please bear with me while I organize the discussion categories and add the initial content. This will take a little time, but my goal is to build a valuable technical resource where both beginners and experienced developers can find answers and contribute their own knowledge.
I invite you to check back regularly. Once everything is in place, I hope you’ll join the discussions, ask questions, share your projects, and help make this community a useful resource for everyone working with SAE J1939.
The Complete SAE J1939 Learning & Development Platform
Quote from Wilfried Voss on July 26, 2026, 3:40 pmWhy the SAE J1939 Starter Kit Is the Best Choice for Learning and Developing Embedded J1939 Systems
When engineers first enter the world of SAE J1939, they often ask a simple question:
Should I start with a single J1939 gateway or buy the complete Starter Kit?
While the SAE J1939 ECU Simulator Board with USB Port is an excellent interface for monitoring and simulating J1939 traffic, the SAE J1939 Starter Kit and Network Simulator provides something far more valuable:
A complete, self-contained J1939 network.
That difference fundamentally changes how quickly you can learn the protocol, develop embedded software, and troubleshoot applications.
The Biggest Challenge for Every Beginner
Unlike many serial communication protocols, SAE J1939 was never designed to operate with a single device.
A J1939 network is exactly that—a network consisting of multiple Electronic Control Units (ECUs).
Many protocol functions only occur when multiple nodes interact:
- Address claiming
- Request messages
- PGN responses
- Transport Protocol transfers
- Network management
- Arbitration
- Error handling
A single ECU simply cannot demonstrate these interactions.
This is why many beginners become frustrated after purchasing only a CAN interface. They quickly discover that they still need another node capable of generating realistic J1939 traffic.
The Starter Kit solves this problem immediately by including two fully functional J1939 nodes, allowing users to create a complete laboratory network without requiring a diesel engine or vehicle.
Understanding What the Starter Kit Really Is
Many people assume the Starter Kit is simply "two USB adapters."
It is much more than that.
Each gateway implements the complete J1939 protocol in hardware, including:
- SAE J1939/21 Data Link Layer
- SAE J1939/81 Network Management
- Address Claiming
- Transport Protocol (BAM and RTS/CTS)
- PGN transmission
- PGN reception
- Request handling
- Message filtering
- Node address configuration
When connected together, the two gateways immediately become a functioning J1939 network that behaves much like two ECUs inside a vehicle.
Why Two Nodes Matter
A CAN controller expects acknowledgements from another node.
Without another active device on the network, communication quickly breaks down.
More importantly, many J1939 features simply cannot be demonstrated with one ECU.
For example:
Address Claim Procedure
One node claims an address.
The second node acknowledges the message.
Now try changing both nodes to the same preferred address.
You can immediately observe:
- Address conflicts
- NAME comparison
- Automatic address negotiation
- Successful or failed claims
Instead of reading about the protocol, you can actually watch it happen.
Request Messages
One node sends a Request PGN.
The second node responds automatically.
This demonstrates one of the most common communication patterns found in real vehicles.
Transport Protocol
Large messages exceeding eight bytes require the Transport Protocol.
With two nodes you can observe:
- BAM transfers
- RTS/CTS transfers
- Packet sequencing
- End-of-message handling
These features are impossible to study with a single isolated ECU.
Continuous Network Activity
Real vehicles continuously exchange PGNs.
With the Starter Kit you can create exactly that environment.
You can:
- simulate engine data
- generate vehicle speed
- transmit coolant temperature
- create diagnostic traffic
- build custom PGNs
- observe arbitration
Everything happens in real time without requiring an actual engine.
Why This Matters for Embedded Development
Suppose you are writing firmware for:
- ESP32
- Arduino
- Teensy
- STM32
- Raspberry Pi
- Linux embedded systems
Eventually your software needs to communicate with another ECU.
Without a realistic network, software development becomes guesswork.
Developers often end up asking:
"Did my software fail?"
or
"Is there simply nobody answering?"
The Starter Kit eliminates that uncertainty.
Your embedded system can immediately communicate with a known-good J1939 node.
You can test:
- PGN transmission
- Request handling
- Address claiming
- Transport Protocol
- Timing
- Error recovery
Because the network itself is under your control, debugging becomes dramatically easier.
Faster Learning
Many engineers begin by reading the J1939 standards.
While the standards are essential references, they are not tutorials.
The fastest learning usually follows this pattern:
- transmit a PGN
- watch the data appear
- modify a value
- transmit again
- observe the result
Within minutes, abstract protocol descriptions suddenly make sense.
Learning becomes interactive instead of theoretical.
Ideal for the JCOM1939 Monitor Software
The Starter Kit was designed specifically to work with two instances of the JCOM1939 Monitor software.
One instance may represent an engine ECU.
The second may represent a transmission ECU.
You can watch messages flowing between both systems while simultaneously:
- recording traffic
- modifying PGNs
- responding to requests
- scanning the network
- simulating ECUs
The result is a complete laboratory environment running entirely on your desktop.
When Is a Single ECU Simulator the Better Choice?
The SAE J1939 ECU Simulator Board with USB Port remains an excellent product.
It is usually the better choice when:
- you already have access to a vehicle
- you are connecting to an existing J1939 network
- you need only one gateway
- you are integrating J1939 into an embedded controller
- you need a compact USB-to-J1939 interface
For experienced developers working with existing equipment, a single gateway is often all that is required.
Why Beginners Should Start with the Starter Kit
If you are new to J1939, the Starter Kit offers several advantages:
- No vehicle required
- No engine simulator required
- Complete J1939 laboratory
- Immediate network communication
- Demonstrates real protocol behavior
- Excellent platform for experimentation
- Ideal companion for learning the protocol
- Excellent environment for embedded software development
Perhaps most importantly, you avoid spending valuable time wondering whether a problem is caused by your own software or simply by the absence of another network node.
Beyond Learning
Many users purchase the Starter Kit to learn J1939.
Later, they continue using it throughout development.
Typical uses include:
- firmware debugging
- regression testing
- software demonstrations
- classroom instruction
- customer support
- hardware validation
- protocol experimentation
Because the network is completely under your control, it becomes an indispensable engineering tool rather than just a training product.
Conclusion
The SAE J1939 ECU Simulator Board with USB Port is an excellent USB-to-J1939 gateway for connecting to existing vehicle networks or integrating J1939 into your own projects.
The SAE J1939 Starter Kit, however, offers something fundamentally different: a complete, working SAE J1939 network.
That single distinction makes it the ideal choice not only for beginners learning the protocol but also for professional engineers developing embedded J1939 applications. Instead of relying on an available vehicle or engine controller, you gain a controlled laboratory where every aspect of the protocol—from address claiming and request messages to transport protocol transfers and ECU simulation—can be explored, tested, and debugged at your own pace.
For anyone serious about understanding or developing SAE J1939 systems, starting with a complete network is not merely more convenient—it is the most efficient path to becoming productive.
Additional Resources
- SAE J1939 Starter Kit and Network Simulator
https://jcom1939.com/jcom1939-gateways/sae-j1939-starter-kit-and-network-simulator/ (JCOM1939 Monitor Pro)- SAE J1939 ECU Simulator Board with USB Port
https://jcom1939.com/jcom1939-gateways/sae-j1939-ecu-simulator-board-with-usb-port/ (JCOM1939 Monitor Pro)- SAE J1939 Starter Kit – Quick Start Guide (PDF)
https://jcom1939.com/wp-content/uploads/2024/04/SAE-J1939-Starter-Kit-And-Network-Simulator.pdf(JCOM1939 Monitor Pro)- JCOM1939 Monitor Software
https://jcom1939.com/ (JCOM1939 Monitor Pro)- JCOM1939 Gateways & Cables
https://jcom1939.com/jcom1939-gateways/ (JCOM1939 Monitor Pro)- Video: JCOM1939 Monitor Pro – Introduction
https://jcom1939.com/video-jcom1939-monitor-pro-introduction/ (JCOM1939 Monitor Pro)- SAE J1939 Starter Kit Simulates Diesel Engine and Demonstrates VIN Request
https://jcom1939.com/sae-j1939-starter-kit-simulates-diesel-engine-and-demonstrates-vin-request/ (JCOM1939 Monitor Pro)
Why the SAE J1939 Starter Kit Is the Best Choice for Learning and Developing Embedded J1939 Systems
When engineers first enter the world of SAE J1939, they often ask a simple question:
Should I start with a single J1939 gateway or buy the complete Starter Kit?
While the SAE J1939 ECU Simulator Board with USB Port is an excellent interface for monitoring and simulating J1939 traffic, the SAE J1939 Starter Kit and Network Simulator provides something far more valuable:
A complete, self-contained J1939 network.
That difference fundamentally changes how quickly you can learn the protocol, develop embedded software, and troubleshoot applications.
The Biggest Challenge for Every Beginner
Unlike many serial communication protocols, SAE J1939 was never designed to operate with a single device.
A J1939 network is exactly that—a network consisting of multiple Electronic Control Units (ECUs).
Many protocol functions only occur when multiple nodes interact:
- Address claiming
- Request messages
- PGN responses
- Transport Protocol transfers
- Network management
- Arbitration
- Error handling
A single ECU simply cannot demonstrate these interactions.
This is why many beginners become frustrated after purchasing only a CAN interface. They quickly discover that they still need another node capable of generating realistic J1939 traffic.
The Starter Kit solves this problem immediately by including two fully functional J1939 nodes, allowing users to create a complete laboratory network without requiring a diesel engine or vehicle.
Understanding What the Starter Kit Really Is
Many people assume the Starter Kit is simply "two USB adapters."
It is much more than that.
Each gateway implements the complete J1939 protocol in hardware, including:
- SAE J1939/21 Data Link Layer
- SAE J1939/81 Network Management
- Address Claiming
- Transport Protocol (BAM and RTS/CTS)
- PGN transmission
- PGN reception
- Request handling
- Message filtering
- Node address configuration
When connected together, the two gateways immediately become a functioning J1939 network that behaves much like two ECUs inside a vehicle.
Why Two Nodes Matter
A CAN controller expects acknowledgements from another node.
Without another active device on the network, communication quickly breaks down.
More importantly, many J1939 features simply cannot be demonstrated with one ECU.
For example:
Address Claim Procedure
One node claims an address.
The second node acknowledges the message.
Now try changing both nodes to the same preferred address.
You can immediately observe:
- Address conflicts
- NAME comparison
- Automatic address negotiation
- Successful or failed claims
Instead of reading about the protocol, you can actually watch it happen.
Request Messages
One node sends a Request PGN.
The second node responds automatically.
This demonstrates one of the most common communication patterns found in real vehicles.
Transport Protocol
Large messages exceeding eight bytes require the Transport Protocol.
With two nodes you can observe:
- BAM transfers
- RTS/CTS transfers
- Packet sequencing
- End-of-message handling
These features are impossible to study with a single isolated ECU.
Continuous Network Activity
Real vehicles continuously exchange PGNs.
With the Starter Kit you can create exactly that environment.
You can:
- simulate engine data
- generate vehicle speed
- transmit coolant temperature
- create diagnostic traffic
- build custom PGNs
- observe arbitration
Everything happens in real time without requiring an actual engine.
Why This Matters for Embedded Development
Suppose you are writing firmware for:
- ESP32
- Arduino
- Teensy
- STM32
- Raspberry Pi
- Linux embedded systems
Eventually your software needs to communicate with another ECU.
Without a realistic network, software development becomes guesswork.
Developers often end up asking:
"Did my software fail?"
or
"Is there simply nobody answering?"
The Starter Kit eliminates that uncertainty.
Your embedded system can immediately communicate with a known-good J1939 node.
You can test:
- PGN transmission
- Request handling
- Address claiming
- Transport Protocol
- Timing
- Error recovery
Because the network itself is under your control, debugging becomes dramatically easier.
Faster Learning
Many engineers begin by reading the J1939 standards.
While the standards are essential references, they are not tutorials.
The fastest learning usually follows this pattern:
- transmit a PGN
- watch the data appear
- modify a value
- transmit again
- observe the result
Within minutes, abstract protocol descriptions suddenly make sense.
Learning becomes interactive instead of theoretical.
Ideal for the JCOM1939 Monitor Software
The Starter Kit was designed specifically to work with two instances of the JCOM1939 Monitor software.
One instance may represent an engine ECU.
The second may represent a transmission ECU.
You can watch messages flowing between both systems while simultaneously:
- recording traffic
- modifying PGNs
- responding to requests
- scanning the network
- simulating ECUs
The result is a complete laboratory environment running entirely on your desktop.
When Is a Single ECU Simulator the Better Choice?
The SAE J1939 ECU Simulator Board with USB Port remains an excellent product.
It is usually the better choice when:
- you already have access to a vehicle
- you are connecting to an existing J1939 network
- you need only one gateway
- you are integrating J1939 into an embedded controller
- you need a compact USB-to-J1939 interface
For experienced developers working with existing equipment, a single gateway is often all that is required.
Why Beginners Should Start with the Starter Kit
If you are new to J1939, the Starter Kit offers several advantages:
- No vehicle required
- No engine simulator required
- Complete J1939 laboratory
- Immediate network communication
- Demonstrates real protocol behavior
- Excellent platform for experimentation
- Ideal companion for learning the protocol
- Excellent environment for embedded software development
Perhaps most importantly, you avoid spending valuable time wondering whether a problem is caused by your own software or simply by the absence of another network node.
Beyond Learning
Many users purchase the Starter Kit to learn J1939.
Later, they continue using it throughout development.
Typical uses include:
- firmware debugging
- regression testing
- software demonstrations
- classroom instruction
- customer support
- hardware validation
- protocol experimentation
Because the network is completely under your control, it becomes an indispensable engineering tool rather than just a training product.
Conclusion
The SAE J1939 ECU Simulator Board with USB Port is an excellent USB-to-J1939 gateway for connecting to existing vehicle networks or integrating J1939 into your own projects.
The SAE J1939 Starter Kit, however, offers something fundamentally different: a complete, working SAE J1939 network.
That single distinction makes it the ideal choice not only for beginners learning the protocol but also for professional engineers developing embedded J1939 applications. Instead of relying on an available vehicle or engine controller, you gain a controlled laboratory where every aspect of the protocol—from address claiming and request messages to transport protocol transfers and ECU simulation—can be explored, tested, and debugged at your own pace.
For anyone serious about understanding or developing SAE J1939 systems, starting with a complete network is not merely more convenient—it is the most efficient path to becoming productive.
Additional Resources
- SAE J1939 Starter Kit and Network Simulator
https://jcom1939.com/jcom1939-gateways/sae-j1939-starter-kit-and-network-simulator/ (JCOM1939 Monitor Pro) - SAE J1939 ECU Simulator Board with USB Port
https://jcom1939.com/jcom1939-gateways/sae-j1939-ecu-simulator-board-with-usb-port/ (JCOM1939 Monitor Pro) - SAE J1939 Starter Kit – Quick Start Guide (PDF)
https://jcom1939.com/wp-content/uploads/2024/04/SAE-J1939-Starter-Kit-And-Network-Simulator.pdf(JCOM1939 Monitor Pro) - JCOM1939 Monitor Software
https://jcom1939.com/ (JCOM1939 Monitor Pro) - JCOM1939 Gateways & Cables
https://jcom1939.com/jcom1939-gateways/ (JCOM1939 Monitor Pro) - Video: JCOM1939 Monitor Pro – Introduction
https://jcom1939.com/video-jcom1939-monitor-pro-introduction/ (JCOM1939 Monitor Pro) - SAE J1939 Starter Kit Simulates Diesel Engine and Demonstrates VIN Request
https://jcom1939.com/sae-j1939-starter-kit-simulates-diesel-engine-and-demonstrates-vin-request/ (JCOM1939 Monitor Pro)

