Procal issue connecting to computer

[Epiphany]

Any resolution from FP?

Sponsored

 

[DillonC]

Any resolution from FP?

I spoke with them on the phone this morning and we didn't figure anything new out. I sent the newer screenshots of errors to them and he said he'll forward them to their engineers.

He said he should have a response by the end of the day from them.

 

[vrtical]

No issues with mine. Installed the software and did a reboot. Auto connected. I am using a Surface on Win 11 so it's only compatibility mode and works with my Forscan. Next up go pull stock.

 

[RoverDude]

I know you've tried six cables.
Just quadruple check air cable to ensure it's a USB cable that has power and data.
Your typical / common USB charger cable is only going to have the wires for power.
If the units lighting up but not connecting, that would be my first guess.

 

[DillonC]

I know you've tried six cables.
Just quadruple check air cable to ensure it's a USB cable that has power and data.
Your typical / common USB charger cable is only going to have the wires for power.
If the units lighting up but not connecting, that would be my first guess.

I actually just had the best reviewed cable on Amazon delivered so I'm going to try that out when I get to the house in a little bit.

 

[vrtical]

ok pulled my stock file then after that connecting back to the pc to do the stock file backup and get the performance tune, the COM is a bit flakey, had to reboot my pc and pull my usb dongle and reconnect to get it to reconnect the procal which it finally auto connected then went through the backup steps, pretty straight forward soo far.

 

[DillonC]

Welp I just tried with the new cable and on my surface pro for the heck of it. A few seconds after it connects I still get the "Error getting registry" pop up. After that pops up you can't go any further.

Also FP's engineer wasn't much help.

 

[Epiphany]

I see Tom Magyar's name in that email. He's the one I spoke to at FP that mentioned that he deals with this stuff everyday for 8 hours...

 

[DillonC]

I see Tom Magyar's name in that email. He's the one I spoke to at FP that mentioned that he deals with this stuff everyday for 8 hours...

Yep he's who I've been talking with. Said he's never seen these problems that I'm having.

 

[RoverDude]

Yep he's who I've been talking with. Said he's never seen these problems that I'm having.

So the new cable is connecting, pulling a serial number.
Ensure that you're in the correct compatibility mode, and try different USB ports.
Or a different computer...?
Something slightly older.

 

[DillonC]

So the new cable is connecting, pulling a serial number.
Ensure that you're in the correct compatibility mode, and try different USB ports.
Or a different computer...?
Something slightly older.

Yeah it's been pulling the serial number from the device with some of the other cables I tried too. I've tried 4 different computers now, oldest being windows 10, and always try every usb port on them.

It shouldn't require all this effort to work imo.

 

[Epiphany]

Are you able to even click on the update button?

 

[DillonC]

Are you able to even click on the update button?

Not after that "Error getting registry" pops up. When you hit "ok" everything gets grayed out, including the update button.

I can hit the update button right after I connect the device, before the error pops up, but if I do the version and serial numbers disappear and the procal software freezes until you force close it.

 

[DillonC]

Update for anyone curious:

I actually spoke with the engineer from Ford Performance on the phone while he remote into my computer.

He messed around in the procal software while I connected/disconnected the device for him. After a bit he said my device has to be faulty.

Got my shipping address and said they'd send me another one.

 

[Peter_benton]

oh crap.... i am seeing the same issues. maybe they sent me your old one!

Sponsored