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.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.
Bookmarks