Am 29.01.2016 um 15:17 schrieb Johan Ström:
>
> Would that be the one based on the device iteration order? Can
> someone elaborate on how that digit is computed? From my quick look,
> it seems to be a number incrementing for every single USB device
> seen, regardless if it matched or not (might be wrong, just
> glanced).
>
Yes, it is that way, not even stable between reboots, as kernel/hardware
enumeration may permute it at will.
>
> Does the DS9490/DS2490 has a serial number that could be used for
> proper identification?
>
The DS2490 hasn't but I doubt there are any DS2490-based adaptors but
the DS9490 out in the wild as the chip isn't available outside of it for
a long time now.
The DS9490 has a built-in DS2401 with family code 81. OWFS currently
uses that chip to identify the DS9490 over USB disconnects which may
happen from time to time, so the enumeration is stable with an owlib
program as long at it is running.
It should be easy to build a very small libusb based program which just
issues the 0x0f Read ROM command on a DS9490, then read back the
provided id. DS2401 are the only chips reacting to that command so if no
iButton is connected to the bus it would also work for a populated bus.
Kind regards
Jan
------------------------------------------------------------------------------
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=267308311&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
