MoTeC Global Forum

I'm trying to learn more about the VCS capabilities of my M150. When I enable it via Tune, I immediately get a CAN Bus Timeout Diagnostic. That tells me the M150 is looking for a particular message or data on the CAN bus, but I haven't been able to figure out what. My video recorder is a VBOX HD2, and I've not been able to have it send whatever the M150 wants.

Everything I find on the subject is usually related to C-series dashes -- but this VCS capability in the M1 must do something?

Anybody know?

Many thanks!

Hi John,

The VCS component of the VCS transmit is designed for data back from MoTeC Camera systems (HD VCS and V2), not from VBox. The messaging received from the HD2 is different and not supported by the VCS Can bus in the M1.

Hi Nathan,

Thank you very much for your answer. Is the VCS protocol published anywhere? I've found the CAN output message format that the MoTeC VCS sends (page 28 of the VCS manual), but I can't find the M1 side.

Hello,

Do you have any other CAN devices connected to the same bus?

Mika

Do you have any other CAN devices connected to the same bus?

I do: an ECUMaster PMU, and an AiM MXS along with the M150 and VBOX HD2. Why do you ask?

Hi
Normally VBOX HD2 only listens on the CANBUS bus and you need two active devices to start the bus.

Mika

Yes, the CAN bus is successfully transferring data from the M1. I can see the 118-120 messages, the 640-652 messages, etc. The VBOX is putting M1 data in its video, etc. All that works fine.

Except that the M1 is raising a VCS exception. According to VBOX this should work:

https://www.youtube.com/watch?v=cn1ZF3p6NCs&t=11s

If I could get VCS protocol documentation, I'm sure I can set up my ECUMaster PMU to provide whatever missing details the M1 and VBOX need to get along.

Are you sending the message described in the VCS manual pg 28 to extended ID (29 bit addressing) 0x0000020 at 1hz. Do you see that message on the CAN bus?

Of course, having the M1 receive status data just to fill in some channels isn't really required, and you can just ignore the CAN Timeout error since you are getting the expected data on the VBOX.

No, not yet, as I didn't know the base id to send it to. I'll give that a try today, and see if:
1. The M1 quits raising the diagnostic, and
2. It responds with useful data that the VBOX can imbed in the video for i2's use in syncing.

thanks!

Looking at the templates (V2_receive_0x01D_Version 1 and VCS Transmit Compound Full) in a Dash Manager, looks like the VCS V2 sends data Dash/ECU to 11-bit CAN ID 0x01D, and Receives the data for overlay on 0x01F.

So you might try those as well.