Percy Zahl

Glad to hear. Anyways I do not understand the actual cause, I suspect some dconf schemata missing for the plugin in the version you are using. May I ask: You use a pre-build .deb package, the live image system install or the latest git-hub and build it yourself?

Dear Takayuki-san, I am thinking about what may be causing this startup crash after "PCS init: looking for org.gnome.gxsm3.pcs.plugin-libinet-json-external-scandata.rp-pacpll-phase-hold-am-noise-limit array_flag=0 pcs_count=0" but do not have a good idea. Nor I have ever see this problem. This "External PAC-PLL (RedPitaya control) " plug-in is always loaded, used or not. If the error is as of this one (may be a missing schema, but that usually is been indicated clearly). You can try to simply delete...

Dear Takayuki-san, I am thinking about what may be causing this startup crash after "PCS init: looking for org.gnome.gxsm3.pcs.plugin-libinet-json-external-scandata.rp-pacpll-phase-hold-am-noise-limit array_flag=0 pcs_count=0" but do not have a good idea. Nor I have ever see this problem. This "External PAC-PLL (RedPitaya control) " plug-in is always loaded, used or not. If the error is as of this one (may be a missing schema, but that usually is been indicated clearly). You can try to simply delete...

Dear Takayuki-san, I am thinking about what may be causing this startup crash after "PCS init: looking for org.gnome.gxsm3.pcs.plugin-libinet-json-external-scandata.rp-pacpll-phase-hold-am-noise-limit array_flag=0 pcs_count=0" but do not have a good idea. Nor I have ever see this problem. This "External PAC-PLL (RedPitaya control) " plug-in is always loaded, used or not. If the error is as of this one (may be a missing schema, but that usually is been indicated clearly). You can try to simply delete...

Hi, what do you need to plot? At the moment the only plots I am able to make are amplitude-distance but am still unable to generate the expected amplitude-distance curves, ??? If you need any custom signal generation you may also use the "GVP" tab to program any action schemes. -P

Oh OK that Retract CI value. Leave that positive, some where 100..300. Q: Is your Z-Scan going the direction as required when you simple test the feedback? Do this test: 1) Just connect Bias (OUT6) -> Tunnel Input Signal (IN0) to simple emulate a current via Bias. 2) Put Current Setpoint to 1nA or so (assuming simple 1nA / Volt for testing) 3) Put Bias = 0V => This should move Z-Scan all the way to fully extended (+10V for positive polarity) 4) Put Bias > "1V", say 2V -- what is > 1nA, this should...

A few points: A) make sure you Z-Polarity is set correctly, this is what determines if + or -10V is fully extended. (Gxsm3 -> preferences) Must restart Gxsm after adjusting. Then it will ask you to confirm to reconfigure the DSP (MK2/3) accordingly. (DO NOT RESTART THE DSP!) B) All CP, CI must be positive. Else you cause internal "confusions"... only for vert special purposes or testing they may be negative in linear transfer mode. C) "Retract CI" is a "speedup" using negative CI (CP=0) temporary...

This is never happening on any of my systems in years. Not while regular scanning. Please list your setup details -- at minimum this: Computer type/CPU/memory/Linux System Version/Swap Size/Free disk space Gxsm version/build/install type? (via Package/Ubuntu GXSM ISO/self build and installed/etc.?) Hardware: MK2 or MK3? Scan setup, size, scan speed... PS: The very only thing may happen or go wrong is if you push the scan speed to the combined limits of the USB bandwidth -- what is a complex figure...