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

Re: Issue starting dongle / dvtool

Expand Messages
  • rdrogo
    As a followup, I ve now also tried: 1) Using the DVToolTest.exe file instead of DVTool.exe. If I do that, I still get the not found error, and get the
    Message 1 of 11 , Jan 21, 2013
    • 0 Attachment
      As a followup, I've now also tried:

      1) Using the DVToolTest.exe file instead of DVTool.exe. If I do that, I still get the not found error, and get the following information in the console:
      Searching 1 FTDI serial devices
      Found FTDI device at index 0 location 530 serial description USB <-> Serial
      Skipping FTDI Device USB <-> Serial
      Found 0 FTDI device(s)

      2) I gave the dongle to a friend to try on his system, and he reported the same behavior as I described above.


      Thanks,
      Ryan
      KI6ZLC
    • vk4tux
      From Win8 the DVTool not found also happens and just needs a retry, then; Qt: Untested Windows version 6.2 detected! DVTool version 2.0beta5 Restored
      Message 2 of 11 , Jan 21, 2013
      • 0 Attachment
        From Win8 the DVTool not found also happens and just needs a retry, then;


        Qt: Untested Windows version 6.2 detected!
        DVTool version 2.0beta5
        Restored parameters:
        UserCallsign=KA8SCP D
        UserMessage=Adrian Win8
        DVDevice=COM10
        AudioInDevice=Microphone (4- Logitech USB Hea
        AudioOutDevice=Speakers (4- Logitech USB Heads
        Gateway=WB1GOF
        Module=C
        FavoriteGW=N
        PTTLock=Y
        AutoReconnect=N
        Style=Windows
        Colors=Default
        FavoriteGWList=
        O/S: Windows UNKNOWN
        name=Microphone (SoundMAX Integrated
        channels=1 2
        frequencies=8000 11025 22050 44100 48000 96000
        byte orders=1
        codecs=audio/pcm
        samplesizes=8 16
        sampletypes=1 2

        name=Line In (SoundMAX Integrated Di
        channels=1 2
        frequencies=8000 11025 22050 44100 48000 96000
        byte orders=1
        codecs=audio/pcm
        samplesizes=8 16
        sampletypes=1 2

        name=default
        channels=1 2
        frequencies=8000 11025 22050 44100 48000 96000
        byte orders=1
        codecs=audio/pcm
        samplesizes=8 16
        sampletypes=1 2

        name=Speakers (SoundMAX Integrated D
        channels=1 2 4 6 8
        frequencies=8000 11025 22050 44100 48000 96000
        byte orders=1
        codecs=audio/pcm
        samplesizes=8 16
        sampletypes=1 2

        name=default
        channels=1 2 4 6 8
        frequencies=8000 11025 22050 44100 48000 96000
        byte orders=1
        codecs=audio/pcm
        samplesizes=8 16
        sampletypes=1 2

        Input devices: Microphone (SoundMAX Integrated Line In (SoundMAX Integrated Di d
        efault
        Output devices: Speakers (SoundMAX Integrated D default
        FTDI serial device on VCP port COM10
        FTDI serial device COM10 valid
        Added audio input device: Microphone (SoundMAX Integrated
        Audio input device changed to Microphone (SoundMAX Integrated
        Added audio input device: Line In (SoundMAX Integrated Di
        Added audio input device: default
        Added audio output device: Speakers (SoundMAX Integrated D
        Audio output device changed to Speakers (SoundMAX Integrated D
        Added audio output device: default
        Style changed to Windows
        Found 1 FTDI device(s)
        Available builtin palettes:
        BlackOnMellon
        BlackOnPink
        BlackOnSeaMist
        Default
        GoldOnBlack
        WhiteOnDarkRed
        WhiteOnNavyBlue
        WhiteOnPurpleBlue
        WhiteOnSteelBlue
        WhiteOnTeal
        Available external palettes:
        Loaded palette :/dvtoolresources/palettes/BlackOnMellon.qpalette
        Loaded palette :/dvtoolresources/palettes/Default.qpalette
        Module changed to A
        Module changed from A to C

        Driver info; FTDI ver 2.8.24.0 driver date 10/4/2010 < Au format

        Driver Management has concluded the process to add Service FTSER2K for Device Instance ID FTDIBUS\VID_0403+PID_6001+A9004UNMA\0000 with the following status: 0.

        Driver Management has concluded the process to add Service Serenum for Device Instance ID FTDIBUS\VID_0403+PID_6001+A9004UNMA\0000 with the following status: 0.

        Driver Management concluded the process to install driver ftdiport.inf_x86_82e6432d4f9259e1\ftdiport.inf for Device Instance ID FTDIBUS\VID_0403+PID_6001+A9004UNMA\0000 with the following status: 0x0.


        vk4tux
      • vk2ah
        Hi, Try running Dv tool2.beta 5. This may help you out. Regards VK2AH
        Message 3 of 11 , Jan 21, 2013
        • 0 Attachment
          Hi, Try running Dv tool2.beta 5.
          This may help you out. Regards VK2AH

          --- In DVDongle@yahoogroups.com, Ryan Drogo wrote:
          >
          > Hi All,
          >
          > I've been having a heck of a time getting the DV Dongle running. Perhaps one of you can pinpoint where I've gone wrong, or what I've not tried.
          >
          > Here's the rundown of what I've done thus far:
          >
          > Systems tried on:
          > Netbook - Atom 1.2GHz processor, 2GB ram, Win 7 Ultimate 32-bit (severely underpowered machine, but tried anyhow)
          > Laptop - Core i5 dual-core w/HT @ 2.5GHz, 4GB ram, Win 7 Enterprise 64-bit
          > Workstation - 2x Xeon quad-core @ 2GHz, 32GB ram, Win 2008 R2
          >
          > I've had the same behavior on all the above systems. Here's the steps I've done, in order:
          >
          > Plug-in the dongle using a usb cable I had in the house (there was none in the box when I got home from HRO). 
          > (Corollary: I've tried 4 different cables, all marked as usb2.0 rated, A to 5-pin mini B)
          >
          > Each system successfully located the drivers on windows update, and installed with no issues.
          > Unplug dongle
          > Rebooted system
          > plugged in dongle, green light pulses slowly
          >
          > Load up the DvTool posted on the dvdongle.com website (currently the java based 1.x series).
          >
          > The systems had both jre 6 and 7 installed
          >
          > The tool loads right up, and pressing Open loads the firmware/version information successfully from the dongle.
          >
          > An audio loopback test (no ambe, straight audio) works great. 
          > I've used both an analog connection to the systems' sound cards (typical laptop crap in the portables, and a soundblaster x-fi audio extreme pcie 
          >
          > in the workstation) and a usb headset I had lying around. 
          >
          > If I try to engage the chip, the first time around (whether I press ambe/loopback, record, or record to file) it sends a stream of 'audio output 
          >
          > buffer empty' messages. I cannot stop when record/record to file are used (it hangs). In all cases, it closes the connection on the stop button 
          >
          > with the following output: 
          > sending ambe packet len 5
          > receive watchdog timeout from localhost/127.0.0.1
          > watchdog thread exit
          > IOException receive socket closed
          > disconnected from localhost/127.0.0.1
          > Device localhost:20002 shutdown
          > Device localhost:20002 closed
          >
          > If I try to Open again and then perform the same action, or another action, it closes the socket after a couple of seconds and I have to shut 
          >
          > down the program to try again. 
          >
          > Steps I've taken to get the java version working:
          >
          > turned off windows firewall
          > turned off antivirus software
          > run java as an admin
          > set the ascpseriald.exe to run as an admin
          >
          > These all resulted in the same behavior as before.
          >
          > I then updated the VCP drivers from the ftdi website, rebooted the system, and plugged in the dongle again. The drivers updated (as evidenced by 
          >
          > the 'installing new hardware' bubble coming up again) and then the same behavior ensues.
          >
          > Here's a sample of the ascp.txt log file:
          > ascp starting
          > connect from 127.0.0.1:63816
          > facu 0/0 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > write ctrlbuf 4 20 1 0 len 4 wlen 4
          > write ctrlbuf 4 20 2 0 len 4 wlen 4
          > write ctrlbuf 5 20 4 0 len 5 wlen 5
          > pktlen   14 type 0 from ambe 0/0 worklen 34 (0e 00 01 00 44)
          > control packet from ambe 14 (0/0) -> 0e 00 01 00 44 56 20 44 6f 6e 67 6c 65 00 
          > pktlen   13 type 0 from ambe 0/0 worklen 20 (0d 00 02 00 44)
          > control packet from ambe 13 (0/0) -> 0d 00 02 00 44 56 31 30 34 30 31 36 00 
          > pktlen    7 type 0 from ambe 0/0 worklen 7 (07 00 04 00 00)
          > control packet from ambe 7 (0/0) -> 07 00 04 00 00 68 00 
          > write ctrlbuf 5 20 4 0 len 5 wlen 5
          > pktlen    7 type 0 from ambe 0/0 worklen 7 (07 00 04 00 01)
          > control packet from ambe 7 (0/0) -> 07 00 04 00 01 6f 00 
          > write ctrlbuf 5 0 18 0 len 5 wlen 5
          > pktlen    5 type 0 from ambe 0/0 worklen 58 (05 00 18 00 01)
          > control packet from ambe 5 (0/0) -> 05 00 18 00 01 
          > uncompressed buffer underrunfacu 0/1 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > compressed buffer underrunfacu 1/1 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > uncompressed buffer underrunfacu 1/2 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > compressed buffer underrunfacu 2/2 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > uncompressed buffer underrunfacu 2/3 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > compressed buffer underrunfacu 3/3 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > uncompressed buffer underrunfacu 3/4 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > compressed buffer underrunfacu 4/4 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > uncompressed buffer underrunfacu 4/5 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > compressed buffer underrunfacu 5/5 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > uncompressed buffer underrunfacu 5/6 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > compressed buffer underrunfacu 6/6 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > uncompressed buffer underrunfacu 6/7 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > compressed buffer underrunfacu 7/7 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > uncompressed buffer underrunfacu 7/8 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > compressed buffer underrunfacu 8/8 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > uncompressed buffer underrunfacu 8/9 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > compressed buffer underrunfacu 9/9 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > uncompressed buffer underrunfacu 9/10 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > compressed buffer underrunfacu 10/10 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > uncompressed buffer underrunfacu 10/11 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > compressed buffer underrunfacu 11/11 tacu 0/0 fncu 0/0 fcu 1000/0/0
          > pktlen    0 type 0 from ambe 11/11 worklen 1629 (00 00 00 00 00)
          > bad pktlen 0 (11/11)
          > 00 00 00 00 00
          >
          > So then I tried the 2.0beta5 version. On all systems, this produces the dreaded No DV Dongle found message, despite the dongle being attached and 
          >
          > the light pulsing slowly. 
          >
          > Following the advice I've found here on the boards, I've then tried:
          >
          > Simply re-installing the FTDI driver from their website
          > Running the FTDI clean utility, rebooting, re-installing FTDI site drivers
          > Running the CDMUninstaller, rebooting, re-installing FTDI site drivers
          > same as above, but re-installing the ones from windows update by just plugging in the dongle
          >
          > If I run listVCP.exe or the ftdireg.bat files I get what appears to be good output. For example, here's the current output of listvcp from the 
          >
          > laptop with the dongle plugged in: 
          >
          > >> HARDWARE\DEVICEMAP\SERIALCOMM
          > namebuf=(\Device\VCP0) namesize=12 valuebuf=(COM4) valuesize=5 ret=0
          > \Device\VCP0=COM4
          >
          > >> SYSTEM\CurrentControlSet\Enum\FTDIBUS
          > namebuf=(VID_0403+PID_6001+6&335c4957&0&2) namesize=32 ret=0
          > SYSTEM\CurrentControlSet\Enum\FTDIBUS\VID_0403+PID_6001+6&335c4957&0&2=6&335c4957&0&2
          > namebuf=(0000) namesize=4 ret=0
          > namebuf=(Device Parameters) namesize=17 ret=0
          > namebuf=(LogConf) namesize=7 ret=0
          > namebuf=(Properties) namesize=10 ret=0
          > namebuf=(Control) namesize=7 ret=0
          > namebuf=(DeviceDesc) namesize=10 valuebuf=(@...,%vid_0403&pid_6001.devicedesc%;USB Serial Port) valuesize=58 ret=0
          >
          > namebuf=(Capabilities) namesize=12 valuebuf=(É) valuesize=4 ret=0
          > namebuf=(HardwareID) namesize=10 valuebuf=(FTDIBUS\COMPORT&VID_0403&PID_6001) valuesize=35 ret=0
          > namebuf=(ContainerID) namesize=11 valuebuf=({b5d18f09-55fe-11e2-b8e1-f0def186c93b}) valuesize=39 ret=0
          > namebuf=(ConfigFlags) namesize=11 valuebuf=() valuesize=4 ret=0
          > namebuf=(ClassGUID) namesize=9 valuebuf=({4d36e978-e325-11ce-bfc1-08002be10318}) valuesize=39 ret=0
          > namebuf=(Driver) namesize=6 valuebuf=({4d36e978-e325-11ce-bfc1-08002be10318}\0001) valuesize=44 ret=0
          > namebuf=(UpperFilters) namesize=12 valuebuf=(serenum) valuesize=9 ret=0
          > namebuf=(Class) namesize=5 valuebuf=(Ports) valuesize=6 ret=0
          > namebuf=(Mfg) namesize=3 valuebuf=(@...,%ftdi%;FTDI) valuesize=23 ret=0
          > namebuf=(Service) namesize=7 valuebuf=(FTSER2K) valuesize=8 ret=0
          > namebuf=(FriendlyName) namesize=12 valuebuf=(USB Serial Port (COM4)) valuesize=23 ret=0
          >
          > >> SYSTEM\CurrentControlSet\Services\FTDIBUS\Enum
          > namebuf=(Count) namesize=5 valuebuf=(?) valuesize=4 ret=0
          > namebuf=(NextInstance) namesize=12 valuebuf=(?) valuesize=4 ret=0
          > namebuf=(0) namesize=1 valuebuf=(USB\VID_0403&PID_6001\6&335c4957&0&2) valuesize=37 ret=0
          > SYSTEM\CurrentControlSet\Enum\FTDIBUS\VID_0403+PID_6001+6&335c4957&0&2A\0000=6&335c4957&0&2
          > regopenkeyexa 3 namebuf=(SYSTEM\CurrentControlSet\Enum\FTDIBUS\VID_0403+PID_6001+6&335c4957&0&2A\0000) ret=2
          > namebuf=(NextInstance) namesize=12 valuebuf=() valuesize=4 ret=0
          >
          > I get similar output on the other systems - that is, it looks like the ports are present and properly enumerated in the registry.
          >
          > Anyone point me in the right direction of something to try next, or is there any other debug output I can provide?
          >
          > Thanks very much!
          > A D-Star Newbie
          > Ryan
          > KI6ZLC
          >
        • vk4tux
          ... He did; So then I tried the 2.0beta5 version. On all systems, this produces the dreaded No DV Dongle found message, despite the dongle being attached
          Message 4 of 11 , Jan 21, 2013
          • 0 Attachment
            --- In DVDongle@yahoogroups.com, "vk2ah" wrote:
            >
            > Hi, Try running Dv tool2.beta 5.
            > This may help you out. Regards VK2AH

            He did;

            "> So then I tried the 2.0beta5 version. On all systems, this produces the dreaded No DV Dongle found message, despite the dongle being attached and
            >
            > the light pulsing slowly.
            >
            > Following the advice I've found here on the boards, I've then tried:
            >
            "

            vk4tux
          • vk4tux
            I would be posting the DVDongle to Robin AA4RC to test. Seems like a rare FTDI chip/hardware issue. I had a rare issue with a serial number on one of mine and
            Message 5 of 11 , Jan 21, 2013
            • 0 Attachment
              I would be posting the DVDongle to Robin AA4RC to test.
              Seems like a rare FTDI chip/hardware issue. I had a rare issue with a serial number on one of mine and Robin provided guidance on reprogramming the correct FTDI serial (not DV s/n).

              good luck

              vk4tux



              --- In DVDongle@yahoogroups.com, "rdrogo" wrote:
              >
              >
              >
              > As a followup, I've now also tried:
              >
              > 1) Using the DVToolTest.exe file instead of DVTool.exe. If I do that, I still get the not found error, and get the following information in the console:
              > Searching 1 FTDI serial devices
              > Found FTDI device at index 0 location 530 serial description USB <-> Serial
              > Skipping FTDI Device USB <-> Serial
              > Found 0 FTDI device(s)
              >
              > 2) I gave the dongle to a friend to try on his system, and he reported the same behavior as I described above.
              >
              >
              > Thanks,
              > Ryan
              > KI6ZLC
              >
            • Kevin Wesolowski
              Did you use the driver package in http://www.ftdichip.com/Drivers/VCP.htm ??? Kevin KD7DFV From: rdrogo [mailto:psychohamster@yahoo.com] Sent: Monday, January
              Message 6 of 11 , Jan 21, 2013
              • 0 Attachment

                Did you use the driver package in

                http://www.ftdichip.com/Drivers/VCP.htm

                ???

                 

                Kevin

                KD7DFV

                 

                From: rdrogo [mailto:psychohamster@...]
                Sent: Monday, January 21, 2013 11:57 AM
                To: DVDongle@yahoogroups.com
                Subject: [DVDongle] Re: Issue starting dongle / dvtool

                 

                 



                As a followup, I've now also tried:

                1) Using the DVToolTest.exe file instead of DVTool.exe. If I do that, I still get the not found error, and get the following information in the console:
                Searching 1 FTDI serial devices
                Found FTDI device at index 0 location 530 serial description USB <-> Serial
                Skipping FTDI Device USB <-> Serial
                Found 0 FTDI device(s)

                2) I gave the dongle to a friend to try on his system, and he reported the same behavior as I described above.

                Thanks,
                Ryan
                KI6ZLC

              • rdrogo
                Yup, sure did.
                Message 7 of 11 , Jan 22, 2013
                • 0 Attachment
                  Yup, sure did.

                  --- In DVDongle@yahoogroups.com, "Kevin Wesolowski" wrote:
                  >
                  > Did you use the driver package in
                  >
                  > http://www.ftdichip.com/Drivers/VCP.htm
                  >
                  > ???
                  >
                  >
                  >
                  > Kevin
                  >
                  > KD7DFV
                  >
                  >
                  >
                  > From: rdrogo [mailto:psychohamster@...]
                  > Sent: Monday, January 21, 2013 11:57 AM
                  > To: DVDongle@yahoogroups.com
                  > Subject: [DVDongle] Re: Issue starting dongle / dvtool
                  >
                  >
                  >
                  >
                  >
                  >
                  >
                  > As a followup, I've now also tried:
                  >
                  > 1) Using the DVToolTest.exe file instead of DVTool.exe. If I do that, I
                  > still get the not found error, and get the following information in the
                  > console:
                  > Searching 1 FTDI serial devices
                  > Found FTDI device at index 0 location 530 serial description USB <-> Serial
                  > Skipping FTDI Device USB <-> Serial
                  > Found 0 FTDI device(s)
                  >
                  > 2) I gave the dongle to a friend to try on his system, and he reported the
                  > same behavior as I described above.
                  >
                  > Thanks,
                  > Ryan
                  > KI6ZLC
                  >
                • Woodrick, Ed
                  Ryan, Not sure what your problem is, but there s evidently something different about your environment. I ve loaded the DVTool beta on a number of computers and
                  Message 8 of 11 , Jan 22, 2013
                  • 0 Attachment

                    Ryan,

                     

                    Not sure what your problem is, but there’s evidently something different about your environment.

                     

                    I’ve loaded the DVTool beta on a number of computers and haven’t had any issues with it. Basically, my rules are:

                    ·         Make sure that the computer has Internet connectivity

                    ·         Insert DVDongle

                    ·         Wait for drivers to be downloaded and installed

                    ·         Start the DVTool software

                     

                    Look for something else that may try to talk to the chip. Anything that supports serial, GPS, mouse, etc?.

                     

                    Look in device Manager under Ports. Do you see a USB Serial Port? What com port number is it?

                     

                    And yes, I’ve run the DVDongle on Windows Vista x32 and x64, Windows 7, x32 and x64, as well as Windows 8, x32 and x64. They all work well and have been no problems for me. And I’ve also run it on an Atom Netbook with no issues.

                     

                    Ed WA4YIH

                     

                    From: DVDongle@yahoogroups.com [mailto:DVDongle@yahoogroups.com] On Behalf Of rdrogo
                    Sent: Monday, January 21, 2013 1:57 PM
                    To: DVDongle@yahoogroups.com
                    Subject: [DVDongle] Re: Issue starting dongle / dvtool

                     

                     



                    As a followup, I've now also tried:

                    1) Using the DVToolTest.exe file instead of DVTool.exe. If I do that, I still get the not found error, and get the following information in the console:
                    Searching 1 FTDI serial devices
                    Found FTDI device at index 0 location 530 serial description USB <-> Serial
                    Skipping FTDI Device USB <-> Serial
                    Found 0 FTDI device(s)

                    2) I gave the dongle to a friend to try on his system, and he reported the same behavior as I described above.

                    Thanks,
                    Ryan
                    KI6ZLC

                  • rdrogo
                    Yeah, I think that s what I m getting towards. I ve been working in a separate email thread with Robin as well, but so far no luck. I ve also now tried the
                    Message 9 of 11 , Jan 25, 2013
                    • 0 Attachment
                      Yeah, I think that's what I'm getting towards. I've been working in a separate email thread with Robin as well, but so far no luck.

                      I've also now tried the dongle on a mac (OS 10.8) and linux (CentOS) machines, with the same result in the java version (closed connection). Couldn't try 2.0 because of code signing policy on the mac and the CentOS machine doesn't have the right ABI support (it's about a year old distro).

                      --- In DVDongle@yahoogroups.com, "vk4tux" wrote:
                      >
                      > I would be posting the DVDongle to Robin AA4RC to test.
                      > Seems like a rare FTDI chip/hardware issue. I had a rare issue with a serial number on one of mine and Robin provided guidance on reprogramming the correct FTDI serial (not DV s/n).
                      >
                      > good luck
                      >
                      > vk4tux
                      >
                      >
                      >
                      > --- In DVDongle@yahoogroups.com, "rdrogo" wrote:
                      > >
                      > >
                      > >
                      > > As a followup, I've now also tried:
                      > >
                      > > 1) Using the DVToolTest.exe file instead of DVTool.exe. If I do that, I still get the not found error, and get the following information in the console:
                      > > Searching 1 FTDI serial devices
                      > > Found FTDI device at index 0 location 530 serial description USB <-> Serial
                      > > Skipping FTDI Device USB <-> Serial
                      > > Found 0 FTDI device(s)
                      > >
                      > > 2) I gave the dongle to a friend to try on his system, and he reported the same behavior as I described above.
                      > >
                      > >
                      > > Thanks,
                      > > Ryan
                      > > KI6ZLC
                      > >
                      >
                    • Adrian
                      Yeah, I think that s what I m getting towards. I ve been working in a separate email thread with Robin as well, but so far no luck. I ve also now tried the
                      Message 10 of 11 , Jan 25, 2013
                      • 0 Attachment


                          Yeah, I think that's what I'm getting towards. I've been working in a separate email thread with Robin as well, but so far no luck.

                        I've also now tried the dongle on a mac (OS 10.8) and linux (CentOS) machines, with the same result in the java version (closed connection). Couldn't try 2.0 because of code signing policy on the mac and the CentOS machine doesn't have the right ABI support (it's about a year old distro).



                        Ok on that, CentOS should be fine, I currently am using fedora 18.

                        Try run > #dmesg in terminal

                        12.482991] usbcore: registered new interface driver ftdi_sio
                        [   12.483078] usbserial: USB Serial support registered for FTDI USB Serial Device
                        [   12.483128] ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
                        [   12.483151] usb 2-1: Detected FT232RL
                        [   12.483153] usb 2-1: Number of endpoints 2
                        [   12.483155] usb 2-1: Endpoint 1 MaxPacketSize 64
                        [   12.483157] usb 2-1: Endpoint 2 MaxPacketSize 64
                        [   12.483158] usb 2-1: Setting MaxPacketSize 64
                        [   12.485786] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
                        [   12.485809] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected
                        [   12.485827] usb 3-1: Detected FT232RL
                        [   12.485829] usb 3-1: Number of endpoints 2
                        [   12.485830] usb 3-1: Endpoint 1 MaxPacketSize 64
                        [   12.485832] usb 3-1: Endpoint 2 MaxPacketSize 64
                        [   12.485834] usb 3-1: Setting MaxPacketSize 64
                        [   12.487973] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB1

                        ttyUSB0 =DV Dongle
                        ttyUSB1 = Dvap


                        I link the script executable (DVTool.sh with modified path) to usr/bin/DVTool

                        ln -s /root/Downloads/DVTool/DVTool.sh /usr/bin/DVTool

                        so;

                        [root@fedora18desk ~]# DVTool
                        DVTool version 2.0beta5
                        Restored parameters:
                          UserCallsign=VK4TUX
                          UserMessage=Adrian 
                          DVDevice=/dev/ttyUSB0
                          AudioInDevice=sysdefault:CARD=Headset
                          AudioOutDevice=sysdefault:CARD=Headset
                          Gateway=REF001
                          Module=C
                          FavoriteGW=N
                          PTTLock=N
                          AutoReconnect=N
                          Style=Cleanlooks
                          Colors=BlackOnSeaMist
                          FavoriteGWList=
                        O/S: Linux
                        name=sysdefault:CARD=Intel
                        channels=1 2 
                        frequencies=8000 11025 22050 44100 48000 
                        byte orders=1 0 
                        codecs=audio/pcm 
                        samplesizes=8 16 32 
                        sampletypes=1 2 3 

                        name=sysdefault:CARD=Headset
                        channels=1 2 
                        frequencies=8000 11025 22050 44100 48000 
                        byte orders=1 0 
                        codecs=audio/pcm 
                        samplesizes=8 16 32 
                        sampletypes=1 2 3 

                        name=default
                        channels=1 2 
                        frequencies=8000 11025 22050 44100 48000 
                        byte orders=1 0 
                        codecs=audio/pcm 
                        samplesizes=8 16 32 
                        sampletypes=1 2 3 

                        name=sysdefault:CARD=Intel
                        channels=1 2 4 6 8 
                        frequencies=8000 11025 22050 44100 48000 
                        byte orders=1 0 
                        codecs=audio/pcm 
                        samplesizes=8 16 32 
                        sampletypes=1 2 3 

                        name=sysdefault:CARD=Headset
                        channels=1 2 4 6 8 
                        frequencies=8000 11025 22050 44100 48000 
                        byte orders=1 0 
                        codecs=audio/pcm 
                        samplesizes=8 16 32 
                        sampletypes=1 2 3 

                        name=default
                        channels=1 2 4 6 8 
                        frequencies=8000 11025 22050 44100 48000 
                        byte orders=1 0 
                        codecs=audio/pcm 
                        samplesizes=8 16 32 
                        sampletypes=1 2 3 

                        Input devices: sysdefault:CARD=Intel sysdefault:CARD=Headset default 
                        Output devices: sysdefault:CARD=Intel sysdefault:CARD=Headset default 
                        FTDI serial device ttyUSB0 found (A9003R9J)
                        FTDI serial device ttyUSB1 found (A6007ELQ)
                        Module changed to A
                        Module changed from A to C
                        Added audio input device: sysdefault:CARD=Intel
                        Audio input device changed to sysdefault:CARD=Intel
                        Added audio input device: sysdefault:CARD=Headset
                        Audio input device changed to sysdefault:CARD=Headset
                        Added audio input device: default
                        Added audio output device: sysdefault:CARD=Intel
                        Audio output device changed to sysdefault:CARD=Intel
                        Added audio output device: sysdefault:CARD=Headset
                        Audio output device changed to sysdefault:CARD=Headset
                        Added audio output device: default
                        Style changed to Windows
                        Style changed to Cleanlooks
                        Found 2 FTDI device(s)
                        Available builtin palettes:
                        BlackOnMellon
                        BlackOnPink
                        BlackOnSeaMist
                        Default
                        GoldOnBlack
                        WhiteOnDarkRed
                        WhiteOnNavyBlue
                        WhiteOnPurpleBlue
                        WhiteOnSteelBlue
                        WhiteOnTeal
                        Available external palettes:
                        Test
                        Loaded palette :/dvtoolresources/palettes/BlackOnMellon.qpalette
                        Loaded palette :/dvtoolresources/palettes/BlackOnSeaMist.qpalette




                        Good Luck

                        Adrian ... vk4tux
                      Your message has been successfully submitted and would be delivered to recipients shortly.