Legacy Commands

From SPM-Wiki
Revision as of 21:33, 27 April 2014 by Ltspm (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Remote

We recommend the use of the new more powerful OLE/COM interface instead. For example through Matlab. This TCPIP interface will not be longer supported in future versions of the program.

The STMAFM program accepts external commands through remote operation. Communication is via a TCPIP connection through the port given by the port pumber. To enable remote access press the <Remote On> button. When enabled remote commands are allowed at any time, i.e. it is the users responsibility that the remote operation does not interfere with the normal operation. Status information is permanently updated.

Clipremote.png

The remote commands are simple Ascii commands. A suitable Scripting program is available through Createc.

STMAFM Remote Commands (Further commands will be added on user request)

The Commands and Parameters are send as Strings. The Strings have to be separated by ',' or CR LF. Only one Command can be send at a time. Parameters are returned as Strings separated by CR LF The first String returned is READY or an ErrorCode.

stmbeep  : For testing: STM beeps

setparam  : Set Parameter // Param[1]: key Name in Param Field, Param[2]: new value (See old parameter menu)

getparam  : Get Parameter // Param[1]: key name in Param Field

scanstart : Start Scan

scanstop  : Stop Scan

scanwaitfinished : Wait until Scan is finished

quicksave : Save the Scanfile

btn_vertspec  : Take a single Vert. Spektrum in point: //param[1], Param[2] ]=imagepixelx,y,coordinate

btn_vertspec_mult: Take multiple Vert. Spectra in points // param[n],param[n+1] in imagepixel coordinates

btn_vertspec_line: Take several spectra along a line / start point: param[1],param[2], end point param[2], param[3]

vertsave  : Save the Vertfile

move_tip_imagecoord: move tip to new position: startpoint: param[1],param[2], endpoint param[3], param[4], number of steps: param[5], delay in dsp cycles: param[6]

getscanstatus: get the present scanstatus; Scanstatus returned as String and as Number