Interface CancaseXL with Labview

[arhten]

i am getting error like 

VXLAPIErrorConverter.vi<ERR>
vector xl driver error 118 XL_ERR_INVALID_PORT

<b>Complete call chain:</b>
\s\s\s\s\sVXLAPIErrorConverter.vi
\s\s\s\s\sXLCanSetChannel.vi
\s\s\s\s\scancase.vi

 I am using vxlapi64.dll api and i am using vectorCanalyzer7.5 and i am using Labview2017 64bit .how to clear this error.Please find below attached file

[arhten]

Can you Please send me one example code for interfacing of canalyzer7.5  with labview2019 64bit

[JMA_eng]

I tried using Vector's CANcaseXL with LabVIEW years ago.  You may want to double check the behavior and if it fits your application.  From memory, their implementation had the same value in the data until they received a new message and not a push/pop from a stack or producer/consumer behavior.  If your system never misbehaves and has repetitive messages like J1939 or NMEA2000 this may be ok.  If something stops communicating or you want to use the hardware as a generic CAN monitor, it likely will not work.  A simple indication of new data or timeout would be a nice feature in the API.  

Cheers,

JMA_eng

[TroyK]

---

@JMA_eng wrote:

From memory, their implementation had the same value in the data until they received a new message

---

No, this is incorrect. See examples of using the vxlapi.dll here: Vector XL Driver - LabVIEW wrappers

Perhaps you are thinking of some other hardware or even maybe the dreadful and defunct LabVIEW driver supplied by Vector for their hardware which was almost completely useless.

The explanation provided in the XL Driver Library API documentation for error 118 XL_ERR_INVALID_PORT is this:

"The driver attempted to access a port by an invalid pointer or index."

Have you defined the hardware and channel indexes correctly for your connected hardware?

Is the portHandle wired in correctly on the block diagram?  Have you tried any of the example code on the page I mentioned above?  Does that work when you select the correct hardware?

[JMA_eng]

TroyK - Thank you.  You are correct, it was the horrible LabVIEW Driver supplied by Vector.

Cheers,

JMA_eng

[arhten]

 Hi, I am getting error like 

Transmit Example.vi<ERR>
vector xl driver error 6255 XL_ERROR

<b>Complete call chain:</b>
Transmit Example.vi

in that Transmit example code.how to fix this error. 

[arhten]

Now there is no error in my Labview code when i run the code but in canalyzer tool i am getting an error like 

System Warning: Not possible to initialize one or more CAN channels.

System CAN driver: Reception overrun - messages are lost.

how to solve this please help me

[arhten]

And also i am getting error in canalyzer tool like Write Queue lost messages.please see the capture attached file

[TroyK]

I've never used CANalyzer.  It is a Vector product, nothing to do with LabVIEW.  You may have better luck asking someone there to help you solve problems with their product.

For the error message "Not possible to initialize one or more CAN channels":

If you start your LabVIEW code first it will open the port with "init access"(ability to set the baud rate etc.).  Only one application can have init access.

If you can't ignore the message in CANalyzer then you will either have to:

1) Start CANalyzer first and NOT try to configure the port in LabVIEW (just trust that the app that has init access configured it properly) or

2) Use a separate CAN port on the same bus for each application.

[c.abraham]

Can someone save and post these vis in 2011 for me please?