topic Re: LabVIEW vxlapi CANCASEXL configuration in LabVIEW

LabVIEW vxlapi CANCASEXL configuration

Azby — Wed, 10 Aug 2011 15:23:20 GMT

Hello!!!

Currently I am trying to develop an application over the vector hw using LabVIEW. I am using the vxlapi.dll to comunicate with the cancasexl and I have had a lot of problems. Currently my problem is the tx/rx. Parallel to my application I have a nother application runing in silent mode to see what is happening in the channels (sniffer). Then only thing I can read qhen I send a message is the ID. no data no dlc nothing else.

Maybe it is a problem in the implementation of the xlreceive.vi?

I'll apreciate some help!!!

Re: LabVIEW vxlapi CANCASEXL configuration

Jorge_C — Thu, 11 Aug 2011 07:29:56 GMT

Hello!

Could you also attach the s_xl_tag_data.vi?? What errors do you get in your application and why do you think the problem is on this vi?

Thanx!

Re: LabVIEW vxlapi CANCASEXL configuration

Azby — Thu, 11 Aug 2011 08:06:50 GMT

Hi..

I cannot see any error in the application, but with the sniffer, I only see the id of the message. I just think there is a wrong addressing to the data inside the xlevent.vi, but I am not sure.

In order to see inside the s_xl_tag_data, I will attach all the VIs concerning to the xlevent.vi

Thanks!!!

Re: LabVIEW vxlapi CANCASEXL configuration

Jorge_C — Thu, 11 Aug 2011 09:46:21 GMT

What are you sending?? I guess is xlevent, but i wanna be sure.

Without enough knowledge about your application (I work with LabVIEW and NI products, but i haven't been working with Vector), it looks like the vi you have developed is working as expected. Any change in the inputs is transferred to the outputs...

In order to perform a deeper debugging, i need to know what you expect to get, where, and if possible, how.

Re: LabVIEW vxlapi CANCASEXL configuration

Azby — Thu, 11 Aug 2011 09:59:06 GMT

Hi.

The main problem is that the vxlapi.dll of vector doesn't recognize my xlEvent, or at least that is what I think. As can you see in my xlEvent, there is a TAG, ID,DLC,FLAG and data, and the olny thing that seems to work is the TAG and DLC. I don't know what I am doing wrong, but I cannot properly transmit.

Every thing seems to work, but I cannot send any can message.

HELPPPpppp....

🙂

Re: LabVIEW vxlapi CANCASEXL configuration

Jorge_C — Thu, 11 Aug 2011 10:30:53 GMT

I think the VI is correct, and that's as far as i can go with my knowledge. I have visited some sites about CAN in order to help you, but i think i might not be the right person to help you with this issue.

The only thing that occurs to me is that you may have constructed the message in a wrong way (maybe in a wrong order). I don't know if you understand Spanish, but this is the link that i have been reviewing http://www.canbus.galeon.com/electronica/canbus.htm.

Everything that you change in the s_xl_event goes through the whole subVIs system, and the s_xl_can_msg is updated. Have you tried the Vector support?

I hope you can figure it out! (and if you do, share your solution with us :D)

Re: LabVIEW vxlapi CANCASEXL configuration

Jorge_C — Thu, 11 Aug 2011 10:40:27 GMT

For example, in the link i sent you in Spanish, they say that there is a bit, called rtr that indicates if the frame has data or not. I think you determine this bit in the flags field of your message.

When you sniff the frame, check all the flags and tell me if you should be able to see data or not.

Re: LabVIEW vxlapi CANCASEXL configuration

Azby — Thu, 11 Aug 2011 16:04:15 GMT

Hello!!

Well, actually I can transmit now ¡¡¡ 😄 !!!, I have the CANoe running as a sniffer so I can see what is happening in the bus. So I can see the Id, DLC, and data, but the data is wrong :s ... I have understood some things, but it is really hard to see what the manual of vector wanted to say (because I don't have very deeply acknowledge of C/C++ and LabVIEW).

I think the trick is to know that union means only one of the elements of the structur (c/c++) can be and that was my fail, implemented all the tags, but when I realize that there is only one that could be, I understand my fail (so I implement a lot of shit hahaha) ... Now I think iam close to achive the right configuration to transmit, but I cannot get it.

Regards.

Re: LabVIEW vxlapi CANCASEXL configuration

Jorge_C — Tue, 16 Aug 2011 08:17:52 GMT

Hi!

How is it going?? I am happy you were able to finally get a transmission. I couldn't test your code, as there is one file left (vlxapi), but if you post it and tell me exactly what error you get (or unexpected behavior) i promise to give it a try.

Good luck!

Re: LabVIEW vxlapi CANCASEXL configuration

Jorge_C — Fri, 19 Aug 2011 07:22:30 GMT

Hi!

Did you get your problem solved?? If so, how did you get it??

Re: LabVIEW vxlapi CANCASEXL configuration

Azby — Mon, 05 Sep 2011 13:22:52 GMT

Hi!

Sorry for the long delay, I was on holydays 🙂

Ok, I tried so many times and so many configurations and at last, I get it!!!. Although I think it is not an elegant solution, for now it is OK for me and it works.

The mainly thing is the xlevent. I took the old vi from (vcan32.dll) as an example and made my own vi.

It is very strange, but the manual user for vxlapi, has a configuraton for xltransmit and xlevent quite different than I, but unfortunatelly I cannot explain it why.....

Maybe you can use the library made from VECTOR to vcan32.dll it works for the CANCASEXL, so if this is the device you want to control, I think it should be ok.

I have to control the CANCASEXL and the MOST as well and that is why I cannot use the vcan32 and have to use the vxlapi.

Regards.

Re: LabVIEW vxlapi CANCASEXL configuration

Amit_C — Tue, 08 Jan 2013 18:59:58 GMT

Hi,

can you send me the transmit strusture pls..

rgds,

Amit

Re: LabVIEW vxlapi CANCASEXL configuration

Azby — Wed, 09 Jan 2013 09:12:47 GMT

Hi.

What structure do you need?

Attached you will find the "transmit structure", I hope it is what you need. You can develop the "receive structure" in the same way, just read the manual of Vector XL and copy what you need from the "transmit structure".

Best regards.

Re: LabVIEW vxlapi CANCASEXL configuration

Amit_C — Wed, 09 Jan 2013 14:34:32 GMT

Hi,

Yes, this is what I wanted. But, I am unable transmit a message. When I try to transmit, I see error frames in canlyzer. Please help.

Attached is the print screen of the VI.

Thanks and Regards,

Amit

Re: LabVIEW vxlapi CANCASEXL configuration

Azby — Wed, 09 Jan 2013 16:20:54 GMT

Please, send me more information regarding the error (where the) or send me your VI, maybe I can point out what is wrong.

Regards.

Re: LabVIEW vxlapi CANCASEXL configuration

Amit_C — Wed, 09 Jan 2013 16:40:24 GMT

Attached library which I am using and the VI.

Re: LabVIEW vxlapi CANCASEXL configuration

Azby — Wed, 09 Jan 2013 17:15:30 GMT

Please, save them to the 2011 version. I cannot open them.

Tomorrow I'll check it.

Regards.

Re: LabVIEW vxlapi CANCASEXL configuration

Amit_C — Wed, 09 Jan 2013 17:51:48 GMT

Hi,

Attached in labview11.

Also I am getting below errors.

Time         Chn     ID   Name   Event Type   Dir     DLC   Data
[+] 98.650824    CAN 2               CAN Error    RxErr         ECC: 11110011, Other Type of Error, Segment = Tolerate Dominant Bits
[+] 98.651856    CAN 2               CAN Error    RxErr         ECC: 11110011, Other Type of Error, Segment = Tolerate Dominant Bits
[+] 98.652886    CAN 2               CAN Error    RxErr         ECC: 11110011, Other Type of Error, Segment = Tolerate Dominant Bits
[+] 98.653756    CAN 2               CAN Error    RxErr         ECC: 11110011, Other Type of Error, Segment = Tolerate Dominant Bits

Along with some form error, etc .

Thanks and regards,

Amit Chincholi

Re: LabVIEW vxlapi CANCASEXL configuration

Azby — Thu, 10 Jan 2013 14:15:12 GMT

Hi.

I tried with your version and it gave me an error. but the error was the HWINDEX you have set to 1 and I set to 0 and then it works.

Regards.

Re: LabVIEW vxlapi CANCASEXL configuration

Amit_C — Mon, 14 Jan 2013 09:49:52 GMT

Thanks a lot. Today I checked it and it works fine. But, when I try with extended Identifiers it sends only 11 bits out of it. Can you please suggest me the changes to be made.

Thanks and Regards,

Amit