USB Access violation Call Library Node AtUSBhid.dll Atmel XMega

[ThiCop]

Hello Martin,

What do you mean with "yes on crash report no on labview.exe report (5out of 5)"?
Which Crash Report do you get?

[SiddySI]

Sorry, with crash report I mean the access violation 0xetc.etc. and with the labview exe report I mean the report about the device\harddrive\dr4. So the issue with the exe report device\harddrive\dr4 is solved and i still get the crashreport 0xetc etc. 

[ThiCop]

Can you share the exact contents (the etcetcetc part 😉 ) of this one?

I want to make sure it still is exactly the same?

[SiddySI]

It is, I always get the access violation 0xC0000005, only the EIP number differs but i don't now what EIP stands for nor if it usefull to register that number.  

Martin

[SiddySI]

Hello Thierry,

Today I wanted to find out which of the property nodes causes labview to crash so I made a very basic vi with just the findhiddevice property node (see attached file). To my surprise the findhiddevice causes labview to crash, I have taken a look at the documentation and I'm pretty sure that the settings for this property node are OK.

The crash report is the same access violation 0xC0000005

Do you have more ideas what might cause the labview crashes I'm getting a bit concerned.

Kind regards, Martin

[ThiCop]

Hello Martin,

I have replied to your e-mail today in out inbox.

Please let me know through one of both channels if you prefer to continue the troubleshooting through e-mail or through the forum posts.

[SiddySI · Accepted solution]

This issue is solved with the help from NI-techs in Belgium and Holland. To help others how may encounter this kind of problems in the future I have writen down the issues and theier solutions hereunder.

Issue 1:

During the testing we found out that the access violation also acuird if we only run the check device property node. The problem was not the check device property node but that we did not close the device. Adding a close device property node afther the check device node solved this issue.

Issue 2:

Is a bit more tricky for me to explain but I will give it a try. When you use a property node that recieves data on the output you have to tell the property node at the input what the node is going to recieve other wise memory issues may accure. The issue was solved by adding a buffer to the input of the read data property node.

Although Iam stil testing the vi all the problems seem to be solved and YES it seems that I have stable communication!. Thanks to Thierry and Bas from NI, Thierry one kudo for your help, Bas you deserve 2 for solving the problems but your are no part off the forum discussion so I have no clue how to give the to you.

Kind regards, Martijn     

[ThiCop]

Good to see that everything got fixed in the end.

Have a nice weekend!

[joemmac]

Hello Martin,

I too am using the AtUSBhid.dll and am experiencing the "Exception: Access violation (0xC0000005)" error.  The error usually occours after my LabVIEW program has completed and I am closing the window.  Occasionaly it occours while the program is running.  I double checked that all of my open resources are being closed (USB HID, COM port via VISA, GPIB via VISA, and two text files), but the error still happens.

Can you please go into some more detail about the two solutions that you used to resolve the issue?

Thanks!

Joe

[SiddySI]

Hi joe, it has been a will working on the issue, i will refresh my memory and get back to you this weekend. Is it possible for you to post the code so I can have a look what you are doing?kind regards, martin