All instruments (eg Neo) are calibrated for:

1. Dark current
2. Linearity
3. Wavelength

When an instrument is used for relative measurement (Neo Transmission measurement kit, Neo Cuvette measurement kit) no absolute calibration is needed and therefore is not carried out.

customer (Innolux) feedback who use DMS:

• very expensive
• many options, but also some limits
• closed system → this is unwanted, here they prefer Admesy which allows easy integration to customer software
• every 50 hours recalibration (lamp) needed
  

When a window of a program is not visible or the top is hidden outside the display area, so it can not be moved by click-and-drag on the title bar there is a trick how to be able to move the window which is (partly) outside the displayed area.

1. Press the two keys 'Alt'+'Space' together, then release the keys → this will pop-up a menu, which you will not see, but is there
2. Press m-key and release the key (this selects the M for _m_ove from the hidden pop-up menu)
3. Press and release arrow key (does not matter which), for example down-arrow-key
4. Then you can move the mouse around. It will have the window "attached" to the mouse and in that way you can move the window in the visible display area (just move the mouse around a bit till you see the window).

This works on an English system. Not known if it will work in other languages as well. You might need to use another key instead of m for 'move' possibly.

Stereopes LED does not use PWM to modify the output, but rather current.
Crius LED does not use PWM currently [2023-05-04], but will make use of PWM in future versions.

The fiber used for Neo Display (for example to attach a 10 mm lens) is the standard fiber for Neo.

Default

Numerical aperture = 0.22
Core diameter = 800 µm

Other versions possibly available on request.

There are two fiber options for the IFC connector. One type is for Neo and the other type for Prometheus colorimeter with 10 mm lens. The fibers must not be interchanged due different optical properties.

Fiber Prometheus: multi-core, NA 0.37
Fiber for Neo: single-core, NA 0.22

Due the different NA (Numerical Aperture) one can differentiate the fibers.

There are no different fiber options for the Prometheus. A Prometheus fiber is built and calibrated with our own IFC fibers. SMA or other fibers are not possible and would also bring no benefit.

The fiber order code describes the exact type of fiber. Not all fibers we use are the same, they have different optical properties. For Prometheus there is only one fiber we offer, currently in the length of 2m. The fiber is different from the fiber we use for Neo, but both use the IFC coupling piece.

[2023-05-09]

Example for standard M8 and Neo fibers

The default fiber has a 800 µm core diameter. For a moment the fiber can be bend up to a radius for 40 mm. Long-term minimum bending radius is 240 mm.

On the website only generic customer firmware versions are listed. Customers versions are available, if not shared directly, they can be requested from manager RnD.

When the listed firmware number is not consecutive, the firmware is only released for specific customer only or revoked for usage.

Example: version 1.1,1.2,1.4 are release on website. This list is missing 1.3. This firmware is revoked, or only updates are included for specific customer versions.

2 filter wheels with 5 positions each

First wheel: XYZ + shutter + 1 free position
Second wheel: ND filters

Titan: fixed lens (and distance)

Helios Y: several lens options

Helios XYZ: limited lens options

No, Prometheus Suite will not support older colorimeters or instruments.

The correct spelling is 'Light Meter', but 'Spectrometer' ;-) For a nicer look we use Lightmeter in the logo. In all other locations we use the correct spelling 'Light Meter'.

All our spectral instruments are spectroradiometers, but to be better visible for search engines and the like we use the generic term 'spectrometer' on a high level (advertisements, headlines, general statements about our series). For a technical description in publications, like leaflets, manuals or whitepapers we use the word 'spectroradiometer' in the text.

No, lenses with IFC for Neo and Prometheus Colorimeter are different and must not be interchanged.

The fiber used for Neo Display (for example to attach a 10 mm lens) is the standard fiber for Neo.

There are two fiber options for the IFC connector. One type is for Neo and the other type for Prometheus colorimeter with 10 mm lens. The fibers must not be interchanged due different optical properties.

Fiber Prometheus: multi-core, NA 0.37
Fiber for Neo: single-core, NA 0.22

Due the different NA (Numerical Aperture) one can differentiate the fibers.

The fiber is completely filled out (with light), therefore the performance is the same here.

No, lenses with IFC for Neo and Prometheus Colorimeter are different and must not be interchanged.

There are two fiber options for the IFC connector. One type is for Neo and the other type for Prometheus colorimeter with 10 mm lens. The fibers must not be interchanged due different optical properties.

Fiber Prometheus: multi-core, NA 0.37
Fiber for Neo: single-core, NA 0.22

Due the different NA (Numerical Aperture) one can differentiate the fibers.

There are no different fiber options for the Prometheus. A Prometheus fiber is built and calibrated with our own IFC fibers. SMA or other fibers are not possible and would also bring no benefit.

The fiber order code describes the exact type of fiber. Not all fibers we use are the same, they have different optical properties. For Prometheus there is only one fiber we offer, currently in the length of 2m. The fiber is different from the fiber we use for Neo, but both use the IFC coupling piece.

[2023-05-09]

The typical Fs error is well below 3%, around 2% to 2.5%.

No, Prometheus Suite will not support older colorimeters or instruments.

16 bit AD chip, where 15 bits are used

Standard warranty is 1 year. This can normally not be extended. For large volume orders where a customer asks for (paid) warranty extension check with the headquarter if and for which conditions this might be possible.

There is no direct import function in Iliad or Prometheus Suite. What one could do is write an own program, import the data there and use our Admesy_Colour.dll, see the documentation in our SDK and Admesy_Colour_DLL_Manual.pdf

We do not have experience with cRIO, but in general PLC’s will work with the following protocols:

• USBTMC host support
• Ethernet via a socket protocol (IP adress + poort)
• RS232

The autorange function does use the raw spectrum of the complete CCD to determine if the autorange parameters are met. Therefore a peak which is outside the chosen wavelength range (chosen in the software), but within the wavelength range of the sensor, will affect the integration time and reported saturation. This can not be changed, due blooming of sensor pixels to neighbor pixels. When that use case is important for a customer, they can use a filter to cut off unwanted wavelengths.

Likely the low pass frequency is set to 0. You need to change that to the relevant frequency, for example 60 Hz (see screenshot). This can be either done by using Iliad and changing the startup settings there (Device - Startup settings) and save ('Write settings').

Another option is using the following commands:

:EEPROM:conf:lpfreq frequency_hz
And after that
:EEPROM:STARTUP:WRITE

To use Admesy (or most other instruments as well) one needs the Instrument Control Toolbox.

Long negative error codes are typical NI-Visa errors. See the following reference:

[2023-01]

a) Mac OS 10.13 and 10.14
b) from 10.15 and newer versions (11, 12).

For Apple Silicon (M1 and M2 processors) there is no “official” support but it is found to be working with Rosetta 2.

An installer for NI VISA is available from the downloads section.One needs to choose the correct version, see the readme (PDF).

https://www.admesy.com/documents/iliad-macos/

Note: on macOS 12 one will get two “error” boxes when starting iliad, then click continue. All should work from then.

Stereopes LED does not use PWM to modify the output, but rather current.
Crius LED does not use PWM currently [2023-05-04], but will make use of PWM in future versions.

The luminous flux is not specified, but the bare LED has an output of 70 lumens. Due the internal losses the output is likely in the range of 10 to 15 lumens. Note: this is just an estimation of the output and nothing spec’d or promised. To determine the actual output one would need to make a luminous flux measurement, typically in an integrated sphere.

The issue is in relation between firewall and the network connection. To resolve this sleep issue, one must allow all connections in the firewall. Please note that if you are creating an own software this application also needs all 3 firewall domains open.

• Calibration data storage

1. Camera calibration

• .mcal are camera calibration files (factory) and are not changed!
• Titan.json includes the user camera calibration. So, if there is a need to transfer the calibration to another PC this file / data should be moved to the other PC.
• Please note that after calibration, on exit the user must choose to save the settings, else data will be lost.

1. Spotmeter calibration are stored in the Titan, at user defined slot.

1. ProgramData

• having restricted rights:
• Logged in user does not want to use another user data. Therefore, this is not the place.
• Local is chosen as for roaming it is too much data.
• We are debating internally if data should be moved to a different folder (documents for example), but for now we keep it here.

1. 1. 1. user can read data and execute
      2. user can create and write data, but this cannot be changed by any other user. Therefore making is not usable to store the data we are referring to!

1. 1. 1. Where the downloaded camera files for example could be placed there, noting point 2.a.2 they cannot remove the files is another user created them.

• Appdata:
  
  i. Local is chosen as for roaming it is too much data.
  ii. We are debating internally if data should be moved to a different folder (documents for example), but for now we keep it here.

We only use F2.0, which is fixed during production.