Error searching support
- Thread starter Efried
- Start date
How do you propose this would work? Since the sensors share a common data line, depending on bad sensor
behavior, one sensor could bring down the entire bus.
For systems with short cable lengths I include DIP switch to isolated each 18B20 - not so much for
troubleshooting but to help associate each with a Temp channel
/tom
behavior, one sensor could bring down the entire bus.
For systems with short cable lengths I include DIP switch to isolated each 18B20 - not so much for
troubleshooting but to help associate each with a Temp channel
/tom
Efried
Active Member
ok, thanks. Some quick connection would be also do.
There are some operational modes which could be tried out (one sinking 50 mA) and error codes..
http://files.maximintegrated.com/sia_bu/licensed/docs/1-wire_sdk_win/TMEX/hse1tmb.html
There are some operational modes which could be tried out (one sinking 50 mA) and error codes..
http://files.maximintegrated.com/sia_bu/licensed/docs/1-wire_sdk_win/TMEX/hse1tmb.html
CAI_Support
Senior Member
For a bad sensor bring down whole bus, the only way to isolate that bad sensor is to disconnect one sensor at a time, because there is just so much you can do for short circuit chip.
If the error is sensor itself not functioning, then look the GUI and found the sensor unique ID code that will help you to identify the bad sensor. Although MAXIM did not mark the sensor ID on the package, you can add a label with partial unique sensor ID on it. When GUI indicates which sensor failed, you can go find that sensor with unique ID and replace it.
If the error is sensor itself not functioning, then look the GUI and found the sensor unique ID code that will help you to identify the bad sensor. Although MAXIM did not mark the sensor ID on the package, you can add a label with partial unique sensor ID on it. When GUI indicates which sensor failed, you can go find that sensor with unique ID and replace it.
