Please add some new supported USB devices
-
Yes I can test a beta version .
Thanks for your offer but I bought yesterday the Pro version
!!Best regards,
Alain -
@al1fch said in Please add some new supported USB devices:
Thanks for your offer but I bought yesterday the Pro version !!
Thank you for your support. If you have any questions or problems, please let me know.
@al1fch said in Please add some new supported USB devices:
Yes I can test a beta version .
Great, thank you. I will probably migrate to another USB serial library (the one that is used by Serial USB Terminal app) and will let you know once I have it implemented.
Best regards,
Klemen -
With 'Serial USB Terminal' from Kai Morich the 3 devices mentionned above are not automaticaly configured, you have to select a suggested generic 'CDC driver' item for them .
Only FT232, FT2232, CP2102, CH340, CH341 and PL2303 are automaticaly configured as listed in Info
Not tried yet ESP32-S3 with native USB , Micro::bit and some others !!
Best regards
Alain -
@al1fch
Thanks for the info.I have just released a new version (v1.0.29), skipping the beta stage. I am fairly confident that it works at least in the same manner as before.
I have added 19 new serial converters - it should now support all devices as Serial USB Terminal does. The drivers should be selected automatically.I will appreciate any feedback after you upgrade to v1.0.29.
Thank you.
Best regards,
Klemen -
Hi
Upgraded done
Raspberry PI Pico with RP2040 OK now
But still no success ("*device unconnected or not supported") with :
LOLIN S2 MINI board with native USB and serial on
LOLIN C3 MINi board with native USB and serial onSerial USB Terminal application sees them as :
Custom-CDC
Vendor ID 303a Name Espressif
Product ID 80c2 Name Lolin S2 MiniCustom-CDC
Vendor ID 303a Name Espressif
Product ID 1001 Name Serial/JTAGBest regards,
Alain -
Thanks for the feedback.
I have implemented custom driver probing for the two "problematic" devices. I will not be so hasty this time and will build a test version so you can try it out.
I will get back to you ASAP.
Thanks again.
Regards,
Klemen -
I have prepared a test version v1.0.30. It's 32-bit, so if you have any problems installing, I can supply 64-bit version.
Please note that you will have to uninstall the Google Play Store version first as this build was signed with my signing key (and not the one from Google). Don't worry if this version is demo - when you reinstall the one from Google Play Store, you will have the pro version associated with your account.
Best regards,
Klemen -
Hi kl3m3n !
Beta 1.03 apk installed
Fully successfull with Lolin-C3 board (native USB)
connection OK , then Basic USB works OKHalf sucess with Lolin-S2 board (native USB)
Connection successful ,
Then, when touching blue button GUI-O whaits some seconds before message : 'connected device does not respond'I know @init is received by ESP (some short blink led added here in BasicUSB code )
I know ESP sending is OK : when I send @init with Serial USB Terminal II can see "@cls @guis BCG:#FFFFFF...." and so on coming on App's screen.
Best Regards,
Alain -
Thanks for the update.
Regarding the Lolin-S2 board (native USB):
Did you try changing the baud rate? Is it behaving similarly? This is strange, since I am now using the same library as Serial USB Terminal application does.
Is there any special configuration that the Serial USB Terminal application uses? GUI-O uses the selected baud rate, 8 data bits, 1 stop bit and no parity.
I will try to get my hands on Lolin-S2 board...
Best regards,
Klemen -
Hi !
Strange, indeed !Same problem when setting Serial.Begin(9600) beside of Serial.begin(115200) in BasicUSB code
(On LOLIN S2 mini Serial is USBCDC Serial, Baud may be changed , not frame )
I Will test another ESP-32 board, TTGO one, with USB connector switchable between UART w CH340 and native USB
No special tuning with Serial USB Terminal anc BasicUSB code , ok with 115200 or 9600bauds, ESP answer to @init is OK.
Best Regards,
Alain