Clik here to view.
emonTH pulse counting firmware error
@digbyt wrote: I have an emonTH bought from the openenergymonitor.com shop (order 11461, 15 Feb 2016) which I believe came with firmware V2.6 installed. It was supplied with a DHT22 and external...
View ArticleemonTH pulse counting firmware error
@glyn.hudson wrote: Hi Digby, Thanks for reporting this issue. I’m trying to understand the fix you are suggesting. Would this not have a significant detrimental effect on battery life? I will need to...
View ArticleemonTH pulse counting firmware error
@digbyt wrote: Hi Glyn, If 'Sleepy::loseSomeTime() returns 0 then it returned before the watchdog expired, so the effect of my change should be to extend the sleep if it is interrupted by a pule....
View ArticleemonTH pulse counting firmware error
@glyn.hudson wrote: Yes, please attach to this thread Read full topic
View ArticleemonTH pulse counting firmware error
@dBC wrote: Possibly unrelated, but your mention of spurious temperature readings reminded me of this bug that I reported a while back and failed to follow up on:...
View ArticleemonTH pulse counting firmware error
@Robert.Wall wrote: D’Oh! I meant to chase that one down, but I’ve been busy, and it had slipped my memory. Read full topic
View ArticleemonTH pulse counting firmware error
@dBC wrote: Actually, I think the deal was I was supposed to remind you, but I tend to report them and move on. Is there a more official channel for reporting coding errors? Read full topic
View ArticleemonTH pulse counting firmware error
@Robert.Wall wrote: I don’t think there’s any official channel. Having been brought up (properly) in industry where there is somebody called the Design Authority, who is responsible for the design,...
View ArticleClik here to view.
emonTH pulse counting firmware error
@glyn.hudson wrote: Robert.Wall: I don’t think there’s any official channel. A github pull request is the best way to submit a bug fix. That way we can review the changes, test, comment and merge the...
View ArticleClik here to view.
emonTH pulse counting firmware error
@dBC wrote: glyn.hudson: A github pull request is the best way to submit a bug fix. I wasn’t trying to submit a bug fix, I was trying to report a bug. I’ve no idea what the correct solution is, and...
View ArticleemonTH pulse counting firmware error
@glyn.hudson wrote: Github issue on the repository in question is the best way to officially submit a bug report. However it’s a good ideas to post on the forum first to confirm that it’s actually a...
View ArticleemonTH pulse counting firmware error
@Robert.Wall wrote: I think it is deficient coding - the error handling is poor. If that’s how you define a bug, it’s a bug. @pb66 has suggested expanding the error code, and I’m in complete...
View ArticleClik here to view.
emonTH pulse counting firmware error
@digbyt wrote: Hi Glyn, Sorry for the slow follow up. I was expecting to get an email when any new posts appeared on this thread, but either I didn’t configure things correctly, or the message went...
View ArticleemonTH pulse counting firmware error
@dBC wrote: Robert, which library do you mean? The Arduino Dallas temperature library does return: hash-define DEVICE_DISCONNECTED_C -127 when there’s a checksum error. get_temperature() accidentally...
View ArticleemonTH pulse counting firmware error
@Robert.Wall wrote: I hadn’t looked at the library, all I looked at was the call to it. But I do know that 85 °C is the default scratchpad value that can be returned, and that needs looking into too....
View ArticleemonTH pulse counting firmware error
@dBC wrote: Did you see my original report (linked above)? It goes into some detail of the failure mechanism, but perhaps not enough, or perhaps not clearly enough? Read full topic
View ArticleemonTH pulse counting firmware error
@Robert.Wall wrote: I did read it at the time, but it meant nothing without looking at the library code itself. That’s what I haven’t had time to do yet. From what you’ve written, it looks as if the...
View ArticleemonTH pulse counting firmware error
@dBC wrote: Yes, I think that would work, but it may be over-complicating things. Perhaps my bug description over-complicated things. All you really need to know about the library is that it returns a...
View ArticleemonTH pulse counting firmware error
@Robert.Wall wrote: If we’re changing anything, the “85 °C” problem needs looking at as well. Read full topic
View ArticleemonTH pulse counting firmware error
@dBC wrote: Fair enough. I’m pretty sure the library doesn’t know about that problem. It returns whatever it gets back from the h/w or -127C if the checksum fails. Given the total ambiguity of an 85C...
View ArticleemonTH pulse counting firmware error
@Robert.Wall wrote: I’m not sure that even the sensor knows that! I think it will come either from incorrect use, i.e. the sensor is powered and then read without being asked to do a reading (85 is...
View ArticleemonTH pulse counting firmware error
@Robert.Wall wrote: No such luck! int get_temperature(byte sensor) { float temp=(sensors.getTempC(allAddress[sensor])); return(temp*10); } Taking all the tests out as above, I can provoke a “-127...
View ArticleClik here to view.
emonTH pulse counting firmware error
@glyn.hudson wrote: Sorry for the delay. I Can confirm I can replicate the issue with humidity reading being affected by the pulse count, interestingly the temperature reading from the DHT22 is not...
View ArticleemonTH pulse counting firmware error
@glyn.hudson wrote: @digbyt would it be possible for you to submit a GitHub pull request with your proposed changes to the sleep function? I’ve just taken a look at your code and there are quite a few...
View Article