I've started integrating a recent JRE into the installer for Windows to ensure that a compatible JRE is available.  Unfortunately, Oracle (the current owner of Java) won't provide JRE's later than 8 without you parting with a little bit o' cash.

Domingo,
    It can be done through the scripting interface.  The trick is creating a detector for each separate stream of data (Char, Brem, Brem Secondary, Char Secondary).  The scripting interface in mcSimulate3 is designed to connect many different types of detectors (Voxellated, PhiRhoZ, Generation Images, EDS-like) to the source of x-ray production (Char, Brem etc.) through the XRayTransport3 class which takes the x-rays from the generation point to the detector through any intervening material.

   What you will want to do is to add more EDS-like detectors.  Currently the (one) EDS detector is passed into mcSimulate3.base.  The current implementation of detectors only allows a detector to accumulate one spectrum.  You'll have to create multiple identical detectors (using File->Preferences) and hook each one up separately to the source you want to measure.  Sources can go into multiple detectors so it is possible to collect arbitrary combinations of mechanisms.   You'll need to modify mcSimulate3.base or something similar to handle multiple detectors.  The code in this function should provide all the hints you need to accomplish this.

Nicholas

I'm guessing Nicholas is dealing with all the "work from home" fun we are all having with covid-19

The answer to your question was at the bottom of tbe python source code he sent you:

 result["Fit"] = sf.getBestFit()  i.e. the best fit spectrum (the fit to your peaks, given the composition you input)
 result["Char"] = sf.getCharacteristicSpectrum() i.e. the characteristic spectrum (your peaks of interest minus background)
 result["Brem"] = sf.getBremsstrahlungSpectrum()  i.e the getBremsstrahlung spectrum (background)

Hope this helps until everyone is back to normal

Best regards,
John Minter

Thanks Anette and Karsten!

I've seen the behaviour you describe, Anette, in both the probe in Denver (which was fixed somehow) and the new one here in NZ especially when trying to go towards very high contrast settings. The image absolutely blacks out and I have to go to the contrast and brightness sliders in order to turn the brightness up sufficiently to get the image back without having to turn the brightness knob many, many times! My issues is more like what Karsten described. I have a perfectly good image and during X-ray mapping + COMPO the image is acquiring just fine then with go black so I'll have a partial BSE image and completed X-ray map images. I have also seen this behaviour also when just navigating around and/or acquiring images. Since many of the samples I've been looking at are volcanic in origin I often get very bright bubbles and holes where charging happens because the carbon coating is lacking in those areas.

I will have to contact JEOL but if it requires a main board replacement then I suspect I will have to live with it for quite some time since the NZ and Australia borders are closed for the time being.

Thanks again!!

Yes, I think all 8530FPlus BSE have that (I was told part of the "Plus" is a new BSE detector). They actually do not shut off but the link between contrast and brightness level is incorrect when you switch to a different gain level and the image goes pitch black because the brightness is so off.

If you use the mapping dialog in the JEOL software, you can actually read out the absolute values for contrast/brightness and see that. You will see that when the detector "shuts off" it changes the brightness level by an order of magnitude down, let's say from a 2000 value to 200. The correct value for brightness is somewhere between 50-30% instead of 10% of the original one. Cycling through the signals somehow seems to go to a different stored brightness level. If you just reduce the contrast, you usually get the image back as well.

I strongly suspect that JEOL is using the old settings for the previous BSE detector and didn't update the installation documentation for the new one but that is just my personal assumption.

Short term solution: Microscope light off (in case you don't already do that) when mapping and in general stay away from the transition point in the contrast levels either by going above or below the values in the settings. Charging (like porous samples that have not enough thick coating) exacerbates this behavior.

Long term solution: Talk to your old Denver service guy (Ken?). He fixed it on the Denver probe according to Heather. I haven't been able to do that yet on mine because the machine was so booked out. I assume that there are some hardware switches to set or something. I couldn't find anything in the software itself.