NefMoto

Hi all,

i am running an M box ecu

i wired up a zeitronix WB sensor to bank 2 using the brown plug and edited my .ecu and .cfg files to reflect the following below.

added the below to my ecu file:
;Name,    {Alias},                        Address,  Size, Bitmask, {Unit},        S, I,            A,     B, Comment
uushk2_w, {O2SVoltageSensorWB}, 0x381114,    2,  0x0000, {WB-AFR} , 0, 0, 0.009766, -9.6, {}
 
added the below to my cfg file:
;Name      [Alias]                     
uushk2_w   AFR-WideBand


When I try to log, ME7L returns an error message saying: "the log variable 'uushk2_w' is not defined in the characteristics file d:\ME7L\ecus\my_test.ecu

One thing to point out is my ecu file was called test.ecu, NOT my_test.ecu. im not sure why its looking for an ecu file prefixed with my_. I tried changing the name of the ecu file and updating the cfg file accordingly and when i log it will still give the same error with the file starting with my_

If i add the ; back to the uushk2_w line in the config file, the log will work properly.


I also want to point out that uushk_w or uushk2_w was not in my ecu file. so i manually added the entire line. not sure if it should have been there and i all would have had to do was edit the address, factor and offset or if it is normal for it to not be there.

I also tried logging bank1 with uushk_w and get the same error message.

Any ideas?

Aliases do not go in the cfg file.

add a ; before your alias.

I edited both cfg and ecu files correctly, i believe.


cfg file:
uushk2_W          ;{O2SVoltageSensorWB}               ; {}

ecu file:
uushk2_w        , {O2SVoltageSensorWB}              , 0x381114,  2,  0x0000, {WB-AFR}  , 0, 0,     0.009766,   -9.6, {}

If i add the ; before the uushk2_w in the config file, ME7L wont log it, i need to remove that in order to log. I simply copied the format/layout of the existing entries on both files when i edited them.

I have a feeling that the issue is either related to my tune, with how my rear o2's were coded out OR the address for the brown connector: Address : 0x381114 is not correct for some reason on my ecu. not sure where to go from here.

Quick question: should the name be uushk2_w or uuhsk2_w? I'm seeing both described in different threads on the internet and not sure if people are just typing it incorrectly when they post or if they are 2 different names.

; comments out the rest of the line.


No, there is something else wrong here. ME7L is likely not using the .ecu file you think you are editing.

uushk, sonde hinter kat.
have you tried to locate my_test.ecu and edit that one?

Ok thanks, I am using uushk, so that is not the issue.

btw .ecu files live in ecus\, .cfg files live in logs\.

If you are editing an .ecu file in the logs\ directory, ME7L will NEVER see it.

yes, i looked in the ecus folder and it was not there. i copied the .ecu file i was using a renamed it my_test.ecu and it still did not work. I forget the message i recieved, but it still didnt work.

That makes no sense. If my_test.ecu was NEVER in the ecus folder, ME7L would not have even launched in the first place.

I can't make head or tail of your problem; none of it makes any sense, nor does your description of what you are trying to do to fix it.

zip up the whole directory (with subdirectories) and post it.

I will do this tonight when i het home.

let me clarify what the problem is and what i have done to try and fix it.

1) I edited my .ecu file called kmh 27.ecu and added the line for uushk2_w as described above

2) I edited my .cfg file by adding uushk2_w and i uncommented the line by removing the ; so it would be a logged variable

3) i pressed the log button on ME7L GUI interface and recieved the error message: "the log variable 'uushk2_w' is not defined in the characteristics file d:\ME7L\ecus\my_kmh 27.ecu"

4) I noticed in the error message that ME7L was looking for an ecu file named: my_kmh 27.ecu. this was not the ecu file i edited or the ecu file that my .cfg file is referencing.

5) I manually copied the kmh 27.ecu in the \ecus folder and renamed the copied file my_kmh 27.ecu thinking that me7L would then find the file and log uushk2_w. it did not work.

here the cfg and ecu files that i happen to have on hand right now. Not sure if is of much use to anyone.

Dude.

From your .cfg file below


Anyway, dont use the GUI if you are trying to debug config file issues, it has all sorts of stupid hardcoded things in it.

Try command line FIRST.

Also, if you must use a front end, use ME7VisualLogger, not ME7GUI

It is DEFINITELY not reading the ecu file you think it is.

Remove ALL of them except the one you want, and see if it still works.

Finally, uushk2_W != uushk2_w

I will try using the visual logger to see if that clears this up.

But just so you dont think im crazy....when i un comment the uushk2_w on the cfg file, the logger looks for a different ecu file, one that was never created. If i add back the ; in the cfg file so uushk2_w so it is not logged the logger will work and it uses the correct kmh 27.ecu file. 

In summary, the logger looks for an ecu file that i never created when trying to log a variable that i manually added to the ecu file.

I'll try the visual logger and report back

You are crazy. That makes zero sense, and I've never seen that behavior.

Again, post the entire directory, zipped.

Also _W is NOT _w

Please double check your case.

you might be right. I started over and was able to get it to work using visual me7logger. My case was different between the ecu and cfg files which was probably causing the problem. now they are both _w and it works.

However, the problem i have now is the sensor reading fluctuates around 19.5 volts all the time. attached is a quick 2-3 gear pull. any ideas why this would happen? i have the zeitronix wb control box red wire connected to terminal 75x and black is grounded directly to the battery. could the ground be causing the sensor to not read correctly?

Then you log either the wrong ram adress or have the wrong factor/offset for the conversion

I double checked my factor/offset and ram address and they are correct. as per zeitronix documentation for the ZT-3, the wb controller reads 9.6 at 0 volts and 19.6 at 5 volts. I am using the following in my ecu file:

Address : 0x381114
Factor : 0.009766
Offset : -9.6

ME7L will either read 9.6 or 19.6 under all conditions: idle, part throttle, wot. The value the logger reads will change if i cycle the ignition off/on.

If I unplug the WB sensor from the wb controller ME7L will read 14.7, or 2.5 volts.

Im not really sure how to proceed. I'm going to try and log the wb directly through the zeitronix software and go from there. 

The output impedance of the ZT isn't low enough (i.e. the input impedance of the IO you're using is too low) and it can't source enough current. You'll likely need an op amp circuit.

The wire harness extension was in contact with the turbo and the wires melted. Im Going to try to clean up the harness by cutting out the melted section and using crimp connectors to join the wires back together.

Woops, that sort of thing kills ecu's  ;D You're lucky it was an external controller. Let us know if you fixed the logging issue with this :)

FYI, I repaired the cable and it still does not work. I cant even connect to the zeitronix data logging software. it will connect and read 5 volts but then it crashes. maybe i screwed up the board when the wires melted.

Im using uushk_w to log my wideband or at least im trying too. Im having trouble with the output of the information into ME7. Not sure if there is a cap I have to work around or just deal with it. Im finding that what my gauge shows and what me7 acquires during a log aren't exactly on the money and accurate. Im using a LC2 from innovate and maybe there is a way to scale it to see correctly. example, when my gauge hits 22 from the car not running of course, Me7 reports 19.x     has anyone had any experience with the LC2 and using the rear o2 channel ( green plug ) 0x00381116 to data log the LC2 controller 0-5V analog output.