Tom,
Yes, the node red ignores the value after decimal, node js doesn’t not handle floating point values very well.
but if you use the Deprecated: Channel 1 Current Calibration Value section it wont ignore that. keep in mind the calibration value needs to be multiplied by 100. can you share a screenshot of your sensor config window in node red ?
We are using the Deprecated: Channel 1 Current Calibration Value section, and the latest post reflects that. So it does seem to be ignoring the decimal.
Multiplying the calibration value by 100 does not make sense to me.
As you can see from the detailed testing, we are consistently measuring a current that is supposed to be 45.6 amps (as measured by an independent CT clamp). To get the NCD Sensor to report this value, the calibration factor has to be greater than 1 (which reports 32 amps) and 2 (which reports 57 amps).
I just tried setting the cal factor to 182 (182*100), and I got the following (the sensor is reporting 4601 amps, which is 100x what it should be).
So my theory is still sound - the cal factor should be around 1.82 for this sensor to work.
Screenshot and table attached.
| Calibration Value | Real Amps | NCD Sensor Amps | New Calculated Calibration Value | Difference in Amps | Comments |
|---|---|---|---|---|---|
| 182 | 45.8 | 4601.979 | 1.8113077 | 100.4798908 | Now trying multiplying by 100 |
| 182 | 45.7 | 4543.44 | 1.830639339 | 99.41881838 | Srtill an issue |
Yea looks like its multiplying by 100.
quick solution will be divide the current value by 100 in node red or on cloud side while we look into lib.
Thank You Bhaskar. We will hold in deploying this sensor for now until we get an update, as access to site is limited if sensor is deployed.
Hi @Bhaskar just following up on this - any timelines on your end for a fix?