Am 12.11.2014 um 08:36 schrieb Andrey:
> Hello.
> I'm developing custom 1-wire devices, based on MSP430 chips.
> Those chips can implement ds2406 + ds1820 + ds2438 in one 1-wire slave.
>
> Is there some kind of “reserved for custom devices” address pool/family
> code I could use? Or may be I must
Am 12.11.2014 um 08:36 schrieb Andrey:
> Hello.
> I'm developing custom 1-wire devices, based on MSP430 chips.
> Those chips can implement ds2406 + ds1820 + ds2438 in one 1-wire slave.
>
Oh, and to prevent you reinventing the wheel: there are Pascal Baertens
BAE0910 and BAE0911 chips, which are re
Am 21.11.2014 um 19:56 schrieb Jerry Scharf:
> Hi,
>
> I am looking at using the MAX31850 chip for my test setup. It is a 3.3V
> only device (will not take 5V on power.) Are there any bus masters
> and/or switches that support 3.3V for the power and data lines?
>
I'd say, don't use parasite pow
Am 23.11.2014 um 09:13 schrieb Jerry Scharf:
>
> I am using a flash only system to be the master of my system for testing
> 300 power supplies. I want to use a MVC database/web design. In a normal
> disk based system, I wouldn't give the fact that the state of the each
> power supplies and micr
Am 01.12.2014 um 07:16 schrieb Андрей Штых:
>
> I have the following problem:
> I connected to my raspberry pi to the LCD display. I used the bus master
> 1-wire DS2482-100. Next bus connected to it DS2408S and LSD display.
> Compiled from source owfs 2.9p8, does not work at all. Any attempt to w
Am 08.12.2014 um 19:14 schrieb Csillag Kristof:
> On 2014-12-08 18:35, Colin Reese wrote:
>> Check the datasheet. These parameters are well-documented.
>
> I tried to.
>
> I looked at http://datasheets.maximintegrated.com/en/ds/DS1921G.pdf
>
> It does not seem to contain the word "easystart".
>
Am 12.12.2014 um 12:03 schrieb joep:
>
> The output of lsmod includes:
> .
> "ds2490 6924 0"
> .
>
If you plan to use owfs with the internal libusb-based driver (--usb
option), you have to blacklist that module. A MUST!
You can use that m
Am 13.12.2014 um 10:54 schrieb joep:
> Hi Jan,
> I confirmed that by blacklisting the ds2490 module the
> errors I was getting (before I did anything with owfs) stopped. I
> blacklisted by including a .conf file in */etc/modprobe.d* with a
> 'blacklist' entry. After reboot the ds2490 w
Am 17.12.2014 um 18:06 schrieb Vasco:
>
> I thought it depends on lack of "magic sequence" that can be sent to
> chips to exit from test mode,
> but if the chip is in test mode only P0
> output does not respond; in my system when a chip does not respond, it
> has the same behavior on all ports ,
Hi,
I just switched over to the sf.net git archive and I see no release
tags, 2.9p1 and so on. Shouldn't there be some?
Maybe you all just missed
$ git push --tags
?
Kind regards
Jan
--
Download BIRT iHub F-T
Am 21.12.2014 um 15:16 schrieb Jan Kandziora:
> Hi,
>
> I just switched over to the sf.net git archive and I see no release
> tags, 2.9p1 and so on. Shouldn't there be some?
>
Ok, I just sorted them all out by hand and pushed the whole list. So
don't wonder when you pull
Am 02.01.2015 um 16:08 schrieb Jan Sennesael:
> Everything was running fine, but when i tried to add a couple of sensors i
> run into some troubles: Since these sensors are on the other side of the
> house, is added a long utp cat5e cable (long= 25m a 30m)
>
Don't use a pair for 1W and GND, as the
Am 03.01.2015 um 09:49 schrieb Jan Sennesael:
>
> @Jan: now i'm a bit surprised, since maxim themselves talk about using
> cat5(e).
>
Where? If yes, they forgot about all they've written in various
application notes before.
In my own experience, plain flat telephone wire is the best.
> Of course
Am 04.01.2015 um 17:33 schrieb Jan Sennesael:
> @Jan: in the document linked by Paul
> (http://www.maximintegrated.com/en/app-notes/index.mvp/id/148) they start by
> saying "The scope of this document is limited to 1-Wire networks that use
> Category 5, twisted-pair copper wire and have 5V bus powe
Am 04.02.2015 um 09:23 schrieb Torrini, Eugenio:
> We are using Owfs in Linux to access a DS1991 and DS1995 through the USB
> DS9490R reader.
> Everything is ok for DS1995.
> For DS1991 we are not able to make it work. Maybe we are doing something
> wrong.
> We know the password of the 3 pages of
Am 10.02.2015 um 16:29 schrieb Lukasz Salwinski:
>
> I've checked the connections, changed Vcc to 5V but 18B20s still does not
> register :o/ DS2483 are on the way but in the I'm tempted to connect the
> sensors directly to rpi just to see if they are ok...
>
Have you made sure the w1 driver is
Am 10.02.2015 um 22:39 schrieb Colin Reese:
> Wait, is that even possible? I thought w1 was for bitbanging on a GPIO,
> having nothing to do with i2c.
>
There are w1 kernel drivers for ds2482, ds2490, bitbanging on a GPIO and
the synthesizeable ds1wm bus master.
CONFIG_W1_MASTER_DS2490=m
CONFIG_W
Am 10.02.2015 um 22:51 schrieb Lukasz Salwinski:
>
> w1 is hardwired to GPIO4 so I'm using GPIO17 to control SLPZ; I can toggle
> DS2484 on/off by setting GPIO17 to 1/0. it seems to be another indicator
> i2c side works fine... it's that just nothing shows up on the 1-wire side :o/
> lukasz
>
N
Am 11.02.2015 um 17:02 schrieb Lukasz Salwinski:
>
> I see... I've been religiously inserting ds2482 module. Does it mean
> I only need i2c_bcm2708 and i2c_dev modules ? Besides ds2482 (explicitly
> inserted) modprobe also returns
>
That's correct. Owfs can (and with --i2c= will) directly talk to
Am 11.02.2015 um 20:12 schrieb Colin Reese:
> Why on earth would you bitbang a 2482 on a Pi when a perfectly good
> i2c bus exists?
>
I beg your pardon?
Bitbanging *onewire* requires no additional chip and is done through a
configureable GPIO on the Raspberry Pi.
In addition, the w1 kernel drive
Am 11.02.2015 um 20:39 schrieb Colin Reese:
> I found the initial post of available methods confusing and
> apparently misinterpreted your response.
>
Sorry, I should have used the serial comma.
http://www.verbicidemagazine.com/wp-content/uploads/2011/09/Oxford-Comma.jpg
Kind regards
Ja
Am 12.02.2015 um 17:19 schrieb Lukasz Salwinski:
>
> not loading ds2482 module did not help - the owfs filesystem is there:
>
Sorting that obvious error out:
Have you connected Vdd of the DS18B20 to GND? That's important if you
want parasite-power mode. But powering the chip with 5V would be bet
Am 15.02.2015 um 21:48 schrieb Colin Reese:
> Yes just run a micro controller non-stop and have it announce presence over a
> serial port.
>
No, USB. I made a simple software for doing this on a random ATtiny
processor with the help of the V-USB firmware.
http://vusb.wikidot.com/project:vusb
K
Am 18.02.2015 um 08:23 schrieb Gregg Levine:
>
> In it he writes that it needed a 4.7K pull up resistor to Vbat. Well I
> found one and attached it. Same strange behavior as before. But what I'm
> concerned with more is what are the rest of us doing with their parts? What
> resistor value was sele
Am 18.02.2015 um 15:34 schrieb Martin Rapavy:
> To add some technical details to my query: the bus master chip in
> question si very similiar to DS1WM (which is something like
> DS2482-800 but with memory-mapped registers, instead of I2C access).
> After browsing the sources for some time I conclud
Am 18.02.2015 um 21:19 schrieb Martin Rapavy:
> I was exactly in favor of avoiding w1 because of bus polling. It is
> important for me not to use the bus frequently (the wire is also
> shared for reading out data from sensors). Do you think that the w1
> polling might be turned off using w1_master_
Am 18.02.2015 um 21:58 schrieb Martin Rapavy:
Option C Memory-mapped IO from userspace, which is
*UGH!*. See module/owlib/src/c/ow/ow_ds2482.c for all the
things to write and change. The disadvantage is owfs has to run
as root to do MMIO.
>>> I don't mind running under
Am 18.02.2015 um 23:07 schrieb Gregg Levine:
> Hello!
> He cited that the resistor was connected to the counter inputs to the
> Voltage Battery input point.
>
> However I'm more inclined to try your idea then his. Which is of
> course what I'm looking for.
>
You certainly need a capacitor for debo
Am 19.02.2015 um 08:59 schrieb Martin Rapavy:
> Hi Paul,
>
> thanks for briefing me on the architecture of OWFS. My master chip
> has almost exactly the same register interface as Dallas DS1WM
> (http://datasheets.maximintegrated.com/en/ds/DS1WM.pdf). It only
> differs in one register: Clock divis
Am 20.02.2015 um 21:40 schrieb Matthias Urlichs:
>
> for home automation I'm (finally) going to implement a couple of
> semi-intelligent 1wire slaves. Control the heating system, water the garden,
> and other things that can't be done by a central server and dumb 1wire
> slaves because the house w
Am 21.02.2015 um 04:49 schrieb Gregg Levine:
> Hello!
> Okay it works as expected with the chosen components to support
> debounce. Oh and I used a magnetically triggered mechanical switch to
> try it.
>
> Next question, can you Jan supply me with a copy of your software? As
> it happens I'd like
Am 21.02.2015 um 08:08 schrieb Matthias Urlichs:
> Jan Kandziora writes:
>
>> I strongly recommend to use Pascal Baerten's BAE0911 device instead of
>> developing a slave on your own.
>
> I already _have_ a slave of my own. (AVR-based; writing code that talks to
&g
Am 21.02.2015 um 08:08 schrieb Matthias Urlichs:
>
> Or the capacitive sensors I want to use (can the BAE0911 even do
> that? an atmega supports them without any additional hardware).
>
You mean a capacitive keyboard? That's only software, on any µC.
The only difference between AVR and any other
Am 21.02.2015 um 21:21 schrieb Peter Hollenbeck:
>
> The higher the value the lower the output.
>
This usually means there already is a voltage divider (or at least a
parallel resistance) in the measurement device and you are superposing
another. You could measure it and calculate the outer pair, b
Am 03.03.2015 um 01:12 schrieb Eloy Paris:
>
>> Hey guys, is this 1-wire? The labelling suggests it is. if so - it's a very
>> good deal.
>>
>> http://www.dx.com/p/temperature-humidity-sensor-dht11-module-for-arduino-deep-blue-works-with-official-arduino-board-288612?utm_source=dx&utm_medium=edm&u
Am 05.03.2015 um 00:10 schrieb Mick Sulley:
>
> I see on the spec sheets for most devices it says max voltage is 5.5v,
> from your experience is it possible to go above that and if so what is
> the maximum?
>
The datasheet of DS2482-800 also says +6V is absolute maximum rating to
prevent permanen
Am 05.03.2015 um 00:59 schrieb Mick Sulley:
> Volt drop on some of the cable runs. Just thought if I started with a
> higher voltage there would be more left at the end:)
>
Before voltage drop on the 1W line gets a problem, you have a problem on
the GND line.
That is because when you have 1V dro
Am 19.03.2015 um 23:06 schrieb Eric Baumann:
>
> Why is the USB disabled?
>
Because you have the libusb devel packages not installed. This is
required while compiling owfs for USB support.
Kind regards
Jan
--
Am 20.03.2015 um 09:36 schrieb Eric Baumann:
>
> I did do
>
> sudo apt-get install libusb-dev
>
> Is this not enough?
>
Depending on your distribution, you may also need a separate
libusb0-compat-dev package
> Where can I find complete installation instructions?
>
These would be distribution
Am 01.04.2015 um 16:15 schrieb HRueck:
> when I want to update to a newer version, do I have to just install the newer
> one or do I have to uninstall first the older one?
>
This depends how you have "installed" owfs. If you have installed owfs
through the package manager of your Linux distributio
Am 01.04.2015 um 19:52 schrieb Ritchie:
> Hi to all,
>
> I am fighting with my 1-wire installation, where I have one bus of five,
> who drives me crazy. I still get a lot of failure in the statistic.
> I checked already cabling, bus structure.
>
How long is your bus? How long are stubs? Which kin
Am 06.04.2015 um 14:26 schrieb Major:
> DEBUG: ow_transaction.c:(222) verify = 1
> * DEBUG: ow_presence.c:(267) Presence of 28 DC 7F DE 05 00 00 84 NOT found
> on bus w1_bus_master1
>
This is the actual error message. If the chip isn't there, you cannot
access its directory.
Check for occassion
Am 07.04.2015 um 22:09 schrieb Ritchie:
>
> Do I have the chance to see, which "1-wire Partner" has/makes the
> problem. Up to now, I just check the values above.
>
A SEARCH involves *all* the slaves on a bus simultaneously, so it's not
really possible to find a single culprit without removing and
Am 29.04.2015 um 02:04 schrieb Paul W Panish:
> I’m providing power and
> ground through the CAT5e cabling.
>
I assume you use one wire for +5V, one wire for 1W and six wires for
GND? That would be correct.
>
> The errors are not just on access to the temperature sensors (which are
> hot), but
Am 29.04.2015 um 18:35 schrieb Paul W Panish:
>
> Thanks for that, I'll implement the verification on write, I didn't
> realize that I could read from the output register without affecting
> state. This may be enough to get the levels of reliability I need.
>
Actually, the DS2408 PIO write comman
Am 30.04.2015 um 04:11 schrieb Loren Amelang:
> 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
Am 30.04.2015 um 14:28 schrieb Paul W Panish:
>
> I have some questions on your comments. The issue of the w1 drivers
> is new to me, and sounds like it may be an explanation of what I'm
> seeing, though I still don't understand why there should be a
> temperature dependence.
>
I don't see any co
Am 16.05.2015 um 20:08 schrieb Matthias Urlichs:
> The MoaT (Master of all Things) is not -- it's a slave :-P
>
Nice, will test this soon, Matthias.
Kind regards
Jan
--
One dashboard for servers and applications
Am 17.05.2015 um 11:21 schrieb Henry:
>
> The "owdir /" by owserver of my raspberian Raspberry is too slow and
> sometimes blind, it not see first 1w-device (in a list by abc) always and
> show next 1w-devices after long time.
>
Having a device listed in / does not mean it is connected to the bus
Am 18.05.2015 um 15:37 schrieb Henry:
>
> I don't think that problem is in a cache. Yet in a debug we can see
> "Byte buffer Data" with full list of my devices. (20 FA 5F 0E 00 00 00)
>
Yes, I see it. Seems owfs is ignoring that result from W1_CMD_SEARCH
from some reason.
Paul has to help here,
Am 27.05.2015 um 07:26 schrieb - -:
>
> That is the main Point. Activation for the simultaneous convert only at the
> Startup from the whole System and having it the whole time active.
>
No. "Simultaneous/temperature" isn't a setting but a bus command which
skips the chip addressing step, then im
Am 22.06.2015 um 14:04 schrieb Eric Baumann:
>
> I have trouble reading from the Hobby Boards Barometer board.
> It seems to be stuck at these values:
> pi@raspberrypi /mnt/1wire/EF.2D652015/barometer $ cat pressure
> 67920
> pi@raspberrypi /mnt/1wire/EF.2D652015/barometer $ cat temperatur
Am 05.07.2015 um 01:54 schrieb Gregg Levine:
> Hello! Can someone confirm or refute this statement?
>
> OWFS supports all devices from the vendor (MAXIM once Dallas
> Semiconductor) no matter how old, and even if they were discontinued
> by them.
>
For the current list of non-supported chips, l
Am 04.09.2015 um 03:59 schrieb Matthias Urlichs:
> This can only be some data somebody forgot to initialize:
>
> # owserver
> [core dump]
>
Just a random guess, disable Zeroconf (--nozero). It's been always the
culprit in all random segfaults I had with owserver, owfs et al.
Kind regards
Am 08.09.2015 um 17:02 schrieb Mick Sulley:
> No configuration files to monitor
>
Well, it's this.
And I doubt /dev/i2c is an existing device node. More likely it's
/dev/i2c-0 or similar.
Kind regards
Jan
--
___
Am 20.09.2015 um 19:21 schrieb Markus Gaugusch:
>
> I have samples of ds2480b and ds2482-800. I don't have a max3232 around to
> convert serial between 3,3V and 5V. Pin7 (GPIO4) is used by DHT22 humidity
> sensor, but possibly I can use another pin for that one.
> I usually solder using breadboa
Hi Paul, Sven and all who it may concern,
I have a legitimate use for --external. I use Raspberry Pis as field I/O
expanders and it mainly uses onewire. BUT I also have some local inputs
and outputs connected to GPIOs. I want these GPIOs to blend into the
owfs structure so I can easily access them
Am 21.09.2015 um 07:28 schrieb Sven Giermann:
> Well, I would like to...
> But I've no experience in debugging on linux, so I had no luck to get it
> running. My "solution" now is to switch all I/O ports to pure 1-Wire, but I
> would still be interested in getting this to work!
>
I now tried on my
Am 21.09.2015 um 23:29 schrieb Jan Kandziora:
>
> Fortunately, I can narrow these crashes down to undefined behaviour
>
> * when a property in the config file is of for example "u" type
> * and the script called does not return any data, or something which
> ca
Am 21.09.2015 um 23:29 schrieb Jan Kandziora:
>
> Still, the tcl language binding seem to have its own crash culprit. Have
> to investigate further.
>
Another oddity: while
* owdir, owread, owget etc. have no problems reading an external node
* owfs and the tcl language bindi
Am 22.09.2015 um 08:50 schrieb Sven Giermann:
>
> What about trying to patch the fake adapter or maybe any other to always
> return -EINVAL - does owserver crash as well?
>
As you siggested, I have patched FS_read_fake_single() so that it always
returns -EINVAL. If I specify
/opt/owfs/bin/owserve
Am 22.09.2015 um 18:47 schrieb Jan Kandziora:
>
> However, if I start the owserver with
>
> /opt/owfs/bin/owserver --debug --fake=FC.67C6697351FF --external
> --configuration=owexternal-test.conf
>
> instead, it crashes upon reading the same node, with both programs.
Am 23.09.2015 um 14:35 schrieb Alex R. Gibbs:
>
> We have dozens of DS18B20 temperature sensors at 3 telescopes. I'd like to
> poll
> them and cache the results so that other programs can retrieve the latest
> temperatures with less than 50ms delay.
>
So basically, you want the other programs
Am 23.09.2015 um 20:14 schrieb Colin Reese:
> Is there a way to set the cache delay?
>
IIRC temperature values are cached as set in settings/timeout/volatile,
in seconds.
> There is the case where you
> don't want sensors read every second (for power consumption, load, or
> other reasons), but w
Am 21.09.2015 um 23:29 schrieb Jan Kandziora:
>
> Still, the tcl language binding seem to have its own crash culprit. Have
> to investigate further.
>
Owlib and all the language bindings depending on it (that is: all that
are not ownet) had another set of bugs which made the clien
Am 21.09.2015 um 23:29 schrieb Jan Kandziora:
> Am 21.09.2015 um 07:28 schrieb Sven Giermann:
>> Well, I would like to...
>> But I've no experience in debugging on linux, so I had no luck to get it
>> running. My "solution" now is to switch all I/O ports to
Am 25.09.2015 um 22:45 schrieb Stefano Miccoli:
> I’m unable to compile on my raspberry pi with Arch Linux ARM:
>
> [...]
>
> After deleting those lines compilation is fine. Unfortunately I cannot test
> USB
> support since I do not have an USB adapter at hand.
>
Stefano,
actually that is beca
Am 30.09.2015 um 14:29 schrieb henry.poo...@regall.net:
> Hello, please How I can contact with Paul?
>
I don't know, his last message was from April, so maybe he's gone...
> I have old and strange problem:
>
> #
> # After long time (2 minutes about) I've got a result:
> #
> #/uncached/20.2B660E0
Am 30.09.2015 um 17:44 schrieb Henry Pootel:
>
> Oh. I've lot of 1w devices which are connected to 4 pin of GPIO
> Raspberry PI.
>
Ah, I see it. Okay, that's a valid reason you want to use the kernel
driver because bitbanging doesn't work too well in userland (needs
realtime scheduling etc.).
Ho
Am 30.09.2015 um 19:45 schrieb Henry Pootel:
>
> I use a kernel v3.12 with w1-gpio module now. The owfs is working
> with errors.
>
> When I check devices by owdir commands, it sometimes lose one or
> more sensors or make a double of existing sensors.
>
Do you run the onewire with 3.3V from the R
Am 01.10.2015 um 10:10 schrieb Henry Pootel:
>
>> Do you run the onewire with 3.3V from the Raspberry's I/O pin? If so,
>> have you checked all your slaves are 3.3V compatible?
>>
>
> No, I use 5V for Rasberry and for w1 devices. It's one 5VDC power supply.
>
Henry, all the I/O pins on the pin he
Am 02.10.2015 um 13:48 schrieb Henry Pootel:
>
> Please look at my pictures. I've got a signal of 1wire busline.
>
The transitions seem ok.
> Do you advise to transfer from 1w_henry to 1w_henry_2 scheme?
> Is the second scheme right?
>
Yes. Yes. Because the Raspi doesn't like 5V on its GPIOs.
Am 02.10.2015 um 13:48 schrieb Henry Pootel:
>
> Do you have a lab with PI and four or more 1W devises on GPIO line
> without DS1WM ? If so, would you show me results of your owdir test?
> (I mean lot of requests to owserver by owdir command.)
>
I checked with linux-3.10.28, a single DS18S20, 1kO
Am 02.10.2015 um 22:25 schrieb Loren Amelang:
>
> So is your 1K pull-up really the specification for a 3.3V supply?
> Could it somehow change my temperature readings?
>
Loren, the bus pullup resistor only affects how fast the Low->High edge
rises after all devices on the bus disable their output
Am 02.10.2015 um 22:25 schrieb Loren Amelang:
>
> Now I get solid, repeatable readings, but one sensor reads 2 degrees
> C above what it read in another system with a 5V bus, and the other
> reads 5C high. (I got distracted by other projects and never resolved
> how that could happen...)
>
A ques
Am 05.10.2015 um 00:45 schrieb Loren Amelang:
>
> I noticed in "28.D6478800/errata": --- up directory die
> C2 trim48077 <-- trimblanket trimvalid NO (0) <-- but
> uncached or reload showed YES... ---
>
> While in "28.884D8800/errata": --- up directory die C2
>
Am 05.10.2015 um 14:23 schrieb Alex R. Gibbs:
>
> However, other clients will have to wait if they happen
> to query owserver during the conversion/read.
>
No. That can only happen if you use parasite powered sensors. Because
parasite power occupies the bus during temperature conversion for
poweri
Am 05.10.2015 um 16:21 schrieb Johan Ström:
>
> (I'm almost sure of this, and I cannot find any evidence of read
> operations executed in ow_simultanous. But please correct me if I'm wrong)
>
No, you are right. Sensors aren't read when triggering simultaneous.
Kind regards
Jan
---
Am 05.10.2015 um 22:25 schrieb Loren Amelang:
>
> Apparently only the "X" part is variable? But they say "A failure
> can be expected to effectively randomize the TH and TL values and can
> induce temperature measurement errors of up to ±60 Degrees
> Celsius." They can't be coding 120C into fi
Am 06.10.2015 um 09:35 schrieb Alex R. Gibbs:
> Hi Jan,
>
> It turns out the sensors are parasite powered. :/ We bought them from
> iButtonLink already packaged that way.
>
Which sensor do you use? Besides the T-Probe-Pipe sensor, they all can
be used as a powered device, too. Just apply +5V to
Am 07.10.2015 um 05:32 schrieb Loren Amelang:
>
>> If you do bitbanging, it is sufficient to unload the w1-gpio driver
>> to have the bus unpowered. Part of its cleanup routine is to float
>> the GPIO pin. I don't think there is another reason but an
>> (unlikely) bug inside w1-gpio to have the bu
Am 09.10.2015 um 07:15 schrieb Loren Amelang:
>
> I modified my Python to read the OWFS "files" more often.
>
> I hope this is interesting enough to justify its length... I believe,
> and see on my scope, that OWFS only reads at 15-second intervals. But
> in the new logs I see changes that pers
Am 09.10.2015 um 21:17 schrieb Loren Amelang:
>
> --> My 14.04 system adds two values to the example shown on that
> page: ha7 60 w1 30
>
> No idea what ha7 is, but I assume w1 is a timeout for declaring that
> no response was received from the w1 mechanism, not a specification
> of how of
Am 11.10.2015 um 08:34 schrieb Loren Amelang:
>
> I see now that is created by w1, independent of OWFS!
>
YES. Most modern Linux distributions have a "sysfs" mounted at /sys.
This pseudo-filesystem exports various static and dynamic information
and settings of the kernel and kernel drivers to use
Am 14.10.2015 um 03:34 schrieb Colin Reese:
>
> I was in the process of updating libraries with new device and had a few
> questions:
>
> 1. Is there a more updated device list than Maxim's here:
>
> https://www.maximintegrated.com/en/app-notes/index.mvp/id/155
>
I don't think so. Though Maxim
Am 19.10.2015 um 22:28 schrieb Loren Amelang:
>
> [...]
> reading with just over 1000 Ohms as a pullup, maintaining the 1-Wire
> bus voltage at just under 3.0 V during conversion. The other DS18B20
> requires a pullup below 600 Ohms and a bus voltage above 3.1 V to
> reach accuracy - but with suffi
Am 20.10.2015 um 20:00 schrieb Ritchie:
>
> I try to analyse the problem with my logic analyser but I can not catch
> so many values and always miss the data of the DS2423. Can I disable the
> function of trying to find new chips on the bus and send only a single
> command to the DS2423 (maybe
Am 21.10.2015 um 02:45 schrieb Loren Amelang:
>
> This is the first I've heard that the w1 driver is supposed to
> implement a strong pullup|
>
Yes, the w1 driver supports it. But you have a beagleboard, which uses a
board definition file to configure its GPIOs, and if that one
accidentally doesn
Am 21.10.2015 um 19:36 schrieb Ritchie:
>
> thanks for taking a closer look too it, but I may try to find a way,
> that the owserver will only send information on request.
>
> Creating extra builds it not needed...
>
> I just thought it was easy to get a dump.
>
> Is there maybe a other good do
Am 22.10.2015 um 12:26 schrieb rot...@gmx.de:
>
> Do they read out the memory page by more than one block and uses the address
> byte as a offset ?
>
When you access any of the counter nodes, owfs doesn't read the memory
contents but only the counter. TA1/TA2 are set to the last byte of
memory in
Am 29.10.2015 um 20:36 schrieb Ritchie:
> Hi to all,
>
> in which Module of the OWFS Server do I have to take a closer look
> in matter of the Read/Write/Copy Scratch Pad function.
>
Are you still working on you DS2423 clone? Then at
module/owlib/src/c/ow_2423.c
See the ow_w_mem function at lin
Am 04.11.2015 um 12:32 schrieb Martin Patzak (GMX):
>
> while further investigating the problem it looks like this:
>
> the value of sensed.BYTE toggles between *55* (00110111) and *183*
> (10110111) for quite a while - so its only flipping one bit.
>
> When I increase the toggling speed, I can
Am 04.11.2015 um 14:46 schrieb Martin Patzak (GMX):
>
> I do not import ow or ownet, but read the file directly in the
> file-system mounted by owfs
> I started out years ago with perl and then transferred part to python. I
> never got around using ow or ownet.
>
In that case, your problem is n
Am 04.11.2015 um 15:17 schrieb Jan Kandziora:
>
> I recommend you to turn away from the owfs pseudofilesystem and use one
> of the language bindings. Or exec() the "owput" and "owget" utilities
>
Sorry, has to read "owwrite" inst
Am 04.11.2015 um 15:56 schrieb Stefano Miccoli:
> I would not blame python, nor owfs, but fuse.
>
Not, it's not fuse.
It's because read() is *not atomic*. As soon you read multi-byte values
from files -such as files whioch contain an ASCII representation of
numbers, as owfs has- you have to take
Am 06.11.2015 um 16:32 schrieb Martin Patzak (GMX):
> Hello All,
>
> owserver version 2.9p8 does not print information set by --error_level
> and the use of --foreground or --debug
>
--debug implies --foreground and --error_level settings, so no need to
set these.
>
> It only seems to print the
Am 06.11.2015 um 21:24 schrieb Peter Hollenbeck:
> I ordered one of these:
> Waterproof DS18B20 Digital temperature sensor
>
> Where I want to measure is 170 feet
>
What do you want to measure? 170 feet seawater depth?
Kind regards
Jan
---
Am 06.11.2015 um 22:11 schrieb Peter Hollenbeck:
> Ocean temperature at depth of about 5 feet.
>
In that case your concerns should be:
* No flame retardants in the cable sheath. Because these are hygroscopic
so seawater will make the sheath crumble.
* UV resistance. Ground cable obviously has zer
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
possible by a medium with low epsilon_r.
Pairing conductors
Am 06.11.2015 um 23:35 schrieb Colin Law:
>
> What twisted pair does do is to reduce electromagnetic pickup.
>
Not for onewire. This only works for symetric drive, when both wires are
a data+/data- line separate from ground.
NOISE
Symetric Receiver
301 - 400 of 843 matches
Mail list logo
