1-Wire Feature Request: UV Sensor using a single calibration value

Ask a Question
,
21

Thanks Windy.

Graeme

22

Brian, I have been testing this today and have been seeing equivalent to 6.8% rH on the 1-WireViewer and 4.97V on Ch0 and 1.06v on Ch1 and 0.0017V in Ch 2, the same channel I see 150mV for Solar.

So for Ch1 giving 1.06v corresponding to 8.1 to 8.7%Rh while we had a max UV of 6 measured of a range of say 15 then it needed perhaps a different range in resistor network for a max of 3.0V (the Honeywell sensor for humidity cannot have a linear output if can measure to 100% at 3.0V which I think is the max A-D range output) but recoding from 8% to say UV6 all I needed to do was x0.79 or so or if supposed to use a divisor to get 0.08 (=8%) to give a value of 6 then x79.0 would give a true integer readin I tried everything. BTW, WD always picked up the new chip’s ROM ID which was transposed into the UV sensor box in Dallas 1-wire.

After every factor change, I went back to Main Save page, resaved and waited for the ibutton cycle check and then went back for a value and there never was a change.

Now I have tried all sorts of factors in there to see whether it was a divide or multiply factor.

The odd thing is: no matter what constant i used, large or small, it has always said just-

[size=100]Raw value: v ,0.0 UV [/size]

And this signal was equivalent to 8%rH, sure a low figure but volts were 1.06v out of 3V range on the AD input to the DS2438Z chip. So it just needed a slight adjustment to give a correct UV figure.

Is there a parameter format wrong there? An added comma? Is there supposed to be a “V” value shown?

I may be able to trial again tomorrow, or at the end of any day.

Thanks

Graeme // Derek Chapman (StokesValleyWx)

(I am using Derek’s board and it is working) It is a low value but there is a signal.

23

Brian, had you missed this post? I am on vacation at home for a week so can do further trials as needed and the sun will be out each day (I hope…)

24

Brian - could you check to see if something is amiss with the display of the data for this new feature? I knew you were very busy since Easter and had not pressed for this to be answewred.

25

use a new .zip update, ready now