I assume that if i install GWv4 that I'll still be able to communicate with all my previous cal files and ECU's?? You should be able to (it is designed to do so). Also I assume that my existing dongle and lead will still work with the newer software?? Yes it will - the upgrade is free of charge. So...

Hi there

I can confirm this happens in GWv3.
It doesn't occur if you use GWv4 - are you able to use this instead?

Best Regards
Pete Bannister

I've tested this on the bench and can connect successfully with GWv4. Please try setting up the port explicitly from the connection settings dialog. Go to: ECU > Connection Settings.... Click the 'advanced' tab and pick 'COM Port' from the port selection box. Select '9600' as the baud rate. Click 'o...

Hi there, A couple of things to try: * Click 'connect' in GW when there is no power to the ECU, and then power up the ECU. This can help avoid the ECU going into telemetry stream mode. * Check that there is nothing interfering on the serial bus (e.g. another controller that is outputting data such a...

OK, its fairly simple: * The dongle has absolutely nothing to do with ECU security. Perhaps there has been a misunderstanding here. * AEM Pro does not require a dongle. * It is not possible to add a security option to AEM ECU's by modifying GW or AEM Pro. The security is implemented in the firmware....

I've hit this wall before and I can assure you it isn't illegal to run debuggers or kernel-mode drivers on my machine that allow me to view everything (in terms of processes, memory,etc) on my machine. What would be illegal is to modify the binaries themselves and hand 'em out for cost/charge, howe...

Here's a pre-release of v3.20r38. This will be properly released after it has undergone more in-house testing.

This just contains the updated files and does not have an installer. To use it, copy the files to the folder that GWv3 is installed in (e.g. "program files/gems/gwv3").

I'll PM you a pre-release of GWv3 (3.20r36) that fixes the issue.

Ok, I've made it happen with S2.79. I think it is an issue with loading the Gin file (I've got a slightly different S2.80 that I'm using here that doesn't appear to have the issue). I'll look into it now and see if I can come up with a resolution for you (either a bug fix to GWv3 or a new GIN file).

I've tried setting up a new calibration for Lancer8 S2.80 and cannot reproduce the problem. The Idle Spark table graph tooks the same in 3.20r21, 3.20r34 and 3.20r35 (the latest release). All display negative numbers of the same scale in the Y axis on my computer. Please could you PM me a calibratio...