O? Maybe it would be smart to just put another ESP32 at each controlled
system location?
Thanks for the intriguing new exploration!
| Loren Amelang | lo...@pacific.net |
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
end of each one on the data line, '-' end to ground wire. The last
sensor connects to the same terminal block by about one meter of cable.
Loren
| Loren Amelang | lo...@pacific.net |
--
Check out the vibr
g that helped was adding a 1N5711 Schottky diode and a 1.5KE20A-T
TVS at each end of the bus (it is driven from the middle).
My system just started its 20th year of continuous operation... Using 1-Wire
for 16 of them.
Loren
|
ding camera video, that would go way
up, but for an occasional switch change or temperature reading I'd expect the
idle value most of the time.
Am I missing something important here, or are people thinking older generations
of Wi-Fi?
Loren
| Loren
s18b20.html>
-
Where physically on the device does the temperature measurement take place?
The DS18B20 does not sense temperature directly through the package. For all
package types, the DS18B20 senses temperature primarily through the GND pin.
Ensuring a good thermal connection between the G
_|___T1:9(1-W signal input)
(Yes, my whole house control system is documented in ASCII. This started back
in the CP/M era, and has outlived t
w hours and then go away for days. Military radar? Spooks?
But that is with an ancient dedicated microprocessor at 5V - not with owfs. It
reads and sets up a different single DS18B20 of the ten connected, every ten
seconds. Often goes for months without a single missed reading now.
|
bling the GPIO
strong pullup properly.
And... I just noticed my test readings aren't quite the same! How can it be
that w1 shows "59 01 4b 46 7f ff 07 10 a2 t=21562" when the ownet proxy returns
"21.625"? And where does the proxy get "21.0625" if the raw
y3 -n 2 -r 2
owserver://10.1.1.4:4304/28.884d8800/type
statement: proxy_obj.read("/28.884d8800/type")
** non persistent : 2.57 ms, 2.75 ms,
** persistent : 1.28 ms, 1.93 ms,
Fixed values a bit faster, temps slower, uncached about the same. Guess that
makes sense.
Loren
| Loren Amelang | lo...@pacific.net |
--
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
ols: db files
services: db files
ethers: db files
rpc:db files
netgroup: nis
---
Always more to learn,
Loren
| Loren Amelang | lo...@pacific.net |
--
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
support
ii owfs-common 2.8p15-1ubuntu4 all common files used by any of the OWFS
programs
ii owfs-doc 2.8p15-1ubuntu4 all Dallas 1-wire support: Documentation
for owfs
ii owfs-fuse 2.8p15-1ubuntu4 armhf 1-Wire filesystem
And all my timings match your slow
y BBB is so incredibly slow
at the timing test, is there any way to add timestamps to those debug lines? I
tried to get the debug to print to syslog, where I assume it would get serious
timestamps, but nothing at all ever
eems to persist in all configurations - each later test in the
same sequence takes a bit longer! Guess I can't understand everything...
Loren
| Loren Amelang | lo...@pacific.net |
--
_
other trick that seemed to help stop the last few rare errors on this long,
perilous route was adding termination on the far end - a (reverse biased)
1N5711 Schottky diode and a 1.5KE20A-T TVS in parallel.
I know, separate cables for 1-wire would be better, but it seems no matter how
much cab
nt with this interpretation:
>>>> non-persistent overhead is a constant small delta with respect to
>>>> persistent connection. Since your owserver is apparently much slower
>>>> than the one which I run my tests, you have a smaller relative
>>>> overhea
o
use "force-reload":
ubuntu@arm:~/Lpkg$ sudo /etc/init.d/owserver force-reload
* Restarting 1-Wire TCP Server owserver
Suddenly it works from out on the network!
pullup value is:
>> (3.30-0.45)/0.006 = 475 Ohms. If the internal pullup worst case was
>> enabled, it would limit our external pullup to 492 Ohms.
>>
> NO! The sink current of a single DS18B20 may be as low as 4mA, so the
> lowest safest pullup operates at 4mA, not 6mA.
Lu
worst case was enabled, it
would limit our external pullup to 492 Ohms.
Loren
| Loren Amelang | lo...@pacific.net |
--
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
750 mS is a
possible bus read time, but apparently a normal read from pyownet adds ~300 mS
of overhead. So somehow a wrongly low value appeared suspiciously soon...
If you'd like to see all the data:
<http://psychoros.or
es/w1_bus_master1# cat w1_master_attempts
2535948
---
They say:
"w1_master_timeout - the delay in seconds between searches"
and mine is clearly 10, so that doesn't seem to define the rare ~4 mS bus
resets. If they were doing the long bus reset between every [write control
buffer] and
On Friday, October 09, 2015 at 5:04 AM,
"Loren Amelang" lo...@pacific.net wrote:
> I believe, and see on my scope, that OWFS only reads at 15-second intervals.
That was true with the Ubuntu 12.04 version. I went back to the scope last
night with a stopwatch app, and found my
[ OK ]
* Starting 1-Wire FTP server owftpd [ OK ]
* Starting 1-Wire HTTP Daemon owhttpd [ OK ]
* Starting 1-Wire TCP Server owserver [ O
On Tuesday, October 06, 2015 at 5:05 AM,
Jan Kandziora j...@gmx.de wrote:
>> My errata display showed the same Trim value the time it said
>> "invalid" as it did all the times it said "valid".
>>
> That may be because the errata/trimvalid node does its own chip read
> without updating the cache v
67.168.225
2015-10-05 09:45:09.072202 67.2116 68.225
---
Still seeing occasional 185 (85C) and 32 (0C) failures, about as often as
before. Not sure why
I guess the other option is that some internal part of a DS18B20 is actually
analog, and influenced by marginal bus power.
Loren
| Loren Amelang | lo...@pacific.net |
--
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
ation for a 3.3V supply? Could it
somehow change my temperature readings?
Clues much appreciated!
Loren
| Loren Amelang | lo...@pacific.net |
--
___
Owfs-developers m
ual equivalent of
>> USB or some other host adaptor, like it appears in my owfs.conf, but
>> accessing a totally different hardware bus? Or have I missed some
>> basic concept here?
Obviously what I'd missed is that the w1 mechanism is separate from my GPIO
connection to 1-
On Wednesday, April 29, 2015 at 12:06 PM,
owfs-developers-requ...@lists.sourceforge.net wrote:
From: Paul W Panish
Subject: [Owfs-developers] Temperature sensitive bus timing using DS18B20
> My problem is that there seems to be a strong temperature dependency for
> bus read/write errors caused by
On Wednesday, April 29, 2015 at 3:35 PM,
owfs-developers-requ...@lists.sourceforge.net wrote:
From: Jan Kandziora
Subject: Re: [Owfs-developers] Temperature sensitive bus timing using DS18B20
...
AS A SIDE NOTE, you have DISABLED the kernel's w1 drivers if you don't
use them? If not, you'll get a
maybe 100' of CAT5 cable. The existing controller sees maybe
two errors per month among all ten sensors, despite the distances and having
most sensors near hot plumbing, motors, and machinery.
Loren
| Loren Amelang | lo...@pacific.net |
by Ubuntu, but the filesystem doesn't appear until I give
the "w1" command to the cape manager.
I understand what Roland's and Paul's config files do. I don't understand how
my own system creates the owfs filesystem without any obvious owfs process or
co
e the official Ubuntu
distribution knows much more than I do. But I do get occasional bad reads and
bogus temperature values, and as I said, the filesystem was getting updated
even while server was stopped.
Loren
| Loren Amelang | lo...@pacific.net |
On Wednesday, October 29, 2014 at 9:27 AM,
e of proving the server is actually
listening on the network, rather than just running.
Loren
| Loren Amelang | lo...@pacific.net |
> 1. Re: Updates while server not running, "simultaneous" kills
> it? (Stefano Miccoli)
>
> Message: 1
> Date: Mon, 27 Oct 2014 00:39:18 +0
d connection abort
---
Aha! Visiting that page kills owserver! That's what made the page loads fail
earlier. At least now I know what not to do...
Sorry if these are all obvious newbie questions,
Loren
| Loren Amelang | lo...@pacific.net |
> 3. Re: Missing data (Paul Alfille)
s. My graphs were always more
like the later part of your blue line - chattering by 1/2 degree where there
should have been a smooth transition.
I have no clues why this started or stopped...
| Loren Amelang | lo...@pacific.net |
On Saturday, September 13, 2014 at 10:29 PM,
owfs-developers
ave not figured that out yet... And the
first one actually reads 2C higher than it should, so the second one is 5C to
7C high! I'm hoping a proper 5V USB interface will fix this...
Obviously the -62 errors are not a big problem for my actual project, but I'm
just really curious how th
doesn't provide statistics?
Am I missing some source of deeper documentation than the web site provides?
Loren
| Loren Amelang | lo...@pacific.net |
--
Open source business process management suite built on Java
ror...
For my production system with a dozen sensors along 100+ feet of cable, I'm
sure a proper 5V interface with active pullup/downs will be required. But I'm
surprised I'm getting offsets when testing with local devices!
Thanks for any clues,
Loren
| Loren Amelang | lo.
38 matches
Mail list logo
