Hi Nico,
I have been running a 1-wire system on a Raspberry Pi with a Sheepwalk
Electronics RPI3 adapter for many years. I believe the adapter uses the
DS2482-800.
The 1-wire network lock up occasionally and needs the +5v supply to the
adapter to be turned off and back on again. I understo
Hi People,
I have some bits that are of no further use to me and wonder if they may
be of use to anyone else.
Qty 1 Embedded Data Systems HA7E serial to 1-wire adapter
Qty 2 DS9097U Dallas Maxim Universal 1-Wire COM Port Adapter
Qty 3 Hobby-boards 8 channel I/O Board
All believed to be in w
If you have ow-shell installed then owdir should show all the devices on
the network
Mick
On 08/05/2022 13:11, Chris Green wrote:
I seem to have lost a couple of 1-wire devices, they were working a
while ago but now don't seem to be appearing. I've tried re-running
owfs but that has done no g
I have just set up a Pi zero with a temp sensor following this -
https://www.circuitbasics.com/raspberry-pi-ds18b20-temperature-sensor-tutorial/
It works OK but I am wondering if I can use the owfs modules with this?
If so what do I set as the server in /etc/owfs.conf
I don't see anything in
uot;
but possibilities are endless.
Bye and thank you for sharing.
Stefano
On 14 Oct 2020, at 15:08, Mick Sulley <mailto:m...@sulley.info>> wrote:
I had a bit of trouble with this and thought it worth sharing the
solution.
With Python2 and pyownet I could use
owp.write(&#x
I had a bit of trouble with this and thought it worth sharing the solution.
With Python2 and pyownet I could use
owp.write('/settings/timeout/directory', 60)
but with Python3 that throws an error, TypeError: 'data' argument must
be binary. I can use
owp.write('/settings/timeout/dire
hanks
Mick
On 08/10/2020 19:47, Mick Sulley wrote:
This is a test setup, all sensors are in a breadboard on the bench,
power is from a Meanwell unit set to 5.1 volts, which is what I
measure at the sensors. So I am pretty confident it is not a wiring
or power supply problem.
Is there any w
15:07 schrieb Mick Sulley:
But owwrite /simultaneous/temperature 1 should trigger a conversion? and
reading latesttemp should then be correct. Here is another. Latesttemp
returns 85 even after owwrite /simultaneous/temperature 1, but read
temperature12 and it works again. I don't understand w
On 08/10/2020 12:26, Jan Kandziora wrote:
Am 08.10.20 um 00:31 schrieb Mick Sulley:
On my test system I have 20 DS18B20 temperature sensors (all powered) to
test out various things. I am setting /simultaneous/temperature waiting
2 seconds then reading latesttemp from all of them.
I have just
On my test system I have 20 DS18B20 temperature sensors (all powered) to
test out various things. I am setting /simultaneous/temperature waiting
2 seconds then reading latesttemp from all of them.
I have just noticed that several are giving 85 reads. If I look with
owhttpd this is what I see
Hi Henrik,
I can't answer you questions I'm afraid but I would add a few comments.
I have been using Pi's since they were first released and yes, I have
had a few problems as well. The most common problem I have found is
power supply, always worth using a decent one, I use Meanwell units in
I have been doing some more testing of voltage reading, this is what I
found
Testing on Pi4 with Sheepwalk RPi3 adapter with 2 voltage sensors, a
DS2437 and a DS2438
Reading voltage from cached takes around 0.06 seconds for each, reading
from uncached takes around 0.28 seconds for DS2437 and 0
Yes I have struggled with that as well. I have discovered how to do it,
but I don't really understand why.
The answer seems to be that to write a 1 you need
owproxy.write('device_id' + '/PIO.BYTE, b'1')
so you need to write the byte value of the string 1, not the byte value
of the intege
Yes I would second that. It is a little ironic that in the owfs suite
of programs the module called owfs it the only one you really should not
use. Basically hte best way is to run owserver which talks to all the
devices, and then your python code talks to owserver.
I have been using pyowne
Thanks Stefano, I have removed it and reinstalled the owserver raspbian
packages and it is back again at 3.2p3
Here is what I see on CRC_errors -
pi@pi4B:~/v12_5 $ python3
Python 3.7.3 (default, Dec 20 2019, 18:57:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for mor
make
make install
### no more running with sudo !!! ###
link owserver_ to dir /usr/bin so it can be found when
executing it with sudo
sudo ls -s /home/mnm/owfs/bin/owserver_/usr/bin/owserver_
On 16.08.20 21:59, Mick Sulley wrote:
First, I noticed a typo in my mail, the CRC value
it is not
a stupid question)
I don't have such devices, so I cannot test this further...
Greetings,
Marty
On 13.08.20 01:04, Mick Sulley wrote:
I have been doing some more testing and have a couple of issues. My
code sets simultaneous/temperature, waits a couple of seconds then
reads lat
I have been doing some more testing and have a couple of issues. My code
sets simultaneous/temperature, waits a couple of seconds then reads
latesttemp from each sensor.
1. Reading latesttemp generally takes 0.07 seconds BUT every 120
seconds every sensor takes 0.75 seconds for a single loop
On 09.08.20 10:52, Martin Patzak wrote:
here is some documentation about the values in /statistics:
http://owfs.sourceforge.net/statistics.html
I do not know if there is more about that within the owfs project...
there should be more at Maxim's website about the interface protocol
whi
e bus or sensor problems.
Additionally you can have a look in /statistics for retries and errors
On 08.08.20 01:04, Mick Sulley wrote:
Update on test findings. Test setup was 19 - DS18B20 temperature, 2
- DS2413 IO and 1 - DS2437 Voltage, Raspberry Pi4 with Sheepwalk RPi3
Adapter
1) /simu
Update on test findings. Test setup was 19 - DS18B20 temperature, 2 -
DS2413 IO and 1 - DS2437 Voltage, Raspberry Pi4 with Sheepwalk RPi3 Adapter
1) /simultaneous/temperature does work, best to read latesttemp.
2) /settings/timeout/presence cannot be set or read via the owhttpd web
page, you
8.20 21:42, Mick Sulley wrote:
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
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 all is gene
its next read, irrespective of which field is read.
I have now tested with 19, 11 and 2 sensors and the slow loop occurs
every 120 seconds. I am intrigued to know what causes this, any ideas?
Thanks
Mick
On 06/08/2020 10:23, Mick Sulley wrote:
OK I will log read times and see what that shows.
Y
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 b
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 t
#x27;)
print sensed
sensed = op.read('/28.DD591502/latesttemp')
print sensed
Marty
On 05.08.20 00:39, Mick Sulley wrote:
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
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
The code is below, when I run it the first loop takes 16 seconds then it
loops at 3 seconds for a while, then a 16 second etc. so it looks
Thanks Jan.
On 09/05/2020 20:14, Jan Kandziora wrote:
Am 09.05.20 um 14:42 schrieb Mick Sulley:
I understand how caching works for temperature sensors, use of
simultaneous etc, but how do I/O modules work in that respect?
I am particularly interested in DS2413. Is there any difference between
I understand how caching works for temperature sensors, use of
simultaneous etc, but how do I/O modules work in that respect?
I am particularly interested in DS2413. Is there any difference between
"owwrite /TestIO/PIO.A 1" and "owwrite /uncached/TestIO/PIO.A 1",
similarly with reading, is it
How about £40 for the 3 DS9097Us ?
On 27/04/2020 20:09, Michael Hughes wrote:
On Mon, 27 Apr 2020 19:22:53 +0100
Mick Sulley wrote:
Greeting. I have just had a very overdue tidy up and as a result I
have some items which are surplus to requirements.
2 X Hobbyboards 8 channel I/O v2.0 (I
Greeting. I have just had a very overdue tidy up and as a result I have
some items which are surplus to requirements.
2 X Hobbyboards 8 channel I/O v2.0 (I have soft copy of the schematic
and user manual)
2 X Maxim DS9097U-009 Universal 1-Wire COM Port Adapter (with id chip)
1 X Maxim DS90
OK that's clear. Thanks Jan
On 24/03/2020 13:08, Jan Kandziora wrote:
Am 24.03.20 um 11:03 schrieb Mick Sulley:
There have been times when using the owhttpd interface page to look at
the various temperatures I have seen 85 at some resolutions and
apparently valid values at other resolu
There have been times when using the owhttpd interface page to look at
the various temperatures I have seen 85 at some resolutions and
apparently valid values at other resolutions. Does it therefore make
sense when reading values within my program to check for a valid read at
12 bit (my normal
s: a mix of restart/reboot/voodo magic to see
if the problem disappears ;-)
By comparing the verbose pyownet log with the owserver one you should
be able to pinpoint the problem.
Good luck!
Stefano
On 9 Nov 2019, at 15:44, Mick Sulley <mailto:m...@sulley.info>> wrote:
I am using
I am using pyownet on a few Raspberry Pi systems, but one has stopped
working. I have updated the OS, removed and reinstalled pyownet and it
still fails. This is what I see -
pi@pi3ether:~ $ python3
Python 3.7.3 (default, Apr 3 2019, 05:39:12)
[GCC 8.2.0] on linux
Type "help", "copyright", "
ges.
Bye
Stefano
On 28 Oct 2019, at 00:34, Mick Sulley <mailto:m...@sulley.info>> wrote:
But that webpage says -
To install pyownet:
$ pip install pyownet
On 27/10/2019 17:09, Martin Patzak wrote:
No, pyownet is not part of ownet.
Type "man ownet"
pyownet has to
0.19 14:54, Mick Sulley wrote:
I am confused. pyownet seems to be working with Python3 for me if I
install it as
sudo pip3 install pyownet
that is unless there are some features of it that I have not used.
Is pyownet included within python3-ownet, or have i misunderstood that?
Also on the
I am confused. pyownet seems to be working with Python3 for me if I
install it as
sudo pip3 install pyownet
that is unless there are some features of it that I have not used. Is
pyownet included within python3-ownet, or have i misunderstood that?
Also on the pypi site https://pypi.org/proj
it fails with
ModuleNotFoundError: No module named 'pyownet'
am I missing something here?
On 26/10/2019 15:24, Matthias Urlichs via Owfs-developers wrote:
On 26.10.19 12:53, Mick Sulley wrote:
Question - is it good practice to always install packages like this as
root?
On L
I have just discovered that if I install pyownet with
pip3 install pyownet
it works fine for programs that I run under my user, but if I run
something with sudo I get
ModuleNotFoundError: No module named 'pyownet'
I can overcome this by installing as root with
sudo pip3 install pyownet
Qu
is only my guess that your problem is
linked to the null terminator, maybe it is something completely
different.)
S.
On 14 Oct 2019, at 00:46, Mick Sulley <mailto:m...@sulley.info>> wrote:
Hi Stefano,
I ran test.py and it completed without error. I then ran it again
and it fai
Hi Stefano,
I ran test.py and it completed without error. I then ran it again and
it failed at B9, I ran it several times more and it failed at B9 each time.
I then made the change you suggested and ran it again, it still failed
at B9. I then rebooted and ran it again and it completed witho
_b, b'T1')
>>> ow.write(node_c, b'X0')
>>> ow.dir()
['/T0/', '/T1/', '/X0/']
>>> ow.read(node_a)
b'T0'
>>> ow.read(node_b)
b'T1'
>>> ow.read(node_c)
b'X0'
>>> ow.read('/
This is getting more weird. Tried a few more things, I can write X0 (ex
zero) to the alias, and I can then write T0 to it?!?! If I write T99 to
it I then cannot write T0 again. My head is starting to hurt! Can
anyone explain this behaviour?
On 10/10/2019 16:17, Mick Sulley wrote:
Thanks
ty of using pyownet.
- some nodes contain binary data:
e.g. '/26./pages/page.ALL', no decoding needed
- numeric values can be converted directly, without the need of
decoding: if owp is a proxy object you have e.g.
>>> owp.read('/26./temperature
I am updating my python code from 2.7 to 3.7, using pyownet to
communicate with 1-wire.
Reads and writes were strings in 2.7 but it seems they are binary in
3.7. I can get around this by appending .decode('utf-8) and
.encode('utf-8) to the read and write functions, but I feel that I am
makin
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
You have to see the 18 for i2c device 0 etc
Nico
Mick Sulley wrote:
> I am having trouble getting owfs to work on Raspbian Buster. I
have posted on t
localhost:4304
Any ideas are welcome!
Thanks!
Linkedin <http://de.linkedin.com/in/rlagus> *Robert Lagus*
+358 (0)40 662 44 99
rob...@lagus.net <mailto:rob...@lagus.net>
On Sun, 15 Sep 2019 at 21:08, Mick Sulley <mailto:m...@sulley.info>> wrote:
Many thanks Colin.
showing errors.
Colin
On Sun, 15 Sep 2019, 12:08 Mick Sulley, <mailto:m...@sulley.info>> wrote:
I am having trouble getting owfs to work on Raspbian Buster. I
have posted on the Pi forum
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=251702&p=1536228#p15
I am having trouble getting owfs to work on Raspbian Buster. I have
posted on the Pi forum
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=251702&p=1536228#p1536228
Someone said they had the same problem but no suggestions to fix it, so
I wonder if anyone here can give me a clue.
I
A few weeks ago I reported a problem with some DS18B20 sensors, then
found it was my mistake. I have just looked at all this again and it is
not that simple!
Having tidied my desk I found I had a lot of DS18B20 sensors and I have
been testing them -
11 work as expected
21 work fine when powere
I will repay him yes.
On 04/08/2019 20:27, Colin Law wrote:
Have you re-paid the first guy? Or did you send them back?
Colin
On Sun, 4 Aug 2019 at 20:09, Mick Sulley wrote:
It was all very simple. I was connecting the sensors via breadboard
type connectors. My old one worked, the new ones
opped it making a good connection.
Thanks for your help, sorry it was a bum steer.
Mick
On 04/08/2019 11:16, Jan Kandziora wrote:
Am 04.08.19 um 10:02 schrieb Mick Sulley:
Yes it does. I also have a DS18S20 inside the test box that I use, that
shows as well. I have just tried a different D
:29, Mick Sulley wrote:
I'm trying to install on Raspbian Buster and failing!
I did the usual updates, then installed owserver owhttpd ow-shell, it
has installed 3.2p3
owdir worked, but that was with the fake devices in owfs.conf. Edited
that out and added dtparam=i2c1=on
sudo i2cdetect
I'm trying to install on Raspbian Buster and failing!
I did the usual updates, then installed owserver owhttpd ow-shell, it
has installed 3.2p3
owdir worked, but that was with the fake devices in owfs.conf. Edited
that out and added dtparam=i2c1=on
sudo i2cdetect -y 1
gives me
Error: Cou
Yes it does. I also have a DS18S20 inside the test box that I use, that
shows as well. I have just tried a different DS2401 and get the same
results.
On 03/08/2019 23:41, Jan Kandziora wrote:
Am 03.08.19 um 22:57 schrieb Mick Sulley:
I recently bought 4 DS18B20 sensors from eBay. When I
I recently bought 4 DS18B20 sensors from eBay. When I received them
they did not work, that is they did not show up on the bus when
connected to a DS9490 USB adapter. I reported it to the seller and got
a refund. I then ordered 10 from another seller on eBay, just tested
those and none of th
Yes indeed, this was the message
I have a Hobyboards 6 channel hub which has been in my drawer for many
years. I did use it but changed over to a Sheepwalk RPi3 ages ago
because that works directly with a Pi. I have been meaning to put it on
eBay but never got around to it, do you want it?
I just had another DS18S20 sensor giving me strange readings, but this
time it was fairly easy to access, so I was able to physically feel how
hot it was.
My web page is based upon the latesttemp value. The pipe it measures
would be at around 25 degrees give or take a bit. I saw it go to ove
and the
Pi. Can I just power cycle the 1-wire adapter and leave the Pi running?
On 13/07/2019 19:58, Stefano Miccoli via Owfs-developers wrote:
On 11 Jul 2019, at 23:10, Mick Sulley <mailto:m...@sulley.info>> wrote:
The reason for the question is that I still have random bus loc
Looking at my system via owhttpd at top level I can see all the devices
and some other things -
bus.0 seems to mean the bus structure, so in there I can see bus.0 to
bus.7 In each of these I see just the devices on that bus plus
interface, simultaneous and alarm, and drilling down into
inter
Yes all of my sensors are powered. I will do more investigation.
Thanks for the comments
On 19/06/2019 09:19, Matthias Urlichs via Owfs-developers wrote:
On 19.06.19 09:39, Jan Kandziora wrote:
The 1W host has to supply current to the 1W line to power all the
parasitic powered slave devices.
My system comprises multiple DS18S20, DS18B20 temperature sensors, some
DS2438 I/O modules and a DS2437 to measure system voltage.
The voltage normally sits at around 5.1 volts, up to maybe 5.15 when no
outputs are on, down to 4.95 with several outputs on.
A while back I saw the voltage drop
I have a humidity sensor which has been running for ages, it has a
DS2438 chip, at least that is what the Sheepwalk site says and it
returns that on read so I guess that is right. I have recently added
voltage measurement to the system, using a chip which was ordered as a
DS2438Z and is marked
4.19 um 16:47 schrieb Mick Sulley:
I just had the Pi on my main control system crash. Looking through
syslog there are load of entries like -
Apr 20 14:47:35 pi-solar kernel: [1816089.721179] w1_master_driver
w1_bus_master1: Family 0 for 00.c611.3f is not registered.
Apr 20 14:48:00 pi-so
I just had the Pi on my main control system crash. Looking through
syslog there are load of entries like -
Apr 20 14:47:35 pi-solar kernel: [1816089.721179] w1_master_driver
w1_bus_master1: Family 0 for 00.c611.3f is not registered.
Apr 20 14:48:00 pi-solar kernel: [1816114.723725] w1_
I am using a DS2438 to measure my system +5v line and log it. As I
understand it the voltage measurement can be triggered by setting
/simultaneous/voltage in the same way as for temperature. As I want to
use both, can I set /simultaneous/voltage and /simultaneous/temperature
together or should
n write to /simultaneous/temperature will
it then read at 11 bit and update latesttemp and temperature11?
Thanks
Mick
On 10/03/2019 19:24, Jan Kandziora wrote:
Am 10.03.19 um 19:46 schrieb Mick Sulley:
OK, but looking through Jan's checklist again -
* power all sensors
* set the sensor EEPROM t
2 bit, that's a valid
reading. Store and go to 2.
?? How do I check the resolution?
7. Power-on-reset. Store an error. Trigger a 12-bit resolution
conversion for that sensor and go to 2.
Thanks
Mick
On 10/03/2019 15:01, Colin Law wrote:
On Sun, 10 Mar 2019 at 14:57, Mick Sulley w
/2019 17:38, Jan Kandziora wrote:
Am 19.02.19 um 14:35 schrieb Mick Sulley:
The failure happened for about 10-20 minutes, reading about every 10
seconds or so, then it recovered and is reading fine again.
All devices are powered.
I could change my code so that it reads fasttemp and if that is 85 it
ve any other masters but your RPI3 boards
already have a DS9503 on each channel.
Paul
On 28 Feb 2019, at 14:14, Mick Sulley <mailto:m...@sulley.info>> wrote:
I know this is a very basic question, but my electronics knowledge
is not great.
Following on from recent discussions
Thanks Paul, that has saved me some work!
On 28/02/2019 18:13, Paul Everett wrote:
Hi Mick,
I’m not sure if you have any other masters but your RPI3 boards
already have a DS9503 on each channel.
Paul
On 28 Feb 2019, at 14:14, Mick Sulley <mailto:m...@sulley.info>> wrote:
I know
I know this is a very basic question, but my electronics knowledge is
not great.
Following on from recent discussions re adding DS9503 to increase
reliability I am trying to design a PCB for them. Looking at the diagram
on page 2 of the spec sheet
(https://datasheets.maximintegrated.com/en/ds
I have been using Pi's since they started and yes, I have had multiple
SD failures. I now run mine from hard drives which I have recovered
from dead laptops. The new Pi's can be set to boot from a hard drive,
the older ones you still need an SD but it is only used at boot to
redirect to the h
sensible
thing to do?
Thanks
Mick
On 19/02/2019 12:49, Jan Kandziora wrote:
Am 19.02.19 um 10:39 schrieb Mick Sulley:
My control system has detected a no read (85) on a DS18B20 temp sensor,
however if I look at it via owhttpd I can see temperature, temperature11
and temperature12, but 85 for
My control system has detected a no read (85) on a DS18B20 temp sensor,
however if I look at it via owhttpd I can see temperature, temperature11
and temperature12, but 85 for fasttemp, temperature9 and temperature10.
How can that happen? The sensor had been working OK. I am running
3.2p3 on
So adding a DS9503 in each of the busses on a DS2482-800 should stop
lock-up problems?
On 17/02/2019 22:13, Alastair D'Silva wrote:
The series resistance within a DS9503 should be sufficient, I hope. It's worth
using these anyway, for ESD protection.
__
I had a temperature sensor fail and replaced it but I am seeing strange
results from the new one.
This is what I see. Why do Temperature 11 & 12 seem OK but 9, 10 and
Lasttemp are all 85? Is it a bad sensor?
*address* 2848999D046C
*alias*
*crc8* 6C
*errata*errat
Hi Jan,
Many thanks for your words of wisdom, I will take them on board.
You say that the DS2482-800 can reset to an unusable state, would the
same apply to the DS2482-100? Sheepwalk now make a dual channel RPi2
and I could stack 2 to get 4 channels and I think I could manage with
that if th
I have a Pi with Sheepwalk RPi3 adapter running multiple temperature and
I/O. I get random read failures and bus lock up, read failures every
day or two, bus lock up every week or so. Currently I have separate
power supplies (Meanwell units) for the Pi and the 1-wire and they are
both floating
Thanks for the reply.
Yes the adapter is based upon the DS2482-800. What value of capacitor
and should it be at the adapter or the far end of the bus? Do I just
need one or one on each bus?
Thanks
Mick
On 04/09/18 00:22, Laurent FAILLIE via Owfs-developers wrote:
Hi,
If the "" is based
I have been plagued by a problem with one of my control systems for a
number of years now and I am still trying to fix it. I have posted a
few times before, and following suggestions I have replaced some of the
cabling and replaced the power supplies with Meanwell MDR-20-5 units
Running 3.1p5
Hi Laurent,
I suffered for several years with a similar issue, I have an 8 bus
system and I would loose 1 or more of the busses, the only way to
recover was to power cycle. From what I have read I don't believe that
there is any other way to reset a DS2482.
Over that time I tried all sorts
with graceful
shutdown.
C
On Sep 24, 2017, at 7:56 AM, Matthias Urlichs via Owfs-developers
wrote:
On 24.09.2017 12:38, Mick Sulley wrote:
Any suggestions on how I can find out what is causing this.
When I had this problem, the root cause was a flaky power supply.
Get a cap-rail-mounted
Several months back I posted about a system lock up problem, Pi 3
running owserver etc 3.1p5 with Sheepwalk
RPi3 adapter and RPi3a splitters giving me 8 busses. All devices are
powered, separately from the Pi. I use python code and pyownet to
monitor and control a mixture of about 35 DS1820 and
Hi People,
Looking for suggestions here.
My system runs on a Raspberry Pi with a Sheepwalk RPi3 adapter and RPi3a
splitters giving me 8 busses, with about 20 temperature sensors and 6
I/O modules, all powered. I was having a few problems loosing one or
more busses, after some investigation I
then.
Mick
On 27/05/17 17:00, Jan Kandziora wrote:
Am 27.05.2017 um 10:02 schrieb Mick Sulley:
There are loads of messages like this
May 25 08:21:32 pi-solar kernel: [1007793.425520] w1_master_driver
w1_bus_master1: Family 0 for 00.ec8a.82 is not registered.
May 25 08:22:21 pi-
No usb messaged, but 1-wire is via a Sheepwalk RPi3 adapter and RPi3a
splitter
On 27/05/17 11:12, Colin Law wrote:
No USB related messages at the time of failure?
Colin
On 27 May 2017 at 09:02, Mick Sulley wrote:
There are loads of messages like this
May 25 08:21:32 pi-solar kernel
ing
messages around the time of failure. If syslog does not go back far
enough look in /var/log/syslog.1
Colin
On 26 May 2017 at 21:35, Mick Sulley wrote:
Thanks for your comments Matthias. It happened again today, same channels I
think. Could it be temperature related? The Pi etc is in the lo
Thanks for your comments Matthias. It happened again today, same
channels I think. Could it be temperature related? The Pi etc is in
the loft and it was around 40C in there today, so the Pi would be
somewhat above that.
Mick
On 09/03/17 10:15, Mick Sulley wrote:
My system is Raspberry
My system is Raspberry Pi 3 running owserver etc 3.1p5 with Sheepwalk
RPi3 adapter and RPi3a splitters giving me 8 channels. All devices are
powered, separately from the Pi. I use python code and pyownet to
monitor and control a mixture of about 35 DS1820 and DS2413
The system has been running
I think it is libusb-dev that is missing.
But do you really need 3.1p5 as you can easily get 3.1p4 from the repro
using the notes that Jan kindly provided -
Edit (or create) your /etc/apt/preferences to contain:
--
Packag
I don't know if this will help to explain the operation, but my code
runs in a continuous loop -
* Read all temperatures
* Set the simultaneous/temperature bit
* Perform logic operations, setting outputs to devices based upon
temperatures read, etc
* Log values to database
* repeat.
Kandziora wrote:
> Am 05.12.2016 um 16:39 schrieb Mick Sulley:
>> OK more research and I have made a bit of progress.
>>
>> adding
>>
>> server: fake=10.053C8A010800,10.2AFE89010800,10.90F889010800
>>
>> to owfs.conf creates these devices with random va
effect. The
values seem to be different for each device, but all are many hundreds
or thousands of degrees.
Is there any way to set individual temperatures for fake devices?
Thanks
Mick
On 04/12/16 23:34, Mick Sulley wrote:
> I am trying to test out some code using the tester facility in
I am trying to test out some code using the tester facility in owfs.conf
If I add
tester=10.053C8A010800
I can see that fake device. Looking at the documentation there is a way
to tell it what value e.g. temperature you would like it to read, from
the documentation (which seems rather confusi
I think you also need libusb-dev if you are compiling it
Mick
On 17/09/16 20:02, samuix wrote:
Hi,
I build the owserver with following options:
./bootstrap
./configure --enable-usb
following messages showed up:
checking if usb support is enabled... yes
checking for LIBUSB... no
..
Depl
Yes I would echo Nigel's comments. I don't think there is a perfect
solution but what is suggested sounds good to me.
Mick
On 14/09/16 10:14, Nigel Titley wrote:
>
> On 14/09/16 09:02, Jan Kandziora wrote:
>> Am 14.09.2016 um 07:21 schrieb Johan Ström:
>>> Colin, Jan, Colin, and everyone else:
OK the examples look OK, I don't know how to do it but if this is our
final solution I will invest the time to find out.
On 11/09/16 21:50, Johan Ström wrote:
> On 11/09/16 22:39, Mick Sulley wrote:
>
>> I just added a new page and it seems pretty easy to me to do that, but I
1 - 100 of 389 matches
Mail list logo
