Aha - I'd missed that in my first read of all the documentation, I'll try
that this evening. If that fixes the timing issue reading VAD from the
ds2438 chips then its only the endian bug on the ds2413 to tackle (and I
have a PIO.BYTE workaround for that!!)
OK - the uncached tree is working
Am 23.02.2014 07:16, schrieb Robin Gilks:
No couplers - hanging off the bus are 16x DS2413 switches and 3x DS2438
battery monitors which are used for measuring the output of a current
transformer and temperature.
How do you access the onewire, direct to USB-Serial or via the w1 kernel
Am 23.02.2014 07:16, schrieb Robin Gilks:
No couplers - hanging off the bus are 16x DS2413 switches and 3x DS2438
battery monitors which are used for measuring the output of a current
transformer and temperature.
How do you access the onewire, direct to USB-Serial or via the w1 kernel
Am 23.02.2014 19:26, schrieb Robin Gilks:
If you look back in the thread you'll see I'm using a USB9097 which is a
ch341 usb/uart and a ds2480b master driver combination.
I read that, but I had the impression you have a bunch of hardware so it
wasn't clear to me what you are actually testing.
Am 23.02.2014 19:26, schrieb Robin Gilks:
If you look back in the thread you'll see I'm using a USB9097 which is a
ch341 usb/uart and a ds2480b master driver combination.
I read that, but I had the impression you have a bunch of hardware so it
wasn't clear to me what you are actually
Am 22.02.2014 05:12, schrieb Robin Gilks:
I've been using 100mS between DS2413 write and DS2438 read on the old
Dallas s/w but even taking it up to 300mS I'm failing to read the correct
value with owfs.
Do you have any DS2409 bus couplers inbetween? OWFS will turn the
switches *every time*
Am 22.02.2014 05:12, schrieb Robin Gilks:
I've been using 100mS between DS2413 write and DS2438 read on the old
Dallas s/w but even taking it up to 300mS I'm failing to read the
correct
value with owfs.
Do you have any DS2409 bus couplers inbetween? OWFS will turn the
switches *every
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It uses the same value that would be returned by strlen(), which excludes the
null termination.
On 02/20/2014 10:59 PM, Robin Gilks wrote:
Greetings all
I've just started to migrate from the public domain Dallas tools (that go
way back to the
On 02/20/2014 10:59 PM, Robin Gilks wrote:
Greetings all
I've just started to migrate from the public domain Dallas tools (that
go
way back to the DOS days as well as Linux) to OWFS and I'm a bit
confused
about the C API interface.
I take it that the buffer in OW_put for example is an
I'm off to try loading 2.7p21 onto the router, if I can get it to cross
compile OK...
OK - 2.7p21 still has a problem on the router so I guess its an endianess
issue. The router I'm using, a TPLink WR-1043ND, uses the AR71XX series
SOC which is MIPS based.
As I said before, all the reads are
I'm off to try loading 2.7p21 onto the router, if I can get it to cross
compile OK...
OK - 2.7p21 still has a problem on the router so I guess its an endianess
issue. The router I'm using, a TPLink WR-1043ND, uses the AR71XX series
SOC which is MIPS based.
Back on 2.8p13 and using
Greetings all
I've just started to migrate from the public domain Dallas tools (that go
way back to the DOS days as well as Linux) to OWFS and I'm a bit confused
about the C API interface.
I take it that the buffer in OW_put for example is an ASCII string but
does it have to be null terminated
12 matches
Mail list logo
