Check in the owserver log (likely /var/log/syslog) to see if it is showing
errors.
Colin
On Sun, 15 Sep 2019, 12:08 Mick Sulley, 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=2
On Sun, 4 Aug 2019 at 23:10, Mick Sulley wrote:
>
> I will repay him yes.
So now you have a surfeit of devices. You will just have to find lots
of other things to measure. :)
Colin
>
> On 04/08/2019 20:27, Colin Law wrote:
> > Have you re-paid the first guy? Or did
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 didn't. I just tried
> connecting via the screw terminals
On Sun, 4 Aug 2019 at 20:05, Mick Sulley wrote:
>
> Thanks Colin, I had forgotten to enable i2c. It all works now.
Excellent
Colin
>
>
> On 04/08/2019 12:13, Colin Law wrote:
> > How are you connecting the devices to the pi?
> > Have you run raspi-config and enabl
How are you connecting the devices to the pi?
Have you run raspi-config and enabled/disabled the appropriate sections?
You have to use sudo with systemctl.
Colin
On Sun, 4 Aug 2019 at 11:29, Mick Sulley wrote:
>
> I'm trying to install on Raspbian Buster and failing!
>
> I did the usual updates
On Tue, 16 Jul 2019 at 19:08, Jaroslav Sobota wrote:
>
> Creating config file /etc/owfs.conf with new version
> Setting up libow-3.2-3:armhf (3.2p3+dfsg1-2) ...
> Setting up owserver (3.2p3+dfsg1-2) ...
> Job for owserver.service failed because the service did not take the
> steps requi
On Mon, 15 Jul 2019 at 21:49, Jan Kandziora wrote:
> ...
> The DS18S20 has 9 bit accuracy only, while the DS18B20 supports 12 bit
> accuracy.
i think that should be 9/12 bits resolution rather than accuracy. I
don't think the accuracy is affected. They are both +-0.5C
Colin
_
On Fri, 17 May 2019 at 09:16, nihar Modi wrote:
>
> Hey, thanks for the reply. But meanwhile I got in new trouble. Owdir command
> sometime shows all the sensors but as I add a new one it randomly shows two
> or three sensors only. I am trying continuously for two days and same problem
> persis
On Mon, 8 Apr 2019 at 22:12, Stefano Miccoli via Owfs-developers
wrote:
>
> Hi all:
>
> owfs.org is down, as reported in https://github.com/owfs/owfs/issues/35
I hope that is not all going to be lost as it appears the domain is
about to expire.
Colin
___
On Sun, 10 Mar 2019 at 14:57, Mick Sulley wrote:
>
> How do I set the resolution?
I always fetch the data at the maximum resolution. If you want to
limit it for display purposes then do it when you display it. There
is no point in throwing away data when you are acquiring it.
Colin
_
Have look at the Sonoff devices and compatibles, which can be flashed
with the Sonoff-Tasmota s/w which is super flexible. There is a huge
variety of devices available.
Colin
On Thu, 21 Feb 2019 at 04:12, joep wrote:
>
> Hi All,
>
> To some extent this follows from thread: Reliability and R
Colin
> Thanks - Rowan
>
> Rowan Sylvester-Bradley
> 22 Fox Green
> Great Bradley
> Newmarket
> Suffolk
> CB8 9NR
>
> Phone: 01440 783157
> Mobile: 07970 111231
> E-mail: ro...@sylvesterbradley.org
>
> On 05/08/2018 16:26, Colin Law wrote:
>
> On 5 Au
On 5 August 2018 at 19:09, Rowan Sylvester-Bradley <
ro...@sylvesterbradley.org> wrote:
> ...
>
>1. Some form of OWSERVER. What do I need to download for this, and
>what is the install process?
>
>
sudo apt-get install owserver ow-shell
So a bit easier than Windows :)
If you decided to tr
On 5 August 2018 at 12:50, Jan Kandziora wrote:
> Am 05.08.2018 um 12:22 schrieb Rowan Sylvester-Bradley:
> > I am trying to use a DS9490R USB-to-onewire adapter.
> >
> > I want to plug it directly into my Windows PC. I may later add a
> > Raspberry Pi or similar, but for now I'm trying to keep t
On 2 March 2018 at 00:48, Gregg Levine wrote:
> Hello!
> I have the most recent numbered release on a Pi3 (now on a Pi Zero W)
> running and working. However since I previously also released the
> newest code via a git clone when setting up the directory.
>
> Now however I need to update things, a
On 6 January 2018 at 00:19, Péter Zsembery wrote:
> Hi,
>
> Back in May last year I asked for help to make OWFS communicate with my home
> developed 1-wire slave device (based on PIC16F877A).
> The hardware configuration is Raspberry Pi RevB with Raspbian 3.18.11 and
> DS2480-100 on I2C.
> Based o
On 19 August 2017 at 13:07, Gabrijel Erman wrote:
> Hi,
>
> I have a issue with owfs and can't figure out what to do. I created an
> raspberry pi 2 process that runs on startup and collects data from 1-wire
> network. What happened is that process just stops at some point. Scratching
> my head why
On 3 August 2017 at 01:29, Loren Amelang wrote:
> On Wednesday, August 2, 2017 at 10:31 AM,
> owfs-developers-requ...@lists.sourceforge.net wrote:
>> 1. Re: Arduino yun as wifi 1wire master
>
> I keep reading these posts saying Wi-Fi is a power hog. I just ordered a pair
> of Raspberry Pi Zero W
nothing related, don't know. I have looked at
> http://www.rsyslog.com/e/2007 and it didn't help me much.
>
> Any ideas?
>
> Thanks
> Mick
>
>
>
> On 27/05/17 08:24, Colin Law wrote:
>>
>> Have a look in /var/log/syslog and see if the
Have a look in /var/log/syslog and see if there are any interesting
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
m/en/shop/shipping/
>
>
> On 04/16/2017 12:04 PM, Colin Law wrote:
>
> On 16 April 2017 at 10:40, Colin Law wrote:
>
> Does anyone know where I can get a LinkUSB in the UK? Homechip have
> gone out of business apparently. It is to replace a failed unit in a
> worki
On 16 April 2017 at 10:40, Colin Law wrote:
> Does anyone know where I can get a LinkUSB in the UK? Homechip have
> gone out of business apparently. It is to replace a failed unit in a
> working system so I would prefer a direct replacement if possible.
Or is it just that Homechip'
Does anyone know where I can get a LinkUSB in the UK? Homechip have
gone out of business apparently. It is to replace a failed unit in a
working system so I would prefer a direct replacement if possible.
Colin
--
Check o
continue waiting for the answer.
>
> S.
>
> On 5 Mar 2017, at 21:08, Colin Law wrote:
>
> The extra header contains version: 0, payload: -1, ret: 0, flags: 0,
> size: 0, offset: 0
> So the element described as size of data element is 0 though that
> described as length of p
On 5 March 2017 at 22:11, Gregg Levine wrote:
> Hello!
> Colin how did you attach your One-Wire device to the Pi Zero? And is
> it in much the same style as that from the discussion from last
> September?
Hi Greg, I have some using LinkUSB and some, with up to two DS18B20 on
wires of up to a few
modate for a
> terminating null byte)
>
> So I confirm: headers with payload == -1 are to be discarded and the client
> should continue waiting for the answer.
>
> S.
>
> On 5 Mar 2017, at 21:08, Colin Law wrote:
>
> The extra header contains version: 0, payload: -1, r
The extra header contains version: 0, payload: -1, ret: 0, flags: 0,
size: 0, offset: 0
So the element described as size of data element is 0 though that
described as length of payload data is -1.
Colin
On 5 March 2017 at 19:34, Colin Law wrote:
> Can I just check there I not a confusion h
ase see https://github.com/miccoli/pyownet/pull/1 where Johan
> Ström corrected a similar bug in my pyownet.
>
> S.
>
> On 5 Mar 2017, at 17:51, Colin Law wrote:
>
> I am trying to debug a problem on the node.js owserver client
> node-owfs and am looking for some clarification of
I am trying to debug a problem on the node.js owserver client
node-owfs and am looking for some clarification of the owserver
protocol if possible please.
Referring to [1] in response to a 1-wire read I expect to see a header
with a payload of the size indicated in the header. Very often what I
ac
r 2017, at 17:48, Jan Kandziora wrote:
>>
>> Am 03.03.2017 um 14:44 schrieb Colin Law:
>>>
>>> I too had expected to see messages about the usb device being
>>> disconnected, or something similar, but there is nothing.
>>>
>> Okay. Then we are a
rule to map
the device to /dev/linkUSB but there is no mention of this anywhere in
the log, as far as I can see.
Colin
On 3 March 2017 at 13:24, Jan Kandziora wrote:
> Am 02.03.2017 um 10:21 schrieb Colin Law:
>> Running a LinkUSB on a pi zero (Raspbian Jessie), with owserver
>>
On 3 March 2017 at 08:42, Martin Patzak (GMX) wrote:
> On 03/02/2017 08:50 PM, Colin Law wrote:
> > It appears that the supplied version is not compiled with the ftdi
> option.
>
> how do you check for that? Why is the Debian package not compiled with
> ftdi?
>
When I
inkUSB out and re-inserting it
> (both on USB side and 1W side, if 1W net is externally powered)? And
> also restarting owserver.
>
> Johan
>
>
> On 02/03/17 10:21, Colin Law wrote:
>> Running a LinkUSB on a pi zero (Raspbian Jessie), with owserver
>> 3.1p4-1 from
Running a LinkUSB on a pi zero (Raspbian Jessie), with owserver
3.1p4-1 from jessie testing, I very occasionally (every few weeks) see
in syslog
Mar 1 22:10:50 pi004 kernel: [194834.694657] ftdi_sio ttyUSB0: failed
to get modem status: -110
Mar 1 22:11:00 pi004 kernel: [194844.694679] ftdi_sio t
On 18 January 2017 at 16:36, Ritchie wrote:
>
>> You didn't answer the question "Are you sure there is nothing else in
>>> /var/log/syslog when you start it?"
>>
>> Colin
>>
>
> Hello Colin,
>
>
> here is the syslog
>
> Jan 18 17:32:06 fhem3 systemd[1]: Started User Manager for UID 1000.
> Jan 18
e there is nothing else in
> /var/log/syslog when you start it?"
Colin
>
> Gesendet: Dienstag, 17. Januar 2017 um 18:25 Uhr
> Von: "Colin Law"
> An: "OWFS (One-wire file system) discussion and help"
>
> Betreff: Re: [Owfs-developers] Problem with owh
On 17 January 2017 at 16:31, Ritchie wrote:
> >then after that what does
> >sudo systemctl status owhttpd
> >show?
>
> $ sudo systemctl start owhttpd
> sudo systemctl status owhttpd
> (white) ● owhttpd.service - Tiny webserver for 1-wire control
> Loaded: loaded (/lib/systemd/system/owhttpd
On 15 January 2017 at 17:01, Colin Law wrote:
> On 15 January 2017 at 16:25, Ritchie wrote:
>> Dear Colin,
>>
>>> Have you started owhttpd?
>>> sudo systemctl start owhttpd
>>> If so what do you see in /var/log/syslog when you start it?
>>
&g
On 15 January 2017 at 16:25, Ritchie wrote:
> Dear Colin,
>
>> Have you started owhttpd?
>> sudo systemctl start owhttpd
>> If so what do you see in /var/log/syslog when you start it?
>
> Jan 15 17:23:22 fhem3 systemd[1]: Starting Tiny webserver for 1-wire
> control...
> Jan 15 17:23:22 fhem3 syst
On 15 January 2017 at 11:56, Ritchie wrote:
> Hi all,
>
>
> the owserver is running now, but the owhttpd does not start.
> see messages:
Was my suggestion to look at the systemd service file helpful?
>
>
> $ sudo service owserver status
With systemd you should be using
sudo systemctl status ows
On 14 January 2017 at 13:33, Ritchie wrote:
>
> ~ $ sudo /etc/init.d/owhttpd restart
> [ ok ] Restarting owhttpd (via systemctl): owhttpd.service.
>
> ~ $ sudo /etc/init.d/owhttpd status
> ● owhttpd.service - Tiny webserver for 1-wire control
> Loaded: loaded (/lib/systemd/system/owhttpd.servi
On 13 January 2017 at 16:16, Ritchie wrote:
> Dear Colin,
>
> how can I get the source code of the version, described in the message,
> because I need to modify the code, to see what happen on the 1-wire bus.
> Because I am working on a 1-wire Slave AVR based for a DS2450.
https://sourceforge.net
On 12 January 2017 at 16:29, Ritchie wrote:
> Dear Jan,
>
> I just decide to reinstall the system new, which is easier than try to
> fix it.
Install owfs from the 'testing' repository using the technique in
https://sourceforge.net/p/owfs/mailman/message/35357871/
Colin
-
On 10 January 2017 at 17:09, Ritchie wrote:
> Dear Sulley,
>
> the usblib-dev is already installed:
>
> sudo apt-get install libusb-1.0.0-dev
Try
sudo apt-get install libusb-dev
Colin
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Note, selectin
On 8 January 2017 at 14:59, Jan Kandziora wrote:
> Am 08.01.2017 um 14:54 schrieb Ekkehard Pofahl:
>>
>> I am using OWFS since more than two years in different versions on a Raspi
>> 2. This alone shows, that I think it is a very good program.
>>
>> From time to time there is the "85 degree" discu
In my code (in a node-red environment) if I get a value of 85 then I
retry after a timeout (1 sec I think) and only if I get three 85 in a
row do I accept it as 85.
Colin
On 6 December 2016 at 10:04, Sven Giermann wrote:
> I have no idea of what pyownet does or how it is implemented...
> But I k
On 13 November 2016 at 22:24, Henrik Östman wrote:
> I believe this one is commonly used:
> https://www.maximintegrated.com/en/products/interface/signal-line-protection-ics/DS9503.html
I think you would need one of those for each device that you wanted to protect.
Colin
>
> // Henrik
>
> Den 20
3/temperature9
>
> eni
>
>
> On 05.11.2016 09:35, Colin Law wrote:
>
> On 5 November 2016 at 08:30, Enrico Hoepfner
> wrote:
>
>> Hello Colin,
>>
>> I've found a workaround - only use an other path to read from owfs-server
>> and dont need
evel-log from owfs-server that this is searching on
> each bus-master when I access with //.
>
> eni
>
>
>
> On 05.11.2016 09:08, Colin Law wrote:
>
> On 5 November 2016 at 07:03, eni wrote:
>
>> Hello Colin,
>>
>> I've exactly the same problem,
On 5 November 2016 at 07:03, eni wrote:
> Hello Colin,
>
> I've exactly the same problem, also with raspberry pi and w1-kernel-modul.
> I've implemented a retry on client-side (OWNet.pm), this works mostly in
> the
> second try, maximum at the fourth time.
> could it be there is a timing problem
On 14 October 2016 at 13:47, Jan Kandziora wrote:
> Am 14.10.2016 um 09:36 schrieb Colin Law:
> > On 14 October 2016 at 00:25, Jan Kandziora wrote:
> >
> >> Am 14.10.2016 um 00:01 schrieb Michael Hughes:
> >>> If I read the humidity from:
> &
On 14 October 2016 at 00:25, Jan Kandziora wrote:
> Am 14.10.2016 um 00:01 schrieb Michael Hughes:
> > If I read the humidity from:
> >
> > /uncached/1F.49D1/main/26A82915002E/humidity
> >
> > and then read the temperature from:
> >
> > /1F.49D1/main/26A82915002E/temperatu
On 13 October 2016 at 16:01, Sven Geggus
wrote:
> Hello,
>
> is there a software connecting a ESP8266+DS18B20 to an existing owfs
> infrastructure
> (e.g. owserver)?
>
> Hardware would be like this:
> http://www.elec-cafe.com/temperature-sensor-on-the-web-
> with-esp8266-and-ds18b20/
An alterna
On 1 October 2016 at 11:43, Arne Raaen wrote:
>
> Should this line be:
>
> $ sudo apt-get install -t testing owserver ow-shell
I think either will do, if they were already installed. If not
installed then it should be install obviously.
Colin
>
>
> ?
>
>
> On 09.09.2016 02.37, Jan Kandziora w
On 19 September 2016 at 13:23, Jan Kandziora wrote:
> Am 19.09.2016 um 10:42 schrieb Colin Law:
>> I have been trying
>> to get to grips with device tree and (on pi with raspbian jessie) in
>> /boot/overlays/README it says
>>
>> "Device Tree makes i
On 4 September 2016 at 19:59, Jan Kandziora wrote:
> Am 04.09.2016 um 19:08 schrieb Colin Law:
>> ...
>> To summarize then, for parasitic mode I should not need an external
>> strong pullup and should be able to use just a 1.5k pullup and to
>> specify
>> d
On 10 September 2016 at 11:52, Johan Ström wrote:
> On 10/09/16 12:13, Colin Law wrote:
>> On 10 September 2016 at 10:21, Johan Ström wrote:
>>> ...
>>> I suggest the following:
>>>
>>> a) For public site, use Github Pages with Jekyll.
>>> We
On 10 September 2016 at 13:02, Jan Kandziora wrote:
> Am 10.09.2016 um 11:22 schrieb Colin Law:
>> Is there really a need for two? Why
>> not just have everything in one?
>>
> Because of access rights. GitHub only allows full developer access to
> anything or no rights
On 10 September 2016 at 10:21, Johan Ström wrote:
> ...
> I suggest the following:
>
> a) For public site, use Github Pages with Jekyll.
> We (the developer community) would use git to push files which are
> rendered & published automatically by github on push.
> If someone is more confortable wit
On 10 September 2016 at 01:00, Jan Kandziora wrote:
> Am 08.09.2016 um 22:32 schrieb Johan Ström:
>>
>> .. what else?
>>
> First: I'd love to get rid of are these personal blogs who give stray
> information bites which are quickly outdated and totally out of control.
> This is the source of most m
On 9 September 2016 at 15:20, Matthias Urlichs wrote:
> On 09.09.2016 15:50, Uwe Bonnes wrote:
>> So you mean that */temperature* should return the thermocouple temperature
>> and */thermocouple should vanish and */coldjunction (or a similar name)
>> should appear and return the internal tempe
On 8 September 2016 at 09:20, Jan Kandziora wrote:
> Am 08.09.2016 um 09:58 schrieb Colin Law:
>> On 7 September 2016 at 23:03, Jan Kandziora wrote:
>>> ...
>>> In reality, we don't need this "simple" markup when all the people who
>>> a
On 7 September 2016 at 23:03, Jan Kandziora wrote:
> ...
> In reality, we don't need this "simple" markup when all the people who
> are contributing to the documentation are developers.
Not necessarily true. I have recently been guided on this list as to
how to interface 1-wire devices to a Raspb
On 5 September 2016 at 20:13, Jan Kandziora wrote:
> Am 05.09.2016 um 17:23 schrieb Colin Law:
>> As in an earlier thread I am using an DS18B20 directly connected to
>> GPIO pins of a Pi Zero with 1.5k pullup, operating at 3.3v. Owserver
>> is version 3.1p1-6 from raspbian
As in an earlier thread I am using an DS18B20 directly connected to
GPIO pins of a Pi Zero with 1.5k pullup, operating at 3.3v. Owserver
is version 3.1p1-6 from raspbian testing.
I have specified
dtoverlay=w1-gpio,gpiopin=4
and done
sudo modprobe w1-gpio pullup=1
This basically works, both when c
On 4 September 2016 at 19:59, Jan Kandziora wrote:
> Am 04.09.2016 um 19:08 schrieb Colin Law:
>>
>> I have it to 3.3V ok. So 4.7k is ok for 3 wire mode but for parasitic
>> it should be 1.5k
>>
> Yes.
>
>>
>> To summarize then, for parasitic mode I
On 4 September 2016 at 17:39, Jan Kandziora wrote:
> Am 04.09.2016 um 17:21 schrieb Colin Law:
>>
>> Could I ask for further clarification on this please? I have used
>> dtoverlay=w1-gpio,gpiopin=4
>> and installed the kernel module using
>> sudo modprobe w1-gpio
On 3 September 2016 at 13:04, Jan Kandziora wrote:
> Am 03.09.2016 um 10:36 schrieb Colin Law:
> ...
> 2. You have to put
>
> dtoverlay=w1-gpio,gpiopin=4
>
> or
>
> dtoverlay=w1-gpio-pullup,gpiopin=4,pullup=5
>
> into your Raspberry Pi boot partition config.txt.
On 3 September 2016 at 14:00, Colin Law wrote:
> On 3 September 2016 at 13:45, Jan Kandziora wrote:
>> Am 03.09.2016 um 14:28 schrieb Colin Law:
>>>
>>> Many thanks
>>>
>> I missed one thing: you have to load the w1-gpio kernel module!
>
> Whic
On 3 September 2016 at 13:45, Jan Kandziora wrote:
> Am 03.09.2016 um 14:28 schrieb Colin Law:
>>
>> Many thanks
>>
> I missed one thing: you have to load the w1-gpio kernel module!
Which I do, I think, by running (only once)
sudo
On 3 September 2016 at 13:04, Jan Kandziora wrote:
> Am 03.09.2016 um 10:36 schrieb Colin Law:
>> I want to use owserver on a raspberry pi (zero) running Raspbian
>> (Jessie) using the method of direct connection to GPIO pins with a
>> pullup resistor. Unfortunately I have f
I want to use owserver on a raspberry pi (zero) running Raspbian
(Jessie) using the method of direct connection to GPIO pins with a
pullup resistor. Unfortunately I have found a fair amount of
conflicting and confusing information on this around the web. Is
there an up to date and authoritative w
On 1 May 2016 at 12:35, John Bass wrote:
> Hello Colin,
>
> You got it, with a 1k resistor(which Jan recommended rather than a 4.7k) from
> VDD to DQ as the pull up..
Not from VDD, from 3v to DQ.
Colin
>
> I'm miffed as well...
>
> John
>
> -Orig
run a few more tests soon, as Jan does not seem to be able to
> reproduce the issue, there must be something wrong here.
>
> I will test the sensor with all three wires connected to make sure it has not
> gone south.
>
> John
>
> -Original Message-
> From: Coli
On 30 April 2016 at 09:35, John Bass wrote:
> OK, just had a read around the good old internet, and found other people with
> the same issue, down to power yet again..
>
> So popped another 1k in parallel thus 500ohms and now it works :-), but not
> reliable :-( getting the odd 85
How long is t
lp
Colin
> Mick
>
> On 29/04/16 16:53, Colin Law wrote:
>> On 29 April 2016 at 16:28, Mick Sulley wrote:
>>> As I was getting desperate I delete ow* from /usr/bin and reinstalled 3.0.0
>>> Just run your commands and I get -
>>>
>>> co
aid you purged owfs, but it is owserver that is installed, so
apt-get purge owserver
Colin
>
>
> On 29/04/16 16:15, Colin Law wrote:
>> On 29 April 2016 at 15:42, Mick Sulley wrote:
>>> My Raspi failed overnight and I am trying to recreate it and pulling my
>>>
On 29 April 2016 at 15:42, Mick Sulley wrote:
> My Raspi failed overnight and I am trying to recreate it and pulling my
> hair out!! I have installed owfs many times, generally downloading from
> SourceForge and installing from that. I have done that this time, it
> didn't work so I removed it (
On 1 March 2016 at 21:56, Peter Hollenbeck wrote:
> I must have something else wrong. When I connect the DS18B20 without a
> resistor the MS-TV disappears.
Is that with the correct connections or the original wrong ones?
Correct the wiring, if it is wrong, and try again. Check the manual
for the
On 1 March 2016 at 18:48, Peter Hollenbeck wrote:
> I have a Raspberry Pi with LinkUSB and a MS-TV reading DC voltage. This
> works.
> Yesterday I added an Adafruit DS18B20 waterproof temperature sensor and it
> worked for a while.
> This morning neither the MS-TV nor the DS18B20 are seen by owfs.
On 24 February 2016 at 14:57, Arley Carter wrote:
> Jerry:
> Forgive me if you consider these stupid questions. Why is your house so
> complex?
> How does this development project add value to your house?
>
> The humble thermostat does the job for me. It is cheap and has never
> failed me and has
On 8 November 2015 at 01:32, Peter Hollenbeck wrote:
> I've not attempted I2C.
> Fear and trembling.
Since you already have the linkusb there is no need to change what you
have. Just connect the other devices to the linkusb along with the
existing sensor.
If you did not have the linkusb then us
On 7 November 2015 at 18:29, Jan Kandziora wrote:
> Am 07.11.2015 um 17:24 schrieb Colin Law:
>>>
>>> *BUT* this only works when the host ground is *not connected* to earth,
>>> not even by a noise filter.
>>> As soon it is, your circuit isn't symetric
On 7 November 2015 at 15:18, Jan Kandziora wrote:
> Am 07.11.2015 um 10:26 schrieb Colin Law:
>>>
>>> When you connect the ground line to data-, you have a different current
>>> on the common ground/data- line because the ground line also carries the
>>>
On 6 November 2015 at 23:33, Jan Kandziora wrote:
> Am 06.11.2015 um 23:35 schrieb Colin Law:
>>
>> What twisted pair does do is to reduce electromagnetic pickup.
> ...
>
> But it is the also the reason it doesn't work this way for onewire.
> Because one
On 6 November 2015 at 22:30, Jan Kandziora wrote:
> Am 06.11.2015 um 23:15 schrieb Colin Reese:
>> Pairing conductors eliminates capacitance problem.
>>
> No, it doesn't. You always have ground capacitance, the only way to
> avoid that is separating the DQ wire from the ground wire as far as
> pos
On 21 September 2015 at 09:50, Nico Bouthoorn wrote:
>
> I'm really puzzled, last night i've got a main power shortage. I'm running
> the owfs on a beaglebone (http://fstab.nl/beaglebone) with linux Debian
> This was working fine for years. Now the owserver don't detect the
> ds2482-800 devic
On 6 June 2015 at 14:05, Reid wrote:
> Thanks Colin, can you point me to any good examples of the use of owserver
> with the USB D9490R interface.
I use the linkusb interface, but I don't think there should be much
difference. To start owserver I just do
owserver -d /dev/ttyUSB1
By the way, I w
On 6 June 2015 at 11:06, Reid wrote:
> Thanks Mick, I had rebooted but when I saw the file /mnt/1wire I thought the
> other files would still be there. When I checked all the subfolders had
> magically disappeared. This is good news but a little alarming that files
> can disappear when you reboot
On 20 May 2015 at 18:43, DavidJ61 wrote:
> I really don't believe it. The device directories has suddenly appeared in
> /mnt/1wire hours after I finished trying to get it working. As for the
> owpython, I've given up on that and opted for just reading the values
> directly from the directory struc
On 29 March 2015 at 15:34, Michael Kalist wrote:
> Sorry I thought I had that included.
>
>
> This parts displays on the screen correctly
> echo -e Garage In $temp1"\n"Garage Return $temp2"\n""\n"Bedroom IN
> $temp3"\n"Bedroom Return $temp4"\n""\n"Main Floor IN $temp5"\n"Main Floor
> RTN $temp6"\n
On 29 March 2015 at 14:32, wrote:
> Hey All I cant seem to get this working. Temps either show wrong temp or no
> temp in graphs.
The first thing to do is to work out which bit is failing. See below
> ...
> #!/bin/bash
>
> # Read temperature from sensor
>
> temp1=`cat /mnt/owfs/uncached/Garag
On 10 January 2015 at 12:51, Ekkehard Pofahl wrote:
> Stefano,
>
> Thank you !
>
> This works. Although it is not obvious for me, why it has to be that
> tidious, ;-) .
When you install a package it installs that package and may also
install other packages that the first one needs in order to fun
On 6 October 2014 04:30, Paul Alfille wrote:
> After all the discussion about serial and usb pairing, I created a new
> little program that does it, called tty2usb
>
> http://sourceforge.net/projects/tty2usb
>
> Currently it only works on linux, but OSX and freebsd would be useful to
> add.
>
> Ex
On 28 September 2014 15:00, Chris Green wrote:
> I have a 1-wire installation which I am trying to diagnose remotely.
>
> A few days ago I had to replace the Beaglebone Black that was running
> with another one becuase I corrupted the memory on the original one
> and didn't have the ability to fix
On 25 September 2014 11:10, Stefano Miccoli wrote:
>
> On 24 Sep 2014, at 16:21, Tomasz Torcz wrote:
>
> On Wed, Sep 24, 2014 at 04:09:23PM +0200, Ekkehard Pofahl wrote:
>
> 2014-09-24 12:29 GMT+02:00 Colin Law :
>
> unplug a linkUSB and plug it straight back in then it m
On 24 September 2014 15:21, Tomasz Torcz wrote:
> On Wed, Sep 24, 2014 at 04:09:23PM +0200, Ekkehard Pofahl wrote:
>> 2014-09-24 12:29 GMT+02:00 Colin Law :
>>
>> > unplug a linkUSB and plug it straight back in then it may change
>>
>>
>> Agreed. But plug
On 24 September 2014 15:09, Ekkehard Pofahl wrote:
>
> 2014-09-24 12:29 GMT+02:00 Colin Law :
>>
>> unplug a linkUSB and plug it straight back in then it may change
>
>
> Agreed. But plugging and unplugging is usually not done on a "production"
> syst
On 24 September 2014 11:08, Ekkehard Pofahl wrote:
>
> 2014-09-24 11:45 GMT+02:00 Colin Law :
>>
>> Whilst useful, that will not get round the problem that ttyusb devices
>> do not always connect with the same device number.
>
>
> Very true. Just make a
On 24 September 2014 09:44, Ekkehard Pofahl wrote:
> Hello,
>
> I agree, that the OWFS server should not start testing each and every
> possibility of the system, to find, whether there are 1-Wire devices
> connected.
>
> To resolve this I suggest to implement something like
>
> "sudo service owse
1 - 100 of 191 matches
Mail list logo
