That is a direct lie.

And if you respond like this when people are trying to help, you really have to consider how interested people will be in really helping you.

The manufacturer documentatin shows generic code for using the sensor. The reason you haven't used this code is that you have either not taken the time to check what samples they have - or you are not interested in generic code but want code specific for you. But code specific for you can't exist without you also having a specific design.

The easiest way to access the sensors is most probably to buy a gateway, interfacing to a PC using USB, Ethernet, a serial port or similar. Then a small PC program can access the sensor and present the information on the display. And also write down information to a file in case you want to see component variations (which of course means that you need a controlled environment so the environment isn't the main cause of the variation).

Whenever you do write "not applicable", it is YOUR responsibility to spend two-ten sentences explaining why an answer isn't applicable. Hiding your head in the sand won't get you anywhere.

You still haven't discussed how the sensor is powered, or cable length. How the sensor is encapsulated (or isn't it?) may also be very significant to the testing. For example - the time constant can vary a lot if the mass of the sensor assembly varies a lot.