working to create com port driver for the usb printer device has FTDI chip

I got a task to create a com port for the USB printer device which has FTDI chip. I have read some OSR link and create a com port driver. When I am updating my driver on USB serial driver then in driver details my driver is showing in place of the USB serial driver. I am new in the windows device driver so I have no Idea how I will send data to the printer. Please show me some path. I am frustrating.

FTDI supplies a com port driver for FTDI usb devices. Does that one not
work for some reason?

Mark Roddy

@Mark_Roddy said:
FTDI supplies a com port driver for FTDI usb devices. Does that one not
work for some reason?

Mark Roddy

Thanks, Mark, We have a custom application for which FTDI driver is not working. So I got a task to create a com port driver. Could you please give me some Idea how I can establish the communication between the created com port driver and the usb printer.

sunil111193 wrote:

Thanks, Mark, We have a custom application for which FTDI driver is not working. So I got a task to create a com port driver. Could you please give me some Idea how I can establish the communication between the created com port driver and the usb printer.

You need to be more explicit about what is not working.  There’s nothing
you can do in a USB serial port driver that FTDI is not already doing in
their driver.

Where, exactly, did you get the driver you started from? Remember, you
don’t want a real serial port driver that expects to talk to a UART,
because that’s not the hardware you have.  You have a USB device.  You
need a USB CDC (Communication Device Class) driver that happens to
expose a serial port-like interface to the operating system, but at the
bottom level, it has to use USB requests (URBs).

And what is it with all these people designing printers with fake serial
interfaces?  There is a 20-year-old standard for USB Printer Devices
that uses simple, native USB interfaces in a well-defined,
well-understood way.  Do that, and you don’t need a communication driver
at all.