Loading ...
Sorry, an error occurred while loading the content.

Re: [tnc-x] Re: USB Drivers Installation Problem

Expand Messages
  • Andy McMullin
    I agree, I ve now filed the mails because I found the discussion interesting. While they could now go private, I love reading such discussions -- thanks for
    Message 1 of 13 , Jul 1 11:08 AM
    • 0 Attachment
      I agree, I've now filed the mails because I found the discussion
      interesting. While they could now go private, I love reading such
      discussions -- thanks for keeping the list alive!

      Andy


      On 1 Jul 2008, at 05:44, Michel Hoche-Mong wrote:

      > Actually, it was nice hearing about this from just a "FYI"
      > standpoint, but yeah, further discussion can probably be taken
      > offline.
      >
      > -michel
      > KF6ZST
      >
      > On Tue, Jul 01, 2008 at 12:41:03AM -0400, John Hansen wrote:
      >> Noel:
      >>
      >> First of all, let me suggest that we move this discussion off the
      >> list.
      >> Please send further emails to john@... because I think we
      >> might risk boring the rest of the folks on the list. I have one of
      >> those old modules on hand, and I'd be happy to send it to you for the
      >> cost of shipping, but I'm wondering if perhaps it might make more
      >> sense
      >> to reprogram both of yours so that they conform to the latest
      >> drivers.
      >> That would involve having you send both modules in. I can promise
      >> you a
      >> 24 hour turn around on them. My guess is that the problem with the
      >> second one is simply a bad solder connection and it can probably be
      >> repaired. If not I'll replace it for free and send both of them
      >> back to
      >> you. But I think you would be better off long term to have the same
      >> drivers work with both modules (so you don't have to worry about
      >> loading
      >> up multiple drivers on your computer), and it would probably make
      >> sense
      >> to make them both the latest drivers.
      >>
      >> Let me know what you think.
      >>
      >> John W2FS
      >> Coastal ChipWorks
      >>
      >> Noel Seeley wrote:
      >>>

      --
      Regards
      Andy, G8TQH
      http://www.rickham.net/
    • Ed L Locklear
      ... John, Using the usbview.exe program reading my module VID=0X0403, PID=0XEBE0. With this information I modified the FTDIBUS.INF and FTDIPORT.INF files.
      Message 2 of 13 , Sep 29, 2008
      • 0 Attachment
        --- In tnc-x@yahoogroups.com, John Hansen <john@...> wrote:
        >
        > The first step, I think is to make sure the product ID and vendor ID on
        > the USB module haven't somehow become changed or corrupted. Go to this
        > page:
        >
        > http://www.ftdichip.com/Resources/Utilities.htm
        >
        > and download the USBView program. Plug in the TNC-X and run the USBView
        > program and hopefully you'll see something listed that looks like "USB
        > Serial Converter" listed on the left side of the screen. If you then
        > click it, on the right side of the screen you'll see a device
        > description for that device. Under ipVendor it should say 0x0402 and
        > under idProduct it should say 0x6001. If it doesn't, there is a
        > programming problem with your device and it may have to be
        > reprogrammed. If it does list this these values, the most likely
        > problem it may be that the drivers have been installed improperly and it
        > may be necessary to uninstall them. There is a driver uninstall program
        > that came with the USB drivers when you downloaded them that should be
        > able to take care of this for you. Anyway, let me know how you make out
        > with the USBView program and we can go from there.
        >
        > John Hansen W2FS
        > Coastal ChipWorks
        >

        John,

        Using the usbview.exe program reading my module VID=0X0403, PID=0XEBE0.

        With this information I modified the FTDIBUS.INF and FTDIPORT.INF
        files. Uninstalled the old drivers, rebooted, and installed new
        drivers for TNC-X w/USB module. Driver installation was successful.

        Preliminary test with UI-View32 with comport 5 as default, program
        booted up, recognized comport 5, and then transmitted (no radio hooked
        up, Green (TX) LED flashed). Set "Beacon Intervals" for fixed station
        at 1 minute. Program has xmitted several times so far without
        incident. Will update with further info when I go mobile. This is
        when it usually carps out.

        Device Manager shows Ports (COM&LPT) = USB Serial Port(Com5).

        Following are the modification for my USB module.

        FTDIBUS.INF:

        [FtdiHw]
        %USB\VID_0403&PID_EBE0.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_EBE0
        %USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6001
        %USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6010&MI_00
        %USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6010&MI_01

        [FtdiHw.NTamd64]
        %USB\VID_0403&PID_EBE0.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_EBE0
        %USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6001
        %USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6010&MI_00
        %USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6010&MI_01

        [Strings]
        Ftdi="FTDI"
        DESC="CDM Driver Package"
        DriversDisk="FTDI USB Drivers Disk"
        USB\VID_0403&PID_EBE0.DeviceDesc="USB Serial Converter"
        USB\VID_0403&PID_6001.DeviceDesc="USB Serial Converter"
        USB\VID_0403&PID_6010&MI_00.DeviceDesc="USB Serial Converter A"
        USB\VID_0403&PID_6010&MI_01.DeviceDesc="USB Serial Converter B"
        SvcDesc="USB Serial Converter Driver"
        ClassName="USB"


        FTDIPORT.INF:

        [FtdiHw]
        %VID_0403&PID_EBE0.DeviceDesc%=FtdiPort232.NT,FTDIBUS\COMPORT&VID_0403&PID_EBE0
        %VID_0403&PID_6001.DeviceDesc%=FtdiPort232.NT,FTDIBUS\COMPORT&VID_0403&PID_6001
        %VID_0403&PID_6010.DeviceDesc%=FtdiPort2232.NT,FTDIBUS\COMPORT&VID_0403&PID_6010

        [FtdiHw.NTamd64]
        %VID_0403&PID_EBE0.DeviceDesc%=FtdiPort232.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_EBE0
        %VID_0403&PID_6001.DeviceDesc%=FtdiPort232.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_6001
        %VID_0403&PID_6010.DeviceDesc%=FtdiPort2232.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_6010

        ;---------------------------------------------------------------;

        [Strings]
        FTDI="FTDI"
        DESC="CDM Driver Package"
        DriversDisk="FTDI USB Drivers Disk"
        PortsClassName = "Ports (COM & LPT)"
        VID_0403&PID_EBE0.DeviceDesc="USB Serial Port"
        VID_0403&PID_6001.DeviceDesc="USB Serial Port"
        VID_0403&PID_6010.DeviceDesc="USB Serial Port"
        SvcDesc="USB Serial Port Driver"
        SerEnum.SvcDesc="Serenum Filter Driver"


        The information above can be cut & pasted into the 2 .INF files
        providing your module shows PID=0XEBE0 and VID=0X0403. However, if
        the PID & VID are different use the last 4 alphanumeric characters
        accordingly into the 2 .INF files. If the PID=6001 or 6010 no
        modifications are necessary.

        Ed, KF4CHG
      • John Hansen
        Yes, that should do it Ed. I have a set a drivers that have those settings that I send people when they run into this problem. John W2FS
        Message 3 of 13 , Sep 30, 2008
        • 0 Attachment
          Yes, that should do it Ed. I have a set a drivers that have those
          settings that I send people when they run into this problem.

          John W2FS

          Ed L Locklear wrote:
          >
          > --- In tnc-x@yahoogroups.com <mailto:tnc-x%40yahoogroups.com>, John
          > Hansen <john@...> wrote:
          > >
          > > The first step, I think is to make sure the product ID and vendor ID on
          > > the USB module haven't somehow become changed or corrupted. Go to this
          > > page:
          > >
          > > http://www.ftdichip.com/Resources/Utilities.htm
          > <http://www.ftdichip.com/Resources/Utilities.htm>
          > >
          > > and download the USBView program. Plug in the TNC-X and run the USBView
          > > program and hopefully you'll see something listed that looks like "USB
          > > Serial Converter" listed on the left side of the screen. If you then
          > > click it, on the right side of the screen you'll see a device
          > > description for that device. Under ipVendor it should say 0x0402 and
          > > under idProduct it should say 0x6001. If it doesn't, there is a
          > > programming problem with your device and it may have to be
          > > reprogrammed. If it does list this these values, the most likely
          > > problem it may be that the drivers have been installed improperly and it
          > > may be necessary to uninstall them. There is a driver uninstall program
          > > that came with the USB drivers when you downloaded them that should be
          > > able to take care of this for you. Anyway, let me know how you make out
          > > with the USBView program and we can go from there.
          > >
          > > John Hansen W2FS
          > > Coastal ChipWorks
          > >
          >
          > John,
          >
          > Using the usbview.exe program reading my module VID=0X0403, PID=0XEBE0.
          >
          > With this information I modified the FTDIBUS.INF and FTDIPORT.INF
          > files. Uninstalled the old drivers, rebooted, and installed new
          > drivers for TNC-X w/USB module. Driver installation was successful.
          >
          > Preliminary test with UI-View32 with comport 5 as default, program
          > booted up, recognized comport 5, and then transmitted (no radio hooked
          > up, Green (TX) LED flashed). Set "Beacon Intervals" for fixed station
          > at 1 minute. Program has xmitted several times so far without
          > incident. Will update with further info when I go mobile. This is
          > when it usually carps out.
          >
          > Device Manager shows Ports (COM&LPT) = USB Serial Port(Com5).
          >
          > Following are the modification for my USB module.
          >
          > FTDIBUS.INF:
          >
          > [FtdiHw]
          > %USB\VID_0403&PID_EBE0.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_EBE0
          > %USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6001
          > %USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6010&MI_00
          > %USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6010&MI_01
          >
          > [FtdiHw.NTamd64]
          > %USB\VID_0403&PID_EBE0.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_EBE0
          > %USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6001
          > %USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6010&MI_00
          > %USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6010&MI_01
          >
          > [Strings]
          > Ftdi="FTDI"
          > DESC="CDM Driver Package"
          > DriversDisk="FTDI USB Drivers Disk"
          > USB\VID_0403&PID_EBE0.DeviceDesc="USB Serial Converter"
          > USB\VID_0403&PID_6001.DeviceDesc="USB Serial Converter"
          > USB\VID_0403&PID_6010&MI_00.DeviceDesc="USB Serial Converter A"
          > USB\VID_0403&PID_6010&MI_01.DeviceDesc="USB Serial Converter B"
          > SvcDesc="USB Serial Converter Driver"
          > ClassName="USB"
          >
          > FTDIPORT.INF:
          >
          > [FtdiHw]
          > %VID_0403&PID_EBE0.DeviceDesc%=FtdiPort232.NT,FTDIBUS\COMPORT&VID_0403&PID_EBE0
          > %VID_0403&PID_6001.DeviceDesc%=FtdiPort232.NT,FTDIBUS\COMPORT&VID_0403&PID_6001
          > %VID_0403&PID_6010.DeviceDesc%=FtdiPort2232.NT,FTDIBUS\COMPORT&VID_0403&PID_6010
          >
          > [FtdiHw.NTamd64]
          > %VID_0403&PID_EBE0.DeviceDesc%=FtdiPort232.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_EBE0
          > %VID_0403&PID_6001.DeviceDesc%=FtdiPort232.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_6001
          > %VID_0403&PID_6010.DeviceDesc%=FtdiPort2232.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_6010
          >
          > ;----------------------------------------------------------;
          >
          > [Strings]
          > FTDI="FTDI"
          > DESC="CDM Driver Package"
          > DriversDisk="FTDI USB Drivers Disk"
          > PortsClassName = "Ports (COM & LPT)"
          > VID_0403&PID_EBE0.DeviceDesc="USB Serial Port"
          > VID_0403&PID_6001.DeviceDesc="USB Serial Port"
          > VID_0403&PID_6010.DeviceDesc="USB Serial Port"
          > SvcDesc="USB Serial Port Driver"
          > SerEnum.SvcDesc="Serenum Filter Driver"
          >
          > The information above can be cut & pasted into the 2 .INF files
          > providing your module shows PID=0XEBE0 and VID=0X0403. However, if
          > the PID & VID are different use the last 4 alphanumeric characters
          > accordingly into the 2 .INF files. If the PID=6001 or 6010 no
          > modifications are necessary.
          >
          > Ed, KF4CHG
          >
          >
        Your message has been successfully submitted and would be delivered to recipients shortly.