vector xl driver: labview wrapper

[lbounds]

Thanks for the reply! That is pretty confusing but it actually makes sense now!

So now I've got the VI to work without errors, but it's still not transmitting correctly to the unit I'm working with. When I set up another CancaseXL to monitor through Canalyzer I always get an error. I have to send multiple times to get the right ID to display but even when I do it's still in the error state. Also, the DLC and data change with every send even though they are set to 8 and 140CE1FFFFFFFFFF.

Any ideas? I attached a screen shot of the canalyzer results for reference. I haven't changed anything in the VI other than to select EXD and to OR the ID with hex 80000000.

I appreciate the help!

[lbounds]

Something I forgot to mention...

when I transmit my message through Canalyzer (on the same computer I'm trying to run your VI with) and monitor through Canalyzer on a different computer (using a separate cancasexl) I'm able to get the message to show up with no error. I found a knowledge base article from NI that said this type of error is often caused by improper termination, but I have 120 ohm resistors on each line and it works through canalyzer so that doesn't seem to be the reason for the problem I'm having.

[dkfire]

And you are setting the correct baudrate in both program? 

I would help if you include your LabVIEW vi that you are using for test. 

[lbounds]

Yeah I have everything set up to 125kBd...

I attached a pdf with a screenshot of the front panel and block diagram I'm using...it's really just the orginal one TroyK designed.

I know the ID and message are correct because when I send them to the unit from canalyzer it does what it's supposed to do. I just have to be missing something

[TroyK]

CANalyzer is indicating a "stuff" error. This is referring to the stuff-bit requirement of the CAN protocol.

The CAN tranceiver chips themselves take care of the stuff-bits, you have no control over it.

I've only ever seen those kind of errors when the device being tested is not correctly biasing the CAN lines or there is something else wrong on the physical layer, bus isn't twisted/terminated properly or something.

[lbounds]

Weird...it doesn't make sense that I can use the same hardware to send from Canalyzer and it works, but when I send from the vi I get the stuff error. I'll keep playing with it though...thanks everyone for the help!

[TroyK]

You're right, it doesn't make sense.

I just re-read your comment in message 11 "Also, the DLC and data change with every send even though they are set to 8 and 140CE1FFFFFFFFFF."

This is a worry, that should never happen. I'm guessing you more often get CRC errors than stuff errors.

In any case this points to a dll or driver problem.

Can you confirm that:

1) You are using the latest vxlapi.dll (NOT the 64bit version, I presume you are using 32bit LabVIEW)

2) The latest CANcaseXL driver from Vector

3) The firmware on the CANcaseXL is up to date

[lbounds]

I am using 32 bit LabView on a 64 bit Windows 7 OS...

I just uninstalled/reinstalled vxlapi.dll- version 9.0.34.0

I have the latest version of CANcaseXL (8.7.16)

All my firmware seems to be up to date as well

Still get the stuff error...just don't get it

[lbounds]

By the way, the Receive vi works perfectly (sees the right message and is error free)...has to be something I'm doing wrong with the transmit

[mainism]

when I try to excuete Transmit Example.vi there 11 errors as below picture I attached.

I'm really newb in Labview and want to experience how does it works.

PLZ help meTT.TT