andriin

Thanks. Indeed, all is doing completely what it should. I literally forgot about the boxcar averaging on ADC1..7 that is well documented... Sorry for the inconvenience Notice that I did not use the MIX-In-N channels for the direct capture, but the SCAN_CHMAPN channels, which you now made easily assignable from within gxsm3. In gxsm2, I actually had the 'bad habbit' of using MIX-In-0 to Mix-In-2 to scan data from the lockin, without any feedback control on these channels. The reasons for that 'bad...

Thanks, that's great! I simply overlooked that useful option to configure the sliders... For that ADC-N scaling: I do not want to get some other unit than volts, I am perfectly fine with that. Rather, I do not get a proper scaling of the output, at least when selecting 'ADC-N', whereas 'In N' is fine. See the attached screenshot. For debug purposes, I feed In 1 with a 1Vp oscillation (by directly connecting it to the bias output and running the lockin). When looking at channel 'In-1', I recover the...

And yet something else I just ran into that is related to scaling of scan channels: If I use an ADC as scan source, there seems to be some problem with the scaling of the scanned image (tested with ADC1 and ADC5). In fact, the data is too small by a factor of approx 14.5. On the contrary, if I select the same input channel as source by using one of the four new user-assignable scan channels, the scaling is correct. In this case, the scan source is In1 instead of ADC1. (These four new channels are...

Ok, I'll stick to the other Mix channels then. "Is the only reason you are asking the "simpler" interface?" In parts, yes, for purely cosmetic reasons - anyways not that urgent that a patch would be needed. But apart from cosmetics, the restriction to ranges from 0...50 on any of the MIX setpoints might impose an important limitation for non-STM usage. Even though I almost never encounter negative setpoints for AFM operation, gxsm2 did not have such a range limit, if I remember correctly. Accordingly,...

Hi I had a question on the ranges and units in the feedback mixer. I am using an Mk3 with the newest gxsm3 from trunk (release: defender of the electron). As I do not have an STM, I use a setpoint on one of the analog inputs for z feedback. In the normal mode (i.e. with configuration unticked in gxsm3 or in non-guru mode in gxsm2), the units of MIX IN 0 are always tied to nA, independent of the assignement for MIX IN 0. So, I always need to use the configuration/guru mode in order to use a setpoint...

Indeed, negcontrol to Z output makes sense... So I can now make out jumps in Z for...

Ok, as it seems to me, uncommenting those two lines and fixing the FW build error...

The second scan functionality with constant height offset XS2nZoff is commented out...