Subject: Re: Installing filter-driver using filter-driver.exe
On Wed, Jun 6, 2012 at 1:19 AM, Devon Lind <devon@xxxxxxxxxxxxxxxx> wrote:
> I am working in a production environment and we are using libftdi to
> program our modules. As of now everything is working fine, but just
> taking a really long time to program our devices (approx. 45 sec)
> before we can actually start testing them. I am using C++ in Windows
> Microsoft Visual Studios .
> As of now I am using system() to open the commandline, open
> install-filter.exe, and install the filter for a specific device.
> Like I said it works fine, but once the filter driver is installed and
> the device has been programmed, the comport changes and forces me to
> disconnect and then reconnect my device in order to run the test
> Here is my function to install the filter driver and using the
> system() function.
> void install_filterdriver()
> // Install filter driver to unprogrammed module using commandline
> application install-filter.exe
> if (fileExists("C:\\install-filter.exe"))
> string commandline_string;
> commandline_string = "C:\\install-filter install
> cout << "C:\\install-filter.exe does not exist. Driver filter
> not installed." << endl;
> Installing the filter along with disconnecting and reconnecting is
> what eats up all the time. I would like to get this process to take
> around half the time it does now.
> Is there any way to do this without disconnecting and reconnecting, or
> installing the filter-driver a different way?
> Thanks in advance.
I think this is a libusb-win32 problem and not a libftdi problem.
You may want to subscribe to libusb-win32 mailing list and
I am the other admin of libusb-win32 but I am more on the
testing side and support side. I do not have a good answer for
you right now. For more difficult questions like this,
Travis (libusb-win32 main developer) may be able to give you
libusb-win32 mailing list:
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx