Support of new devices petitions #7

Open
felHR85 opened this Issue Apr 9, 2015 · 22 comments

Comments

Projects
None yet
@felHR85
Owner

felHR85 commented Apr 9, 2015

Currently UsbSerial supports FT232, PL2303, CP210x, CH34x and CDC serial devices. If you know any Usb to Serial converter which is not supported please, list them here.

Felipe

@felHR85 felHR85 added the enhancement label Apr 9, 2015

@felHR85 felHR85 self-assigned this Apr 9, 2015

@felHR85 felHR85 changed the title from Support of new devices to Support of new devices petitions Apr 9, 2015

@bejibx

This comment has been minimized.

Show comment
Hide comment
@bejibx

bejibx Jul 20, 2015

I'm trying to communicate with Cypress FX3 chip using your library but with no luck for now. Don't know what kind of serial device they use though.

bejibx commented Jul 20, 2015

I'm trying to communicate with Cypress FX3 chip using your library but with no luck for now. Don't know what kind of serial device they use though.

@felHR85

This comment has been minimized.

Show comment
Hide comment
@felHR85

felHR85 Jul 20, 2015

Owner

Two possible sources of the problem:

  • They use a vid and pid that I didn't register.
  • They use a custom solution, so a driver for that device should be developed.

The first source of problems should be easy to solve. Instead of use

UsbSerialDevice serial = UsbSerialDevice.createUsbSerialDevice(device, usbConnection); 

Try to compile the app each time with a different driver device to see if someone works.
These are the constructors for each driver

CDCSerialDevice  serialDevice = new CDCSerialDevice(device, usbConnection);
CH34xSerialDevice serialDevice = new CH34xSerialDevice(device, usbConnection);
CP2102SerialDevice serialDevice = new CP2102SerialDevice(device, usbConnection);
FTDISerialDevice serialDevice = new FTDISerialDevice(device, usbConnection);
PL2303SerialDevice serialDevice = new PL2303SerialDevice(device, usbConnection);
Owner

felHR85 commented Jul 20, 2015

Two possible sources of the problem:

  • They use a vid and pid that I didn't register.
  • They use a custom solution, so a driver for that device should be developed.

The first source of problems should be easy to solve. Instead of use

UsbSerialDevice serial = UsbSerialDevice.createUsbSerialDevice(device, usbConnection); 

Try to compile the app each time with a different driver device to see if someone works.
These are the constructors for each driver

CDCSerialDevice  serialDevice = new CDCSerialDevice(device, usbConnection);
CH34xSerialDevice serialDevice = new CH34xSerialDevice(device, usbConnection);
CP2102SerialDevice serialDevice = new CP2102SerialDevice(device, usbConnection);
FTDISerialDevice serialDevice = new FTDISerialDevice(device, usbConnection);
PL2303SerialDevice serialDevice = new PL2303SerialDevice(device, usbConnection);
@felHR85

This comment has been minimized.

Show comment
Hide comment
@felHR85

felHR85 Jul 20, 2015

Owner

I found Cypress has his own USB-UART controller. Probably they used it http://www.cypress.com/documentation/datasheets/cy7c65213-usb-uart-lp-bridge-controller

Owner

felHR85 commented Jul 20, 2015

I found Cypress has his own USB-UART controller. Probably they used it http://www.cypress.com/documentation/datasheets/cy7c65213-usb-uart-lp-bridge-controller

@anddax

This comment has been minimized.

Show comment
Hide comment
@anddax

anddax Feb 4, 2016

Please add Moxa USB-Serial device VID 0x110a PID 0x1150. Thank You!

anddax commented Feb 4, 2016

Please add Moxa USB-Serial device VID 0x110a PID 0x1150. Thank You!

@felHR85

This comment has been minimized.

Show comment
Hide comment
@felHR85

felHR85 Feb 4, 2016

Owner

What chipset does it use? FTDI, CP210x... @anddax

Owner

felHR85 commented Feb 4, 2016

What chipset does it use? FTDI, CP210x... @anddax

@anddax

This comment has been minimized.

Show comment
Hide comment
@anddax

anddax Feb 4, 2016

Probably Prolific Pl2303. On Windows is show Prolific 067B VID2303.
On Android Your Program not found it.
On Fedora Linux is show VID 0x110a PID 0x1150 vendor MOXA.
Device name Moxa Uport 1150

anddax commented Feb 4, 2016

Probably Prolific Pl2303. On Windows is show Prolific 067B VID2303.
On Android Your Program not found it.
On Fedora Linux is show VID 0x110a PID 0x1150 vendor MOXA.
Device name Moxa Uport 1150

@vmsJames

This comment has been minimized.

Show comment
Hide comment
@vmsJames

vmsJames Feb 11, 2016

Here's a new device that Intermec is using - when their serial adaptor is attached onto the device (CN51), you can then find:
VID: 0x067e
PID: 0x2800

I asked them what chipset they're using: Texas Instruments TUSB3410

Here's a new device that Intermec is using - when their serial adaptor is attached onto the device (CN51), you can then find:
VID: 0x067e
PID: 0x2800

I asked them what chipset they're using: Texas Instruments TUSB3410

@felHR85

This comment has been minimized.

Show comment
Hide comment
@felHR85

felHR85 Feb 13, 2016

Owner

@anddax I've added the Moxa Uport 1150 in the UsbSerial 4.0 release

Owner

felHR85 commented Feb 13, 2016

@anddax I've added the Moxa Uport 1150 in the UsbSerial 4.0 release

@felHR85

This comment has been minimized.

Show comment
Hide comment
@felHR85

felHR85 Feb 13, 2016

Owner

@vmsJames Actually UsbSerial doesnt support the TUSB3410 chipset. I will try to get a cheaper one.

Owner

felHR85 commented Feb 13, 2016

@vmsJames Actually UsbSerial doesnt support the TUSB3410 chipset. I will try to get a cheaper one.

@ge0rg

This comment has been minimized.

Show comment
Hide comment
@ge0rg

ge0rg Mar 9, 2016

Contributor

FTD312D seems to be a very interesting newcomer. It's a UART module that provides an USB Host to Android's AOA interface and that seems to allow charging of the Android device in operation. The product page is listing a demo app and SDK documentation, but so far I failed to find the relevant downloads. Still, it looks like a very interesting choice for DIY projects.

Contributor

ge0rg commented Mar 9, 2016

FTD312D seems to be a very interesting newcomer. It's a UART module that provides an USB Host to Android's AOA interface and that seems to allow charging of the Android device in operation. The product page is listing a demo app and SDK documentation, but so far I failed to find the relevant downloads. Still, it looks like a very interesting choice for DIY projects.

@felHR85

This comment has been minimized.

Show comment
Hide comment
@felHR85

felHR85 Mar 10, 2016

Owner

Hello @ge0rg !
It seems a very interesting module. I will try to gather information and I wouldnt mind to buy a cheap one for testing.

Owner

felHR85 commented Mar 10, 2016

Hello @ge0rg !
It seems a very interesting module. I will try to gather information and I wouldnt mind to buy a cheap one for testing.

@pcancela

This comment has been minimized.

Show comment
Hide comment
@pcancela

pcancela Mar 14, 2016

Hello felHR85,

It would be great if your library supports Intermec's Usb Serial adapter p/n 225-737-002 with VID: 0x067e - PID: 0x2800.

Is it really a Texas Instruments TUSB3410 chipset?

Is there anything I can do to help?

Cheers

Hello felHR85,

It would be great if your library supports Intermec's Usb Serial adapter p/n 225-737-002 with VID: 0x067e - PID: 0x2800.

Is it really a Texas Instruments TUSB3410 chipset?

Is there anything I can do to help?

Cheers

@felHR85

This comment has been minimized.

Show comment
Hide comment
@felHR85

felHR85 Mar 14, 2016

Owner

Hello @pcancela
I don't have any of those USB serial adapters so I don't really know what chipset they use.
The greatest help would be letting me get one of them as I am always open to add support for new chipsets ;)

Owner

felHR85 commented Mar 14, 2016

Hello @pcancela
I don't have any of those USB serial adapters so I don't really know what chipset they use.
The greatest help would be letting me get one of them as I am always open to add support for new chipsets ;)

@Leftyist

This comment has been minimized.

Show comment
Hide comment
@Leftyist

Leftyist Apr 7, 2016

Hey felHR85,

Any chance of supporting chip CP2130 in the future? I'm trying to implement it now, but having some difficulties. Otherwise, would you have any tips to offer?

Thanks!

Leftyist commented Apr 7, 2016

Hey felHR85,

Any chance of supporting chip CP2130 in the future? I'm trying to implement it now, but having some difficulties. Otherwise, would you have any tips to offer?

Thanks!

@felHR85

This comment has been minimized.

Show comment
Hide comment
@felHR85

felHR85 Apr 7, 2016

Owner

Hi @Leftyist
I didn't know that one. I am always open to support new devices. I would do the implementation if I could got one.
Here it is the documentation, it looks pretty good

Owner

felHR85 commented Apr 7, 2016

Hi @Leftyist
I didn't know that one. I am always open to support new devices. I would do the implementation if I could got one.
Here it is the documentation, it looks pretty good

@felHR85

This comment has been minimized.

Show comment
Hide comment
@felHR85

felHR85 May 1, 2016

Owner

I just added support for CP2130 and its SPI interface. Hope you can take a look @Leftyist

Owner

felHR85 commented May 1, 2016

I just added support for CP2130 and its SPI interface. Hope you can take a look @Leftyist

@echo22

This comment has been minimized.

Show comment
Hide comment
@echo22

echo22 Jun 22, 2016

Hi, I'm trying to talk to a STMicroelectronics Nucleo F401RE but for now without success. On the log console I have this message I/CDCSerialDevice: Control Transfer Response: -1. It does not happens if I use an Arduino, wich works fine. What kind of problem could be?
Thanks! Nice library!

echo22 commented Jun 22, 2016

Hi, I'm trying to talk to a STMicroelectronics Nucleo F401RE but for now without success. On the log console I have this message I/CDCSerialDevice: Control Transfer Response: -1. It does not happens if I use an Arduino, wich works fine. What kind of problem could be?
Thanks! Nice library!

@lucianommatos

This comment has been minimized.

Show comment
Hide comment
@lucianommatos

lucianommatos Jun 24, 2016

Hello Felipe, I'm using your library to connect an Arduino UNO R3 to my Android smartphone and trying to light up a LED from the app but I have problems... I've checked and figured out that maybe the PID and VID are not supported by this library. How would I solve this problem? Should I make a fork and solve this? Can you guide me? hahaha! Thanks! By the way, congratulations for your library!
(Picture of the toast arduino info)
1cf2d397-8090-40d1-85df-98064e0b71e7

Hello Felipe, I'm using your library to connect an Arduino UNO R3 to my Android smartphone and trying to light up a LED from the app but I have problems... I've checked and figured out that maybe the PID and VID are not supported by this library. How would I solve this problem? Should I make a fork and solve this? Can you guide me? hahaha! Thanks! By the way, congratulations for your library!
(Picture of the toast arduino info)
1cf2d397-8090-40d1-85df-98064e0b71e7

@red15530

This comment has been minimized.

Show comment
Hide comment
@red15530

red15530 Aug 31, 2016

It does not work with a USB microcontroller PIC18F14K50 VID 0x0408 PID 0x000A

It does not work with a USB microcontroller PIC18F14K50 VID 0x0408 PID 0x000A

@Chewie9999

This comment has been minimized.

Show comment
Hide comment
@Chewie9999

Chewie9999 Jan 25, 2017

It doesn't work with Juniper SRX300 routers.
On the Droidterm Pro error it says "USB Device not supported: Unknown device
Vendor: Cygnal Integrated Products, Inc."
In Windows, it shows up as the following:
USB\VID_10C4&PID_8470&REV_0101
Interestingly, under windows the Manufacturer says "Silicon Laboratories", not Cygnal.
The Human-readable driver name is "Juniper Networks BX Series System Console" if you want a more generic name for it.
Would it be possible to add support for this device?

Thank you!

It doesn't work with Juniper SRX300 routers.
On the Droidterm Pro error it says "USB Device not supported: Unknown device
Vendor: Cygnal Integrated Products, Inc."
In Windows, it shows up as the following:
USB\VID_10C4&PID_8470&REV_0101
Interestingly, under windows the Manufacturer says "Silicon Laboratories", not Cygnal.
The Human-readable driver name is "Juniper Networks BX Series System Console" if you want a more generic name for it.
Would it be possible to add support for this device?

Thank you!

@Omcsesz

This comment has been minimized.

Show comment
Hide comment
@Omcsesz

Omcsesz May 1, 2017

It doesn't work with FT311D Ic.

Omcsesz commented May 1, 2017

It doesn't work with FT311D Ic.

@kovleventer

This comment has been minimized.

Show comment
Hide comment
@kovleventer

kovleventer Aug 4, 2017

The E+H HART Commubox uses the CP210x chipset, but I could not find the corresponding entry (VID: 0x10C4, PID: 0x8135), so I had to add that directly in my project.

The E+H HART Commubox uses the CP210x chipset, but I could not find the corresponding entry (VID: 0x10C4, PID: 0x8135), so I had to add that directly in my project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment