Android Question usbserial 2.5 lib demo app ... where ?

[peacemaker]

HI, All

Strange, that cannot find on the forum.

 

[emexes]

V2.4 is available here: http://www.b4x.com/android/forum/th...pports-more-devices.28176/page-11#post-259167
This update adds support for devices connected to multiple USB adapters.

V2.5 is available as an attachment to this post. It is identical to version 2.4 referenced aboce but adds the required flag for Pending Intents when targeting SDK 31+.

I'm guessing that the demo included with V2.4 was deemed a good-enough demo for V2.5 also.

If it isn't, then looks like you've scored yourself an opportunity to get on to Santa's good list. ?

 

[peacemaker]

Thanks !
Tried, but my CH34x example is not supported

 

[emexes]

Tried, but my CH34x example does not supported

Well, that aligns with the V2.4 documentation:

*UsbSerial supports various popular chips that support serial emulation over a USB connection
*and provides a common API to communicate with them all.
*The devices recognised by this library include:
*
*Various Prolific PL2303 based USB serial devices.
*
*Various FTDI FT232 based devices including Arduinos that use FTDI USB serial chips.
*The FTDI "status byte" bug on reading input in version 1.0 of this library is fixed.
*
*Various Arduinos that use an Atmel 8U2 or 16U2 programmed as a CDC ACM Virtual Comport.
*USB versions of the Roboclaw controller which act as an CDC ACM Virtual Comport in mode 15.
*
*Silicon Labs CP2102 and possibly others of that series of USB to UART Bridges.

but there is also a glimmer of hope here:

*Supported devices are recongised by the combination of their VendorID and Product ID, a list of which is
*precomiled into the library. A device that is compatible with one of the four device drivers listed above
*but that is not recognised may be supported using the SetCustomDevice method. this is most likely to be useful
*for devices implementing the USB CDC (Communications Device Class) ACM (Abstract Control Model) which is a
*vendor-independent publicly documented protocol.

That'll be "may" as in might, not "may" as in can.

Note that you might need to install some spyware a driver to the device at the other (non-CH34X) end of the USB cable.

 

[emexes]

And if your CH34X is BLE, then it's "may" as in will probably not.

Ignore the Bluetooth reference. I am having serious brainfade today. No idea how my thinking jumped from USB to BLE.

 

[peacemaker]

No, it's pure wired USB. It works with felUsbSerial lib. But i hoped that maybe the standard lib started to support, never tried before.

 

[emexes]

Speaking of brainfade, I forgot to include this link re: drivers. ?

https://sparks.gogo.co.nz/ch340.html

 

[tulerpeton]

I'm guessing that the demo included with V2.4 was deemed a good-enough demo for V2.5 also.

If it isn't, then looks like you've scored yourself an opportunity to get on to Santa's good list. ?

Hi!
The website "basic4ppc" is down, where can I find a demo for the library UsbSerial 2.5 ?

 

[DonManfred]

The website "basic4ppc" is down, where can I find a demo for the library UsbSerial 2.5 ?

It is in this post! At least the library
https://www.b4x.com/android/forum/t...-2-0-supports-more-devices.28176/#post-163320 See the downloads there....

V2.5 is available as an attachment to this post. It is identical to version 2.4 referenced aboce but adds the required flag for Pending Intents when targeting SDK 31+.

 

[tulerpeton]

It is in this post! At least the library
https://www.b4x.com/android/forum/t...-2-0-supports-more-devices.28176/#post-163320 See the downloads there....

Yes but only the lib without any sample it is difficult to use.

 

[agraham]

The demo is here. Don't use the library, it's v2.4. Use v2.5 in the link above