Remote COM Server documentation

[John Donovan]

In case you are interested in trying out the Remote COM server for controlling your EPMA instrument by writing your own custom scripts, the download is here:

http://www.probesoftware.com/download/Remote.msi

Contact Probe Software if you need the login and password.

Documentation describing the available instrument functions that can be called from Excel, MatLab, LabView are described in the attached pdf. A number of examples are provided to get one started.
john

Edit by John: The Remote.pdf attachment has been updated.

[John Donovan]

The latest TestRemote installation msi package now contains the complete source code for compiling TestRemote.exe. Previous versions did not have the TestRemote.ico, TestRemote.rc and TestRemote.res files.

Download here:

http://www.probesoftware.com/download/Remote.msi

[Ben Buse]

Has anyone created a script for checking spectrometer count reproducibility when approaching at element from different directions and distances?

So measure peak and background position x10, when approach from 5mm below;
Then measure peak and background position x10, when approach from 5 mm above;

Then change to from 20mm below & 20 mm above

etc...

[Probeman]

Has anyone created a script for checking spectrometer count reproducibility when approaching at element from different directions and distances?

So measure peak and background position x10, when approach from 5mm below;
Then measure peak and background position x10, when approach from 5 mm above;

Then change to from 20mm below & 20 mm above

etc...

It should be easy enough to modify the TestReproduce.xls macro example that is installed with Remote.

Be sure to save it as a .xlsm file to a folder other than the application folder, though I've attached a renamed file below.

[Netasp]

The link is not working(http://probesoftware.com/ftp/Remote.msi), how to get the file(Remote.msi)?

[John Donovan]

The link is not working(http://probesoftware.com/ftp/Remote.msi), how to get the file(Remote.msi)?

This will work:

http://www.probesoftware.com/download/Remote.msi

Also the links in the above posts are now fixed. Sorry about that!

Please note that the Remote interface will only work with Probe for EPMA.

[Ben Buse]

Great I'm now using TestStability.xls in the remote folder

This bit of code doesn't seem to ever end loop, as counters never end together, - it only works with one counter.

Code Select Expand

' Wait for counts
alldone% = False
Do Until alldone
alldone% = True
For motor% = 1 To tunablespecs%
done% = tremote.RemoteGetCountStatus(fixedspecs% + motor%)
If Not done% Then alldone% = False
DoEvents
If ierror Then GoTo StabilityCountCancel
Next motor%
Loop
Any ideas?

I cheated and ran the loop until slightly longer than the count time, and stored the count intensity for each counter when done

Great to be able to run from code

Ben

[Ben Buse]

It's great you can simulate it...

Just modified TestStablity so positionB is a random position within drive limits

Now need to try on instrument

[Probeman]

Great I'm now using TestStability.xls in the remote folder

This bit of code doesn't seem to ever end loop, as counters never end together, - it only works with one counter.

Code Select Expand

' Wait for counts
alldone% = False
Do Until alldone
alldone% = True
For motor% = 1 To tunablespecs%
done% = tremote.RemoteGetCountStatus(fixedspecs% + motor%)
If Not done% Then alldone% = False
DoEvents
If ierror Then GoTo StabilityCountCancel
Next motor%
Loop
Any ideas?

I cheated and ran the loop until slightly longer than the count time, and stored the count intensity for each counter when done

Great to be able to run from code

Ben

I don't know. The TestStability app seems to run OK on my computer in simulation mode.  See attached image.

The only thing I can suggest is to maybe add some short delays in the loop.  Do Excel macros support say, the Sleep system call?

I did note that the macro seems to count 10 seconds on the first cycle when it should count 20 seconds, and then it seems to throw that data away, but then it proceeds fine with the remaining cycles.

Probably an initialization issue in the macro code, but I'm sure you can figure that out!

[John Donovan]

Great I'm now using TestStability.xls in the remote folder

You must copy all Excel files from the C:\Program Files (x86)\Probe Software\Remote folder to another folder that is not write protected, in order to run or edit them.

I would also save these older Excel files to their new Excel macro file extensions: *.xlsm