[collectd] onewire plugin does not allow family code 28
Hello List, i try to work a bit with the one wire sensor DS18B20+ The Problem with the DS18B20 is: he has a family code of 28..not 10. So the onewire plugin seems to ignore the sensor. The man page says Currently only temperature sensors (sensors with the family code 10, e. g. DS1820, DS18S20, DS1920) can be read. If you have other sensors you would like to have included, please send a sort request to the mailing list.. And here it is Setup: Hardware: DS9490R + 1xDS18B20+ Software: gentoo 64bit with 3.15.5 kernel + owserver -u + collectd 5.4.1 from official portage tree. Start owserver simple with owserver -u Testing if he is working: owget returnes: /28.100x /81.Ax000 /bus.0 /settings /system /statistics /structure /simultaneous /alarm owget /28.100x /28.100x/address /28.100x/alias /28.100x/crc8 /28.100x/die /28.100x/family /28.100x/fasttemp /28.100x/id /28.100x/locator /28.100x/power /28.100x/present /28.100x/r_address /28.100x/r_id /28.100x/r_locator /28.100x/temperature /28.100x/temperature10 /28.100x/temperature11 /28.100x/temperature12 /28.100x/temperature9 /28.100x/temphigh /28.100x/templow /28.100x/trim /28.100x/trimblanket /28.100x/trimvalid /28.100x/type owget /28.100x/temperature12 25.9375 So1wire natively works, but not with collectd onewire plugin. some testings with the onewire plugin offers Device -s localhost 4304 -- works better than localhost:4304. # Sensor 10028505/ # Sensor 28.10028505/temperature # Sensor 28.10028505 fasttemp Sensor 28.10028505 result: onewire plugin: OW_get (/) failed. status = 0x; different testings, with or without the hardware ID, with or without the familiy code, with or without the special attribute temperature or temperature12 won´t work. always the same error. Can someone help me ? thorsten ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
[collectd] Onewire Plugin
Hello, found this (verry old) discusion about the onewire plugin for collectd. A small way to get a lot of sensors to work and automatic datacollection will be to extend the onewire.c file for more than one type. I have test this only with the type 28, but this was working also for me and i suggest that this will work ever. I have extend the selection for all 1-Wire devices what bring a “temperature” as result in my patch (attached). Maybe with that the go ahead of the rework of the onewire-plugin will come. Best regards, Roland Franke onewire.c.patch Description: Binary data ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Onewire Plugin
Hi All, Thanks Tomas - all is working. I'm afraid I didn't go with your patch in the end (mainly because I lost the ability to automatically read a sensor without specifically including the path location in the configuration). However, it pointed me in a direction which enabled me to cobble together a working solution. Apart from a very minor patch to the onewire module, most of the time was spent on OWFS. i really didn't like the way this made the readings available (under a sub-directory). Reading the comments, I suspect that this is a OWFS design problem, rather than collectd. If ever I get the time, I might look into this a bit more. Since i am looking at a large system, hints tips prior to this welcomed. Best regards, Phil On 13 January 2012 17:36, Phil White manx@googlemail.com wrote: Hi Tomas, Thanks - I'll have a look over the weekend, and let you know how I get on. Cheers On 13 January 2012 16:52, Tomas tomasa...@googlemail.com wrote: Hi Phil, you could use my patch - see http://mailman.verplant.org/pipermail/collectd/2011-November/004810.html This would solve your problem with device family 28 (had the same problem). For the other device with 7E you can use the other option which offers the patch - to use direct accss by specifying the whole OWFS path (also documented in the patch). Or just use it as an inspiration :-) Best regards, Tomas On 13/01/2012 14:55, Phil White wrote: Hello all, Long ago, I looked at collectd and 1-wire monitoring, and never progressed because I had problems with owfs, and because of the plugin's 'experimental' status (though I do use collectd for other monitoring). I revisited the issue the other day, and still can't get things to work (though for different reasons). I have DS18B20 as my temperature sensors, rather than the DS18S20 that the plugin appears to recognise. These report themselves as a device with the prefix '28', rather than 10 - therefore collectd does not record data from these sensors. Now, I'd rather like to have a play with the plugin, and attempt to get this working. Rather than just submit a request, I'd rather like to get my hands dirty, and fix it myself. Just because I have never done any coding in C really shouldn't stop me, should it?! Another reason being that I also have a device prefix '7E', which is somewhat different, and I'd also like to see this one recognised. Therefore, can someone offer some 'beginners tips' as to how I'm going to start on the '28' issue - advice info? Which files, and what I need to do in order not to break anything? Many thanks, Phil ___ collectd mailing listcollectd@verplant.orghttp://mailman.verplant.org/listinfo/collectd ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
[collectd] Onewire Plugin
Hello all, Long ago, I looked at collectd and 1-wire monitoring, and never progressed because I had problems with owfs, and because of the plugin's 'experimental' status (though I do use collectd for other monitoring). I revisited the issue the other day, and still can't get things to work (though for different reasons). I have DS18B20 as my temperature sensors, rather than the DS18S20 that the plugin appears to recognise. These report themselves as a device with the prefix '28', rather than 10 - therefore collectd does not record data from these sensors. Now, I'd rather like to have a play with the plugin, and attempt to get this working. Rather than just submit a request, I'd rather like to get my hands dirty, and fix it myself. Just because I have never done any coding in C really shouldn't stop me, should it?! Another reason being that I also have a device prefix '7E', which is somewhat different, and I'd also like to see this one recognised. Therefore, can someone offer some 'beginners tips' as to how I'm going to start on the '28' issue - advice info? Which files, and what I need to do in order not to break anything? Many thanks, Phil ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Onewire Plugin
Hi Phil, you could use my patch - see http://mailman.verplant.org/pipermail/collectd/2011-November/004810.html This would solve your problem with device family 28 (had the same problem). For the other device with 7E you can use the other option which offers the patch - to use direct accss by specifying the whole OWFS path (also documented in the patch). Or just use it as an inspiration :-) Best regards, Tomas On 13/01/2012 14:55, Phil White wrote: Hello all, Long ago, I looked at collectd and 1-wire monitoring, and never progressed because I had problems with owfs, and because of the plugin's 'experimental' status (though I do use collectd for other monitoring). I revisited the issue the other day, and still can't get things to work (though for different reasons). I have DS18B20 as my temperature sensors, rather than the DS18S20 that the plugin appears to recognise. These report themselves as a device with the prefix '28', rather than 10 - therefore collectd does not record data from these sensors. Now, I'd rather like to have a play with the plugin, and attempt to get this working. Rather than just submit a request, I'd rather like to get my hands dirty, and fix it myself. Just because I have never done any coding in C really shouldn't stop me, should it?! Another reason being that I also have a device prefix '7E', which is somewhat different, and I'd also like to see this one recognised. Therefore, can someone offer some 'beginners tips' as to how I'm going to start on the '28' issue - advice info? Which files, and what I need to do in order not to break anything? Many thanks, Phil ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Onewire Plugin
Hi Tomas, Thanks - I'll have a look over the weekend, and let you know how I get on. Cheers On 13 January 2012 16:52, Tomas tomasa...@googlemail.com wrote: Hi Phil, you could use my patch - see http://mailman.verplant.org/pipermail/collectd/2011-November/004810.html This would solve your problem with device family 28 (had the same problem). For the other device with 7E you can use the other option which offers the patch - to use direct accss by specifying the whole OWFS path (also documented in the patch). Or just use it as an inspiration :-) Best regards, Tomas On 13/01/2012 14:55, Phil White wrote: Hello all, Long ago, I looked at collectd and 1-wire monitoring, and never progressed because I had problems with owfs, and because of the plugin's 'experimental' status (though I do use collectd for other monitoring). I revisited the issue the other day, and still can't get things to work (though for different reasons). I have DS18B20 as my temperature sensors, rather than the DS18S20 that the plugin appears to recognise. These report themselves as a device with the prefix '28', rather than 10 - therefore collectd does not record data from these sensors. Now, I'd rather like to have a play with the plugin, and attempt to get this working. Rather than just submit a request, I'd rather like to get my hands dirty, and fix it myself. Just because I have never done any coding in C really shouldn't stop me, should it?! Another reason being that I also have a device prefix '7E', which is somewhat different, and I'd also like to see this one recognised. Therefore, can someone offer some 'beginners tips' as to how I'm going to start on the '28' issue - advice info? Which files, and what I need to do in order not to break anything? Many thanks, Phil ___ collectd mailing listcollectd@verplant.orghttp://mailman.verplant.org/listinfo/collectd ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
