Hi Roland I’m sorry to hear you’re having problems with the new build of PicoScope for Mac. We are aware of a few customers who are experiencing sluggish behaviour with the UI. We are currently investigating potential solutions. I don’t think the spec of your system is the problem as it is similar t...

Our latest beta release of PicoScope, 6.10.2, is now available for download. This release has long awaited log-scale feature.

You can download our beta free of charge from: http://labs.picotech.com/. Please download it and let us know what you think.

Hi Christian As the installation cache has been removed it is not possible to uninstall PicoScope. However, it is possible to remove the installation from the MSI database to allow you to install a later version of PicoScope. The later version should overwrite the old application, drivers, etc so th...

Hi Armino

We are already aware of the problem with the bloated trace file. This only affect PS2000 and PS3000 series scopes.

The good news is that we've already fixed it and it will be available in the next release of PicoScope 6.

You are not really supposed to distribute 32 and 64 bit drivers in the same package but we do. It makes the user experience much simpler. The way I do it is to have the two separate driver package conditionally installed depending on the arch. There will always be a DPInst in the system directory an...

It looks like the third parameter is the culprit. bufferLth should be an Integer.

You should also be careful with the return type - this needs to be an Integer too, otherwise your return values may look odd.

Hope this helps

You can perform a silent install on x64 but you will require a different driver package. If you install PicoScope onto a x64 system, you will find a folder called 'system' in the installation directory. This folder contains all the files required for the x64 driver package.

Hope this helps

Hellow Jay It doesnt sound like you are doing anything wrong. It could be your function prototype causing you the problem. PicoScope 6 also calls this funtion so we know it is possible to call it from .net. Here is our prototype (C#): [DllImport(_DRIVER_FILENAME, EntryPoint = "ps5000SetEtsTimeBuffer...

Hi Brian Thanks for you comments. The installer attempts to connect to CRL.VERISIGN.NET to verify the digital signature. The signature is applied so that windows can be satisfied that the software has not changed between Pico uploading it and you downloading it. This is a good thing because it ensur...

We have no .net examples specific to the HRDL but our other examples should point you in the right direction when it comes to interop. A useful reference for interop can also be found here: http://msdn.microsoft.com/en-us/library/ms235282.aspx If you are having any particular problems, please post t...

VB can call into DLLs so the tc0832.dll should be no problem. We have no .net examples specific to the tc08 but our other examples should point you in the right direction when it comes to interop. A useful reference for interop can also be found here: http://msdn.microsoft.com/en-us/library/ms235282...

1) Yes. You would definetley use the out keyword. 2) The error about the parameter signature being incorrect would suggest a problems with your declarations. I've only taken a quick look but it looks like you have used longs where you should have used ints (a managed long is 64s bit whereas a native...

[DllImport("usbadc11.dll")] public static extern Boolean UsbAdc11OpenUnit(); why should this code always return true even if the Usb adc11 is not connected. Firstly, the UsbAdc11OpenUnit() function returns a handle not a boolean. The handle will be zero if nothing is connected. Secondly, there is s...

The system shouldnt try to load PicoPP.sys unless a Pico USB device is plugged in. You can stop it from being loaded by deleting all keys that start Vid_0ce9&Pid_fffa in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\ Note that if there is a Pico USB device on the system, this will not stop t...

I've reported this as a bug in the installer but in the mean time you can get going by doing the following: Find the directory that the program was installed to, normally C:\Program Files (x86)\Pico Technology\PicoScope6. There should be a sub folder named system. In this directory there is an appli...