crash on startup with brand new scope
crash on startup with brand new scope
i'm running arch linux and installed the following packages from aur:
- picoscope7beta
- ps7b_libpicoipp
- ps7b_libpicocv
- ps7b_libps2000a
i had been playing around with the demo scope for a few days prior to making my purchase, however on receiving the scope today i misunderstood the message saying my scope was unsupported as it being unsupported in ps7 and not that i had the wrong driver installed (2000a instead of 2000).
so i replaced the installation with ps6 and in the process realised the mistake with the drivers. ps6 worked fine once that was resolved, however because i only have hidpi screens the app itself is near unusable, so i figured i'd reinstall ps7 with the correct drivers.
that brings me to my current problem and crash. it seems as tho ps6 wrote something to the device that ps7 cannot read and is crashing during connection? i googled and could not find anyone experiencing this, so i'm not sure what to do exactly.
is it possible to factory reset the device and start a fresh with ps7? or have i misunderstood the problem?
thanks, mae
Re: crash on startup with brand new scope
edit: it didn't attach... it still won't attach so here's a pastebin: https://0bin.net/paste/WnCmTf7c#ryWD5Kc ... v0ZWHBfYUV
Re: crash on startup with brand new scope
Does the software start if you don't have the 2204a connected?
Technical Support Manager
Re: crash on startup with brand new scope
Re: crash on startup with brand new scope
ps. are all my posts going to be put into the moderation queue? it makes this rather difficult.
Re: crash on startup with brand new scope
ok, so i went and removed the
Code: Select all
~/.local/share/Pico Technology
however, after closing ps7 and starting it again with the 2204a connected, it gives me the same error as first reported. i then deleted the directory and the problem still persisted.
Re: crash on startup with brand new scope
Technical Support Manager
Re: crash on startup with brand new scope
ok so, after looking thru the logs it first loads the ps2000 driver and then when it gets to "default_configuration" it attempts to load the ps3000a driver which isn't installed:
Code: Select all
Checking driver '/opt/picoscope/lib/libps2000.so' exists in executable path '/opt/picoscope/lib/
Finished loading ps2000.dll
Finished loading ps2000.dll
Opening device using DLL ps2000.dll
Opening device successful. Error NoError.
Device opened IZ146/104: PS2000 PS2204A PS2000
Attempting to load ps2000.dll from '/opt/picoscope/lib/libps2000.so'
Checking driver '/opt/picoscope/lib/libps2000.so' exists in executable path '/opt/picoscope/lib/
Finished loading ps2000.dll
Opening device using DLL ps2000.dll
Opening device unsuccessful. Error NoError
Opening device successful. Error NoError.
Device opened IZ146/104: PS2000 PS2204A PS2000
Starting to load file 'default_configuration'
Attempting to open PS6 File, File is streamed as object
ps3000a.dll System.DllNotFoundException: ps3000a.dll assembly:<unknown assembly> type:<unknown type> member:(null)
at (wrapper managed-to-native) PCD.hl+a.c(PC.hw,System.Text.StringBuilder,int16,int16&,PC.ia)
at PCD.hl.dk (System.Text.StringBuilder lek, System.Int16 lel, System.Int16& lem, PC.ia len) [0x00031] in <8e4062e655fe439197134207deea4db2>:0
at PCD.hs.s (PC.ia fwx) [0x00009] in <8e4062e655fe439197134207deea4db2>:0
at PCD.hs.DoGetDriverPath () [0x00008] in <8e4062e655fe439197134207deea4db2>:0
at Pico.Common.Dal.Adc.Handles.DeviceHandle.get_DriverPath () [0x00000] in <8e4062e655fe439197134207deea4db2>:0
at Pico.Common.Dal.Adc.Handles.DeviceHandle.DoIsDllAvailable () [0x00057] in <8e4062e655fe439197134207deea4db2>:0
Finished loading ps3000a.dll
File 'default_configuration' is not supported - File was saved on a PS3406B device using an unsupported driver for this version of PicoScope.
Code: Select all
File 'default_configuration' is not supported - File load integrity check failed.
Re: crash on startup with brand new scope
i just noticed that the aur packages were updated 18 hours ago, so version 7.0.98_1r11193 works but 7.0.97_1r11109 does not.