Announcement

Collapse
No announcement yet.

uLCD-70DT-AR and USB-PA5

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Click image for larger version

Name:	2016-03-23_13-27-34.png
Views:	258
Size:	21.7 KB
ID:	51636


    This is what I get here. (Note this is for a Programming Cable, not PA5-II, but the driver and process is identical).
    James

    Comment


    • #32
      Originally posted by James_4DSystems View Post
      Faults and failures do happen from time to time, which is why we have a RMA process to get faulty modules replaced. You being in Brazil and travelling to the US to get the module is unfortunate, and I will try and see if there is something we can do to get you a replacement directly, even though this should be done through Mouser.

      I am just trying to go through every possible thing I can think of, in case it is not hardware related, as you have no idea how many people we have doing incorrect things, and it being User error rather than a hardware problem. I am merely trying to assure this is not the case with you, and I don't believe it is the case with you. As if we sent you a tested replacement directly, and it does the same thing for you when you receive it, then we are back at square 1 aren't we.

      So let me ask again, just to be 100% clear and sure.
      You have uninstalled the driver via Device Manager.
      You have uninstalled the Silicon Labs driver from Add/Remove Programs? Likewise with the old FTDI drivers you attempted first?
      You have restarted your PC
      You have connected the PA5 to your PC again, without the display module.
      It comes up as an unknown item, right?
      You have then attempted to install the Silicon Labs driver, using the installer
      Still an unknown item?
      Disconnect it form your PC and plug it in again. Still unknown?
      If so, then really it has to be hardware, as this is not rocket science, these things normally just work. I cant recall any previous failure regarding a PA5.

      Also - you said windows says 'The best software driver is already installed' etc. Any idea what software driver it thinks it has loaded? your screenshots didnt seem to show it.

      Regards


      Well, here are the videos, doing exactly what you asked for.

      1º Part: https://vid.me/jOgt
      2º Part: https://vid.me/VaIg

      Comment


      • #33
        Originally posted by James_4DSystems View Post
        Well it seems it is still loading the wrong driver....

        Can you do the following and try and force it to update, as for some reason it is not loading the right one - extremely weird.

        1. Open the Device Manager Control Panel.
        2. Select the faulty device, right-click on it, and select 'Update Driver Software'.
        3. Click on 'Browse my computer for driver software'
        4. Click on 'Let me pick from a list of device drivers on my computer'.
        5. Click 'Have disk'.
        6. Point it to the file slabvcp.inf from the folder where you extracted all the driver files to.
        7. Click on Open and then OK.
        8. Select the Silicon Labs driver from the list, click Next
        9. Click on Yes to continue the installation if you receive a message saying 'Installing this driver is not recommended because Windows cannot verify that it is compatible with your hardware.'.
        10. Click 'Close' to complete the installation.
        11. Select Yes to reboot if asked. If not asked, we recommend that you reboot the computer anyway.

        And that should be it...

        Please confirm. I just did the above with my one here, which already had a driver installed, but I updated it using the above.

        If you look at the end of the second video, once that everything you had suggested failed, I already tryied to do this but It shows that message saying that the driver isnt the compatible with the device, or with the x64 system.

        Comment


        • #34
          I'm sorry for the language being in portuguese, I already reverted it back, but I think you can "understand" the procedure, if you have any doubt just ask.

          Comment


          • #35
            OK, thanks for doing that, you are doing it all right.

            Near the end of the video, when you did the instructions above in Post #30, there is a tick box to only install compatible items. CAn you untick that, and see if it lists the right driver then, as it may be in a pickle somehow and thinking its something else.

            Very strange though.
            This is the last thing to try

            Click image for larger version

Name:	2016-03-23_13-43-47.png
Views:	182
Size:	34.2 KB
ID:	51641

            Regards
            James

            Comment


            • #36
              Originally posted by James_4DSystems View Post
              [ATTACH=CONFIG]n51636[/ATTACH]


              This is what I get here. (Note this is for a Programming Cable, not PA5-II, but the driver and process is identical).

              Can you please provide me the .inf file you used? Just to make sure...

              Here is mine, downloaded from the link you informed, that show that error on the video.


              Code:
              ;/*++
              ;
              ;Module Name:
              ;
              ;    SLABVCP.INF
              ;
              ;    Copyright 2013-2015, Silicon Laboratories Inc.
              ;
              ;Abstract:
              ;    Installation INF for Silicon Labs CP210x device
              ;
              ;--*/
              
              [Version]
              Signature="$WINDOWS NT$"
              Class=Ports
              ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
              Provider=%Provider%
              DriverVer=11/20/2015,6.7.2.200
              CatalogFile=slabvcp.cat
              PnpLockDown=1    ; "a driver package should set PnpLockDown to 1" -- MSDN
              
              ; ================= Device section =====================
              
              [Manufacturer]
              %ManufacturerName%=SiLabsModelsSection, NTx86.6.1, NTamd64.6.1, NTarm.10, NTarm64.10
              
              ;Models section for installation of x86 driver on Windows 7 and above
              [SiLabsModelsSection.NTx86.6.1]
              %USB\VID_10C4&PID_EA60.DeviceDesc%      =SiLabsDDInstallSection.NTx86, USB\VID_10C4&PID_EA60        ; USB\VID_v(4)&PID_d(4)
              %USB\VID_10C4&PID_EA70&Mi_00.DeviceDesc%=SiLabsDDInstallSection.NTx86, USB\VID_10C4&PID_EA70&Mi_00    ; USB\VID_v(4)&PID_d(4)&MI_z(2)
              %USB\VID_10C4&PID_EA70&Mi_01.DeviceDesc%=SiLabsDDInstallSection.NTx86, USB\VID_10C4&PID_EA70&Mi_01
              %USB\VID_10C4&PID_EA71&Mi_00.DeviceDesc%=SiLabsDDInstallSection.NTx86, USB\VID_10C4&PID_EA71&Mi_00
              %USB\VID_10C4&PID_EA71&Mi_01.DeviceDesc%=SiLabsDDInstallSection.NTx86, USB\VID_10C4&PID_EA71&Mi_01
              %USB\VID_10C4&PID_EA71&Mi_02.DeviceDesc%=SiLabsDDInstallSection.NTx86, USB\VID_10C4&PID_EA71&Mi_02
              %USB\VID_10C4&PID_EA71&Mi_03.DeviceDesc%=SiLabsDDInstallSection.NTx86, USB\VID_10C4&PID_EA71&Mi_03
              %USB\VID_10C4&PID_EAD0.DeviceDesc%      =SiLabsDDInstallSection.NTx86, USB\VID_10C4&PID_EAD0        ; USB\VID_v(4)&PID_d(4)
              
              ;Models section for installation of x64 driver on Windows 7 and above
              [SiLabsModelsSection.NTamd64.6.1]
              %USB\VID_10C4&PID_EA60.DeviceDesc%      =SiLabsDDInstallSection.NTamd64, USB\VID_10C4&PID_EA60        ; USB\VID_v(4)&PID_d(4)
              %USB\VID_10C4&PID_EA70&Mi_00.DeviceDesc%=SiLabsDDInstallSection.NTamd64, USB\VID_10C4&PID_EA70&Mi_00    ; USB\VID_v(4)&PID_d(4)&MI_z(2)
              %USB\VID_10C4&PID_EA70&Mi_01.DeviceDesc%=SiLabsDDInstallSection.NTamd64, USB\VID_10C4&PID_EA70&Mi_01
              %USB\VID_10C4&PID_EA71&Mi_00.DeviceDesc%=SiLabsDDInstallSection.NTamd64, USB\VID_10C4&PID_EA71&Mi_00
              %USB\VID_10C4&PID_EA71&Mi_01.DeviceDesc%=SiLabsDDInstallSection.NTamd64, USB\VID_10C4&PID_EA71&Mi_01
              %USB\VID_10C4&PID_EA71&Mi_02.DeviceDesc%=SiLabsDDInstallSection.NTamd64, USB\VID_10C4&PID_EA71&Mi_02
              %USB\VID_10C4&PID_EA71&Mi_03.DeviceDesc%=SiLabsDDInstallSection.NTamd64, USB\VID_10C4&PID_EA71&Mi_03
              %USB\VID_10C4&PID_EAD0.DeviceDesc%      =SiLabsDDInstallSection.NTamd64, USB\VID_10C4&PID_EAD0        ; USB\VID_v(4)&PID_d(4)
              
              ;Models section for installation of arm driver on Windows 10 and above
              [SiLabsModelsSection.NTarm.10]
              %USB\VID_10C4&PID_EA60.DeviceDesc%      =SiLabsDDInstallSection.NTarm, USB\VID_10C4&PID_EA60        ; USB\VID_v(4)&PID_d(4)
              %USB\VID_10C4&PID_EA70&Mi_00.DeviceDesc%=SiLabsDDInstallSection.NTarm, USB\VID_10C4&PID_EA70&Mi_00    ; USB\VID_v(4)&PID_d(4)&MI_z(2)
              %USB\VID_10C4&PID_EA70&Mi_01.DeviceDesc%=SiLabsDDInstallSection.NTarm, USB\VID_10C4&PID_EA70&Mi_01
              %USB\VID_10C4&PID_EA71&Mi_00.DeviceDesc%=SiLabsDDInstallSection.NTarm, USB\VID_10C4&PID_EA71&Mi_00
              %USB\VID_10C4&PID_EA71&Mi_01.DeviceDesc%=SiLabsDDInstallSection.NTarm, USB\VID_10C4&PID_EA71&Mi_01
              %USB\VID_10C4&PID_EA71&Mi_02.DeviceDesc%=SiLabsDDInstallSection.NTarm, USB\VID_10C4&PID_EA71&Mi_02
              %USB\VID_10C4&PID_EA71&Mi_03.DeviceDesc%=SiLabsDDInstallSection.NTarm, USB\VID_10C4&PID_EA71&Mi_03
              %USB\VID_10C4&PID_EAD0.DeviceDesc%      =SiLabsDDInstallSection.NTarm, USB\VID_10C4&PID_EAD0        ; USB\VID_v(4)&PID_d(4)
              
              ;Models section for installation of arm64 driver on Windows 10 and above
              [SiLabsModelsSection.NTarm64.10]
              %USB\VID_10C4&PID_EA60.DeviceDesc%      =SiLabsDDInstallSection.NTarm64, USB\VID_10C4&PID_EA60        ; USB\VID_v(4)&PID_d(4)
              %USB\VID_10C4&PID_EA70&Mi_00.DeviceDesc%=SiLabsDDInstallSection.NTarm64, USB\VID_10C4&PID_EA70&Mi_00    ; USB\VID_v(4)&PID_d(4)&MI_z(2)
              %USB\VID_10C4&PID_EA70&Mi_01.DeviceDesc%=SiLabsDDInstallSection.NTarm64, USB\VID_10C4&PID_EA70&Mi_01
              %USB\VID_10C4&PID_EA71&Mi_00.DeviceDesc%=SiLabsDDInstallSection.NTarm64, USB\VID_10C4&PID_EA71&Mi_00
              %USB\VID_10C4&PID_EA71&Mi_01.DeviceDesc%=SiLabsDDInstallSection.NTarm64, USB\VID_10C4&PID_EA71&Mi_01
              %USB\VID_10C4&PID_EA71&Mi_02.DeviceDesc%=SiLabsDDInstallSection.NTarm64, USB\VID_10C4&PID_EA71&Mi_02
              %USB\VID_10C4&PID_EA71&Mi_03.DeviceDesc%=SiLabsDDInstallSection.NTarm64, USB\VID_10C4&PID_EA71&Mi_03
              %USB\VID_10C4&PID_EAD0.DeviceDesc%      =SiLabsDDInstallSection.NTarm64, USB\VID_10C4&PID_EAD0        ; USB\VID_v(4)&PID_d(4)
              
              ;DDInstall sections (one per x86, amd64, arm, arm64)
              ; Note: If/as we are building a Universal driver package, we can not use a DefaultInstall section.
              [SiLabsDDInstallSection.NTx86]
              AddReg=silabser.AddReg
              CopyFiles=silabser.Files.Ext
              FeatureScore=0x40    ; a single-byte hexadecimal number between 0x00 and 0xFF, A lower featurescore value specifies a better feature score rank, where 0x00 is the best feature score rank.
              
              [SiLabsDDInstallSection.NTamd64]
              AddReg=silabser.AddReg
              CopyFiles=silabser.Files.Ext
              FeatureScore=0x40    ; a single-byte hexadecimal number between 0x00 and 0xFF, A lower featurescore value specifies a better feature score rank, where 0x00 is the best feature score rank.
              
              [SiLabsDDInstallSection.NTarm]
              AddReg=silabser.AddReg
              CopyFiles=silabser.Files.Ext
              FeatureScore=0x40    ; a single-byte hexadecimal number between 0x00 and 0xFF, A lower featurescore value specifies a better feature score rank, where 0x00 is the best feature score rank.
              
              [SiLabsDDInstallSection.NTarm64]
              AddReg=silabser.AddReg
              CopyFiles=silabser.Files.Ext
              FeatureScore=0x40    ; a single-byte hexadecimal number between 0x00 and 0xFF, A lower featurescore value specifies a better feature score rank, where 0x00 is the best feature score rank.
              
              
              ;DDInstall.Services sections (one per x86, amd64, arm, arm64)
              ; Note: If/as we are building a Universal driver package, we can not use a DefaultInstall.Services section.
              [SiLabsDDInstallSection.NTx86.Services]
              Addservice = silabser,0x00000002,silabser.AddService
              
              [SiLabsDDInstallSection.NTamd64.Services]
              Addservice = silabser,0x00000002,silabser.AddService
              
              [SiLabsDDInstallSection.NTarm.Services]
              Addservice = silabser,0x00000002,silabser.AddService
              
              [SiLabsDDInstallSection.NTarm64.Services]
              Addservice = silabser,0x00000002,silabser.AddService
              
              [silabser.AddService]
              DisplayName    = %silabser.SvcDesc%
              ServiceType    = 1                  ; SERVICE_KERNEL_DRIVER
              StartType      = 3                  ; SERVICE_DEMAND_START
              ErrorControl   = 1                  ; SERVICE_ERROR_NORMAL
              ServiceBinary  = %12%\silabser.sys
              
              ; common registry entries 
              [silabser.AddReg]
              HKR,,NTMPDriver,,silabser.sys
              HKR,,RateLimitPurgeMS, 0x10001, 0x64, 0x00, 0x00, 0x00
              HKR,,OverrideDefaultPortSettings, 0x10001, 01,00,00,00
              HKR,,InitialBaudRate, 0x10001, 00,C2,01,00        ;115200 initial baud rate
              HKR,,InitialLineControl,, "8N1"                ;8-bits, No parity, 1 stop bit
              HKR,,PortSubClass,1,01
              HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"
              
              ;DDInstall.HW sections (one per x86, amd64, arm, arm64)
              [SiLabsDDInstallSection.NTx86.HW]
              AddReg=SiLabsDDInstallSection.HW.AddReg
              
              [SiLabsDDInstallSection.NTamd64.HW]
              AddReg=SiLabsDDInstallSection.HW.AddReg
              
              [SiLabsDDInstallSection.NTarm.HW]
              AddReg=SiLabsDDInstallSection.HW.AddReg
              
              [SiLabsDDInstallSection.NTarm64.HW]
              AddReg=SiLabsDDInstallSection.HW.AddReg
              
              [SiLabsDDInstallSection.HW.AddReg]
              HKR,,"SelectiveSuspendTimeout",0x00010001,10000
              ; Attention! The EnablePowerManagewment value is no longer supported.
              ; If you need to disable Selective Suspend, uncomment the following line:
              ; HKR,,"DisableS0Idle",0x00010001,1
              
              [silabser.Files.Ext]
              silabser.sys
              
              [SourceDisksNames.x86]
              1=%Disk_Description%,"slabvcp.cat"
              [SourceDisksNames.amd64]
              1=%Disk_Description%,"slabvcp.cat"
              [SourceDisksNames.arm]
              1=%Disk_Description%,"slabvcp.cat"
              [SourceDisksNames.arm64]
              1=%Disk_Description%,"slabvcp.cat"
              
              [SourceDisksFiles.x86]
              silabser.sys = 1,x86
              WdfCoinstaller01011.dll=1,x86
              
              [SourceDisksFiles.amd64]
              silabser.sys = 1,x64
              WdfCoinstaller01011.dll=1,x64
              
              [SourceDisksFiles.arm]
              silabser.sys = 1,arm
              WdfCoinstaller01011.dll=1,arm
              
              [SourceDisksFiles.arm64]
              silabser.sys = 1,arm64
              WdfCoinstaller01015.dll=1,arm64
              
              [DestinationDirs]
              Silabser.Files.Ext = 12 ; windows\system32\drivers

              Comment


              • #37
                Here is the rest.

                Code:
                ;-------------- WDF Coinstaller installation
                [DestinationDirs]
                CoInstaller_CopyFiles.KMDF.1.11 = 11 ; windows\system32
                CoInstaller_CopyFiles.KMDF.1.15 = 11 ; windows\system32
                
                ;DDInstall.CoInstallers sections (one per x86, amd64, arm, arm64)
                ; "You can use any INF section in a universal INF file except for [CoInstallers]" -- MSDN
                [SiLabsDDInstallSection.NTx86.CoInstallers]
                AddReg=CoInstaller_AddReg.KMDF.1.11
                CopyFiles=CoInstaller_CopyFiles.KMDF.1.11
                
                [SiLabsDDInstallSection.NTamd64.CoInstallers]
                AddReg=CoInstaller_AddReg.KMDF.1.11
                CopyFiles=CoInstaller_CopyFiles.KMDF.1.11
                
                [SiLabsDDInstallSection.NTarm.CoInstallers]
                AddReg=CoInstaller_AddReg.KMDF.1.11
                CopyFiles=CoInstaller_CopyFiles.KMDF.1.11
                
                [SiLabsDDInstallSection.NTarm64.CoInstallers]
                AddReg=CoInstaller_AddReg.KMDF.1.15
                CopyFiles=CoInstaller_CopyFiles.KMDF.1.15
                
                [CoInstaller_CopyFiles.KMDF.1.11]
                WdfCoinstaller01011.dll
                [CoInstaller_CopyFiles.KMDF.1.15]
                WdfCoinstaller01015.dll
                
                [SourceDisksFiles]
                WdfCoinstaller01011.dll=1
                WdfCoinstaller01015.dll=1
                
                [CoInstaller_AddReg.KMDF.1.11]
                HKR,,CoInstallers32,0x00010000, "WdfCoinstaller01011.dll,WdfCoInstaller"
                [CoInstaller_AddReg.KMDF.1.15]
                HKR,,CoInstallers32,0x00010000, "WdfCoinstaller01015.dll,WdfCoInstaller"
                
                
                ;DDInstall.Wdf sections (one per x86, amd64, arm, arm64)
                [SiLabsDDInstallSection.NTx86.Wdf]
                KmdfService = silabser, SiLabs_wdfsect.1.11
                
                [SiLabsDDInstallSection.NTamd64.Wdf]
                KmdfService = silabser, SiLabs_wdfsect.1.11
                
                [SiLabsDDInstallSection.NTarm.Wdf]
                KmdfService = silabser, SiLabs_wdfsect.1.11
                
                [SiLabsDDInstallSection.NTarm64.Wdf]
                KmdfService = silabser, SiLabs_wdfsect.1.15
                
                [SiLabs_wdfsect.1.11]
                KmdfLibraryVersion = 1.11
                [SiLabs_wdfsect.1.15]
                KmdfLibraryVersion = 1.15
                
                ;---------------------------------------------------------------;
                
                [Strings]
                Provider="Silicon Laboratories Inc."
                ManufacturerName="Silicon Labs"
                Disk_Description=                      "Silicon Labs CP210x USB to UART Bridge Installation Disk"
                USB\VID_10C4&PID_EA60.DeviceDesc=      "Silicon Labs CP210x USB to UART Bridge"
                USB\VID_10C4&PID_EA70&Mi_00.DeviceDesc="Silicon Labs Dual CP210x USB to UART Bridge: Enhanced COM Port"
                USB\VID_10C4&PID_EA70&Mi_01.DeviceDesc="Silicon Labs Dual CP210x USB to UART Bridge: Standard COM Port"
                USB\VID_10C4&PID_EA71&Mi_00.DeviceDesc="Silicon Labs Quad CP210x USB to UART Bridge: Interface 0"
                USB\VID_10C4&PID_EA71&Mi_01.DeviceDesc="Silicon Labs Quad CP210x USB to UART Bridge: Interface 1"
                USB\VID_10C4&PID_EA71&Mi_02.DeviceDesc="Silicon Labs Quad CP210x USB to UART Bridge: Interface 2"
                USB\VID_10C4&PID_EA71&Mi_03.DeviceDesc="Silicon Labs Quad CP210x USB to UART Bridge: Interface 3"
                USB\VID_10C4&PID_EAD0.DeviceDesc=      "Silicon Labs CP2102N USB to UART Bridge"
                silabser.SvcDesc="Silicon Labs CP210x USB to UART Bridge Driver"
                PortsClassName = "Ports (COM & LPT)"

                Comment


                • #38
                  I got it from the same link, so surely it would be the same.

                  Attached.
                  Attached Files
                  James

                  Comment


                  • #39
                    Originally posted by James_4DSystems View Post
                    OK, thanks for doing that, you are doing it all right.

                    Near the end of the video, when you did the instructions above in Post #30, there is a tick box to only install compatible items. CAn you untick that, and see if it lists the right driver then, as it may be in a pickle somehow and thinking its something else.

                    Very strange though.
                    This is the last thing to try

                    [ATTACH=CONFIG]n51641[/ATTACH]

                    Regards

                    Yeah, sure, I made another video, since it's much easier to get on the same page.

                    Here is it: https://vid.me/XX0y

                    I had already tried that before too, but didn't found any driver that matched, and when clicking on "have disk" the same error still happens...

                    Comment


                    • #40
                      Originally posted by James_4DSystems View Post
                      I got it from the same link, so surely it would be the same.

                      Attached.

                      Well, I tried with your attachment too, indeed the same error still persists...

                      Comment


                      • #41
                        Thanks - yep, very strange and I am out of ideas.
                        It shouldn't be this hard and I am sorry its taken all this time, this is just the first one like this we have seen which doesn't work.

                        Sales has approved shipping you a replacement PA5 directly from HQ, at our cost. Shipping is horrendous cost to Brazil, but its been approved.
                        I have someone testing a uUSB-PA5-II out of stock right now, before it is shipped.

                        Please send me an email with your address details. james at 4dsystems dot com dot au

                        Regards
                        James

                        Comment


                        • #42
                          Originally posted by James_4DSystems View Post
                          Thanks - yep, very strange and I am out of ideas.
                          It shouldn't be this hard and I am sorry its taken all this time, this is just the first one like this we have seen which doesn't work.

                          Sales has approved shipping you a replacement PA5 directly from HQ, at our cost. Shipping is horrendous cost to Brazil, but its been approved.
                          I have someone testing a uUSB-PA5-II out of stock right now, before it is shipped.

                          Please send me an email with your address details. james at 4dsystems dot com dot au

                          Regards


                          Cool, yes, the shipping is very cost and the delivery takes to long, and the worse part is the Customs that will probably tax it upon arrival. That's why I bought it when I was in the States.
                          I'm sending you the e-mail.

                          Thanks for the effort.

                          Comment


                          • #43
                            Originally posted by James_4DSystems View Post
                            Thanks - yep, very strange and I am out of ideas.
                            It shouldn't be this hard and I am sorry its taken all this time, this is just the first one like this we have seen which doesn't work.

                            Sales has approved shipping you a replacement PA5 directly from HQ, at our cost. Shipping is horrendous cost to Brazil, but its been approved.
                            I have someone testing a uUSB-PA5-II out of stock right now, before it is shipped.

                            Please send me an email with your address details. james at 4dsystems dot com dot au

                            Regards

                            E-mail forwarded, please confirm the receipt.
                            Last edited by Arank; 23rd March 2016, 11:40 AM.

                            Comment


                            • #44
                              received, replied.

                              Regards
                              James

                              Comment


                              • #45
                                Originally posted by James_4DSystems View Post
                                received, replied.

                                Regards


                                It worked, out of the box.
                                I got the repleacement today, and didn't even need to manually install the drivers, just plug and play, connected and it was recognized.

                                Thanks very much.

                                Comment

                                Working...
                                X