memphis242 / can_node_board

Board design, software, and tooling for PIC18 MCU-based boards to send/receive J1939 messages over CAN 2.0B for general purpose use.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

can_node_board

Summary

A board to send J1939 messages to wheel loader controllers over CAN (2.0B Extended Frame) for testing purposes using the MCP2515 CAN Controller + MCP2562 CAN Transceiver + PIC18F4620 microcontroller. This can probably also just be used in general for sending CAN messages, but you would need to edit the code as needed for your purposes. A visual demonstration of this board's operation is given in this link:

What Problem This Solves

I intend to integrate this board with a test bench I built at work for a particular controller, along with any necessary switches/knobs, in order to make it more intuititve to test and have everything together as a "package". The test bench tests the controller outside of the machine it would normally be in, so when it is turned on, if it doesn't receive certain messages over CAN (e.g., from the engine controller(s) and transmission controller), then it throws errors and this prevents the controller from being fully tested. I have set up CANalyzer to fulfill this purpose at work, but I thought that having a separate board that I would just put on the test bench would make the testing process more efficient than having to look for an available Vector Bus module and setting up CANalyzer.

NOTE! The actual specific J1939 messages I am sending wil NOT be pushed onto this remote directory, for obvious purposes! However, example J1939 messages from the SAE J1939-71 standard document are included for demonstration purposes.

Structure of This Repo and How To Build

For the code, the directory structure is a pretty standard one, with a main project directory "can_node_board_SW.X", an include directory ("./inc") for the header files, and a source directory ("./src") for the .c files that correspond to the header files. Within the main project directory is the main.c file, along with some test source and header files that I used in the process of developing and testing my code.

The "can_node_board_SW.X" folder has the '.X' extension because this project was done on the MPLAB X IDE. If you download this repo, you can open this project on MPLAB X by selecting this "CAN WL SIM.X" folder. In addition, note that the #include statements made within the various files will work only if you add the "inc" subdirectory under Project Properties > XC8 Compiler > Include Directories > (add the "inc" relative path -- you can use the Browse button). With all that, you should be able to build the project just fine with default XC8 options within MPLAB X.

MPLAB X IDE version: v5.45
XC8 C Compiler version: v2.31

For the hardware, that will be under the "hardware" directory and is where I have the KiCAD files for any relevant schematics, part libraries, and PCB-related files.

Hardware Used

The choice of microcontroller - PIC18F4620 - was because I wanted to use the same microcontroller that I was using for my embedded systems class, which also satisfied my requirements for number of I/O. This microcontroller does not have an integrated CAN controller, so I chose the MCP2515 CAN Controller IC from Microchip. Note, they did have a newer version of the IC - the MCP2518 - but that wasn't available as of October 2021 due to the worldwide chip shortage... Likewise, the MCP2562 CAN Transceiver was selected based on availability and desired package.

Motivation & Reasoning

I wanted to get more in detail with the various layers that make up a CAN node, and thought this was a great opportunity for that.

What Makes This Project Unique

I have not exhaustively searched for similar projects, but I am sure there are plenty. The references section shows two Microchip application notes of boards built using a similar set up to me and programmed in assembly. I have seen some colleagues use a Raspberry Pi + CAN Hat and run some python scripts to replay CAN traces. However, what makes this project unique to me is that it a) uses an 8-bit microcontroller, b) is a project that involves me developing/testing everything myself from the code to the circuit, c) does not utilize ready-made solutions, d) is also meant to send J1939 messages, not just generic CAN messages, and e) is a project that solves my particular problem.

References

Microchip Application Note AN215
Microchip Application Note AN212
CAN Controller MCP2515 Product Page
CAN Transceiver MCP2562 Product Page
Microcontroller PIC18F4620 Product Page
Several application notes from Microchip and TI for explaining CAN and J1939
I also had access to the SAE J1939 standard documents

About

Board design, software, and tooling for PIC18 MCU-based boards to send/receive J1939 messages over CAN 2.0B for general purpose use.


Languages

Language:SWIG 77.1%Language:C 20.0%Language:Makefile 2.8%Language:Shell 0.1%Language:Assembly 0.0%