Exposed a simple set of 8 full Probe Vectors for a simple but full user configurable VP program. May add flag for FB on/off?
Please update MK3 code + Gxsm/HWI if you need more then about 4000 values for VP probing on MK3. A FIFO buffer size mismatch was resolved and now there no size limitation beyond bandwidth and a max N per VP section of 2^15 (this may soon also be lifted as MK3 all vars are 32bit, only limited by HWI for MK2/3 compatibility reasons as of now) any more.
See also previous News post!
Mk3 new mode "fast-scan" related patches released in CVS. Update to latest DSP&Gxsm2.
Working on optimized real time "grey-2d" view with better update, automatically switching to full frame updates and skipping forward to current data -- if scanning fast and update rate does not allow line by line. May freeze "Red Line" temporary.
Various small updates, mostly convenience...... read more
For MK3 only:
-- new experimental fast scan mode:
It's a while since the last update.
Gxsm project presentation at SPM Workshop Lednice 2013, meeting with Gwyddion developers. Great workshop!
A couple new features, fixes and more.
-tracking data visualisation plugin
-updates and additional control to the PL VP mode for more detailed control.
-for safety: mover dialog is set to insensitive while scanning now.
-new feature "BlueLine". If you know what I mean with "RedLine" (current scan line profile of a channel) -- now you can add a "BlueLine" within the same profile view but taken from channel+1. Assuming normally here you use CH for some "->" and CH+1 for "<-" data, but limited to this. And, yes -- both Red... and Blue... can include a number of "history" or previous scan lines, just as much as you configure different colors for Red/Blue Line in preferences.... read more
Gxsm developer at AVS, Tampa, FL.
If any Q's or need for discussions, get in touch with me at the AVS!
Just send me a message.
please update the DSP code (Mk2) if you need the counter, some previous code changes left it non functional due to a missed assembly code adjustment. Sorry, fixed now.
GEORGE T. HANYO AWARD
Dr. Percy Zahl, Brookhaven National Lab., “for outstanding leadership in the development of state-of-the-art, open-source software package and associated hardware for data acquisition and analysis in scanning probe microscopy and spectroscopy.” The award was established in 1996 by the Kurt J. Lesker Company in the memory of George T. Hanyo, a highly skilled, long-time employee of the company.... read more
The MK3-Pro PAC/PLL implementation is ready for testing! Need some one with hands on a real working tuning fork based system willing to learn how to use and test it...
The new implemented "scope" feature allows life signal watching/recording via new tool "PACscope" (provided via SRanger CVS) + tune and PAC (ampl/phase) step response measurements.
This neat feature allow not only to monitor PAC/PLL signals but also any other "signal" at full rate in two channels. Now also backported and available on MK2!... read more
Latest code ramblings, Version:
GXSM 1.30.0 "Meetinghouse Warrior"
This is all related to the new MK3-Pro support with added PAC/PLL GUI and controls + direct PLL data interconnections with Gxsm2:
The first version of the Gxsm with embedded PAC/PLL control and hookup into the feedback mixer is going life.
A few screenshots are attached and I highlighted major new settings... also new a life watch for actual/peak DSP load in PanView:... read more
A few updates on the latest CVS release of Gxsm2 "Arosa Express" V.1.27.3:
new parameter to control (false) early Auto Approach terminations via setting a max allowed settling time, so occasional "glitches" causing a positive FB-delta are not any more termination the approach early. See Configuration tab of the Mover Control dialog.
now also hooked to PyRemote are all VP-*-Execute buttons allowing you to fully and freely program via python any complex VP-probing/spectroscopy! Hooked via the action method, action id is shown as tooltip while hovering over the Execute Button you need to automatize. (Enable Gxsm->Help->Enable Remote Tips)... read more
FYI: please do NOT update from CVS, nor Gxsm-2.0 or SRanger. The DSP binary/code contains a not yet resolved bug most likely related to DSP code linking/address issue (DSP crashes at load or randomly later). As the GXSM HwI in CVS depends on the latest (broken) DSP code, do not update. The last stable version is from 2011-10-14 or earlier. Use this for CVS checkout by date for a working version. Sorry for the inconvenience. Will update once issue is resolved.
Happy Thanksgiving to all our GXSM friends!
A few news and updates, and yes -- got also a few of out conference ToDo list items on the way!
Now just in CVS "Lindau Historic*" Version Gxsm 1.27.2.
** Z-probe: added repeat and a limiter function (testing!) The limiter option works on a signal on CH0..3 checking for > or < a limit and if so it bascially "fast-forwards" the VP at max rate while holding all outputs (frozen), then it assumes (VP must be designed to match -- i.e. the user must check "DUAL" in control window) as a symmetric (inverse vector to proceed the exact same number of steps in fast forward mode to return to the conditions as the "hold condition" was detected. Per design data is still read and transferred at the "hold section", but at max rate. This so far has a side effect as no time stamp is transmitted with each data packet, only at every section start and this the time scale may look a little odd.... read more
gxsm builds and runs OK on Nany (Ubunty 11.04). But do not use this I-phone/pad style window manager Unity -- no good, no clue. Just log on with the "Classic" style and all is fine.
After lots of discussions and many long unsuccessful debugging sessions, hacking in trains and airplains.... a great conference and discussions with the Gxsm community we got a little step forward now as I am back to my "office" and the latest Version "Lindau Historic" is in CVS:
** most important, the random auto-plot related display refresh of VP profile views caused crashes on latest ubuntu systems. Bug fixed. (Nested gtk/ploting calls in g_thread environments...).... read more
We will be presenting a Poster at the NC-AFM Lindau, 2011 http://ncafm2011.unibas.ch along side with a little more demonstrational material and a MK2-A810.
Take the chance to meet the Gxsm developers and discuss your needs!
added automatic zoomed view for scan area+tip (centered, zoomed to fit) to shop tip within current scan area (grey outline) and bigger green outlined tip symbol. Only appears in PanView if the "black" scan area is getting kind of small to see where the tip is (set to about 1/6 of pan size).
Please consider this as a major new release and be careful with a first test on your system.
I checked and tested it -- so far so good.
A set of major improvements, additions and DSP level code revisions including a change to higher precision (full 32bit based) math for scan signals including a new coded 64bit (Q31xQ31->Q31) multiplication for high precision vector rotation so the HR mode can take full advantage now for all XYZ Offset and Scan signals -- including life plane correction via Z0 adding (analog in you HV Amp via mod or ext offset input) -- now working even better.... read more
Added a per default empty folder/window (tabbed window) "DSP-Control-User Tabs" what now accepts tab from the DSP-Control window (MK2 only) via DnD!
Open the second "DSP-Control-User-Tabs" window via window menu -- it will be empty at the beginning, then drag a tab into it...
Just arrange your favorite set of "VP modes" per DnD, also included Tab reordering via DnD in both windows.
Feel free to minimize/close one or even use both.... read more
Few minor patches in CVS.
Slope correction mode works very nice! Kind of like it ;-)
Please watch out -- I noticed the CVS-checkout/update right now not been in syn with my commits...
New experimental feature, every thing else is expected to be solid and stable as by current testings.
Gxsm Version Naming Scheme added ;-)
Added support for DSP level VP based real time (atom/molecule/feature) tracking modus, "TK-tab" (MK2-A810 only)
Added support for real time (analog) slope correction. Now analog-output of "plane fit" via ZOffset (Z0) out -- this needs to be added to Z via your Piezo Amp for example. (MK2-A810 only)
Parameter for X&Y slope are to be adjusted/tuned manually. Parameters are invariant to offset and rotation. I.e. via 90 deg rot you can easy adjust the Y slope while watching the "red line" (x-scan)...... read more
Adjusted configuration file to accept now also python version 2.6 -- a quick test, seams working OK.
In case you never used it or scared of things a like -- just try this:
Create a file names "remote.py" and put in you current working directory. (this is the default, but can be set in Preferences/Paths)
Edit it and put these 4 lines in it:
emb.startscan()... read more
compiles in impressive "time real = 7min57sec" on this little machine!
For heads up, I like to thank SoftdB again for providing me and GXSM project with their latest DSP Flagship, the all new MK3 with the all 32bit TMS320C6424.
I hooked up my A810 and about ready to go -- porting the code as needed is starting about now.
There will be a new HwI and DSP code soon for the MK3.
And for a little more insights -- this new DSP is powerful enough to (at least stand alone) run a PLL for tuning fork based AFMs up to about 90kHz. And thanks to our great developers at SoftdB -- they have a prototype running (stand alone analog in out so far)! Plan is if possible form performance (TBD) a library will be available for this to be embedded with the GXSM optimized DSP code for this some time. And if needed, a dual DSP solution will do the trick.... read more
Please update from CVS if you are extensively using multi probe/raster STS etc. for many 1000s of probe events.
So far for every event was a new NetCDF variable set generated (two vars for each event with multiple dimensions) and beyond about 4200 events this exceeded the NETCDF_MAX_VAR limitation and caused a gxsm exit as time of saving. Also this was terribly slow and inefficient.
Now I optimized this and collecting all probe events with same set of dimensions into one variable with one more dimension (number of events) -- this should virtually eliminate any further limitations and also saving/loading is now much faster.