Hello,

Looking for advice/info from users of the Admesy Spectro/Colorimeters. They seem to be very competitively priced.

Has anybody used the Hera spectro and has some insights on his precision, reliability and possibly some quirks it might have? With 2.3 nm bandwith can it be used to profile the new technologies (QD-OLED, new laser projectors)?

From the three colorimeters PCM2-100, PCM2X-270, PCM2X-271 which one do you think has the best price/performance ratio? Also some insights on precision, reliability and possibly some quirks they might have? There is so little info about this colorimetres from real users....

Thank you,
Cristian

Not really sure what to say.
They basically perform as expected.
As for which is the best price/performance, that is really down to your specific needs vs. the prob's specification.

Steve

Well, I ordered a Hera spectro so I will report some real user experience in the future.

Now I have an LTE licence and from what it seems the PRO version is cheapest to support the Admesy Hera. Correct?
What I don't understand is that from the documentation the PRO version (which is almost 4 times more expensive than LTE) seems to loose support for specific manufacturer internal probes (which LTE has). So in PRO version I will loose the abiliy to control the EIZO internal probe on my CG319X?

Not sure where you saw that info, but no, PRO doesn't lose any LTE features or capabilities.

The 'manufacturer' LTE or PRO license levels do obviously have such restrictions.

Steve

My bad, but what "except alternative manufacturer specific" means?

Screenshot

That is for the 'Manufacturer Specific' license levels, as said.
So if you were to purchase an ASUS manufacturer specific license, it will NOT work with EIZO, Dell, etc inbuilt probes.
It will also ONLY generate LUTs for uploading into an ASUS monitor, not for use elsewhere.

Steve

Ok, I have a Hera unit on my desk. Using CS PRO
With patchsets lower than roughly 3,5 nits Hera will report 0. According to specs should go as low as 0,05 nits.
Strangely this unit reports fw 1.19 which is the last one listed on the website. But your guide shows a Hera with fw 1.28

1

2

Sorry to say, no idea.
ColourSpace just reports exactly the value that any probe sends.
And as for the firmware, you will have to ask Admesy that.

Steve

Their software (Iliad) reads flawlessly on this probe and firmware as low as 0.08 nits which is how low this display can go.

Does the Iliad software report the same meter settings as you are using in CS? That can make a definite difference, especially on measurements at lower luminance.
Also, Admesy has an alternate driver for use only with ColourSpace and one of its competitors, although both can use the NI-VISA driver the Iliad software installs.You might try that as well.

RollsRoyce

Ok, this is something completely new to me. What alternate driver? From where? I am using the NI-VISA drivers.
Do you have a Hera spectro?

No - the drives will not change any probe readings.
The two different drivers are totally interchangeable.
(We are not actually sure why there are two different drivers... something to ask Admesy.)

But any issues with readings are down to the probe and the settings used, because as stated ColourSpace just reports the data the probe provides.

Steve

I made a test. Sending full black to an EIZO CG319X with a REC709 100 nits calibration. This display usually goes as low as 0,08 nits when set to 100nits.
Hera spectro is quoted to go as low as 0,05 nits. So I am not measuring something out of specs.

In screenshot 1 you see 20 measurements with auto-range set to OFF. Of course they are all over the place in terms of luminance. What you see on the left are the Hera settings after a cold start (POWER OFF THEN ON).

In screenshot 2 you see 20 measurements with auto-range set to ON. Very stable luminance, around 0,08 nits. The only thing I changed was auto-range to ON.
SP.Int.Time is dynamically changed by the probe. I did not touch that control. But from what I see it settles to 1 sec. Actual measurement time is always 20 secs.

My observations:
' Every measurement done in Iliad, regardless of the setting of auto-range, returns a result. This does not happen in CS, roughly below 3,5 nits.
- Frequency (Hz), Adjmin (%), Max Int. Time (μSec) - this 3 parameters are not present in Iliad

This is something you will need to discuss with Admesy.
ColourSpace uses their API, and all values ColourSpace reports are from the probe.
But I would check the setting you have in the ColourSpace menu for Admesy.

Steve

Can you confirm that the Hera you used for writing the code in CS had fw. 1.28 as in the screenshot used in your guide?