On 17/11/2015 05:18, Matthias Urlichs wrote:
> On 16.11.2015 20:36, Jan Kandziora wrote:
>> When you turn on debugging, you get a nice
>>
>> "Attempt to use a branched path (DS2409 main or aux) when bus master
>> doesn't support it."
> … along wih a ton of other messages which caused me to conveni
On 16.11.2015 20:36, Jan Kandziora wrote:
> When you turn on debugging, you get a nice
>
> "Attempt to use a branched path (DS2409 main or aux) when bus master
> doesn't support it."
… along wih a ton of other messages which caused me to conveniently
overlook this.
In message <51d7464c.1040...@g
Am 16.11.2015 um 20:58 schrieb Colin Reese:
> While we are on adapter compatibility, I was looking at some DS1982
> by request and noticed that it and a few other of its ilk (1985,1986)
> require a programming pulse of 12V.
>
> I also noted that the DS9490R, linkusb, and anything else without
> ac
On 16/11/2015 21:58, Colin Reese wrote:
> While we are on adapter compatibility, I was looking at some DS1982 by
> request and noticed that it and a few other of its ilk (1985,1986) require a
> programming pulse of 12V.
>
> I also noted that the DS9490R, linkusb, and anything else without access
On 16/11/2015 21:36, Jan Kandziora wrote:
> Am 15.08.2015 um 16:45 schrieb Matthias Urlichs:
>> Hi,
>>
>> I have an older 1wire network with a bunch of DS2409 (1st-gen HobbyBoards
>> hub,
>> among others). I just tried to replace a DS9490R with a LinkUSB interface.
>> The
>> result was … less th
While we are on adapter compatibility, I was looking at some DS1982 by request
and noticed that it and a few other of its ilk (1985,1986) require a
programming pulse of 12V.
I also noted that the DS9490R, linkusb, and anything else without access to 12V
are not compatible with this command. Th
Am 15.08.2015 um 16:45 schrieb Matthias Urlichs:
> Hi,
>
> I have an older 1wire network with a bunch of DS2409 (1st-gen HobbyBoards
> hub,
> among others). I just tried to replace a DS9490R with a LinkUSB interface.
> The
> result was … less than I expected.
>
> # owdir
> /1F.0CB20400
>
We're a supplier of the LinkUSB. Let me have a word with iButtonlink and
see what they say.
Remember, the LinkUSB is effectively a combination of a LINK45 and an
FTDI USB/serial adapter. The LINK45 in turn emulates a DS9097U-S09. So I
suspect what the OWFS code is doing is pretending that the
I’m using a LinkUSB interface… no idea what’s wrong with your setup, but let me
share my configuration.
Here is my owfs.conf:
server: LINK = /dev/linkUSB0
server: port = 4304
server: readonly
server: error_level = 2
server: error_print = 1
/dev/linkUSB0 is a symlink to the actual device. The Li
Hi,
I asked this a couple weeks ago. No reply, unfortunately.
Does anybody know whether it's possible to fix this? I'd hate to dig
through my home cabling to find+rip out these DS2409 things, they're
buried rather well, behind the newly-installed power wiring …
On 15.08.2015 16:45, Matthias Urli
On 15.11.2015 19:32, Colin Reese wrote:
> What about changing port mode, e.g. digital, analog, pwm, pull-ups, etc?
Pullup etc. shouldn't be a problem, just needs some owfs support to be
useable. digital/analog, PWM etc. would require some slave code update
as currently the array sizes are fixed. I
That's not moat-related, nor owfs-related: "Internal compiler error".
I'd check for updates on your env, or change Linux dist or something.
For the record, line 476 of ow_moat.c is
static ZERO_OR_ERROR FS_r_alarm_status(struct one_wire_query *owq)
i.e nothing fancy at all.
On 16/11/15 01:10, C
12 matches
Mail list logo
