On Fri, Apr 27, 2012 at 03:53, Michael Markstaller m...@elabnet.de wrote:
owfs 2.8p14 is fully unusable/broken with DS9490, maybe I'm just the only
one with this constellation (please dissent!)
Oh no, I fully agree!
The only way working with OWFS and DS9490 are hacks: fall back to older
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 25.04.2012 13:36, schrieb Ivan Lisenkov:
Is this patch is in CVS already or I should to patch it by myself?
No it isnt and I also would clearly flag it as a hack, I'm no
C-programmer and I probably only understand 50% of the code..
But OTOH it
Is this patch is in CVS already or I should to patch it by myself?
Best Regards,
Ivan, PhD
On Sun, Apr 22, 2012 at 9:55 PM, Michael Markstaller m...@elabnet.de wrote:
Thanks, I already thought I'm the only one using (several hundred btw)
DS9490 in real life ;)
Though, I have no single
Thanks, I already thought I'm the only one using (several hundred btw)
DS9490 in real life ;)
Though, I have no single 1w-hub here and maybe I can't explain it good
enough but the problem is mainly about (re)initialisation and the
reset-stuff, pretty sure in this now..
best regards
Michael
Am
THANK YOU THANK YOU THANK YOU!
I've been plagued by this issue and was about to give up using some old
boards with 2490's.
The issue seems to happen when discovering devices behind a switch.
Instead of crashing totally, we get a bunch of delays and retries and
finally get the data.
Nice
Something like:
http://owfs.cvs.sourceforge.net/owfs/owfs/module/owlib/src/c/ow_opt.c?r1=1.155r2=1.156
;)
Getting back on the subject: Would be good if someone with a real
installation, longmany BM would also test, it improved reliability here
by many 100%.. Also compared with 2.8p2
Never had a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Getting back on this, attached two patches..
This is definitely no fix but more a works-for-me-HACK! though it
might outline where trouble starts..
At least in two of my testbeds it improves owserver running reliable
with multiple DS9490 and long
hi, could you add a version information at debug output too? maybe at
the start of ow program, just to us know what's the version...
this could be easier to know what we are debugging
Em 3 de abril de 2012 08:09, Michael Markstaller m...@elabnet.de escreveu:
-BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 03.04.2012 16:48, schrieb Roberto Spadim:
hi, could you add a version information at debug output too? maybe
at the start of ow program, just to us know what's the
version... this could be easier to know what we are debugging
There was no
sorry i wrote wrong...
could you make a patch that put ow version at debug output? :)
Em 3 de abril de 2012 23:18, Michael Markstaller m...@elabnet.de escreveu:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 03.04.2012 16:48, schrieb Roberto Spadim:
hi, could you add a version
I changed the subject..
Am 16.03.2012 14:49, schrieb Paul Alfille:
To hunt this down, you find that heavy USB activity causes communication
failures and puts owfs is an unusable state?
No, I don't think thats a root cause. My last tests where done with only
1-4 DS9490R on a powered hub without
11 matches
Mail list logo
