At zero mph the result will be out of range, it needs to switch to liters/hr or galon/hr{I need to revise how these are calculated and will update the post when ready}.
At zero mph the result will be out of range, it needs to switch to liters/hr or galon/hr{I need to revise how these are calculated and will update the post when ready}.
Here is the static flow in l/hour and gallons/hour formulas.
I also added INJ dc% if you want to add that too.
that's some good stuff. i don't know if i'll use it in this version or not just because i want to get the thing released but i'll see what i can do
i see that the large mode is a bit of a fail, i might just leave it disabled for this release as well just so i can get it rolled out.
I'm not thrilled with what it does when maximized and the default size for me is still taller than available desktop height on a 1366x786 display. This is probably an outside case b/c I'm running Ubuntu Unity and the task bar is permanently pinned to the left edge. I don't think anything critical is getting clipped off but I'd be perfectly happy if it would maximize correctly. But for some reason it never loses the title bar like the graph window does when it's maximized, and thus is still larger than the available desktop height. I'll tinker a little with the source and see if I can find what differences there are between graph and the main ui. If I can figure that out I'll log my commute with it this evening.
It's not important, but I'm about to die without the spacebar attached to the play/pause function.
Appologies for being away for a while.
Just spent a small fortune on a Thermal Spray system so I'm now able to spray Thermal Barrier Ceramic coatings.
Laptop screen cracked a few weeks ago & now it's spread across most of the screen.
Had the car in garage for a few weeks while we were away, on a trickle charger. Battery is now toasted & won't hold a charge.
So I'm unable to test at the moment until I can get these sorted.
Mitch
'95 Z28 M6 -Just the odd mod.
'80 350 A3 C3 Corvette - recent addition.
Scrunching the main buttons down to a height of 32 and setting the default font to 9pt got the main window to fit - the controls on it were too large to render the window maximized so it "wrapped". I noticed you removed the titles from the playback and log frames, but unfortunately QT doesn't seem to let you recover the lost real estate the title occupied.
I have a similar issue on the settings window that's causing the wideband settings to get "smushed". I don't have time at the moment but possibly reducing the default font and getting rid of the update checking frame would give a bit more real estate.
I'm not sure I would classify the large mode a fail - it seems ok to me. The only problem I have is the default font size goes really small when I switch large mode off.
Update: No issues logging.
In all I think there's just a bit of polish needed for those of us with lower resolution displays. I think the temperature, speed and idle frames could be compressed to eliminate unused space, and the size of the DTC text widget reduced to give the important fields more real estate. The adaptive font scaling is a little weird at my resolution - i.e. the O2 fields are using a size smaller font than the BPW fields because of the width of the information, but the larger font looks like it would fit easily.
Also, to make the key accelerators work all that's needed is:
Code:#include <QShortcut>
Last edited by spfautsch; 10-23-2019 at 03:13 AM. Reason: Update
Steveo,
I had emailed you awhile back about some logs and info from a flash routine that started to error out mid flash and the retry script went wacky on me. Not sure if you received it. I have soldered some sockets and put new chips on that ECM so will be trying to reflash soon.
Couldn't ever find out if it was the computer, the ecm or the cable. I don't think it was software related but instead of a failure it should pause in place, allow you to check connection and then start the erasing again in my opinion.
Last edited by JustinSEO; 10-28-2019 at 03:52 PM.
hey justin! yeah maybe it should be a user choice. i think knowing what i know now i could write a more robust recovery but i ditched all my testing gear. i was going for automatic and it does retry on failure but maybe a manual mode wouldn’t be a bad idea. ideally just use interfaces that are stable of course....
Posting Permissions
Reply With Quote
Bookmarks