Current state of the DiscoveryF3 port is that it assumes usb to be permanently active.

PIOS_USB_CheckAvailable needs to return transfer_possible (this should be added

discoveryf3: Find a solution for the "No usb vsense" problem about taulabs HOT 4 CLOSED

taulabs commented on July 18, 2024

discoveryf3: Find a solution for the "No usb vsense" problem

from taulabs.

Comments (4)

lilvinz commented on July 18, 2024

James, you experimented with this. Can you please write a short sum up on your findings? Thanks.

from taulabs.

peabody124 commented on July 18, 2024

PIOS_USB_CheckAvailable needs to return transfer_possible (this should be added as a configuration option in the structure or happen automatically if vsense is NULL) (this should be sufficient to get telemetry going)
In the bootloader before PIOS_USB_CableConnected there should be a 1-2 second delay before querying PIOS_USB_CableConnected. I found too long actually produced other problems so we should make the GCS bootloader more tolerant of the device responding slowly.

from taulabs.

lilvinz commented on July 18, 2024

The usb seems to be somewhat broken on that. The f4 port doesnt fully support the common api and the transfer_possible is never set. For the f1 i cant tell. This has to be investigated intensively.

from taulabs.

lilvinz commented on July 18, 2024

Stac fixed it in https://github.com/PhoenixPilot/PhoenixPilot/pull/128.

from taulabs.

Recommend Projects