Since the library is made to communicate with FTDI/Arduino (which are always 8N1) I don't see the use of changing those settings.
Hi Toley,
I agree the Arduino is fixed at 8N1 but the FTDI devices are not necessarily fixed & are usually settable, e.g. if you plug a FTDI USB to Serial adapter into your desktop pc & open the relevant comport using something like hyperterminal you are given the choice to select these parameters.
Yes most new devices are fixed to 8N1 but there definately are legacy devices out there which are not 8N1. Being able to set data bits to 7 atleast will cover older devices. Also don't forget parity, hardware handshaking etc!
Thanks, Tom
@wexican, I will add it if / when they update the native library.
This library is a wrapper for this open source project: usb-serial-for-android - Android USB host serial driver library for CDC, FTDI, Arduino and other devices. - Google Project Hosting
It requires Android 3.1+.
I think this part is my trouble...not really clear to me how to :sign0013:Did you try to connect the Samsung device to a USB-serial converter?
Android fails to open the USB port.
Try the solution proposed here: http://www.b4x.com/forum/additional...03-usb-rs232-adaptor-driver-5.html#post120979
Unable to load component info ResolveInfo{a08f6b88 b4a.example1.main p=0 o=0 m=0x108000}
error java.lang.NumberFormatException: Invalid int: "1eaf"
supportedDevices.put(Integer.valueOf(UsbId.VENDOR_LEAFLABS),
new int[] {
UsbId.LEAFLABS_MAPLE,
});
public static final int VENDOR_LEAFLABS = 0x1eaf;
public static final int LEAFLABS_MAPLE = 0x0004;
<?xml version="1.0" encoding="utf-8"?>
<resources>
<!-- 0x0403 / 0x6001: FTDI FT232R UART -->
<usb-device vendor-id="1027" product-id="24577" />
<!-- 0x2341 / Arduino -->
<usb-device vendor-id="9025" />
<!-- 0x16C0 / 0x0483: Teensyduino -->
<usb-device vendor-id="5824" product-id="1155" />
<!-- 0x1eaf / 0x0004: Maple & Olimex Maple -->
<usb-device vendor-id="7855" product-id="0004" />
</resources>
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?