Hi Guys -

I just uploaded GMECM Edit version 1.0. <a href = "http://www.markmansur.com/gmecmedit/">Get it!</a>

(this is related to <a href = "https://www.thirdgen.org/techbb2/showthread.php?s=&threadid=159532">this thread</a>)

<p align="left"><b>Whats new in this version:</b></p>
<ul>
<li>first &quot;official&quot; release!</li>
<li>added compare functionality to tables.</li>
<li>completely re-wrote Bin Stacker. This is now compatible with chip switches
(www.moates.net) and can also be used for stacking 16k bins on 32k chips (29C256).
Included is the ability to save/load stacked chip layouts.</li>
<li>added the ability to highlight the currently selected row in the table editor.
Can be toggled in preferences menu.</li>
<li>&quot;quick copy&quot; button added for copying constants from the compared
bin to the active bin.</li>
</ul>
<p><b>Bug fixes</b></p>
<ul>
<li>upgraded compiler to VC7 (.NET), which exposed new bugs to fix (mostly memory
issues).</li>
<li>fixed bug where saving table after selecting a constant/flag without closing
table editor will corrupt a bin.</li>
<li>constant/flag editors disabled (do not accept input) when constant/flag
not selected.</li>
<li>other not-noteworthy minor fixes.</li>
</ul>
<p><b>Known Issues with this version:</b></p>
<div align="center"></div>
<ul>
<li>Help sucks. Wanna help?</li>
<li>Let me know what you find ...</li>
</ul>

 

I like the layout of this software a lot.

Things I hope you add:
- Make the window expandable for people with high resolution so you can see everything in the constants menu.
- For the Info field that is currently not used in your software. I think you should add to the ECU format in a way that would not interrupt other software programs that reads the ECU file format like Winbin.

For example at the end of each item in the ECU file you could add a comment line that your program would look for.
For example /* ITEMinformation: type info here */

 

Nice to see someone contributing.

At a glance it seems to be really nice.

THANKS.
Bruce

 

Mangus,

I think you are on to something here. The fact that your editor is free AND the fact that you are regularly updating it could, in my opinion, spell the eventual death of WinBin. I like what you have done and I can easily see it growing. Great job.

I really liked the suggestion of allowing the window to be resized. Another suggestion is to maybe approach comparing the tables as per what TunerCat is doing? Instead of having two windows up for the original and the comare just have one window up. When you click on compare then slap the differences in that table. This makes it easy to locate and examine the differences. That's just my preference though.

Here's a quick bugfix:
If you open a bin and DON'T open an ECU then when you click on View->Table Editor... you get a major error (WinXP).

Tim

 

Thanks for great input and kind words, guys!

Trax - I'll fix the bug for the next version. Sorry about that!

regarding window resizing - the next *major* version (hopefully 2.0, but maybe 3.0), I plan on revising the entire UI. It will become more of a "workspace" (much like tunercat) that will allow you to resize everything, as well as place anything anywhere.

regarding the compare bin ... thats a good idea (and I think it would be fairly easy to implement) ... perhaps I could make it an option to either open the compare table separately or simply show the differences in the original table ... I'll look into it!

Regarding the comment lines for additional info in the ECU's ... by george, i think this is a great idea ... look for this in the next version! =)

M

 

I like it. I like it a lot! I still like Tunercat and winbin for the graphical view of the tables. It's like excel within the editing program = eye candy and it's easy to see if one cell was overlooked.

 

graphing is coming!!! Please understand, though, that because of the my programming environment (I'm NOT using Visual Basic nor am I using MFC - both of which make graphing and other such controls VERY simple to implement), I am left to actually write the functionality of such controls myself. The grid control in the table editor and bin stacker is hand written. So this takes time (and lots of work!) ... but rest assured, I'm working on it!

 

Thanks for taking the time to write this program.It easy to understand even for a newbie at this stuff.

 

Good stuff. Can't wait to through away winbin and TC

 

Another bug:
When you open the software and have no Bin or ECU file open and you hit Ctrl-N to create a new ECM Item it creates a fatal error and the program crashes.

 

fixed ... along with the crash when opening the table editor with no ecu/bin. next version will contain these fixes (as well as MORE features - i was up until 4am last night). i'll post it next weekend.

 

Not sure if this is exactly your program related problem or not, but whenever I open the program it's "stuck" in the task bar on the bottom of my screen (kinda like if I were to "minmize" the window), the shortcut keys still work and allowed me to burn my first chip ever and it worked. Your program is a lot easier than trying to figure PP2 out. 8 files on one chip seems too fun. Win98/Gateway 750ish? I'll try to DL again and re-install. Thanks

 

This looks great!

- Using 1227730_8D.ecu and open up AUJP.bin and i get "invalid element size" when looking at "Options" in constants....

- Using 6Ev010.ecu I cant find "injector pulse vs. mg/s"

Otherwise it looks great! I will do some more testings this weekend.

What is the best .ecu to use with the 730 ECM?

/N.

 

welp, i can tell you that the "errors" you see are likely due to syntax errors in the ecu you selected (i haven't opened a single ecu that didnt have errors of some sort. i tried to correct all errors with the ecu's included in my app.)

check for missing commas, etc.

regarding your questions about what the best ecu to use ... i dont know. my TA uses the 165 $6E code ... ask elsewhere in this forum and I'm sure you'll get an answer ...

M

 

I want to add my thanks for all of your effort and wanted to let you know that I emailed you a revised copy of the 1227730_8d.ecu file. I posted a seperate thread in this forum to let anyone know that was interested in the revised copy. I added 4 constants for the 3rd and 4th gear Torque Converter Clutch lock/unlock points and called the file 1227730_8dm.ecu. I was hoping that you might make it available on your website. That is if you feel it is o.k. to do so. If not that's o.k. too. I'll try to make it available via email if not.

Thanks again,
Glen

 

Awesome, thanks!

 

This is an excellent alternative to WinBin. Thanks for your efforts, and for making it free.
Ral

 

I like the layout a lot better than WinBIN, it kinda makes everything seem more manageable. Great job man

 

so is this program like tunercat. lets us modify our bins. will it work with a 8746 91 TBI.

 

Yes. yup. yeah. Isn't it great

 

thanks for the encouragement! i've got yet more in store ...

meanwhile, let me know what other things you'd like to see (in addition to "whats coming") or what issues you have found. once again, i hope you can make this *your* software!

(and for those of you who are wondering, i will support this software for as long as i own my car. i've had it for 7 years now and have absolutely no intention of [ever] getting rid of it. so the outlook is good =)

 

did this get resolved? if not, try deleting the gmecmsettings.dat file in the executeable directory and restart the applicaiton. this holds the window locations (among other things). if they get corrupt (or somehow are inaccurate), they can position the app outside the viewable (desktop) area. this is likely whats happening.

if you do the above and you still have problems, let me know.

 

This is weird. I'm using the unregistered 30-day version of TunerCat and I'm comparing it to EMECMEdit v1.0 and it appears that when I change something like say for example the Max RPM Fuel cut off, if I set this to 5837.59 in GMECMEdit, save the file, then open it in TunerCat it shows it set to 15604 RPM's! So then if I set it to 5817 in TunerCat, save it, then open the file again using EMECMEdit it shows it to be set at 15659.57 RPM's! What's going on? Am I missing something? I admit I'm a newbie but this just doesn't make sense I'm using the 7730.ECM file with GMECMEdit and the $8D file with TunerCat and I'm editing the BIN for my 92 GTA which is a standard SD LB9 Auto file...

 

Mangus, very easy to understand! Reminds me of Tuner Cat minus the graphs! Way to go! It's awsome!
TY TY TY TY TY TY TY TY TY

 

One question, Why are there 2 730 ecm bin files?

 

There's a problem with offset 41f on the 730 ECUs. Elementsize=2? Is that right? It should be 1, I think.

Also, going to that element and viewing it shows 1.#J then moving away and back it becomes 0.85. What this does to the .bin is change the default 0 (from aujp1615.bin) to a 3. Since Elementsize is 2, it writes the 3 into 420. There shouldn't be a write at all, I'm not sure why the program is toggling the 0 to a 3. Aside from that, it's writing in the wrong positions.

 

this is fixed in the next version (the 1.#J).

regarding the ECU's ... fix it! thats what the program is for. if the element size should be one, set it to one. that would keep it from writing in the adjacent byte.

perhaps I should not have included anything but the $6E ecu (since thats what I use, and therefore can offer help with).

I'll strip them from the download in the next version and simply offer non-supported ECU's on the site as separate downloads.

-----

this also answers a question above where the user sees different values in tunercat - this is likely due to inaccuracy in the ECUs (or maybe tunercat).

----

these are all problems with the ECU files themselves. I cannot, unfortunately, verify ECU validity. That is left up to the user.

 

I've already done so, but felt it necessary to make people aware, especially since it involves the 730.

The 1.#J problem is the same as the toggling of 0->3 for that byte, or are you referring to a display issue? I don't think there's anything that can be done on the .ECU file, as far as I know, regarding the toggling.

Thanks for taking care of that! I'm liking GMECM much better than WinBin so far.

I don't have TunerCat, so I don't know what the deal is with that.

 

...wish i found this before I dropped $90 for tunercat last week

 

Just downloaded it again and haven't had any problems with it.

 

The options constant you see is not right. This is what it should be.

/* Item 6: vats enable(b4) */
{
/*startAddr =16,
/*columns =1,
/*rows =1,
/*elementSize =1,
/*bitMask =80,
/*offset =0,
/*mulOrDivOrBit =0,
/*factor =1,
/*map_name =vats enable(b4),
/*ylabel = option,
/*yaxis =b7 b6 b5 VATS b3 b2 b1 b0,
/*xlabel = },
/*xaxis = ,,
};

/* Item 7: dual(1) or single(0) air valve (b2) */
{
/*startAddr =17,
/*columns =1,
/*rows =1,
/*elementSize =1,
/*bitMask =80,
/*offset =0,
/*mulOrDivOrBit =0,
/*factor =1,
/*map_name =dual(1) or single(0) air valve (b2),
/*ylabel =option,
/*yaxis =b7 b6 b5 b4 b3 dual b1 b0,
/*xlabel = },
/*xaxis = ,,
};

/* Item 8: Mag Speed Sensor */
{
/*startAddr =18,
/*columns =1,
/*rows =1,
/*elementSize =1,
/*bitMask =80,
/*offset =0,
/*mulOrDivOrBit =0,
/*factor =1,
/*map_name =Magnetic Speed Sensor,
/*ylabel =option,
/*yaxis =b7 Mag b5 b4 b3 b2 b1 b0,
/*xlabel = },
/*xaxis = ,,
};

 

91Z28-350

This is over my head?? Should I copy and paste that into the .ecu file or what?

/N.

 

Yep, just copy and paste it in there, and delete the "options" section that you see.

 

What is the element size? what does it do and what is it for???

 

elementsize = 1 means 8 bits, or 1 byte
elementsize = 2 means 16 bits or 2 bytes (aka 1 word)

This is polluting this thread as it doesn't apply to Mangus, post any non GMECM followups/queries in another thread.

 

or, even better, use GMECM edit to delete the "broken" ecu items, and create new ecu items (within the program) and input the information listed in the post!

there should be no reason to ever actually have to open the ecu as a plain text file! (er... at least I hope not!).


also, to answer a previous post, the 1.#J issue happens because the byte at the location you're trying to view is 0 AND multordivorbit is 1 (divide) ... unfortunately i didn't catch the divide by zero in this case. So, if you see 1.#J, just know that you're looking at zero. =)

I've fixed the issue for the next release.

 

Thanks. I have hit some alignment issues with the labels, where I had to open up the text file. Some of the spacing comes out weird, I'll see if I can reproduce it but there are times where a space or two is added before the label.

I do work faster with text files though, it helps to be a developer and having a real editor. I'm filling out the full 730 ECU for my own usage (all values), and am noticing some things that have interdependencies between fields. Is there a way to link the fields? An example would be a certain offset would be a value bias. A table would then use that bias to bias it's values. I don't have the offsets offhand, for a more specific example. It can be worked out by hand, but would be nice to be able to view the data appropriately.

 

I'm completely lost as to what you're talking about. =)

regarding the strange spaces you find before the label, if you mean the axis labels, this is because of the way the ECU file format was created (not by me, mind you). Y axis labels have to be 5 characters. x axis have to to be 3. if you have only 1 character in a y axis label, i need to append 4 spaces to the label in order to maintain file format compatibility.

 

Hehe, OK.

For what I thought was the display bug, if you edit one of the flags fields that is formatted perfectly, and just save it, some fields may shift. I think it is because some .ecu files pad space at the end (except for the last b0 field), and GMECM pads at the front. It's not really a big deal. I haven't really looked at WinBin, so I can't comment on that too much, other than to say I don't like the interface for WinBin.

For the "linking" request. If you look at anht_hac.pdf L8137 has a bias for a table residing in 8138-81A7. The table has this equation. TBL = (VAL + L8137 Bias) * (256/90). This could be worked out by hand, but could be misconstrued if one isn't aware that what is currently displayed is not biased. As far as I know, there currently isn't a way to apply a bias to a table or another constant, and having that bias reside in at a discrete offset. It's a nice to have, and may break compatibility with the current .ECU files, if it were to be implemented.

 

I cant seem to find "BPW FUEL vs. LOAD", msec of inj. PW table in the $6E code?

is this only availible in Tunercat?

/N.

 

if its in tunercat, it is possible to add it to an ECU as well. just find out what the factor/offset, etc, are and create an item for it! =)

 

Ah yes. I see what you're saying. When you say "shift" you mean they move towards the right...

yes, this is because of leading spaces. I can offer the option of choosing leading or ending spaces, i suppose. look for this in the next version.

as a temporary fix, append the spaces to the end of the field yourself. this will force the text to be left justified.

 

Well hope someone can look into this becaurse I dont have the knowledge to do this. You can see the table in the "sticky" the def. #32B tuning article an this forum......

/N.

 

$32b is not $6E.

 

So the That table is only for 32B code? Do I only have the MAF tables to adjust with 6E code? Can someone with Tunercar and 6E def. file verify?

/N.

 

version 1.01 has been <a href ="http://www.markmansur.com/gmecmedit">uploaded</a>

fixes include the "1.#J" issue, app crash when creating new ECU item when no ECU is loaded, and app crashing when opening the table editor with no ECU loaded.

M

 

Got it, thanks! Once you get all the graphs and everything going I'll make a donation since I'll be using your program instead of TunerCat...