Jamie, what does dmesg output after you plug in the device in Linux?
you should be able to use the ftdi fixer (not by ftdi, but by some linux guys) to set the pid and vid.
the key is to have only one dongle plugged in and refer to it by /dev/ttyUSB0. it will then set the vid and pid for you if you give it both arguments to the CLI.
sudo ./ft232r_prog --old-pid 0x0000 --new-pid 0x6001
you don't refer to it by ttyUSB0 in mark's program (that's the one I was thinking of).
that's why I said, make sure only ONE ftdi dongle is on your system. his app will find it and set its pid and vid. that's why you don't give /dev/ttyUSB0 on the command line. it would have been sensible to do that, but he makes you have only 1 connected and if he finds it, he writes to it.
can you omit the 'old' stuff and just feed it the new vid and pid?
maybe even try setting just one at a time?
ftdi_init(&ftdi);
atexit(&do_deinit);
memset(&ee, 0, sizeof(ee));
ee.old_vid = 0x0403;; /* default; override with --old_vid arg */
ee.old_pid = 0x6001; /* default; override with --old_pid arg */
process_args(argc, argv, &ee); /* handle --help and --old-* args */
if (ftdi_usb_open_desc(&ftdi, ee.old_vid, ee.old_pid, NULL, ee.old_serno)) {
fprintf(stderr, "ftdi_usb_open() failed for %04x:%04x:%s %s\n",
ee.old_vid, ee.old_pid, ee.old_serno ? ee.old_serno : "", ftdi_get_error_string(&ftdi));
exit(ENODEV);
}
atexit(&do_close);
maybe your device is just plain BAD (?)
-----Original Message-----
From: Mark Lord
Sent: Thursday, April 23, 2015 6:43 PM
To: Jamie M.
Subject: Re: FTDI chip unbricking, with vid 0000 AND pid 0000 plz help!
The device has to show up in "lsusb" for anything on Linux to work with it.
So, do "lsusb" without it plugged in, then plug it in (wait a few secs)
and do "lsusb" again, and compare. Anything new show up?
--
Mark Lord
Real-Time Remedies Inc.
Comment by Nuno Gonçalves: "The driver (2.12) is back on windows update. Clones are getting bricked again."
Any confirmations?
NEW LabVIEW Driver for DE-6000 is available for collecting data from the DE-6000. The driver is written in LabVIEW 2013 and requires the optional DE-6000-DTK IR-USB interface adapter.
Everything about the "DE-6000" is dodgy to me.
However, to be fair to IET, the LabVIEW driver is nothing whatsoever to do with the FTDI driver. Think of it more like the front end graphical interface. Does the DE-6000 include this driver, hence the huge markup, or is it another "request a quote" add on?
However, to be fair to IET, the LabVIEW driver is nothing whatsoever to do with the FTDI driver. Think of it more like the front end graphical interface. Does the DE-6000 include this driver, hence the huge markup, or is it another "request a quote" add on?
Thanks to a member here and the group he belongs to I managed to get the protocol details for the DE5000 with the express mission of creating my own de5000 labview drivers. Whenever I get around to finishing it I wonder what would happen if I tired release them into labviews online driver repository
maybe your device is just plain BAD (?)