Change in the Bitbang Trigger calculation #62
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have modified the trigger calculation. According to the Intenet there is a difference in the trigger time for the DHT11 and DHT22. This is take into account in the library in the Child classes with the parameter
However, this is not calculated for the Bitbang portion, and the time used is the time normally used for the DHT22 sensor.
Calculation when pulling the line down to start the lecture will be calculated according to the
self._trig_wait
parameter that depends on the sensor usedOld C library different time, maybe that is why for a lot of people this works better. (if interested see this https://github.com/jposada202020/DHT_Investigation)