Connecting PS 5443D to LabVIEW

Post your LabVIEW discussions here
Post Reply
brucep
Newbie
Posts: 0
Joined: Wed Jan 20, 2021 10:42 pm

Connecting PS 5443D to LabVIEW

Post by brucep »

Hi I'm trying to connect my PS 5443D to LabVIEW. I've downloaded and installed PicoSDK 10.7.19 (64-bit). The examples (both 5000 and 5000a since I'm not sure which one I should use) are achieved from GitHub. When I open the example file, it always warns me that cannot find some vi files (SubVI is missing). And if check the Instrument Driver Finder, there shows no connected instruments detected. I'm wondering how shall I connect my PS to LabVIEW 2020. Thanks so much for your help.
[img1][/img1]
[img2][/img2]

Yande
Attachments
img1.jpg
img2.jpg
image1.jpg
image2.jpg

HannesAIRSENSE
Newbie
Posts: 0
Joined: Fri Jun 04, 2021 10:58 am

Re: Connecting PS 5443D to LabVIEW

Post by HannesAIRSENSE »

Hi,

I had the same problem and found a PicoScope.llb on GitHub, but LabVIEW can't found my Picoscope 5443D. I get a Error 5003.
Does it work with your LabVIEW now?

Greetings
Hannes

brucep
Newbie
Posts: 0
Joined: Wed Jan 20, 2021 10:42 pm

Re: Connecting PS 5443D to LabVIEW

Post by brucep »

Hi Hannes,

Unfortunately, I cannot solve it either. I now choose to use matlab, which I feel is easier to do the data streaming I need. If you're interested in that, I may be able to help.

Best,
Yande

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

Re: Connecting PS 5443D to LabVIEW

Post by Martyn »

The error code 5003 means the device can't be found. This may be due to not installing the correct SDK from our downloads page to match your LabVIEW version 32bit or 64bit https://www.picotech.com/downloads, or more commonly because you are trying to run the ps5000 examples and not the ps5000a ones which are needed for the 5443D https://github.com/picotech/picosdk-ni- ... er/ps5000a

You also need the llb from the shared folderhttps://github.com/picotech/picosdk-ni-labview-shared/tree/4b23ba5445099462b4eb4c0e1505b85cc4a40edb
Martyn
Technical Support Manager

Post Reply