Solving Prolific PL-2303 USB to Serial Comm Port installation issues

Hello everybody,
More and more machines are comming without Parallel and serials ports, they are comming with USB external ports only.
Some have the RS-232 and Parallel headers in the motherboard, and that should last for about a year I think.
At any rate, the issue I was facing is the following:
(a) Installing Prolific PL-2303 USB to Serial Comm Port on Windows XP Pro SP3 works OK and system runs fine. there are some capacity issues regarding the buffer size, but that is another post.
(b) Installing on WEPOS 1.1 SP3 on some motherboards (Older ones) that have at least the Parallel headers and a serial port, the device also works as with (a)
(c) Installing on WEPOS 1.1 SP3 with a machine with only external USB's (no parallel / serial port or headers). The installation process runs OK. but when the device
is plugged I get the following error message:
"An error ocurred during the installation of the device"
"A service Installation section in this INF is invalid"
(d) Installing on POSReady 2009. I get the same as with (c)
This is how I solved, after many frustrating reboots with the same message about the INF section and multiple Prolific drivers tried.  I started digging windows:
(1) Find the setupapi.log and read it, if the OS is a fresh install it will not be too long.
(2) Read this:
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ComPort] in "c:\windows\inf\oem15.inf".
#I320 Class GUID of device remains: {4D36E978-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_067B&PID_2303\5&B6C3FC&0&2".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ComPort.NT.Interfaces] from "c:\windows\inf\oem15.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_067B&PID_2303\5&B6C3FC&0&2".
#-035 Processing service Add/Delete section [ComPort.NT.Services].
#E339 Add Service: Binary "C:\Windows\system32\DRIVERS\serenum.sys" for service "Serenum" is not present.
#E032 Error 0xe0000217: A service installation section in this INF is invalid.
#E275 Error while installing services. Error 0xe0000217: A service installation section in this INF is invalid.
#E122 Device install failed. Error 0xe0000217: A service installation section in this INF is invalid.
#E154 Class installer failed. Error 0xe0000217: A service installation section in this INF is invalid.
[2010/02/13 23:32:24 2004.2]
(3) So it was the serenum.sys file that Windows needed to find in the ..\system32\drivers folder. I got the serenum.sys from one of the temporary folders created by the installation process.
(3a) So, I think that windows installs this sys file if it recognizes the motherboard has at least one parallel or serial port.
(4) So good luck when installing your serial device to your POS solution. I will open another thread if I have problems with the buffer size of the device.
Humberto Sequeira

Hello Terry,
Indeed, they were not intended as POS system, the EEE Top machines are candy to the eye, but for my taste they do not work in POS environment (I give them 1 year before they pop). Regarding the other, well competition is tought, so you have to get creative in order to keep costs down, and this one can be used as a waiter stations, that do not need heavy serial comunications.
Anyways, the POSReady does not install these system files if the installation does not detect a serial or parallel port (which make sense, as why would it install drivers for a device that is not detected). I posted this for others to be aware of this when they select the hardware that will be offered to their customers, as good old "on mother-board" serial and parallel ports cannot be beaten by their USB imitations (IRQ and memory addressing processing are needed for end devices to function properly).
Have a great weekend,
Humberto

Similar Messages

  • Lenovo X131e doesn't work with Prolific PL2303 based USB to Serial Adapter and Windows 7 x64

    This is sort of a bug report. A Lenovo X131e with Windows 7 x64 and the PL2303 driver including 1.6, 1.61 and 1.7 will not successfully install the driver - Windows always reports "Driver Install Failed" on plug in to USB 3 or USB2 ports. However, putting a USB2.0 hub inbetween the USB to Serial Adapter and either USB port type makes the adapter work fine. This was not the case with the X130e. I'm not sure where to report this beyond this posting, but more of an FYI.

    If the USB can be used for other equipment,
    That may be compatibility issues for USB and Prolific PL2303.
    Don't plug Serial Adapter when installing the driver,
    Ofter installation, Connect serial adapter to see whether it is working normally.
    I am a volunteer, don't work for Lenovo. I am a software engineer.
    thinkpad x61t, os:win7 Awavo Software com port monitor serial port monitor

  • Select serial comm port in sub vi during run-time

    Hi, would like to be able to select the comm port (serial RS232) in sub vi to use in main vi during run time. How can I do this? Have tried and failed, for on startup an error occurs because I have not selected a port yet. An example would be invaluable! Thanks alot, Madri

    Hi Madri !
    What you could do is to intercept the com errors, and open a configuration vi either if there is an init error or if the user has pressed a "Change port" boollean (or menu...). Do not forget to close the previously opened serial port, and to open/init the new one. I have attached a small example of this idea.
    Of course com errors can have various origins, and do not require always to change the serial port. So, you have some additional work to do.
    Hope this helps
    CC
    Chilly Charly    (aka CC)
             E-List Master - Kudos glutton - Press the yellow button on the left...        
    Attachments:
    Select_port.vi.zip ‏12 KB
    Com_with_serial_init_vi.vi.zip ‏13 KB

  • Reading Data from serial (Comm) Port in developer200 forms 6i

    Dears,
    I have developed an application using Dev2k forms 6i.
    I need to read data from a device (weigh bridge) that is attached to PC on comm port.
    scenario: when a vehicle comes on the Weigh bridge it calculates its weight and send it to the PC on serial port.
    on when-button-pressed event I want to get data into a text field on form.
    If any one has developed such form please help me.
    Thanks and regards

    you can:
    create java class -> wrap plsql -> invoke plsql-code from button trigger
    googling java class instead of creating =)

  • Too many usb comm ports

    Good Morning,
        I've run into what may be issue soon, where we have the units being tested that have built in USB ports that appear as serial comm ports. The problem is that every time we connect a UUT that hasn't been run on that computer before Windows assigns it a new com port number. My concern is that quite soon, as the production line gets into full swing, we will hit the "magic number" of 255, the highest com port number and I don't have any idea what Windows will do at that point. Before I start writing code to parse the new com port number returned by VISA, and adjust" the registry entries accordingly, I want to know if it is necessary. I figure that there are a couple of possible scenarios, that Windows complains and won't issue a com port #, that Windows starts over at the beginning, or that Windows just hits 255 and then keeps reissuing it. I would prefer that it be the later two, don't want to have my program messing around in the registry, and really don't have time at the moment, nor access to the machine(s) to experiment to see.
    Thanks,
    Putnam
    Certified LabVIEW Developer
    Senior Test Engineer
    Currently using LV 6.1-LabVIEW 2012, RT8.5
    LabVIEW Champion
    Solved!
    Go to Solution.

    I'm not sure that I understand your answer. The problem is that on our test stands we will see hundreds of the product boards go by over the life of the boards. As I have seen with "standalone" usb-serial adapters, when a new one is plugged in, that the computer hasn't "seen" before, it will assign it the next available comm port #. It probably knows that it hasn't seen it before by some serial numbering type scheme that is returned in the USB's header info when plugged in. As the hardware design for the unit containing this USB interface is essentially frozen, and as that side of the design group won't see it as a problem in the target systems (where the boards won't be "talked to" via the USB path) it is unlikely that I can get any hardware/firmware changes. I'm not sure that would be the way to go anyway. Definitely not going to get a change to the BOM at this point (on top of which I'm an outside contract test consultant). So I will have to address the problem on my side of the fence. I haven't looked yet, but am pretty certain that the Com#'s are stored in the registry, so I can just make sure that I "reset" those numbers before they get to 255, but am never comfortable with my programs modifying the registry.
    Putnam
    Certified LabVIEW Developer
    Senior Test Engineer
    Currently using LV 6.1-LabVIEW 2012, RT8.5
    LabVIEW Champion

  • HP 6550b BIOS Unabled COMM PORT (SERIAL)

    Hi,
    I have an HP Probook 6550b with BIOS version F.23, I can see my Ricoh PCI connections like USB, SD/MMC Reader and the 1394 Port, but I can't found my Serial COMM PORT??
    Thx for your Help!

    Hi:
    Did you install the AMT driver?
    http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=3688870&sp...

  • Use Prolific based USB-to-Serial with Solaris 10

    Hi all,
    I currently use a Dynex DX-UBDB9 adapter, which is a Prolific PL-2303 based USB-to-Serial adaptor and it seem to be working OK in almost all situations (with Sun Ray, my laptop, and so on).
    I put it in the USB port #0 on a Sun Fire V240, and the server saw it:
    # cd /dev/cua
    # ls -al
    total 18
    drwxr-xr-x   2 root     root         512 Jan  8 14:17 .
    drwxr-xr-x  17 root     sys         5120 Jan  8 14:37 ..
    lrwxrwxrwx   1 root     root          47 Jan  8 14:17 0 -> ../../devices/pci@1e,600000/usb@a/device@1:0,cu
    lrwxrwxrwx   1 root     root          51 Dec 22 10:20 a -> ../../devices/pci@1e,600000/isa@7/serial@0,3f8:a,cu
    lrwxrwxrwx   1 root     root          51 Dec 22 10:20 b -> ../../devices/pci@1e,600000/isa@7/serial@0,2e8:b,cuIt is appearing as the "0" up here. I followed the procedure on the Sun site for using a "tip" connection (the procedure is for a Edgeport device, and is described at: http://www.sun.com/io_technologies/USB-Faq.html#Serial point #4), and I added the following line to the "/etc/remote" file:
    u0:\
            :dv=/dev/cua/0:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:but I'm not able to use it for a "tip" connection yet. I get this error:
    # tip u0
    tip: /dev/cua/0: No such device or address
    all ports busyIs there someone here who could help me out getting a functionning "tip" session using my Prolific based USB-to-Serial adapter?
    Thanks in advance!!

    Hi Martin and thanks for the reply. This is very strange to me, because when in use on a Sun Ray station, I can use this adapter - from my Sun Ray station - to make a tip connection!! But when I connect it directly to the V240 server, I'm not able to.
    The "prtconf -v" says that about the USB device:
            usb, instance #0
                System software properties:
                    name='ddi-forceattach' type=int items=1
                        value=00000001
                Hardware properties:
                    name='pm-want-child-notification?' type=boolean
                    name='driver-minor' type=int items=1
                        value=00000000
                    name='driver-major' type=int items=1
                        value=00000002
                    name='root-hub' type=boolean
                Device Minor Nodes:
                    dev=(66,0)
                        dev_path=/pci@1e,600000/usb@a:1
                            spectype=chr type=minor
                            dev_link=/dev/cfg/usb0/1
                        dev_path=/pci@1e,600000/usb@a:2
                            spectype=chr type=minor
                            dev_link=/dev/cfg/usb0/2
                    dev=(66,4096)
                        dev_path=/pci@1e,600000/usb@a:hubd
                            spectype=chr type=minor
                            dev_link=/dev/usb/hub0
                device, instance #0
                    Driver properties:
                        name='pm-components' type=string items=3 dev=none
                            value='NAME= usbsprl0 Power' + '0=USB D3 State' + '3=USB D0 State'
                    Hardware properties:
                        name='driver-minor' type=int items=1
                            value=00000000
                        name='driver-major' type=int items=1
                            value=00000002
                        name='usb-product-name' type=string items=1
                            value='USB-Serial Controller D'
                        name='usb-vendor-name' type=string items=1
                            value='Prolific Technology Inc. '
                        name='usb-release' type=int items=1
                            value=00000110
                        name='usb-num-configs' type=int items=1
                            value=00000001
                        name='usb-revision-id' type=int items=1
                            value=00000400
                        name='usb-product-id' type=int items=1
                            value=00002303
                        name='usb-vendor-id' type=int items=1
                            value=0000067b
                        name='compatible' type=string items=9
                            value='usb67b,2303.400' + 'usb67b,2303' + 'usbif67b,classff.0.0' + 'usbif67b,classff.0' + 'usbif67b,classff' + 'usbif,classff.0.0' + 'usbif,classff.0' + 'usbif,classff' + 'usb,device'
                        name='reg' type=int items=1
                            value=00000001
                        name='assigned-address' type=int items=1
                            value=00000002
                    Device Minor Nodes:
                        dev=(78,0)
                            dev_path=/pci@1e,600000/usb@a/device@1:0
                                spectype=chr type=minor
                                dev_link=/dev/term/0
                                dev_link=/dev/tty0
                        dev=(78,131072)
                            dev_path=/pci@1e,600000/usb@a/device@1:0,cu
                                spectype=chr type=minor
                                dev_link=/dev/cua/0

  • K7N2 Delta-ILSR - USB to Serial Adapter Doesn't Work!

    Is anyone aware of an error such as the follows with the K7N2 Delta-ILSR?
    I am trying the use a USB to Serial Adapter, namely the a Prolific PL-2303.
    However, my PC does not seem to like it, nor does it what to cooperate with it at all.
    On one occasion i have managed to get the device to show in the Manager window with the exclamation mark,
    and upon checking its properties it told me: Prolific This device cannot start. (Code 10).
    I have un-installed all my system USB drivers and the device drivers, and reinstalled them, but again, no matter what i do i cannot get it to work.
    Any ideas peeps?
    Cheers, G.

    Don't think it will this time, but on occassions booting into SafeMode and removing possibly half-installed copies of USB devices from Device Manager has helped.
    Is this what you are looking for, Henry?
    http://www.prolific.com.tw/eng/downloads.asp?ID=33
    "Note: Please take notice of the installation order. First, run the InstallShield wizard,
    and then plug in the USB to Serial adapter"
    ...How many times have I said that, if a USB device needs a driver you install that before attaching the device!?

  • Usb to Serial port adapter

    I have a gilsson usb to serial port bi directional adapter cable which uses the Prolific pl-2303 chipset. I am attempting to use this cable to interface a Mac Mini with a Harsper PDP plasma television.
    I am attempting to control the functions of the television via the serial port on the television. i.e. Turn on, input, volume, etc.
    What I need is software, or source code that would allow me to send hexidecimal commands to the television and receive the task completed codes.

    ZTerm will allow serial communications. Get it to ensure that throughput is happening as expected.
    RealBasic will allow you to roll your own with a fair amount of ease.
    A long time ago I used the above to communicate with my cellphone to send and receive text messages via the serial port, so I know it can work. Understanding the protocols is the difficult part...

  • USB to Serial port adapter - Mac thinks  it's a modem

    I’m trying to connect my Mac’s USB port to a Sony Beta SP recorder's Serial Port using a generic USB to Serial adapter which uses the Prolific PL-2303 chip.
    I’m using the latest Prolific Universal driver, but when I plug in the USB cable I get a message that a ‘new network device has been detected’ and suggesting that I use System Preferences to set it up. But in System Preferences it seems to think the USB to Serial adapter is a modem and is looking for a phone number and other configuration data.
    Does anyone know how to get it to work as just a serial communication device to my Sony’s serial port? If I get it working I'll be connecting it to an RS232 to RS422 adapter to talk to the Sony port.
    Thanks.

    Thanks Andy.
    I'll have a go again. It was late last night when I was trying to set it up, so maybe a fresh brain will have more success. I did try to 'Cancel' the network preference window that opened, but got the impression that it would not work unless I did 'something'. Someone else told me I could cancel that message permanently within System Preferences, so I'll try that too. Yet another bit of advice I got was that I would have to install 'MacPorts' and run something called 'Minicom' to set up the serial parameters. Windows was so simple by comparison
    As a non-techie (at least in all these software and protocol issues) I'm more than a little confused.
    Regards
    Message was edited by: esmonde

  • How do I pragmmatic​ally determine what comm ports my serial instrument​s are on?

    I am building a test stand that incorporates 5 serial instruments; 2 digital loads and 3 power supplies. I can use my PC's device manager to figure out which comm port each device is on and set the VISA Resource Name so everything runs as expected. All is well at this point. The problem comes in when an instrument's USB connection is unplugged and replugged, at which point the system may renumber the port assignments; the result is that my program errors out, I have to figure out what port everything is on all over again, and change the VISA Resource Name for all of my instruments. While this is a minor annoyance for me as the developer, this would make the program unusable by the user.
    While "don't ever unplug an instrument" is a sensible answer, the fact is that these things happen from time to time - like for calibration - so I want the program to work regardless of instruments being unplugged.
    Is there a way to have the vi automatically identify what port each instrument is on?

    I've used a USB connected barcode scanner that appears as a COM port. If it is left connected to the same USB port the COM port remains constant but if it is disconnected and then put back into a different port the COM port changes. This sounds similar to your problem so I'll share how I solved things for my application.
    The scanner I use accepts commands and will respond with a known string when I send a character 'I' via the serial connection. Using this I can see if the scanner is connected to the expected COM port (default port is stored in an ini file).
    If this fails I create an array of possible serial ports by trying to open COM1 and checking for an error. If this does not generate an error I add it to an array. Next I try the same with COM2, COM3 up to COM16 (for example). This gives me a list of COM ports I can open.
    I then iterate through the array trying for a response and stopping either when I get the expected response and continuing with the application or if the device is not found by the time I get to the end of the array I show the appropriate error condition to the operator.
    If your instruments can return some kind of ID that will allow you to identify them as mentioned in another reply then this method could be used. Your 3 power supplies and 2 digital loads would need to be able to return a unique identifier otherwise you wouldn't be able to tell them apart and I think you'd possibly run in to problems.

  • PC Suite - no USB and Serial Connection Type avail...

    I have been trying to solve this problem for days now. I have Windows XP and Nokia 5310. After I installed Nokia PC Suite, there is no USB or Serial connection type in the Connection Manager; it only has Blue Tooth and Infrared conection available. I have install and uninstalled PC suite and used PC Suite Cleaner to clean the installation. I also went into the add and remove program in the control panel and click on "change" to fix the Nokia Connection Manager and Nokia Connectivity Cable Driver. It still didn't work. The thing is that the first time when installed PC Suite on my laptop, it did have USB connection option. Later after uninstalled PC Suite and reinstalled it, it start to have this problem. I am extremly frustrated. Can anyone help please?

    Thanks for your reply. I have solved the problem by following your instruction below:
    Go to Start --> Settings --> Control Panel --> Software, there you need to uninstall all Nokia software (Nokia PC Suite, Nokia Cable driver, PC Connectivity Solution ...)
    Download and run Nokia PC Suite Cleaner
    Reboot your computer
    Download and install PC Suite here.
    Connect your phone via USB cable (if possible use a different USB jack) and follow the instructions on the screen.
    Maybe when I uninstalled Chinese version of PC suite, the order in which it was uninstalled was not the one you suggested above. So,I followed your instruction and uninstall order to uninstall PC Suite again. I also uninstalled all the antivirus, spyware, and firewall before I reinstall the PC Suite. It worked; then, I reinstalled all the other security software again after I had reinstalled the PC Suite. Although it worked, I still didn't know what exactly cause the problem the first place, PC Suite version, Security protection software, or the order which it was uninstalled? All it matters is it's working.

  • Using usb as serial connecting to cisco router not working

    Tried using ZOC and securecrt and both shows only /dev/tty-Bluetooth.....
    any ideas how can I use USB as serial connection to router?

    Hi and welcome to the forums!
    GREAT FIRST POST!! Very clear and specific. You don't know how rare that is
    Is the laptop in a docking bay?
    Content "encryption" meaning Content protection is turned off, right?
    Are you able to backup and sync with the Desktop software?
    Do you have the correct folders on the card?
    Blackberry, music, ringtones, pictures, videos, voice notes?
    (blackberry has to be first).
    Last one, how did you format the card?
    Thanks
    Update device drivers manually:
    http://www.blackberry.com/btsc/search.do?cmd=displ​ayKC&docType=kc&externalId=KB13336&sliceId=SAL_Pub​...
    Message Edited by Bifocals on 11-19-2008 08:36 PM
    Click Accept as Solution for posts that have solved your issue(s)!
    Be sure to click Like! for those who have helped you.
    Install BlackBerry Protect it's a free application designed to help find your lost BlackBerry smartphone, and keep the information on it secure.

  • USB Console (Serial) Driver fails to install on Windows 8.1 x64

    The USB console cable driver v3.1 will not install on Windows 8.1 x64.  Had a similar problem with Windows 7 x64 but this was fixed using Greg's (greggar25) excellent step-by-step procedure (see post: https://supportforums.cisco.com/discussion/11492306/usb-console-driver-install-failing).
    I am using the driver from this link: http://software.cisco.com/download/release.html?mdfid=282774228&flowid=7442&softwareid=282855122&release=3.1&relind=AVAILABLE&rellifecycle=&reltype=latest
    I followed the same procedures I did for Windows 7 and the install goes without a hitch.  Reboot and connect the USB cable, opened Device Manager and now I have a COM Port randomly appearing and disappearing with its number incrementing well above 1,000.
    A few times while it appeared for a few seconds, I was able to right click on the properties, update the driver and chose Cisco Serial and it settled down but it did not assign a COM port.  Then a few seconds later, it starts the disappearing/reappearing thing again.
    Anyone have luck getting this to work with Windows 8.1 x64?

     Hi,
    open Device Manager by simply typing the words on the Windows 8.1 Start Screen. The Search Charm opens and click Device Manager in the displayed list. 
    In Device Manager a new hardware category, CiscoUsbConsoleWindowsDriver, is displayed. It has two components: the Cisco Bus enumerator and the Cisco USB to Serial adapter. Expanding the Ports hardware category shows a new Cisco Serial port. 
     or 
    Look into below 
    https://supportforums.cisco.com/discussion/11492306/usb-console-driver-install-failing
    1) Install the usb console driver\windows 64\setup(x64)
    2) Follow the wizard and accept the defaults
    3) Restart the computer (the installer usually says it needs a restart)
    4) After restarting the computer, plug in the usb cable
    5) The computer should say installing Device driver software and fail at the Cisco Virtual Comm Port00
    6) Click the Windows button, right click computer, manage
    7) Under Computer Management, Click Device Management
    8) Go to Ports (COM & LPT)
    9) You should see the Cisco Virtual Comm Port00 with a Yellow Exclamation point on it
    10) Right Click on the Cisco Virtual Comm Port00 and select Properties
    11) Click the Driver Tab
    12) Click Update Driver
    13) Select Browse my computer for driver software
    14) Select Let me pick from a list of device drivers on my computer
    15) Choose the Cisco Serial Driver
    16) Device Driver is installed successfully, take note of the com port it is using and enjoy.
    HTH 
    Sandy 

  • Macbook Pro Late 2008 usb to serial cable stops communicating after Yosemite upgrade

    I recently updated my MacbookPro to Yosemite and have found that my usb to serial cable no longer works. I've tried reinstalled drivers multiple times with no success when I connect my Gigaware usb to serial cable and conect my cisco console cable which used to work fine on Mavericks but now I get no output in my terminal program secureCRT.
    I when my cable is connect I see the following in dev
    hugh-millers-macbook-pro-77:dev Yogi$ ls tty.*
    tty.Bluetooth-Incoming-Port tty.HughsiPhone-WirelessiAP
    tty.Bluetooth-Modem tty.PL2303-00002006
    hugh-millers-macbook-pro-77:dev Yogi$ ls *PL*
    cu.PL2303-00002006 tty.PL2303-00002006
    hugh-millers-macbook-pro-77:dev Yogi$
    Here is what I see in System Information
    USB-Serial Controller:
    Product ID: 0x0fba
    Vendor ID: 0x05ad (Y.C. Cable U.S.A., Inc)
    Version: 3.00
    Speed: Up to 12 Mb/sec
    Manufacturer: Prolific Technology Inc.
    Location ID: 0x04100000 / 4
    Current Available (mA): 500
    Current Required (mA): 100
    SecureCRT is set to use /dev/cu.PL2303-00002006
    Has anyone experienced this issue, can anyone assist?
    Mac Info
    MacBook Pro (15-inch, Late 2008)
    2.53 GHz Intel Core 2 Duo
    4 GB 1067 MHz DDR3

    You can use this : http://www.macupdate.com/app/mac/51344/serial but let me tell you that last night I found the way to do it with Coolterm for free http://www.macupdate.com/app/mac/31352/coolterm
    I think that the problem is the installation , you have to copy to sudo kextload /System/Library/Extensions/ProlificUsbSerial.kext or in my case  I used this as reference, now it is working....
    http://www.xbsd.nl/2011/07/pl2303-serial-usb-on-osx-lion.html
    I hope this can help

Maybe you are looking for