On 01/03/16 14:11, Stefano Miccoli wrote:
Really weird, since it should just use semi-low-level USB messages to
tell the device to send a Break; the OS should not interfere?
Further weirdness.
I just noticed that my main network (FreeBSD, same version, with LinkUSB
v1.5) suffers from the restore-baudrate/break-issue too.
I tried that LinkUSB dongle in my virtual Ubuntu, and it worked fine. So
I can rule out differences in the dongles at least.
Also tried with my full bus connected, and it still worked fine (on the
Ubuntu)...
So: two different machines, same OS, same dongle. Working on one, broken
on one. Could it be something with the USB host?
If this cannot be fixed, my solution is to disable the 9600->19200
transition, unless explicitly asked for via the baud rate setting.
OK for the proposed solution: but also the infinite loop should be
avoided: if for some reason the LinkUSB is stuck at 19200 baud,
owserver should not hang at ''owserver -d ftdi:i:0x0403:0x6001’'
After N retries, it should give up? Makes sense.
BTW I’ve never understood if it is better to use the LinkUSB in native
mode or in DS9097U emulation mode: any suggestion on this topic?
Native mode should possibly give you faster scanning, as we don't have
to do the search algorithm from OWFS. But I haven't benchmarked.
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
