ok cool i'll flip them around for the next release, thanks for the feedback!
Printable View
ok cool i'll flip them around for the next release, thanks for the feedback!
i don't suppose you have a BLM split or anything so you could confirm that left/right are correct too? ;)
Yes, but it will be a week before I get another opportunity on an LT1.
BTW is there documentation of what the individual cylinder balance test results are useful for? I got a significantly different result each time I ran the test, but this is on an LT1 that had had an intermittent random misfire at idle for the four years I've been tuning it. Runs fine under load though. If anything, I'd use the one at a time test to see if it was only one cylinder causing the intermittent misfire.
yeah most people arrive at that conclusion, the cylinder drop test doesn't work well at the moment. dropping cylinders manually and going 'by feel' seems to be the best bet. i may remove the feature but right now i'm lazy.Quote:
If anything, I'd use the one at a time test to see if it was only one cylinder causing the intermittent misfire.
again, any documentation is in the tooltips for each feature. no plans to write any actual docs or help files.Quote:
is there documentation
4.0 beta 3 now: http://fbodytech.com/download/223/
improved the knock plotter, improved graphing (color overlay for cl/pe modes + some presets), fast logging patch works properly now. fixed that blm re-ordering, thanks sherlock!
almost ready for 'stable' release, only issues i know of.. vin programming now displays the last digit but refuses to program, and autospark can't be enabled while connected for some reason.
I threw a tooltips issue on Github... did it take?
Additional:
1. on 4.0 Beta1, if I hit ESC instead of the EXIT button after a write, the MAIN screen seemed to get stuck on "disconnecting".
2. How hard is it to use both D12 and D27 simultaneously as dual wideband inputs?
On the FLASH menu, there's a checkbox that says "Insert Patches." Where are those patches selectable at? Is there any way to display selected patches on the FLASH screen?
yep, and i fixed those, thanks! i spend too much time on new features and serious bugs, so any errors you catch like that are really helpful.
i'll look into that, i've never tried keypresses in the flash screen. i wasn't even aware that the escape key did anything. i'll try making the escape key just signal the exit button, maybe that'll fix it.Quote:
Additional:
1. on 4.0 Beta1, if I hit ESC instead of the EXIT button after a write, the MAIN screen seemed to get stuck on "disconnecting".
medium hardness. i'll get to that in 4.1 or something. the way i coded in wideband support is really hacky, it was a huge afterthought, so adding a second wideband sensor will require some rewriting for sure.Quote:
2. How hard is it to use both D12 and D27 simultaneously as dual wideband inputs?
i have a dual channel wideband, so it's on my wanted list, but i'm not sure how far i want to take it.
out of curiosity, what advantages do you want from dual widebands?
making left/right/combined selectable in the analyzer is kind of a bitch and i can't see any real useful static analysis coming out of it, so i might just settle on being able to read/graph them separately, but have the analyzer only do averaging of both sensors. the analyzer is the main reason i got wideband input working in the first place.
this makes it a bit redundant since most dual sensors have their own averaging output of both sensors anyway, don't they? (mine does) so really, i guess it's low priority. knowing one bank is slightly leaner than the other isn't even that useful except for identifying a mechanical problem.
nope. eehack's patch is a single 'patch set' as a version (new versions may be an improved or expanded version of that patch, but will always include previous patches).Quote:
On the FLASH menu, there's a checkbox that says "Insert Patches." Where are those patches selectable at? Is there any way to display selected patches on the FLASH screen?
this patch is all or nothing, not a bunch of little individual patches you can choose from.
but i will explain why
it's pretty much safe to install every modification on every ecm that eehack flashes (and that's why it's enabled by default). they're designed in a way that does not affect your tune in any way that you'd observe from the tuning end of things, only how eehack works with your ecm to scan/log/tweak parameters.
i thought about making them selectable, but that would require each patch having a status bit, and it would get annoying to maintain and test all combinations of the patches, so i decided against it. i'm not going to actually patch code that affects how the engine runs due to that being a violation of eehack being a scanning/logging/testing tool, so there's no conceivable reason that one engine needs a different set of patches than another.
by design they are passive as well, and don't modify your bin on disk (not even optionally), they only modify it while being flashed, to ensure that any bin editing tools you use wont be affected. this also means that reading a 'patched' bin and tuning it may be a bad idea (not now, but in future releases) so it's expected that tuners keep track of their own bins on disk and back them up. this is because future patches may passively relocate tables to gain space for more real-time tuning options.
for example, the first patch version in 4.0 only increases logging throughput (optional) and adds AFR target to the datastream in a way that doesn't interfere with any other datalogging tools. the next patch, i plan to add some mode4 features to modify more parameters in realtime, as well as enable e-side direct ram querying (t-side already has that from the factory).
eehack queries the ecm for a patch version when it connects, and enables the appropriate features for the patch version.
this is kinda explained in the tooltip too as well as previous posts, but just thought i'd elaborate. eehack will never give you 'patches' like closed loop idle or blm lockers. that's EEX's territory. eehack is not a bin editing tool and never will be.
Hi Steveojust been playing with latest EEHack and noticed cts & iat readings are different compared with Datamaster The car was warmed upLast temps in Datamaster were 94.3C and iat was 29.0CEngine still idlingLoaded EEHack cts: 71.2C and iat 44.0CAlso just running the Knock scope between 2 different logs did not seem to clear the display first & leaves the first set still showing.OK. just gone to the graph page & plotted data. load new logfile & old data is still displayed.I also download the version of EEXTRA.xdf on the recent thread. It errors on loading with "Illegal char '
i'm pretty sure mine is correct, and datamaster is wrong. eehack uses a commonly used lookup table for temperature, datamaster uses a linear equation. temperature sensors aren't linearQuote:
Hi Steveojust been playing with latest EEHack and noticed cts & iat readings are different compared with Datamaster
of course i just stole the table from the V6 datasheet, but it should be the same as many other GM ecms that use the same temp senders seem to use it.
Code:// this is a 2d table to convert a/d counts to temperature in celcius.
// divide result by 10 (ex idx0=-35.1)
const int ad_to_celcius[256] = {
-351,-348,-344,-340,-321,-303,-284,-265,-246,-228,-209,-190,-171,-153,-134,
-115,-96,-78,-59,-40,-32,-24,-16,-8,0,8,16,24,32,40,48,56,64,72,80,88,
93,99,104,110,116,121,127,133,138,144,149,155,161,166,172,178,182,187,192,
196,201,206,210,215,220,224,229,234,238,243,248,253,257,261,265,269,274,278,
282,286,290,295,299,303,307,312,316,320,324,328,333,337,341,345,350,354,358,
362,366,371,375,379,383,388,391,395,399,403,406,410,414,418,421,425,429,433,
436,440,444,448,451,455,459,463,466,470,474,478,481,485,489,493,496,500,504,
508,512,516,520,524,529,533,537,541,545,550,554,558,562,567,571,575,580,584,
589,594,598,603,608,613,617,622,627,631,636,641,645,650,655,660,665,671,676,
681,686,691,696,702,707,712,717,722,727,733,738,744,749,755,761,766,772,778,
783,789,794,800,806,811,817,823,830,838,846,854,862,870,878,886,894,902,910,
918,926,934,942,950,961,972,982,993,1004,1015,1025,1036,1047,1058,1069,1079,
1090,1101,1112,1123,1145,1168,1190,1213,1235,1258,1280,1303,1325,1348,1370,
1393,1415,1438,1460,1460,1460,1460,1460,1460,1460,1460,1460,1460,1460,1460,
1460,1460};
the knock scope definitely clears itself, as do all the other analyzers.Quote:
Also just running the Knock scope between 2 different logs did not seem to clear the display first & leaves the first set still showing.
you have to clear the log manually before loading a new one. loading a log in eehack appends to current data. this is by design so entire sets of logs can be easily spliced together for graphing and analysis.
as this seems to confuse lots of people, the next version of eehack has a warning dialog when you press 'load' that offers to clear the old log for you
eextra isn't mine, but it's working fine for me?Quote:
I also download the version of EEXTRA.xdf on the recent thread. It errors on loading with "Illegal char '
i think i've decided to offer an option for linear temperature scaling just so it matches other tools properly.
edit: also think i might have made an error in that table somewhere, it does seem to be a bit far off..
damn i did miss that coolant temp output in the datastream is actually linearized. i'll fix that.
Nice one! Apologies for the logfile loading. I do dimly recall reading about them being appended. I reloaded EEXTRA and can confirm it does now work OK.ThanksMitch
yet another new beta
http://fbodytech.com/download/223/
planning to release soon, will hold off on dual channel wideband etc. until the next release.
one thing that needs more testing is that autospark can crash when you're connected and you enable/disable it. i think this version fixes it, but i'd like to be sure.
Beta4 is not opening for me. Beta3 opens just fine.
works for me on both computers i have, try downloading it again?
I just found out this program, seems very nice!!! I have a few questions.
Is it safe to use the flash tools with the PCM in the car (not in a bench)?
If I understood correctly a patched BIN should not be read and tuned again. You can't patch it first then start tuning? What would be the best way to do with patches?
I am going to repair a couple of corrupted PCMs in a week or so (socketing and flashing). I have a bench setup, if you need to test any flash routines I can do it.
Thanks for the hard work. You should set up a paypal donate button in the program, lots of effort in this tool.
of course, 98.2% safe!!
most people flash LT1s in-car. just make sure headlights are off, stereo off, heater off, connection stable, etc.
eehack tries to help by testing for connection stability before beginning the flash routine
you aren't the first person to misunderstand what eehack's 'patches' are, or how they work.Quote:
If I understood correctly a patched BIN should not be read and tuned again. You can't patch it first then start tuning? What would be the best way to do with patches?
i'm sorry i didn't document it better, i can't figure out how to explain it more clearly.
eehack's patches are inserted passively during flash specifically so you DONT have to worry about them.
it's done this way for a few reasons:
- nothing is ever written to disk, your tune on disk is not altered. you don't have to think about how you will 'un-patch' or save backed up 'un-patched' copies of bins. what a total waste of time. eehack does not edit bins.
- if the patches affect your car, just flash again with the checkbox unchecked.
- i wont have to distribute updated special XDF files with patches in them.
- tunercat users can use my software
you don't have to do anything. nothing will break. just leave the patch button checked. tune as normal. it's designed specifically so you dont' have to worry about it or do anything. just tune as normal and enjoy a few small enhancements to datalogging.
right before it flashes, it just flips a few bytes around. that's all.
there's one downside:
if you read that bin later, it's not exactly the same bin that you wrote. it's been altered.
right now that doesn't matter, but what if i have to patch a table relocation to enable some new feature in the future?
in short, just keep copies of the bins you're tuning on disk if you're going to leave patching enabled, dont use the ecm's eeprom as a backup for your virgin bin files. if you're planning to read your bin file back from the ecm every time you tune it, seriously, reconsider how you tune.
i think calling them 'patches' keep convincing everyone that i'm somehow messing with their tune?
if any of this bothers you, uncheck the patch box.
cool! it's working very well right now, but hang tight 'cause the next beta will need some testing, im working on increasing the write block size.Quote:
I am going to repair a couple of corrupted PCMs in a week or so (socketing and flashing). I have a bench setup, if you need to test any flash routines I can do it.
other people have suggested that too. you know, for the life of me, i can't seem to navigate around paypal's site and get a donate button working... maybe i'll try again.Quote:
Thanks for the hard work. You should set up a paypal donate button in the program, lots of effort in this tool.
i found a stupid mistake i made with the cylinder numbering in the 'cylinder disable' routine. (again..)
i made a mistake thinking cylinders were numbered from 1-8, as there was no documentation and a brief read of the code seemed to indicate that.
i just read the disassembly again and the value is AND'd with 0x07. this effectively placed a ceiling of 7 on the number, meaning it has to be 0-7 instead. and if you AND 0x07 with 0x08 you get zero.
so:
01234567=18436572
I tried downloading it again. Beta4 still won't work. Even updated the libraries just in case.
any errors messages? what exactly happens?
i really didn't change much between the two releases.. nothing that should make it not start, anyway..
can you check your windows error log?
new beta, managed to hack in a donate button, a few other changes..
i'd really like someone to help test:
- my new cylinder numbering for the cylinder disable test...(noid light or a scope should do it)
- auto trans: the tcc lockup thing
- auto trans: gear selector
http://fbodytech.com/download/223/
also hope this runs for sherlock, otherwise lets do some troubleshooting
I think this sums it all for me. It is as I imagined it would work but I wanted to be sure. So as long as you always flash with eehack you can tune as usual without worrying about anything. If you by mistake flash using winflash nothing happens, you only lose the datalogging enhancement. Cool!!
some reports today, using Beta3 (apologies):
1. When I'd lose connection to the PCM, it would never successfully reconnect. If I hit "disconnect" and then "connect," it came back up almost instantly.
2. Auto trans gear selectors do not work.
3. I got several Blue Screens of Death once I got over 20,000 records. ERR_MULTIPLE_INT... something. My phone camera did not capture it.
I will try the newest version momentarily.
Beta5 isn't working for me either. I'm trying multiple compatibility options (run as admin, compatibility for win7), no success, and no error messages.
The other complicating factor is that Windows 10 is doing some major updates. At least they did on 12/25 right before I installed Beta4. But Beta3 still works even after that.
I am getting an error on system startup now "There was a problem starting C:\Windows\System32\LogiLDA.dll"
The specified module could not be found. I will try installing this.
i'd believe that, they should be working in the latest beta.Quote:
2. Auto trans gear selectors do not work.
that's a mouse driver. i think your computer is haunted.Quote:
I am getting an error on system startup now "There was a problem starting C:\Windows\System32\LogiLDA.dll"
i've tested it to well over a million records (which is a huge unrealistic amount of records) on windows xp, windows 7, and windows 10.Quote:
3. I got several Blue Screens of Death once I got over 20,000 records. ERR_MULTIPLE_INT... something. My phone camera did not capture it.
one thing you could try doing, is use the old beta and 'reset settings', then close it right away. perhaps there's a bad pathname in there or something? still, i haven't really changed anything that'd prevent it from starting.. god knows how your mouse driver dissapeared, or eextra got corrupted during download either.Quote:
Beta5 isn't working for me either. I'm trying multiple compatibility options (run as admin, compatibility for win7), no success, and no error messages.
i can't reproduce that problem, either. are we talking key-off key-on kind of 'lost connection' or something else?Quote:
1. When I'd lose connection to the PCM, it would never successfully reconnect. If I hit "disconnect" and then "connect," it came back up almost instantly.
Lost connection was while driving on the highway on a 30 minute trip. Someone else was driving, I was in the passenger seat monitoring connection. All of a sudden the error #s would start skyrocketing, so I'd hit "disconnect" and "connect" and quickly everything was back up and recording.
I tried opening 4.0 Beta3 and hitting "Reset to Defaults" on the config menu, then opening 4.0beta5, and no dice. I'm not getting any error messages either. Is there some way to open it such that I get error messages?
that kind of desync shouldn't happen, and it should reconnect on its own after a few seconds of errors.
i'm going to try building eehack against a newer version of QT and let you try that.
if that fails, im going to have to consider windows 10 UNSUPPORTED for the time being.
i only have three users with windows 10, and all of them have crazy problems nobody else has.
Oh no, it COULDN'T be windows 10.... :P
That's too bad, I'll be using Win10 on a tablet in the spring as soon as I get the car out of storage. Win10 will become much more prevalent rather quickly going forward with the free upgrade MS is giving away.
I could run it, but the PCM is in the car with the cable hardwired to the harness so I can't connect to anything right now.
What are the QT libraries used for? It looks like they aren't officially supported on Win10.
the entire program is based on QT. QT is a gui and portability layer to assist in rapid c++ development. im not good with gui programming, so it lets me roll the program out quickly and easily. without QT i would never have had time to write this junk. QT also offers the opportunity for the program to run on linux which is cool.Quote:
What are the QT libraries used for? It looks like they aren't officially supported on Win10.
prevalent on desktops, yeah. but on hardcore tuning machines?Quote:
That's too bad, I'll be using Win10 on a tablet in the spring as soon as I get the car out of storage. Win10 will become much more prevalent rather quickly going forward with the free upgrade MS is giving away.
sure it's a shame if all of your tuning software is buggy under windows 10 or with high dpi tablets, but it'd also be a shame if i had to waste many hours of my free time to support 2016 model shiny new devices with my utility software for tuning 1994 era 8 bit ECMs...
i'll try my best to get it working, but since it's free software and runs on throw-away hardware, please, get hardware that works with my program instead of making me blow a ton of useful development time that i could spend on good stuff. seriously, people throw out windows 7 laptops now, and this software is useful enough to keep an old machine around for tuning.
keep in mind, even if it stabilizes under windows 10, this is not the most awesome ui ever. this thing is a FIXED PIXEL INTERFACE. if you are running it on a high dpi tablet, you will be very dissapointed. it's not touchscreen optimized and does not scale well because i don't care about touchscreens and high dpi screens... and i have zero plans to make it dpi-scaleable. it's a crap ton of work. my fields dont get bigger as windows forces them to cram large font sizes in them as my interface is not dynamic enough. ui-wise, this is written like 90s software, not like 2016+ software. at the very least it'll require some compatibility mode stuff for such devices to make things readable.
lets find out, here's QT 5.5.1, i wrapped it in an installer, if this doesn't work, i don't know what will.Quote:
Oh no, it COULDN'T be windows 10.... :P
i still have NO idea why it wouldn't even start on that computer, though, it's hard to imagine it's QT's fault...
http://fbodytech.com/download/223/
i got a windows 10 virtual machine going and reproduced the problem, it just doesn't start, although i have no idea what's going on yet.
edit: found the problem with it mysteriously not starting. also played around quite a bit in the virtual machine (although not connected to a car) and couldn't make it fail.
Steve, Beta6 isn't running either. I used the installed and put it in C:\Program Files(x86)\eehack just as it asked, then copy/pasted all of the additional files over from the other folder where I had the previous versions installed, being careful not to overwrite any newer files. Same problem as before. I tried running Beta3 from that folder, and I get a "the application failed to start because it could not find or load the Qt platform plugin "windows".
I'm still able to run Beta3 just fine from my other folder.
Just for giggles, I threw beta6 (eehack.exe by itself) into my other folder where Beta3 runs, and it says "The procedure entry point ?registerNormalizedType@QMetaType@@SAHABVQByteArra y@@P6AXPAX@ZP6APAX1PBX@ZHV?$QFlags2W4TypeFlag@QMet aType@@@@PBUQMetaObject@@@Z could not be located in the dynamic link library C:\Users\me\Documents\eehack\eehack.exe."
If you'd rather me take this offline or via email we can do that so I'm not crapping up this thread with windows related problems.
running beta 6 with beta 3 libraries wont work. im using a different set of libraries to see if it fixes your windows 10 issues. thats why i included new libraries with the installer for you; so please do use the included libraries that come with beta 6.
sorry about the platform plugin issue, that was an issue with the installer itself (first time using it). you can correct it yourself if you want, it'll be fixed in the next installer. you need to make a 'platforms' folder in c:\program files\eehack and place the qwindows and qminimal dll files in there.
uploaded a new version as beta 7 that the installer should be working with