5244D - no response from LabVIEW

Post any questions you may have about our current range of oscilloscopes
Post Reply
BSI
Newbie
Posts: 0
Joined: Wed May 12, 2010 3:15 pm
Location: Canada

5244D - no response from LabVIEW

Post by BSI »

Hi,

Dev computer:
Win 10
LV 2015 SP1
Pico SDK 32_10.6.97 installed. (with ps5000a.dll ver 2.1.17.1454 ; ps5000aWrap.dll ver 1.0.1.97, picoipp.dll 1.3.0.18) and a few other .lib files.
scope: 5244D connected to USB 3.0

I am trying the example(s) downloaded from github. At this stage I just want to test an open/close, get the device info etc... "OpenUnit-2" generates an error right at the start so kind of stuck now. The handle remains -1 coming out of this node, and the raw status is 268435457. However the Error Handler function does some weird adding/substracting of 5000 in the LabVIEW example code, and produce a 268430457 , as unknown code (internally due to the 5000 offset), BUT this code actually is in the list, and refers to the picoipp.dll missing.

So in short, it does not seem to work, and the error status is suspicious.

As far as the documentation is concerned there is nothing referring the many function calls that appear to use the version "-2" in the examples' function nodes. So that does not help either. What are all the "-2" versions of these calls please?

Thx for helping with this.
L.
Attachments
OpenUnit-2.JPG
Top
BSI
Newbie
Posts: 0
Joined: Wed May 12, 2010 3:15 pm
Location: Canada

Re: 5244D - no response from LabVIEW

Post by BSI »

using ps5000aOpenUnit call instead of the "-2" version fixes it. Make sure the call change is actually taken in the CN node, I had tried that test yesterday with no luck... :shock:

What about all these "ver 2" calls though?
L.
-->
--> using ps5000aOpenUnit call instead of the "-2" version fixes it. Make sure the call change is actually taken in the CN node, I had tried that test yesterday with no luck... :shock:

What about all these "ver 2" calls though?
L.
Top