<wpwrak>
ah, but that one has 2 x micro. my y-cable.pdf has only one micro. the full-size USB A male goes into PC or laptop
<wpwrak>
yes, the ¥ cable looks like what i have in mind
atommann has joined #qi-hardware
<xiangfu>
Yes.
<xiangfu>
¥cable. :)
<wpwrak>
though the description seems to suggest that it may not be able to deliver power to the micro B side
<wpwrak>
err, ¥ 12 ;-))
<xiangfu>
archang: have tested on his phone.
<wpwrak>
so "¥" means "money" ? i didn't know it was used for RMB, too, only noticed it for Yen.
<xiangfu>
¥ both RMB JPY
<wpwrak>
heh, just like "$" is also used for all sorts of "pesos". in some countries, they add letters (which doesn't necessarily help. e.g., in uruguay, they put a "U" for uruguay and an "S" because it's plural. so you get "U$S", which you'll of course read as "US$" (which would be a lot more expensive). very confusing.)
rejon has joined #qi-hardware
<archang>
Cellphone test result on 9.9 RMB cable: OTG works fine, tested on usb keyboard/mouse and usb disk; the power line only supports the otg slave device, no charging to my phone.
<wpwrak>
hmm, so it's not quite what we want
<archang>
we need to charge both the slave and host?
<wpwrak>
it's nicer for anelok if it doesn't have to use its battery
<wpwrak>
not that there would be any charging (i hope :)
<wpwrak>
by the way, i'm making good progress with fixing the board errata. almost done with the principal changes. then i'll have to update and check the BOM.
<wpwrak>
the coming version of the board will be almost identical to the prototype i have now, except that it's 1 mm wider (so the FPC of the OLED will suffer less), the rfkill switch is will really be just rfkill (and not system-kill), the crystal should be a bit more reliable (i had a layout bug there), and there will be a better diode on VUSB
<wpwrak>
(plus a bunch of minor improvements)
FAMAS has quit [Read error: Connection timed out]
atommann has quit [Ping timeout: 264 seconds]
rejon has quit [Ping timeout: 265 seconds]
Nik05 has quit [Read error: Connection reset by peer]
Nik05 has joined #qi-hardware
<archang>
wpwrak: an interesting thing about the 9.9 cable: cannot charge my nexus5 but ok on a nexus4...
<archang>
and can power up a raspberry pi...
<archang>
so it should meet the need
wej has quit [Ping timeout: 245 seconds]
wej has joined #qi-hardware
wolfspraul has joined #qi-hardware
jekhor has joined #qi-hardware
atommann has joined #qi-hardware
<wpwrak>
archang: interesting. i think what makes the behaviour of such cables difficult to understand is that there are two mechanisms at play: one is the physical connection of VBUS and the other is the charger detection the software on the phone/tablet/etc. does
<wpwrak>
the device only charges if there is a physical connection and the software decides to use it. so the same cable can work with some devices and not with other. worse, this may change after a sw update.
<wpwrak>
and who knows, maybe there's some random element in this, too ;-)
<wpwrak>
in the case of anelok it's simple: anelok will just assume the port can do 500 mA and it will tell this to the device. anelok itself needs only very little power, so as long as the port can do 500 mA, it'll be fine.
<wpwrak>
looking at the pictures ... oh wow, the second cable is pretty complex !
jekhor has quit [Ping timeout: 244 seconds]
xiangfu has quit [Ping timeout: 264 seconds]
jekhor has joined #qi-hardware
archang has quit [Ping timeout: 244 seconds]
sulky has quit [Ping timeout: 272 seconds]
sulky has joined #qi-hardware
archang has joined #qi-hardware
sulky has quit [Ping timeout: 245 seconds]
sulky has joined #qi-hardware
pcercuei has joined #qi-hardware
atommann has quit [Quit: Leaving]
jekhor_ has joined #qi-hardware
jekhor__ has joined #qi-hardware
jekhor has quit [Ping timeout: 256 seconds]
jekhor_ has quit [Ping timeout: 255 seconds]
atommann has joined #qi-hardware
atommann has quit [Quit: Leaving]
jekhor_ has joined #qi-hardware
jekhor__ has quit [Ping timeout: 240 seconds]
pcercuei has quit [Ping timeout: 244 seconds]
pcercuei has joined #qi-hardware
Haswell has joined #qi-hardware
pcercuei has quit [Ping timeout: 255 seconds]
jekhor has joined #qi-hardware
jekhor_ has quit [Ping timeout: 255 seconds]
valhalla has joined #qi-hardware
valhalla_ has quit [Ping timeout: 244 seconds]
pcercuei has joined #qi-hardware
rejon has joined #qi-hardware
pcercuei has quit [Ping timeout: 264 seconds]
sb0 has quit [Quit: Leaving]
pcercuei has joined #qi-hardware
wej has quit [Ping timeout: 250 seconds]
jekhor_ has joined #qi-hardware
jekhor has quit [Ping timeout: 244 seconds]
wej has joined #qi-hardware
lrockhq has joined #qi-hardware
jekhor_ has quit [Ping timeout: 264 seconds]
Nik05 has quit [Read error: Connection reset by peer]
Nik05 has joined #qi-hardware
mth has quit [Ping timeout: 264 seconds]
FAMAS has joined #qi-hardware
FAMAS has quit [Max SendQ exceeded]
jekhor_ has joined #qi-hardware
lrockhq has quit [Quit: Leaving]
lrockhq has joined #qi-hardware
lrockhq has quit [Changing host]
lrockhq has joined #qi-hardware
lrockhq has quit [Client Quit]
wolfspraul has quit [Quit: leaving]
wolfspraul has joined #qi-hardware
mth has joined #qi-hardware
wolfspraul has quit [Quit: leaving]
<DocScrutinizer05>
no chargiing not automatically means the power isn't connected to the micro plug. Actually I can't think of a Y-cable that doesn't connect VBUS to each plug
<DocScrutinizer05>
ooh, [2015-01-06 Tue 08:43:38] <archang> wpwrak: an interesting thing
<wpwrak>
DocScrutinizer05: it would kinda make sense not to connect power to the "data host" if there's a concern about overloading the "power host". but it's hard to say (without physical examination) whether the cable manufacturers do something like this.
Nik05 has quit [*.net *.split]
valhalla has quit [*.net *.split]
Haswell has quit [*.net *.split]
Jay7 has quit [*.net *.split]
atgreen has quit [*.net *.split]
porchao has quit [*.net *.split]
DocScrutinizer51 has quit [*.net *.split]
newcup has quit [*.net *.split]
dos1 has quit [*.net *.split]
ysionneau has quit [*.net *.split]
qi-bot has quit [*.net *.split]
Ornoterm1s has quit [*.net *.split]
larsc has quit [*.net *.split]
mth has quit [*.net *.split]
kyak has quit [*.net *.split]
tumdedum has quit [*.net *.split]
mirko has quit [*.net *.split]
roh has quit [*.net *.split]
ysionneau has joined #qi-hardware
Ornotermes has joined #qi-hardware
qi-bot has joined #qi-hardware
Jay7 has joined #qi-hardware
atgreen has joined #qi-hardware
DocScrutinizer51 has joined #qi-hardware
dos1 has joined #qi-hardware
Haswell has joined #qi-hardware
<wpwrak>
the development of such cables may be an evolutionary process: someone makes a nonstandard cable, sees what happens. then the next one makes a slightly different one, see if that causes less trouble in the field, and so on. once a design seems to work really well (at least with a product that's hot at the time), everyone clones that design. then things change (new device becomes fashionable, new droid version, etc.), etc.
valhalla has joined #qi-hardware
Nik05 has joined #qi-hardware
porchao has joined #qi-hardware
mth has joined #qi-hardware
kyak has joined #qi-hardware
tumdedum has joined #qi-hardware
mirko has joined #qi-hardware
roh has joined #qi-hardware
jekhor_ has quit [Ping timeout: 255 seconds]
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #qi-hardware
DocScrutinizer05 has quit [Read error: Connection reset by peer]
archang has quit [Remote host closed the connection]