J1939/CAN Bus limit on PID's that can be monitored

Firmware
,
1

Hello Everyone! First post here on the forums.

Is there a limit on how many CAN PID's that can be monitored, recorded, or transmitted remotely?

The hardware in question is the tracker , monitor-one , and the new Tachyon.

I had previously done some work with the Boron and a CAN to SPI module and had good success with it. However, I was only using ~2-4 messages. I am now wondering how any of the listed products would perform as a engine monitoring setup and be able to push out ~100 different types of commands via CAN/J1939.

Thanks in advance,
Zach

2

The Tracker One and Monitor One have a MCP25625 SPI CAN controller, which is basically the same as the MCP2515 but has an integrated PHY. There's no limitation on the number of messages you can send as they're just raw bytes being sent. If you are using hardware filtering, there are chip limits for the number of filters. The CAN library is a very thin layer on top of the chip, and it's open source so you can modify it if necessary.

The Tachyon doesn't have a CAN interface, but you could connect a CAN controller by SPI. There are a number of hats available that support CAN that may be compatible with Tachyon. Another advantage of this is that there are full libraries such as CANOpen available for the Raspberry Pi that should be easily ported to Tachyon.

3

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.