pgmfi.org

I have some screen shots of .csv's and map traces generated by ECUControl. Something screwy is going on.



This is a maptrace from a bin based on NG62. The engine idles darn well. However, notice the odd position of the maptrace. It's odd because as you'll see in the next screen cap, the map trace isn't in the correct position, and not reading correctly.



Look at the logged ignition advance. It's at 24.3 degrees. WTF? The timing is dead on at idle. The timing doesn't vary AT ALL when idling, which, is pretty effing awesome of TE. Also notice that the row and column are reading where it normally should, but the maptrace is definitely off.



Ok, look at this. This is an NG63 (Final 2) bin with maps copied and pasted directly from the previous NG62 bin. Negative duty cycle and timing values? I know that's wrong because the engine still idles dead on 16*BTDC.

What's going on?

FYI, this is not my car. I am helping tune a car on the West coast. This is kind of annoying. =/

Well, WTF:



I just re-re-re downloaded this file:

download/file.php?id=7702

Uninstalled all previous versions of ECU control, standalone and plugin, re-registered the plug in .dll in TE 3.2.10 and then I get version .15 showing up when I install it.

Help?

Ok, so I just un-installed EVERYTHING TE and EC related. Then I restarted and re-installed TE 2.5x, then TE 3.2.1 then installed EC x.17, then the Extra Tables plugin. Now I get 6.1.17 coming up. Strange.

How does one properly install x.17 over .15? Unregister the older version in TE then install x.17 then register it?

I am confused, and I'd rather not have the dude doing this go through all this again.

HALP ME, HALP ME! Somebody SAVE MA BAAAAABY!

1. go to TE>plugin manager and uninstall the 3.1.15 dll file from TE
2. download 6.1.17, then go to TE>plugin manager and install 3.1.17 dll file to TE
3. start the plugin and you should get 6.1.17

if you dont uninstall from the plugin manager, it will still pull from the last know file location.

as far as the wrong row values, anything older than 6.1.17 will log the drive gear in the row address for ng63 and should be correct for any other ng6x code. so as long as you are sitting still, the row will not change from 0. as far as the wrong pulsewidth and timing values, im not exactly sure. it seems to work correctly on my laptop...but will double check it.

archive or delete anything older than 6.1.17, as that should work correctly when switching from ng6x to ng63. in the older code the row is calculated by dividing the rpm value by 16 and saved in a certain address...in ng63 the gear value is saved in that address and the datalogger takes the rpm value and divides it by 16 instead.

Ok, I walked him through the process, and it worked now. He's gonna try datalogging with an NG63 based bin.

Will EC x.17 log ELD automatically?

Thanks again. You are continually the dude!

Ok, same deal: Wrong values all over the place. It seems that everything is messed up past the row and column calcuation.

Is there any option on how to configure what gets output into the csv file? I still want to know how to log the ELD.

just to be sure, your using an ng63_final(2) rom and ecucontrol 6.1.17? the log to file should say pulsewidth instead of duty cycle...make sure hes still not using 6.1.15.

currently no way to change the log to file stuff...but you have a point about the eld. i will add all the other sensor values and get you another version to try...i believe i still have your email.

attached is a screenshot i just took and a log to file, everything looks good on my end. i will check this out more tomorrow.

wifes gonna kill me if i dont turn off teh computer!

Ugh, this gets more complicated. I viewed your test log (thank you by the way!) and it is waaaaaaaaaaaay different than what he is sending me.

His datalogs are still showing the old headers, but 6.1.17 shows up at the top of his window? The other odd thing is his maptrace shows correctly, AND he doesn't get any negative values showing in his live view.

Is there any reason why the log would be getting screwed up?

I gotta troubleshoot his setup (again).

Thanks again for the help, man! You ROCK!

To compare-

The dudes log:



fastcrxsi90's log:



This is funky. =(

For situations like this, and trust me, I was pulling my hair out for 2 weeks trying to find what the cause of my messed up installation was......wipe windows XP out and reinstall!....nothing else worked for me, even a thousand installs and reinstalls of TE wouldn`t fix my problem.The more software you have on the laptop the more screwy your windows and system32 folder is.Fresh windows, install drivers, install TE 3.2.1, install ECUcontrol 6.1.15 and 6.1.17 and put all the resource files of both TE and ECUcontrol in system32 and you should be fine!

Put the resource files into system32 in the Windows directory? We haven't tried that. What does that do differently?

That seems weird, but, I can tell hi to try it. His laptop was just recently fixed with a fresh windows install, and I don't think he's got much if anything else on the laptop.

You either register the .ocx and .dll files manually (command prompt, regsrv blabla) or put the files in system32.Same thing.Putting the files in system32 worked for me better.But don`t overwrite the ones that are already there.

email sent...let me know what happens

I know this might sound retarded, but, what exactly do you mean archive the .dll?

Got the email. Thanks!

either delete the current ecucontrol.dll file or move it to some other sub folder and keep it just in case the new version doesnt work for some reason. since the file names are the same between versions of ecucontrol, its easy to mix them up. i also have a bad habit of not deleting old versions...