Hi Guys, Has there been any changes to PIO pin handling for DS28EA00s?
I hooked up another DS28EA00 Sensor with a Solid State Relay connected to one of the PIO pins and it all works except that a short time after I turn it on via the owhttpd Web GUI by writing a 3 to the PIO.BYTE to drive both PIO pins, the PIO.BYTE gets mysteriously reset back to 0. It seems to be fine while nothing else is running on the PC but if I have either temploggerd or my temperature control python script running (from cron every minute), the PIO.BYTE gets set back to 0. The sensor is defined in the temploggerd config file and is recorded and graphed correctly and my python script did not reference the sensor at all. One thing I did notice was that the PIO.BYTE get set back to 0 as soon as the python script started. I noticed this as the script prints out messages as it progresses and I was seeing the PIO.BYTE reset 0 before any messages or at the same time as the first message. I have other DS29EA00 sensors driving the same sort of Solid State Relays and they seem to all be fine. Is there any logging or debug facility that will help me to track down the cause of a DS28EA00 PIO.BYTE being reset back to 0? I was running 2.8p8 but upgraded to 2.8p12 and it still seems to have the same problem - very strange... Regards Alex Shepherd ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
