and it does switch the correct outputs. So there is no big-little-endian-mixup at this particular point!
On 11/05/2012 12:32 PM, Silvio Schmieder wrote: > > Yes, if you read a single PIO the state is always '0', but reading PIO.BYTE > shows the correct BYTE value. > > > Martin Patzak (GMX) wrote: >> >> I confirm. Furthermore is interesting, that when e.g. switching Bit 0 >> with PIO.BYTE setting to "1" the PIO.0 does NOT get updated as it >> normally is the case; it stays on "0"! >> >> >> On 11/05/2012 09:49 AM, Silvio Schmieder wrote: >>> >>> Yes, exactly. If I send the correct BYTE value how I wrote in post >>> before, >>> the PIO's switches how it should. >>> >>> >>> Paul Alfille-2 wrote: >>>> >>>> If I understand you correctly, you can set specific PIO channels with >>>> the >>>> PIO.BYTE, but not via PIO.n, correct? >> >> >> ------------------------------------------------------------------------------ >> LogMeIn Central: Instant, anywhere, Remote PC access and management. >> Stay in control, update software, and manage PCs from one command center >> Diagnose problems and improve visibility into emerging IT issues >> Automate, monitor and manage. Do more in less time with Central >> http://p.sf.net/sfu/logmein12331_d2d >> _______________________________________________ >> Owfs-developers mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> >> > ------------------------------------------------------------------------------ LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
