ps5000aRunBlock Crashes LabView

Post your LabVIEW discussions here
Post Reply
bburnham
Newbie
Posts: 0
Joined: Fri Oct 04, 2019 6:08 pm

ps5000aRunBlock Crashes LabView

Post by bburnham » Fri Oct 04, 2019 6:27 pm

Hello. We are using LabView 2018 64 bit with a PicoScope 5244B and Windows 10. We have installed the PicoSDK 10.6.13 (64 bit) and are using the latest .llb files from that SDK.

LabView is able to communicate with the PicoScope for set up without trouble. We then call PicoScope5000aSettingsandRun.vi to begin the data acquisition. This VI works up until the Call Library Function Node titled ps5000aRunBlock. As soon as this is called LabView crashes with the following message:

LabView 2018 encountered a problem and needs to close. You can help disgnose...etc.

Exception: Access violation (0xC0000005) at EIP=0x0000018E00000000
Version: 18.0.1f4(64-bit)

Any thoughts as to what's happening, and how to get around it, would be appreciated.

silmaril
Newbie
Posts: 0
Joined: Wed Oct 16, 2019 6:22 am

Re: ps5000aRunBlock Crashes LabView

Post by silmaril » Wed Oct 16, 2019 7:24 am

I'm not sure what's happening there, but you should make sure that all Call Library Function nodes are configured to use Calling convention "C" (not "stdcall (WINAPI)").

The official LabVIEW example VIs don't do this consistently, so this might be wrong if you just copied them.

Unfortunely, the documentation is not 100% clear in this aspect:Calling conventions are not mentioned in the section talking about Microsoft Windows, but for Linux and macOS you can find the sentence "The drivers use the cdecl calling convention" - I assume it's the same for Windows.

Martyn
Site Admin
Site Admin
Posts: 3714
Joined: Fri Jun 10, 2011 8:15 am
Location: St. Neots

Re: ps5000aRunBlock Crashes LabView

Post by Martyn » Wed Oct 16, 2019 8:42 am

Have you tried the examples that we provide on our GitHub Pages
Martyn
Technical Support Manager

Post Reply