June 2016 Release Candidate 2

[Blacky]

a "touch calc_pids.txt" from bash crated a empty file and that seems to do the trick Is that file missing in the installer? Does it contain important data?

That file contains user defined calculated PIDs. It won't cause any problems if it is empty. However, the reason that it is missing might cause other problems.

EFILive stores the names of the folders in which all the configuration files are stored in the registry here:
\\HKEY_CURRENT_USER\Software\EFILive\V7.5\Properti es\Dir
You may need to manually change those folder names to match where the files were actually installed (My Documents\EFILive\V7,5\...).

Regards
Paul

[EspenT]

That file contains user defined calculated PIDs. It won't cause any problems if it is empty. However, the reason that it is missing might cause other problems.

EFILive stores the names of the folders in which all the configuration files are stored in the registry here:
\\HKEY_CURRENT_USER\Software\EFILive\V7.5\Properti es\Dir
You may need to manually change those folder names to match where the files were actually installed (My Documents\EFILive\V7,5\...).

Regards
Paul

Hi and thank you for your answer. The paths in \\HKEY_CURRENT_USER\Software\EFILive\V7.5\Properti es\Dir appears to be correct. Also all other files where created correctly by the installer

[vortecfcar]

Error report during .cax usage on a custom axis definition. Even though I've adjusted my settings I continue to get an error. The .cax simply makes editable one of the axis in an existing efilive defined table.



Nick

[Taz]

Only one cax exclusion - that's not too bad. I get a dozen plus cax exclusions happen on both E67 and T43 operating systems.

[Highlander]

custom axis definition? how did you manage to change those?

[joecar]

Error report during .cax usage on a custom axis definition. Even though I've adjusted my settings I continue to get an error. The .cax simply makes editable one of the axis in an existing efilive defined table.

Is it because the cax overlaps an existing table (rather than the OS or other cax definitions)...?

[vortecfcar]

I assume, yes joecar.

The cax defines a column or row used in an existing efilive table.

[Blacky]

Error report during .cax usage on a custom axis definition. Even though I've adjusted my settings I continue to get an error. The .cax simply makes editable one of the axis in an existing efilive defined table.

Nick

Can you send me the definition for that calibration? I'll check which EFILive cal it is overlapping and why.
Send to paul@efilive.com

Regards
Paul

[vortecfcar]

Email sent

[Tre-Cool]

Can i add a feature request to enhance the program either in 7.5 or for v8?

Currently in the scanner properties you can set a default pid or dashboard layout.

What i think would be a handy thing to add would be to have a Default Pid file selection based on controller & if the auto transmission selection box is selected on the ecu connection screen it will load an alternative (auto) pid. Limit it to 4 or 5 controllers (if it means less coding)

To save you from adding in every controller currently supported in efilive in the above screen, create a new tab window where you tick or select what controllers you want to be enabled for the above screen.

Does this sound like a good idea?