LabVIEW for PicoScope 4424 - 4000GetBlock.vi Error 1097

Post your LabVIEW discussions here
Post Reply
kamranesmaeili
Newbie
Posts: 0
Joined: Fri Jul 20, 2018 1:51 pm

LabVIEW for PicoScope 4424 - 4000GetBlock.vi Error 1097

Post by kamranesmaeili » Fri Jul 20, 2018 3:00 pm

I have an error with the PicoScope4000ExampleBlock.vi https://github.com/picotech, showing me an error when I click on running the VI.

I have tried PicoScope4000ExampleStreaming.vi and it seems to be working fine.
The error comes from the PicoScope4000GetBlock.vi located in the middle of circuit diagram in PicoScope4000ExampleBlock.vi, showing me an error status of 'Error 1097 occurred at Call Library Function Node in PicoScope4000GetBlock.vi' with possible reason(s): 'Labview: (Hex 0x449) An exception occurred within the external code called by a Call Library Function Node. The exception might have corrupted the LabVIEW memory. Save any work to a new location and restart LabVIEW.'

LabVIEW version 18 (32bits) 2018
Windows 10 x64-based PC - located on 'Program files (x86)'
PicoScope 6.13.6 - located on 'Program files (x86)'
PicoSDK 10.6.12 - located on 'Program files (x86)'

The files attached show the libraries I have copied into /LabVIEW2018/resource/ and their link to the SDK files in 'C:\Program Files (x86)\Pico Technology\SDK\lib'

Any idea where this might be coming from?
Attachments
PicoScope4000.llb
PicoScope4000.llb
(265.2 KiB) Downloaded 208 times
PicoScope.llb
PicoScope.llb
(158.38 KiB) Downloaded 215 times

kamranesmaeili
Newbie
Posts: 0
Joined: Fri Jul 20, 2018 1:51 pm

Re: LabVIEW for PicoScope 4424 - 4000GetBlock.vi Error 1097

Post by kamranesmaeili » Mon Jul 23, 2018 6:12 pm

I have realised it resulted from the VI version I was running. I have downloaded the 32-bit example files and it seems to be working fine.

AndrewA
PICO STAFF
PICO STAFF
Posts: 230
Joined: Tue Oct 21, 2014 3:07 pm

Re: LabVIEW for PicoScope 4424 - 4000GetBlock.vi Error 1097

Post by AndrewA » Wed Jul 25, 2018 12:53 pm

Yes you need to use the correct versions of the examples that match your version of LabVIEW.
ie 32-bit example with 32-bit LabVIEW
As a few of the data types are different for dll function calls. But code should be the same.
See forum post- topic12601.html see point 9.

You do not have to copy dll's etc to LabVIEW resource folder.
Just install the SDK and this will enter the dll's into the PATH variable. You can even install both 32 and 64-bit SDK packages.

For the dll properties, do not add a path just the file name of the dll.
These maybe set in some of our examples but we are work to change them as they are updated.
Regards Andrew
Technical Specialist

Post Reply