Printable View
First my hardware:
Attachment 7043
Now my Conductivity probe (PL) settings:
Attachment 7044
Conductivity graph:
Attachment 7045
Problems:
(1) Profilux records data, but does not record the unit of measurement.
(2) When data is graphed, there is no unit of measurement ... and, the data appears to fluctuate significantly (with water temperature?). Should show a pretty much straight line.
Did you checked this checkbox?
Attachment 7054
If you change the unit in the midle of the record you get different values.Quote:
When data is graphed, there is no unit of measurement ... and, the data appears to fluctuate significantly (with water temperature?). Should show a pretty much straight line.
Yes, the box was checked ... all of the other probe measurements have the units included.
The measurement units have not been changed since the probe was setup ... those graphed results would seem to need many changes to the units over a short period of time through the night.
Did you opened the saved file with an editor and there is no units in the file?Quote:
Profilux records data, but does not record the unit of measurement.
We can't reproduce your problem.
Attachment 7061
Tested it with the ProfiLux here and the units are saved.
Well, as you can see, the problem exists.Quote:
Originally Posted by Artur
The txt file is recorded with units ... the other question, why the huge swings in the data?
Attachment 7072
Attachment 7073
Here are the latest data of temperature (C) and conductivity (kg/L):
(1) there are still no units displayed for the conductivity graph, and
(2) why the swings in the conductivity data ... is it related to temperature? How can I prevent this occurrence?
Thanks.
Attachment 7083
I am sorry for the missunderstanding, yes i can see that there are no values in the graph.Quote:
there are still no units displayed for the conductivity graph, and
We will check it and fix it with the next GHL Control Center version.
Thank you, Artur.
Any response to the second part of my previous post:
(2) why the swings in the conductivity data ... is it related to temperature? How can I prevent this occurrence?
Sorry but I can't tell you what it could be, i will forward it to my colleagues.