1
0
mirror of https://github.com/mik3y/usb-serial-for-android.git synced 2026-08-26 23:50:13 +00:00

CDC setDTR()

kai-morich
2025-08-08 16:01:22 +02:00
parent b2ecdffc11
commit 71528fc0df
+7 -3
@@ -18,15 +18,19 @@ Check with an App like ''Serial Example'' in this project, if your device is sho
For an incomplete list of older Android devices with known issues look [[Compatible-Android-Devices|here]]. For an incomplete list of older Android devices with known issues look [[Compatible-Android-Devices|here]].
== My USB device is recognized, but no driver is detected == == My USB device is recognized, but no driver is detected ==
The library includes a list of USB vendor and device ID's (VID/PID) that are typically used by the supported chips. In case of unusual ID's, use a [https://github.com/mik3y/usb-serial-for-android#probing-for-unrecognized-devices Custom Prober] or specify a fixed driver. CDC-ACM devices are detected by by USB interface types. For other devices the library includes a list of USB vendor and device ID's (VID/PID) that are typically used. In case of unusual ID's, use a [https://github.com/mik3y/usb-serial-for-android#probing-for-unrecognized-devices Custom Prober] or specify a fixed driver.
Non USB-to-Serial devices like mass-storage, mouse, GPC receivers, ... and rarely used USB-to-Serial chips including Hoitek HE2325U and FTDI FT312D are not supported. Non USB-to-Serial devices like mass-storage, mouse, GPC receivers, ... and rarely used USB-to-Serial chips including Hoitek HE2325U and FTDI FT312D are not supported.
== My device is connected, but I receive no data ==
== My device is connected, but I receive no / wrong data == A common issue is wrong baud rate.
For CDC-ACM devices try setting DTR, see [[FAQ#user-content-I_am_using_an_Arduino_Uno_Sparkfun_Pro_Micro_or_other_Arduino_but_codeSerialwritecode_does_not_send_data|other]] FAQ entry.
== My device is connected, but I receive wrong data ==
A common issue is wrong baud rate. A common issue is wrong baud rate.