The bottom line is that I’m still not able to get HelloPico in Xojo running. If you get status code 282 (0x011A) you need to connect the scopes 5v external supply. Then you won't need to copy dll's into your project folder.
Xojo verison install#
If you are not using the current SDK windows installer, I would delete all Pico dll files from your system and download and install it. You could then use this with our programmers guides.
Showing the new C/C++ data types vs the Xojo data types
One thing you could do is create a table of data types using the DrDAQ code.
Xojo verison how to#
I had to set the serial number string to serial number of my unit, as don't know how to set the serial string to NULL. TextInfo3.Text = S.StringValue(0,requiredSize) SLegnth = ps5000aGetUnitInfo(handle, S, 255, requiredSize, 0) TextInfo2.Text = S.StringValue(0,requiredSize) SLegnth = ps5000aGetUnitInfo(handle, S, 255, requiredSize, 4) TextInfo1.Text = S.StringValue(0,requiredSize) SLegnth = ps5000aGetUnitInfo(handle, S, 255, requiredSize, 3) Status = ps5000aOpenUnit(handle, serial, 1) = cstr(ScopeOutput)Ĭode: Select all Declare Function ps5000aOpenUnit Lib "ps5000a.dll" (ByRef handle As Integer, serial As Ptr, resolution As Int64) As Int32ĭeclare Function ps5000aCloseUnit Lib "ps5000a.dll" (ByVal handle As Integer) As Int32ĭeclare Function ps5000aGetUnitInfo Lib "ps5000a.dll" (handle As Integer, S As Ptr, stringLength As Integer, ByRef requiredSize As Integer, info As Int64) As Int64 ScopeOutput = ps5000aOpenUnit(Handle, "", 1) txt.ĭeclare Function ps5000aOpenUnit Lib "ps5000a.dll" (ByRef Handle as Short, ByVal Serial as CString, ByVal Resolution as Integer) as UInteger Once I get mine up and running, I'll try to distribute it here, though it wouldn't accept the xojo_binary_project extension and blocked me when I changed it to. Of course, if anyone has Xojo example code already running for a PicoScope (I saw that there were examples for DrDAQ), that would be greatly appreciated. If I know what can be going wrong, then I can troubleshoot it.
Xojo verison .dll#
DLL correctly because I see the Pico logo show up and a progress bar scan. What are the different reasons that ps5000aOpenUnit could return the value 3? I know that it's accessing the. There's really practically nothing to my program so my simple and concrete question is: It does this consistently, whether or not VB.net is running, even if I unplug/replug the scope. All is right with the world.Īnd then I code nearly identical code in Xojo and the first line returns 3. Status = ps5000aChangePowerSource(handle, status) Status = ps5000aOpenUnit(handle, vbNullString, DeviceResolution.PS5000A_DR_12BIT)Īs expected, it returns 282 since the scope is bus powered and, after VB checks for this, this line is executed: I started with the VB.Net example code and, after moving a few files into the appropriate directories, I was able to get it to compile and run. Fundamentally, I can't figure out why ps5000aOpenUnit keeps returning my scope status as 3 in Xojo while it returns 282 (as desired) in the VB.Net example code.
I'm trying to get in contact with my PicoScope 5244A in an in-house application that I'm writing in Xojo and I'm stumbling on the first step in the process.
0 kommentar(er)
