Re: [Owfs-developers] Simultaneous not working

> On 6 Aug 2020, at 21:42, Mick Sulley wrote: > > I did change to persistent and I didn't see a difference. > > Just a quick background. The persistent=True option is useful to shave a few milliseconds from each owserver query by not having to create and pull down a TCP socket and for

Re: [Owfs-developers] Simultaneous not working

hmm 300 seconds. Strange... I use /presence only in case a read or write fails (which is very rarely) - I then check /presence before re-reading or re-writing of that module. In my first 1 wire net routing I was going along existing paths with power-cables and I had modules disappearing and CRC16

Re: [Owfs-developers] Simultaneous not working

No, just tested again and it now delays every 300 seconds.  Not the faintest idea why that should be. I have a couple of I/O and a voltage sensor, so I will set it up again tomorrow with those in as well. What do you use /presence for?  I have never used it before today. Mick On

Re: [Owfs-developers] Simultaneous not working

I read the 25 powered sensors every 30 seconds and I don't experience a delay every 120 seconds (my /presence is at default 120) I use /presence only when I get an error reading a sensor (happens very rarely, but it happens) Then I wait until the sensor is present again before reading it. I use

Re: [Owfs-developers] Simultaneous not working

I did change to persistent and I didn't see a difference. //settings/timeout/presence /is what is causing it.  I had tried changing it yesterday, via the httpd web page, but this time I checked it with owread and that showed it still at 120, so I changed it to 20 with owwrite re-ran my Python

Re: [Owfs-developers] Simultaneous not working

Did you check if persistent=True makes any difference? > On 6 Aug 2020, at 16:21, Mick Sulley wrote: > > Well this gets more curious. I am now measuring the time for each read, > reading type, power and latesttemp. Time for all is generally < 0.1 seconds, > but then when I hit the slow loop

Re: [Owfs-developers] Simultaneous not working

Thank you Stefano On 06.08.20 16:19, Stefano Miccoli via Owfs-developers wrote: > I agree that using the “persistent” network object for the present use > case could speed up things, see > > > >

Re: [Owfs-developers] Simultaneous not working

looks like you are getting close :-) I checked, and the only timeout of owserver that matches 120 is //settings/timeout/presence / On 06.08.20 16:21, Mick Sulley wrote: > > Well this gets more curious.  I am now measuring the time for each > read, reading type, power and latesttemp.  Time for

Re: [Owfs-developers] Simultaneous not working

Well this gets more curious.  I am now measuring the time for each read, reading type, power and latesttemp.  Time for all is generally < 0.1 seconds, but then when I hit the slow loop the read for type is around 0.7 seconds, the others still < 0.1 seconds.  I don't really need type so I

Re: [Owfs-developers] Simultaneous not working

I agree that using the “persistent” network object for the present use case could speed up things, see

Re: [Owfs-developers] Simultaneous not working

I read the CRC16 attribute from /statistics     /CRC16_error = op.read('/statistics/errors/CRC16_errors')/ where op is the persistent(!)  /pyownet/ object, created like this: /    from pyownet import protocol// // //    op = protocol.proxy(server,port=port)/ On 06.08.20 11:23, Mick Sulley

Re: [Owfs-developers] Simultaneous not working

OK I will log read times and see what that shows. You say 'I also log if the error of the 1wire bus changes.' how do you do that? No I don't really need to read that fast, this is just a test setup to get a better understanding so I can hopefully fine tune my main system. There should not

Re: [Owfs-developers] Simultaneous not working

It looks like your timing has improved after all! in your original Python-code you could time every read for each sensor. I have also powered sensors and a read is usually faster than 0.1 seconds. I log in a file if the read took longer than 0.3 seconds, which is almost never the case. I also log

Re: [Owfs-developers] Simultaneous not working

OK I've done more testing, owhttpd was running and a web page open, I closed that and killed owttpd but it didn't seem to make any difference. From what you write it seems there's another process accessing the sensors concurrently. Maybe a kernel driver? Check that first. I don't think

Re: [Owfs-developers] Simultaneous not working

Am 05.08.20 um 00:39 schrieb Mick Sulley: > Running v3.2p3 on Raspberry Pi,  I have set up some DS18B20 sensors on a > test system, all of them are powered, but simultaneous does not seem to > be working > Triggering /temperature/simultaneous just sends "Skip ROM, Convert T" on the bus. If you

Re: [Owfs-developers] Simultaneous not working

I based my code on a mail from Jan 13/3/2020 which said the best way was $ owwrite /simultaneous/temperature 1 $ sleep 1s $ owread /uncached//latesttemp $ owread /uncached//latesttemp $ owread /uncached//latesttemp I was thinking that the problem may be with my Python code, but I have just

Re: [Owfs-developers] Simultaneous not working

... actually I checked my current code and I saw, that I do not read /latesttemp, but read from /uncached/id/temperature so reading from /uncached does not trigger a new conversion. Only when you read a second time without triggering /simultaneous I also saw that I increased the wait after issuing

Re: [Owfs-developers] Simultaneous not working

Hi Mick, by reading the /uncached value, you are causing a new conversion. Read only /latesttemp and it should work fine. here is my test program, when I first tested simultaneous and pyownet: > import time > from pyownet import protocol > > op = protocol.proxy("razmaban",port=4304) > error = 0