Percy Zahl

Good! And as of your preferences you can adjust it's behavior via a few settings exposed in the dconf-editor for gxsm4 settings. best regards -Percy Dr. Percy Zahl Email: pzahl@bnl.gov Center for Functional Nanomaterials WWW: http://www.bnl.gov/cfn Bldg. 735 - NC Brookhaven National Laboratory Work: +01 (631) 344-2968 Upton, NY 11973-5000, USA .^. /V\ //G\ Visit Gxsm now! Unlimited and free SPM+ software: /(XSM)\ -----> http://gxsm.sf.net<------ ^^-^^ From: discussion@gxsm.p.re.sourceforge.net discussion@gxsm.p.re.sourceforge.net...

Hello again, quick update: I fixed the remaining Splash startup (not closing) issue for SR-MK2/3. And a few more details related to Wayland and DSP window position management via Gxsm4.

I added a new RTQuery "B" option for Bias readback so the PanView shows this now correct. (New) I tested the scope as provided via the python script mk3_spm_configurator.py -> 6 SPM Oszilloscope. It works just as fine. See example screenshot. Sorry, no clue what goes wrong for you.

I'll have to setup my SR3 and see what is going on, I honestly have not used that script/scope in a long time.

I do see a USB (Read) Connection Timeout error as main cause. Does that happen with all Oszi Settings? May be only with very large #points? Do you see any other USB errors in systemlog (sudo dmesg" )? Other traffic heavy loads/devices on the same USB bus? Is your USB cable proper USB 2.0 rated, excessive long, externders, etc. I used to use USB 2.0 compliant extenders with no issues, but must be rated and connected correctly. Today also USB 3.x shoudl work just fine. (but in USB 2.0 compatible mode,...

I do see a USB (Read) Connection Timeout error as main cause. Does that happen with all Oszi Settings? May be only with very large #points? Do you see any other USB errors in systemlog (sudo dmesg" )? Other traffic heavy loads/devices on the same USB bus? Is your USB cable proper USB 2.0 rated, excessive long, externders, etc. I used to use USB 2.0 compliant extenders with no issues, but must be rated and connected correctly. Today also USB 3.x shoudl work just fine. And finally: there is no easy...

I do see a USB (Read) Connection Timeout error as main cause. Does that happen with all Oszi Settings? May be only with very large #points? Do you see any other USB errors in systemlog (sudo dmesg" )? Other traffic heavy loads/devices on the same USB bus? Is your USB cable proper USB 2.0 rated, excessive long, externders, etc. I used to use USB 2.0 compliant extenders with no issues, but must be rated and connected correctly. Today also USB 3.x shoudl work just fine.

the python script crashes? you should be able to run this in parallel to gxsm. should not have any side effects besides using bandwidth and you can reconfigure the signals for the scope and that will change the by gxsm setup monitoring default. thus the current monitor in pan view may change the value to what ever you picked.