FATAL_ERROR in 0.9.17

[jrhall]

When I run MegaTunix (Mac OS X) using version 0.9.17 I get the following debug messages:

FATAL_ERROR: direct_lookup_data, table "" is null



Has anyone else seen this? Everything else appears to work fine.
Thanks,
Joel

[djandruczyk]

When I run MegaTunix (Mac OS X) using version 0.9.17 I get the following debug messages:

FATAL_ERROR: direct_lookup_data, table "" is null



Has anyone else seen this? Everything else appears to work fine.
Thanks,
Joel

What were you doing to get it to do that? What ECU firmware? can you provide steps to reproduce it?
That eror is indicative of a lookuptable problem, hence it could be a typo in a interrogation profile, or a missing lookuptable file.

[jrhall]

I am running 029y4 and I fire it up on the command line by typing "megatunix"
It then spews out via stdout||stderr the FATAL_ERROR message over and over again.
This is before I even attempt to use the interface. Lmk if I can provide any other helpful info.
Even though it spews this message I continue to use it with no obvious problems.
Joel

[djandruczyk]

I am running 029y4 and I fire it up on the command line by typing "megatunix"
It then spews out via stdout||stderr the FATAL_ERROR message over and over again.
This is before I even attempt to use the interface. Lmk if I can provide any other helpful info.
Even though it spews this message I continue to use it with no obvious problems.
Joel

I tried the release here, and I can't replciate your issue. Did you set any nonstandard lookuptables? or do you have any private interrogation files in ~/.MegaTunix/Interrogator/Profiles that are overriding the default ones? The eror indicates a lookuptable is missing/blank, and a realtime value that depends upon that is not getting converted correctly (i.e. temperature, map, AFR, lambda, etc) and thus one of your gauges is probably off. Its not critical, but can cause datalogs that are less useful, and other anomalies making tuning harder.

[jrhall]

I don't use any non-standard look-up tables and I blew away my ".Megatunix" directory and all the files under
"/usr/share/local/MegTunix" and did a "make install" again from my build to get a clean install. The error still occurs. I am using
a LC-1 wideband and 4bar map if this helps as well. I am now going to try using the dtrace tools on Mac OS X to see if I can figure out which file it is trying to read. Any other suggestions are welcome.
Joel

[djandruczyk]

I don't use any non-standard look-up tables and I blew away my ".Megatunix" directory and all the files under
"/usr/share/local/MegTunix" and did a "make install" again from my build to get a clean install. The error still occurs. I am using
a LC-1 wideband and 4bar map if this helps as well. I am now going to try using the dtrace tools on Mac OS X to see if I can figure out which file it is trying to read. Any other suggestions are welcome.
Joel

4 bar sensor is the issue. Hence why I needed ALL the information. I have replciated it and am working on a fix.

[djandruczyk]

code is fixed in CVS in the PRE_0_9_18-branch. I had previously failed to check if lookuptable is not defined during a vector processing statement, which led to the value being set to a blank string, hence the errors your saw. The only artifact of that is the errors you saw, the values should have been correct in the gauges and in the logs.

[jrhall]

Thanks for the fix. Yes, you are correct that MegaTunix behaved normally even though I saw the message in the debug.