No luck with that either.
get bus.0 & bus.1 now
but the directories are all empty
same with uncached.
Switched over to /dev/usb/tts/0
Startup goes like this.
ERR: fuse mount point: /tmp/endelig
Beside recompiling?
Perhaps the problem is the first pass at the adapter. Try:
owfs /dev/usb/tts/1 /dev/usb/tts/1 /tmp/endelig/ --foreground --error-level 9
On Sunday 23 April 2006 02:54 pm, Kurt André Selbach wrote:
> Is there an easy way i can do this?
> increase the timeout?
>
> On 4/23/06,
Is there an easy way i can do this?
increase the timeout?
On 4/23/06, Paul Alfille <[EMAIL PROTECTED]> wrote:
> Ok, I'll just increase the timeout.
>
> Paul
>
> On Sunday 23 April 2006 11:22 am, Kurt André Selbach wrote:
> > owfs /dev/usb/tts/1 /tmp/endelig/ --link --foreground --error-level 9
> >
Am Sonntag, 23. April 2006 08:23 schrieb Christoph Scheurer:
> Hi,
>
> Besides more restrictive electrical specifications and timeouts to prevent
> the bus to be locked, SMBus is a subset of I2C, i.e. for the protocol
> every I2C master device can send all commands a SMBus slave is able to
> under
Great. It looks exactly like the one I got (at your recommendation) from
lm_sensors-2.10.0/kernel/include/i2c-dev.h
Thanks,
Paul
On 4/23/06, Christoph Scheurer <[EMAIL PROTECTED]> wrote:
This is a nice discussion of the interoperatbility:http://www.maxim-ic.com/appnotes.cfm/appnote_number/47
Ok, I'll just increase the timeout.
Paul
On Sunday 23 April 2006 11:22 am, Kurt André Selbach wrote:
> owfs /dev/usb/tts/1 /tmp/endelig/ --link --foreground --error-level 9
>
>
> [EMAIL PROTECTED]:/# grep '.' /tmp/endelig/statistics/errors/*
> /tmp/endelig/statistics/errors/BUS_Overdrive_errors:
owfs /dev/usb/tts/1 /tmp/endelig/ --link --foreground --error-level 9
[EMAIL PROTECTED]:/# grep '.' /tmp/endelig/statistics/errors/*
/tmp/endelig/statistics/errors/BUS_Overdrive_errors: 0
/tmp/endelig/statistics/errors/BUS_PowerByte_errors: 0
/tmp/endelig/statistics/erro
Looking through the code, the only branches that make sense involve
timeout errors on the serial port. I'll add some debugging code, but
there is a way to see it now!
After a startup like above (even without any attempted bus activity except startup), look at statistics/errors at
BUS_read_errors
B
Oh, didn't see you allready had it uploaded :-)
removed everything including fuse/libfuse reinstalled everything.
2.3p0 seems stable - but it doesnt seem to talk to my adapter.
Can't get any information from my sensor, and it says my adapter is
"Bad Adapter"
[EMAIL PROTECTED]:/# owfs /dev/usb/tt
Hi Christian,
Do you have any idea if the new build would take, hours or days/weeks?
Have a nice weekend folks!
On 4/23/06, Paul Alfille <[EMAIL PROTECTED]> wrote:
> Hi Christian,
>
> Ooops, I'll look at it.
>
> Reconnect mutex shouldn't be needed any more. We reconnect before a
> transaction
Hi Christian,
Ooops, I'll look at it.
Reconnect mutex shouldn't be needed any more. We reconnect before a transaction, and lock the bus.
Extensive testing on USB reconnects show a beautifully "self-healing" machine.
Triggering a "reconect" is done after 5 consecutive unsuccessful BUS
resets, to
This is a nice discussion of the interoperatbility:
http://www.maxim-ic.com/appnotes.cfm/appnote_number/476
I'll also attach the i2c header file I was refering to earlier.
Christoph
On Sun, Apr 23, 2006 at 08:23:57AM +0200, Christoph Scheurer wrote:
> Hi,
>
> Besides more restrictive electr
The latest 2.3p0 doesn't compile... reconnect_mutex is used in ow_lock.c but
is never defined.
I'm building a new version now anyway...
/Christian
> -Ursprungligt meddelande-
> Från: [EMAIL PROTECTED] [mailto:owfs-developers-
> [EMAIL PROTECTED] För Paul Alfille
> Skickat: den 22 april
13 matches
Mail list logo
