Am Dienstag, 18. Oktober 2011, 00:40:37 schrieb ekgnkb3d:
> Hi Jan and others
>
> Jan Kandziora wrote:
> > Which host adapter do you use?
>
> OK, I forgot to mention the used hardware - sorry:
> An embedded ARM with 400MHz
> The 1-Wire bus master is connected via I2C a DS2482-100
> The temperature will be read from DS18B20 temperature9
>
Ok. I²C is CPU-hungry, as it involves busy-loops on kernel level for most I²C
hosts. Bitbanging hosts are most annoying as they need the kernel to stop for
10µs after each bit. Nothing useful to do in such a short time.
> Jan Kandziora wrote:
> > What's the loop delay?
>
> At time of the previous posting I used 5s loop delay accessing the
> "uncached" values
>
That isn't too tight. When scanning for new chips ("Search ROM"), 5s ist tight
on I²C. If you only access chips by "Match ROM", it should go down to 100ms
without problems. At least with the PentiumM I use in my embedded system.
I haven't checked the temperature sensors, though. Are you sampling/reading
them directy, or do you trigger /simultaneous/temperature before, then delay
the loop, then read?
Kind regards
Jan
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
