MoTeC Global Forum

I hope all is well with everyone.

I am on the hunt for any insight or direction to documentation that may lead me to resolve the issue on hand. Sections below include: issue on hand, hardware on hand, and troubleshooting performed.

ISSUE:
I am unable to transmit CAN-BUS messages from a C185. (End goal of transmitting messages to a Racelogic VBOX Lite)

HARDWARE:
-C185 & Loom (Advanced math, pro analysis, display creator options)
-Phytools PCAN View
-CAN-BUS sensors for test purposes
-Racelogic VBOX Lite

TROUBLESHOOTING PERFORMED:
-Verified C185 & PCAN interface loom quality
-Verified C185 CAN-BUS communication by receiving messages successfully from CAN BUS sensors
-Verified PCAN operation by receiving CAN-BUS data transmitted between a sensor to the C185
-Listened (no data found) for C185 CAN BUS transmitted messages using another C185 CAN BUS line(used CAN Inspector) and PCAN View. (repeated process for message types "single" and "compound"
-Trialed using "v2_transmit_0x01F_Version 1" CAN-BUS comms template that was included in dash-manager install files
-Trialed using CAN BUS transmit template made from scratch.
-Verified Baud rate and base address settings while using CAN Inspector and PCAN View
-Searched through forums, webinars, user manuals, dash manager help documents, Motec Documents DTN0019, CTN0015 "Communications and Setup"/"Motec CAN Addresses"

I have attached my CAN-BUS transmit comms setup template made from scratch just in case I am having an off week and doing something odd.

Sincerely,

Jeremiah Wennermark
Man & Machine Consulting

Hi,

Having a look at the template that you attached, there doesn't appear to be an issue with how it is configured as far
as how the channels are setup.

I would add a diagnostic channel into the template and then look in Monitor Channels to see if there is an error reported by the diagnostic.

The template is fine (it works in a unit on my desk). Couple of things to check:

When you are testing the receive is there another node on the bus other than the PCAN? If the PCAN is the only other device make sure that it is set to acknowledge messages and not just listen. If another device doesn't set the acknowledge bit the Dash will not transmit messages. Typically all CAN devices will set the acknowledge bit when a message is received, however CAN sniffers will normally let the user decide whether it sets the bit or not. This allows you to read a CAN bus silently without any other device knowing it is there.

Make sure that there is at least 1 terminating resistor on the bus.

Racelogic VBOX need other device in same CAN bus to work.

adrian wrote:The template is fine (it works in a unit on my desk). Couple of things to check:

When you are testing the receive is there another node on the bus other than the PCAN? If the PCAN is the only other device make sure that it is set to acknowledge messages and not just listen. If another device doesn't set the acknowledge bit the Dash will not transmit messages. Typically all CAN devices will set the acknowledge bit when a message is received, however CAN sniffers will normally let the user decide whether it sets the bit or not. This allows you to read a CAN bus silently without any other device knowing it is there.

Make sure that there is at least 1 terminating resistor on the bus.

Adrian, you hit the nail on the head. The "set acknowledge message" was deselected. After selecting that I still had intermittent comms issues which I then tracked down a break in 1 of the terminating resistors that would open depending on the position of the harness. After repairing the resistor the PCAN received messages as expected. Thanks!

Mika wrote:Racelogic VBOX need other device in same CAN bus to work.

Mika thanks for the input. Is an additional deviced needed on bus due to the fact that the VBOX will not transmit an acknowledged message or is something else in play?