CAN Frame Signal Conversion not showing correct values

[jkro]

Hello,

I am using a combination of Hooovahh's Vector XL Driver LabVIEW Wrapper and CAN Frame Signal Conversion to read CAN frames from a test bench with multiple analog sensor and thermo couples that are connected to a CSM DAQ. CSM DAQ is connected to a Vector VN1610 CAN USB interface.

In a first step I created a VI the is only focusing on the CAN stuff to get rid of any influence of other parts of the test bench VI. Therefore I used Hooovahh's Example CAN Read Write.vi and modified it to my needs. With that I was able to reproduce the same issues.

Receiving of CAN frames is working. But I am facing two issues:

1. Conversion from CAN frames to signal values are not showing the correct values. Signal values were checked with CSMconfig and CANape with same DBC file: here the correct values were shown. Pictures of Block Diagramm and DBC file attached.
2. From time to time I am receiving following error after I stopped the VI via Stop Button and run it again. Some times stopping and re-running is working fine. After unplugging and plugging the VN1610 interface it is working again.
   1. Error 6112: vector xl driver error 112XL_ERR_INVALID_ACCESS

Can anybody help me with these two issues?

[Hooovahh]

I'm not sure why you aren't getting the correct conversion.  Attached is a VI that converts to 4 of the signals you had listed and they generate different data.

I'm pretty sure this is using version 1.8 of the package that I just downloaded from my blog.

As for the device error.  You are using the stop button on the front panel correct?  Not the stop button next to the run arrow?  Stopping the VI this way will halt all communication, and can leave the device still opened, and then trying to use it again will generate an error.  The VI Properties window under Appearance can help you hide this stop button so that you don't accidentally hit it.  If you are using the stop button on the front panel it should clean up the device access properly.

[jkro]

I started the VI on a different laptop with same LabVIEW Version and here the CAN frame to signal conversion is working correctly. Do you have any idea what could cause this?

The device error is in fact caused by an unclean exit routine. After modification, it almost always runs smoothly.

[Hooovahh]

Very weird, maybe the wrong DBC was used?  Or an older one was selected from the database some how.

[jkro]

DBC file was same. Copied the complete project file from one to the other laptop.

Bad news. Used the new laptop today again and now same issues with CAN signals occured. I don't have any clue. DBC file was not changend inbetween.