Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DS18B20 value when in Task #4 returns always 0 #2891

Closed
tparvais opened this issue Feb 16, 2020 · 17 comments
Closed

DS18B20 value when in Task #4 returns always 0 #2891

tparvais opened this issue Feb 16, 2020 · 17 comments
Labels
Category: Plugin Related to supported sensors Type: Bug Considered a bug

Comments

@tparvais
Copy link

tparvais commented Feb 16, 2020

I observe that if I configure a DS18B20 in 4th row , the measure is always 0

I have this with different Wemos D1 Mini

When moving this snesor in another place, no problem

another sensor in that 4 row is not a problem neither (generic sysinfo for example)

Last Mega release be. of February. I only change the number of task from 12 to 24 in custom.h

Thomas

@uzi18
Copy link
Contributor

uzi18 commented Feb 16, 2020

so if you changed 12->24 tasks you need to wipe out configuration - they are not compatible thats why you have problems.

@tparvais
Copy link
Author

Hi can you be morte explicit? I don’t understand what I have to,do practically

@Domosapiens
Copy link

I have seen similar Task 4 problems:
#2786 (comment)
I resigned myself to it and moved the DS18B20 to another task number.

@uzi18
Copy link
Contributor

uzi18 commented Feb 17, 2020

first you need to flash blank.bin to your module and reflash new firmware, than reconfigure

@Domosapiens I guess gpio-16 is not well suited for dallas, try other gpios

@TD-er
Copy link
Member

TD-er commented Feb 17, 2020

Last Mega release be. of February. I only change the number of task from 12 to 24 in custom.h

Can you run meminfodetail from the command field on the tools page?
If you have executed that command, the next time you open the system info page, it will show a graphic layout of the settings file at the end of the page.
Just check there is no overlap in data segments in your settings file.

And like @uzi18 suggested, also make sure you don't use the wrong pins (probably nothing to do with this issue, just a generic remark)

If you have it in position 4, are there other instances of the Dallas plugin active?
If so, at what position?

I probably also replied something similar in the issue linked by @Domosapiens , but just as generic info about what happens in the ESP when processing tasks.
It will process the tasks in the order of the task ID. (rows in the table on the "Devices" page)
So if the first 4 tasks are using Dallas sensors, then it may be the time to process them is too short and may reveal a bug in the timing of that plugin.
By moving it lower in the list (and having another tasks in between) it may just have enough time to process the other sensors data.

So what you could do to test, is try to make task nr 4 the first Dallas task and see if that makes the bug move "lower" on the list of tasks.

@TD-er TD-er added Category: Plugin Related to supported sensors Type: Bug Considered a bug labels Feb 17, 2020
@uzi18
Copy link
Contributor

uzi18 commented Feb 17, 2020

please paste here screenshot from your devices/tasks configuration

@tparvais
Copy link
Author

how to interpret this ?
image

@tparvais
Copy link
Author

image

@TD-er
Copy link
Member

TD-er commented Feb 17, 2020

The layout of the settings looks good. (no overlap)
You can see by the numbers in the last column that the sections do not overlap eachother and the top line does show how the sections interleave in the settings file.
The bottom line of each type of section (represented with a color) does show how much of each section is used.

@uzi18
Copy link
Contributor

uzi18 commented Feb 18, 2020

it is curious why exactly 4th task is not working properly, because other works well.
please try to set for task 4th dallas address from eg. 10th and vice versa.
maybe something is wrong with sensor itself (fake/clone? )

@jimmys01
Copy link
Contributor

Those are a LOT of sensors. Topology and wiring is also play also a big part in the success of this endeavour. Bravo for making it work at all!

@tparvais
Copy link
Author

I of course try to change the sensor that was working perfectly . Only task#4 gives issue

@Domosapiens
Copy link

I guess gpio-16 is not well suited for dallas

gpio-16 is excellent for DS18B20 (3 other sensors proved it on this unit and 14 other units proved it)

Topology and wiring is also play also a big part

, yep, but not for this problem.

First you need to flash blank.bin to your module

...and what function has update OTA ?

So if the first 4 tasks are using Dallas sensors,

No ...never was the case

So what you could do to test, is try to make task nr 4 the first Dallas task

No, initially task 4 was the first Dallas task, but I needed to move it
.
.
.

The remarkable and common observation is:

Only task#4 gives issue

.....?

@uzi18
Copy link
Contributor

uzi18 commented Feb 19, 2020

ok so for now please try to exchange tasks configuration

@f4gqk
Copy link

f4gqk commented May 19, 2020

Good evening tparvais

I'm looking for the firmware that would have more than 12 devices.

It's for a heating project where I have 8 zones. Each zone needs two outputs on an MCP23017.

To be able to use my wemos and MCP23017 fully I need to know where I can download the new compiled and modified file.

thank you

Sebastien

@tonhuisman
Copy link
Contributor

Bonsoir tparvais

Please don't use Github issues for generic support requests, and please use English, as it is the common language here.
I have replied to your question in the forum.

@tonhuisman
Copy link
Contributor

Dallas temperature sensors have got a big overhaul some time ago so this issue can be closed.

@TD-er TD-er closed this as completed Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Plugin Related to supported sensors Type: Bug Considered a bug
Projects
None yet
Development

No branches or pull requests

7 participants