-
USB Connection
ProfiLux 3.1T; FW 6.26; S/N: 1605111020
GCC 1.0.84
Installed both FTDI and Prolific USB drivers and I can't connect to the aquarium computer with the supplied USB cable.
I would like to update to F/W 6.27 because I cannot use the Mitras lightbar and hope this update fixes it.
What can I do to fix the USB connection ?
-
When you have the USB cable connected to your PC and P3.1, what do you see in device manager COM Ports/LPT?
Unknown device?
-
Unknown USB Device (Device Descriptor Request Failed)
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Forgot to mention it's windows 10
-
Uninstall the drivers you installed earlier. You only need to install the driver found in the GCC folder.
Here's how to get to it:
1. Go to C:
2. Select Program Files (x86)
3. Select GHL Control Center_V1084 *Current version of GCC*
4. Select Driver
5. Select dpinst_x64 or dpinst_x86
The necessary driver for connecting to the ProfiLux will begin downloading.
-
[solved]
Thanks,
That did the trick; didn't see it in the manual though!
-
Hi,
I have the same problem. I tried to install driver from Center_V1085 dir but it doesnt help. Windows 10 complains about unknown USB device. Any idea what's wrong?
-
aseppa, when you have the USB cable connected to your PC and ProfiLux, what do you see in your device manager screen? Look at Ports(COM & LPT).
-
I see nothing there. In 'Universal Serial Bus controllers' I see Unknown 'USB device (Device Description Request Failed)'.
I've tried usb connection with my laptop and desktop. In both cases the same thing happends.
-
If Ports (COM & LPT) is not listed at all in device manager, that means the PC is not detecting anything connected to the USB port on the PC. The ProfiLux driver will only show up in COM & LPT.
Please use another USB port and not any USB ports on a hub.
-
I tried different ports with same result. Windows is complaining about unrecognized usb device.
My goal is to update the latest firmware and i guest using tcp/ip that's not possible?