PI Error upon starting map acquisition_v.1.5.4.18

[Henny Cathey]

 Hi all - Has anyone seen this error before when starting PI acquisitions (I'm using JEOL8530f):
"Probe returned JEOL error -5: maximum logical unit number error Occurred during reading crystal"?
If so, what does it mean, and how did you troubleshoot and fix the problem? I was setting up a series of maps, and partway through "Read ELM" started failing (unresponsive; then was reading only 2 of 5 spectros...). I tried manually entering the data for each element, but the run crashed when I started. I've tried the usual solutions of closing all softwares, cycling power to OPE and also to the intelligence unit, installing latest updates of PfE and PI), using a back-up crystals.dat file (thinking existing one may have been corrupted), starting fresh with a new map acquisition file...but I'm not getting anywhere except that "Read ELM" functionality has been restored. I'm still getting that error when trying to launch a run.
Any help will be appreciated!
Thanks,
Henny

[John Donovan]

Has anyone seen this error before when starting PI acquisitions (I'm using JEOL8530f):
"Probe returned JEOL error -5: maximum logical unit number error Occurred during reading crystal"?

This error is documented here:

https://smf.probesoftware.com/index.php?topic=633.msg3695#msg3695

Dan Ruscitto had this error when he had to re-install the PFE/PI software and forgot to enter the JEOL Security code in the Probewin.ini file.

If so, what does it mean, and how did you troubleshoot and fix the problem? I was setting up a series of maps, and partway through "Read ELM" started failing (unresponsive; then was reading only 2 of 5 spectros...). I tried manually entering the data for each element, but the run crashed when I started. I've tried the usual solutions of closing all softwares, cycling power to OPE and also to the intelligence unit, installing latest updates of PfE and PI), using a back-up crystals.dat file (thinking existing one may have been corrupted), starting fresh with a new map acquisition file...but I'm not getting anywhere except that "Read ELM" functionality has been restored. I'm still getting that error when trying to launch a run.

This maximum logical unit error has nothing to do with the Crystals.dat file.  That file just defines the crystal names and 2d spacings for each crystal type.

This error is an error directly from the JEOL instrument when asking for the current crystal on a spectrometer.

Does PFE report a similar error?  I'm surprised a re-set of the intelligent unit didn't fix it.  These errors are almost always a hardware/firmware/network issue.

Let's work on this off-line and report the solution once we've got more data.  Please contact me by email directly.

[John Donovan]

Has anyone seen this error before when starting PI acquisitions (I'm using JEOL8530f):
"Probe returned JEOL error -5: maximum logical unit number error Occurred during reading crystal"?

This error is documented here:

https://smf.probesoftware.com/index.php?topic=633.msg3695#msg3695

Dan Ruscitto had this error when he had to re-install the PFE/PI software and forgot to enter the JEOL Security code in the Probewin.ini file.

If so, what does it mean, and how did you troubleshoot and fix the problem? I was setting up a series of maps, and partway through "Read ELM" started failing (unresponsive; then was reading only 2 of 5 spectros...). I tried manually entering the data for each element, but the run crashed when I started. I've tried the usual solutions of closing all softwares, cycling power to OPE and also to the intelligence unit, installing latest updates of PfE and PI), using a back-up crystals.dat file (thinking existing one may have been corrupted), starting fresh with a new map acquisition file...but I'm not getting anywhere except that "Read ELM" functionality has been restored. I'm still getting that error when trying to launch a run.

This maximum logical unit error has nothing to do with the Crystals.dat file.  That file just defines the crystal names and 2d spacings for each crystal type.

This error is an error directly from the JEOL instrument when asking for the current crystal on a spectrometer.

Does PFE report a similar error?  I'm surprised a re-set of the intelligent unit didn't fix it.  These errors are almost always a hardware/firmware/network issue.

Let's work on this off-line and report the solution once we've got more data.  Please contact me by email directly.

After a few days of communication with Henny we discovered that somehow (she has no idea how), the JEOL security number had been deleted from the Probe Image configuration dialog on her computer:



The security number was still available in Probe for EPMA, so she was able to copy that over to Probe Image and everything worked again.

The thing that confused us at first was that the error returned from the JEOL instrument when this security code is missing, was basically saying that it could not read the WDS crystal positions.  But we had pointed out that Dan Ruscitto had this same error when his JEOL security code was missing!

Doh!