PCLink and Firmware 6.19 Released!

[TechDave]

This went up late last week: PC Link Downloads | Link Engine Management

Release Notes: https://www.linkecu.com/pclink/Link Engine Management PC Link G4X Updates 26112020.pdf

Known issue with the drivers, see here: https://forums.linkecu.com/topic/13145-ftd2xxdll-is-missing/

[SimonSTI]

Nice list of upgrade! It's funny I just disable the fuel overrun after hours of investigation on why my blip on downshift did not work, works like a charm now, but I'll be able to enable it again with this update. Will have to wait until spring to test that out, it's winter here.

[zaihas.chan]

Need a solution to FTD2XX.DLLis missing issue without real hardware connected. I usually open my file in a desktop PC when im at home doing logs reviews.

[TechDave]

35 minutes ago, zaihas80 said:

Need a solution to FTD2XX.DLLis missing issue without real hardware connected. I usually open my file in a desktop PC when im at home doing logs reviews.

You only have to plug in a G4X ECU, it does not need to be powered.

[zaihas.chan]

thanks dave. that will do. Thanks for the help!

[Rozsko]

Thanks guys. Nice list of changes. Keep them coming.

[Paul Dare]

Hello guys,

I have followed the above advice for the .DLL issue, and it is still not working for me. Any further advice?

[Adamw]

Have you plugged an ecu into the laptop yet?

[Nathan M]

Hey guys,

Im having the exact issue with the drivers. I have tried using the above fix but the ecu is not showing up on device manager for me to uninstall the old drivers. 

[dx4picco]

same boat for me, I tried installing the pclink g4x on a linx tablet, but I'm getting the dll issue too. I plugged the ecu in (that works great on the computer) and the ecu doesn't pop up in the device manager, so I cannot delete the current driver if there is one. also a brand new win10 install. any clue on the steps to get it working?

[Adamw]

All you need to do is plug in a ecu.  If it is not showing up in device manager under USB devices when plugged in then I would be suspicious your OTG cable is not working.

[dx4picco]

I have plugged, a mouse, a usb key and a keyboard to verify that its working, and that exact cable did work in the past on another linx trablet that runs on a g4+ car as display

[Adamw]

With the ecu plugged in, do you have anything in device manager in the US Bus controllers like below?

[dx4picco]

No, pluging the ECU doesn't trigger anything on the tablet. 

Pluging a USB key triggers a USB mass storage and a mouse gives PS/2 mouse in that list. 

[Adamw]

Ok, that seems odd.  You might have to use 6.18 for now until our engineers are back from holiday.  I suggest you email [email protected] so they can get a ticket in the system and escalate it to engineering if they cant help.  

[Nathan M]

Same thing as dx4picco.  Brand new laptop and nothing shows up. Even the 6.18 doesn’t work. The only thing that works is a 2 year old laptop with a much older windows 10 build. 

[Adamw]

4 hours ago, Nathan M said:

Same thing as dx4picco.  Brand new laptop and nothing shows up. Even the 6.18 doesn’t work. The only thing that works is a 2 year old laptop with a much older windows 10 build. 

6.18 doesnt even use the direct USB driver.  Do you hear the windows ding dong when you connect the USB cable?  What ECU do you have?  Can you give us a screen shot of windows device manager comport section with the ecu plugged in.

[Mattias Sandgren]

I'm running 6.19.99 on my tuning laptop and remember this was an issue for me already back in whatever version was the latest in August 2020. 

Graphics and windows are not scaled and sized properly.  Examples are attached.

The large screenshot is where the log list doesn't show the last two rows, can't reach them. Not as irritating as the too small request windows.

It's a Lenovo X1 laptop running the latest drivers in Windows 10. Can I supply any information that could help?

[Electredge]

Windows 10 uses a stupid font scalar... open up display settings you will see the font scalar most likely reads 200%... lower it closer to 100-150 and it should fix it

[Nathan M]

On 1/1/2021 at 1:33 AM, Adamw said:

6.18 doesnt even use the direct USB driver.  Do you hear the windows ding dong when you connect the USB cable?  What ECU do you have?  Can you give us a screen shot of windows device manager comport section with the ecu plugged in.

Sorry it took so long to get back to you. There is no usb connection sound. And I know the usb ports work cause I can connect to the Link Aim dash I have. I have the G4x Monsoon. I can get you a screen shot but it dosent show up at all. 

[Nathan M]

here is the screen shot. 

[Adamw]

What type of laptop is it?  Does it have normal USB ports or are you using some type of adapter?  Are you using the cable that came with the ecu?  

[Nathan M]

25 minutes ago, Adamw said:

What type of laptop is it?  Does it have normal USB ports or are you using some type of adapter?  Are you using the cable that came with the ecu?  

Its a hp AMD Ryzen cpu laptop that's about 6 months old. It does have normal USB ports and no I'm not using any adapter and I'm using the cable that came with the ecu. I would really like to switch to this newer laptop as its MUCH faster then the one that can connect. That one like I said is using Windows 10 also but about 2 years old Windows 10. The laptop itself is 7+ years old. So I have no idea. It seems to me that something is up with newer Windows 10 operating systems. Cause unlike the other threads also I've had the older laptop connected for 30+ min without it discounting. Its never randomly disconnected.   

[Nathan M]

And I've also used a 3rd laptop that was about the same age as my newer run and it does the same thing. So I don't know if it has to do with like the fire wall or permissions. I also took a screen shoot of how the Link Aim street dash comes up in the devise manager and it shows up in a completely different spot.   

[Nathan M]

Any idea yet? I’ve tried a lot of different things. Try redownloading pc link well the ecu is plugged in. Deleted and re-installed the usb drivers on the computer. Factory reset on the laptop. Bios update. Setting changes. Nothing.