Need driver help!

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dupe576
    New Member
    • Feb 2008
    • 1

    Need driver help!

    Hey,

    My boss put me in charge of getting this pin pad device to work with our software.

    We have it plugging into the usb port with a converter cable that converts it to a rs232 port. This converter cable uses the pl2303 driver to aid with this.

    I am new to drivers, particularly on the windows OS. My question is how do I use this driver to communicate with the device?

    I'm trying to read into it but am being overloaded by information and I think I could use some help. I was reading something about using the win32 api and using create file to get a handle? I found this to be quite confusing and am having trouble finding examples of how to use this handle. Isn't there just some standard I/O library I can use to communicate? Please help!



    2 ] : [USB DEVICE] on Port 1 Address : 2

    uniqueID : USB/Adr_2&Port_1&Vi d_067b&Pid_2303 &Rev_0400&Ver_0 110&DevClass_00 &DevSubClass_00 &NumC_01

    driverKeyName : {4d36e978-e325-11ce-bfc1-08002be10318}\0 000

    friendlyDeviceN ame: Prolific USB-to-Serial Comm Port

    Object Type : Device, DeviceImpl, NonJUSB

    Device Descriptor:

    bcdUSB : 1.1

    Device Class : 0 ( device )

    Device Subclass : 0

    Device Protocol : 0

    Max Packet Size : 64

    idVendor : 1659 0x67b

    idProduct : 8963 0x2303

    bcdDevice release number : 4.0

    iManufacturer : 1

    iProduct : 2

    iSerialNumber : 0

    NumConfiguratio n : 1



    Configuration Descriptor:

    wTotalLength : 39

    bNumInterfaces : 1

    bConfigurationV alue : 1

    bmAttributes : 160 Device supports Remote Wakeup!

    bMaxPower : 50 ( 100mA)



    Interface Descriptor[0]:

    bInterfaceNumbe r : 0

    bAlternateSetti ng : 0

    bNumEndpoints : 3

    bInterfaceClass : 255

    bInterfaceSubCl ass : 0

    bInterfaceProto col : 0

    iInterface : 0



    Interface[0] Endpoint Descriptor[0]:

    bEndpointAdress : 1 IN Pipe Data flows from Device to Host

    bmAttributes : 3 Type: interrupt

    bMaxPacketSize : 10

    bInterval : 1

    getEndpoint : 129 81

    Interface[0] Endpoint Descriptor[1]:

    bEndpointAdress : 2 OUT Pipe Data flows from Host to Device

    bmAttributes : 2 Type: bulk

    bMaxPacketSize : 64

    bInterval : 0

    getEndpoint : 2 2

    Interface[0] Endpoint Descriptor[2]:

    bEndpointAdress : 3 IN Pipe Data flows from Device to Host

    bmAttributes : 2 Type: bulk

    bMaxPacketSize : 64

    bInterval : 0

    getEndpoint : 131 83
  • HfX
    New Member
    • Feb 2008
    • 6

    #2
    Originally posted by dupe576
    Hey,

    My boss put me in charge of getting this pin pad device to work with our software.

    We have it plugging into the usb port with a converter cable that converts it to a rs232 port. This converter cable uses the pl2303 driver to aid with this.
    ...
    Hi,

    Afaik the pl2303 is a converter from USB to Serial so your pin pad should be accessible via a newly created serial port.
    Take a look at device manager (start -> run -> devmgmt.msc) under the Ports section.
    You should see a new serial Communications Port after plugging in your converter cable. You can change serial ports also there so for example if your application needs the new port as COM1 you have to change settings for current COM1 to be e.g. COM3 and then you can re-assign your new port to COM1. This can be done via "Properties->Port Settings->Advanced"

    Also if your boss used any other device that might have a serial 2 usb adapter eg. GPS-Modules or whatever it could be, that the wrong driver is installed on the system and windows uses the old or wrong one. It might be more tricky then to find the problem.

    I hope I could help

    Best regards

    Peter

    Comment

    Working...