ok cool i'll flip them around for the next release, thanks for the feedback!
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.
Last edited by sherlock9c1; 12-22-2015 at 07:34 AM.
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.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.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.Originally Posted by sherlock9c1
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.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.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).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.
Last edited by steveo; 12-23-2015 at 07:59 AM.
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 '
EEXTRA.XDF i made that from steveos eex with the use of the e and t side maps.txt from that thread . I have no problems loading it. Could be a corrupt download.
97z28 A4 obd1 swap(16188051)
Tunerpro Newbie
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 linearHi 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.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?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..
Last edited by steveo; 12-25-2015 at 10:17 PM.
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
no need to apologize, nobody got that the first time around. when you find yourself having to explain the same things to many different users, it's a design problem. only takes a 'yes/no' dialog and we can have it both ways.
Posting Permissions
Reply With Quote
Bookmarks