VCOM Toolkit Multiplexed messages (CAN) cause PROVEtechRBS C.D. error 200

[Pianne]

Hi all,

I recently started using the NI VCOM (Vehicle Communication) Toolkit to set up a CAN network with a 3rd party controller.
I got the thing running on a PXI RT target using the provided a DBC file and the PROVEtechRBS Custom Device from the toolkit.

I managed to configure the AUTOSAR E2E protocol for outgoing messages.

The problem I'm facing now, is that the Custom Device goes into error state (errorcode 200) when I add multiplexed CAN messages to the Veristand project.

One of those problematic messages is the "VIN" message.

(Error string from the logfile in the RT target: 

Error: RE (Code: 200): Signal 'CAN_VCU_Tx.Vehicle.VIN.VIN_0.NVINPart3' not found for writing

What I found is that the message signals are organized differently in the DBC file and RBSConfig tool versus in the System Definition tree and the "Import Channels" tool... I suspect that's causing the problem.
Any idea how to correct this? I couldn't find anything in the manual, on the forums or on the net...

Import channelsDatabase editorRBSConfigVS System Explorer

[Pianne]

Nevermind 😞

It appears that the Messages "VIN" (0x301) and "CarConfig" (0x300) are sent automatically and that adding them to Veristand causes the Custom Device to throw an error. I couldn't find any documentation about this, however ☹️

For now I can live with the fact that the data for both "VIN" and "CarConfig" is all zeroes but I wonder how one is supposed to get actual 'VIN' and 'CarConfig' data to be sent in those messages... Using default values?