Ahti Legonkov
unread,May 30, 2016, 8:09:20 PM5/30/16Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to flysig...@googlegroups.com
Hi!
I connected Flysight via USB OTG hoping to copy data to the other
device, but I found an unpleasant surprise - the host device (Android)
detects Flysight as high power device and refuses to communicate with
it unless I connect it via powered USB hub. Not a blocker, but very
annoying. It seems that Flysight assumes that it can recharge itself
whenever USB cable is connected. So I thought it's just a firmware
problem, but looking at the schematic, it turns out that charging
can't be controlled by the firmware.
Other thing I noticed was that the USB configuration descriptor says
that the device can draw 250mA, which causes Android device to refuse
communication. Since battery charging cannot be disabled, it seems
it's possible that Flysight draws more than 100mA even before it's
enumerated. This isn't allowed by USB standard, if I understand it
correctly.
I have a proposal for the next revision of hardware - let the firmware
enable/disable charging of the battery to avoid the need for powered
USB hub when connecting Flysight to battery powered devices.
--
lego