Profilux 4e Firmware Update Problem

[Bootleg]

I have been attempting to update the firmware on my P4e, and cannot figure out the USBVCOM. I watched the video on GHL's channel titled: USBVCOM Manual Driver Install (How-to) but when I get to the part at 0:32, I do not see any "unknown device". Screen shot below.

Has anyone run in to this issue? I think the USBVCOM port number is needed for the firmware update to work.

Thanks!

 

[windemerejack]

follow the following video from start to finish and you will update your p4e

 

[Bootleg]

follow the following video from start to finish and you will update your p4e

All good until 2:23 when there is no USBVCOM on the device manager...

 

[Member No 1]

All good until 2:23 when there is no USBVCOM on the device manager...

Unless I'm seeing things, from the screen shot in your OP, isn't that the USBVCOM set to Comm4?

 

[Bootleg]

A bit hard to see, but the how to video shows the GHL Virtual Communications Port and USBVCOM as separate items, and requires the port number for the USBVCOM for the firmware update...

 

[windemerejack]

Have you updated gcc to the latest firmware before you started?

 

[windemerejack]

You need V1.1.3.2

 

[Bootleg]

I have V1.1.3.1 installed. Isn't V1.1.3.2 the beta version?

 

[windemerejack]

Its the latest version, its the one you want.
https://www.reef2reef.com/threads/n...ncreased-dosing-pump-support-and-more.700531/

 

[Bootleg]

Installed GCC V1.1.3.2 and manually installed USBVCOM but getting an error "This device cannot start. (Code 10)". In theory I could proceed with the firmware update designating COM5 for the USBVCOM but I am concerned with the error message that the update will go sideways.

 

[Vinny@GHLUSA Verified Sponsor]

This usually happens if the cable is not fully inserted in either the PC port or P4 port. It can also happen if any end of the USB connector gets salt stains or corrosion on it.

If neither are the case, then restart the P4, remove the USB cable, re-insert the USB cable and try again.

 

[Bootleg]

Tried all of the above, no changes. I can't see it being the cable since there is no communication issue with the P4 using GCC and GHL Virtual Communications Port shows on COM4 as working. It is specifically the USBVCOM (COM5) with the error. Keep in mind I had to go through a work around to install the USBVCOM driver, the "unknown device" never appears on Device Manager.

 

[SuncrestReef]

I don’t know if this will help or not, but the symptoms you’re describing sound exactly like a problem I once had with a different Windows device driver. The solution for me was to boot Windows in a special mode where it allows unsigned drivers to operate. It might be worth a shot to try this. See https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/ for instructions.

 

[Ditto]

rerun the setup tool, this time when you do it right click on it and run as administrator. It going to ask if you want to repair, say repair.

After the installation is completed connect the P4 and reboot the computer.

 

[Bootleg]

rerun the setup tool, this time when you do it right click on it and run as administrator. It going to ask if you want to repair, say repair.

After the installation is completed connect the P4 and reboot the computer.

Which setup tool are you referring to?

 

[Ditto]

The software installation.