matlab not connecting to 4284

Post your MATLAB discussions here
Post Reply
mmatheny
Newbie
Posts: 0
Joined: Tue May 12, 2015 12:41 am

matlab not connecting to 4284

Post by mmatheny »

Hi,

The unit will not connect via Matlab, but will connect with the software from pico. The device does not appear in the instrument control toolbox dialog. I am using software api PS4000Asdk_r10_5_2_1 and 64 bit matlab. I followed the video to include the ps4000a.llb, the wrap, and picoIpp.llb into the directory containing the example scripts. I installed windows sdk 7.1 and ran mex -setup. Upon trying the generic block script i get the message:

[PicoScope 4000 Series (A API) MATLAB Instrument Driver

Number of units found: 0

Serial number(s):

Opening PicoScope 4000 Series device...

Instrument Device Object Using Driver : picotech_ps4000a_generic.mdd

Instrument Information
Type: Oscilloscope
Manufacturer: Pico Technology Ltd.
Model: PicoScope 4000 Series (A API)

Driver Information
DriverType: MATLAB generic
DriverName: picotech_ps4000a_generic.mdd
DriverVersion: 1.1.22

Communication State
Status: open

Setting Device Parameters...

Error using icdevice/connect (line 112)
An error occurred while executing the driver connect code.
Unit not supported
If this error is not an instrument error, use MIDEDIT to inspect the driver.
][/quote]

If I use the specific serial number I get the same error message.

What am I missing?

Hitesh

Re: matlab not connecting to 4284

Post by Hitesh »

Hi mmatheny,

I presume you mean dll instead of llb files? :?:

If you have installed the latest stable release of the PicoScope 6 software (6.10.16.2), then new USB kernel drivers have been installed which are not compatible with the dlls provided in the SDK (which preceded this release).

Please e-mail support@picotech.com and we can provide some compatible dll files.

A new SDK build will be available soon.

Regards,

mmatheny
Newbie
Posts: 0
Joined: Tue May 12, 2015 12:41 am

Re: matlab not connecting to 4284

Post by mmatheny »

Hi Hitesh,

That seemed to fix the problem. Thanks!

Post Reply