eCtune

Ok, I was about to make a few changes to my cal when presto! The tables window dissipears. So, what do I do? click the button up top to reveal it and there are no scroll bars, and nothing pops up. Strange right? It pulls a Hudini and completely goes away. Now; I then clicked the Parameters window and the scroll bars popped up and I see this: If I drag that scroll bar at the bottom all the way to the left, or even click on the area to effectively go \"page left\": The parameters window dissapears (because it's location in the parent window is all the way to the right); but I can not find the tables window, or the sensors pane, etc.... they are gone. All of the windows that were open at the time of the alien abduction are gone. Now; get this the scroll tab stays all the way to the right... won't acknowledge I am scrolling left. Here is a pic of that: Now, If I click and drag the slider to scroll right, I end up back where I started. Now, I close eCtune; load it again, and now I see this: Notice the scroll bar at the bottom? This is the second time this has happened; I can't produce a step that caused it, because, really, I didn't do anything but move the mouse around and click once to change a fuel value and presto; it all dissipeared. Now, specifically where I clicked was on the 2D graph of the fuel map, I was clicking to drag over a selection. Second bug: I get this error about 75% of the time after I click \"stop recording\" when logging: No clue why; it's been doing it for a while, but no specific steps can be found to reproduce. I'm not asking for a miracle on these errors; but thought I would make them public because I am pulling my hair out trying to figure out the steps to reproduce.

did you scroll the bars? i think it the tables were in the invisible region. if you press the table button. It closes if open and reopen the table window look first pic where you horizontal scroll bar indicator is... The other log recording bug.. Give me steps

I get that \"save marker errored with: Unable to read beyond the end of the stream.\" error all the time. It will usually happen after I've been running the program a while and have made a bunch of changes. Other than that there are no \"i did that and this happens\" time scenarios. Datalogging stops working after that too, but unplug usb and plug back in fixes that. (yes I'm running the latest drivers) I will try to screen capture and remember what I was doing exactly next time.

timmydogg wrote:I get that "save marker errored with: Unable to read beyond the end of the stream." error all the time. It will usually happen after I've been running the program a while and have made a bunch of changes.

That is a pretty accurate description of how it happens to me. I like to put my laptop into standby mode and resume where I left off... This is why it's hard for me to get a list of steps to reproduce on this one... I am waiting on it to happen shortly into a tuning session (with reload of eCtune shortly before the error). As for the scroll bars error:

calvin wrote: think it the tables were in the invisible region.

I agree; but no matter how much I tried, I could not find it... scroll tab would never move from the far right of the scrollbar... weather I clicked on the grey space to effectively "page-over", or drag the scroller all the way to the left; it would stay over there. I am kinda stumped by this bug; though I have only seen it twice. I think you might remember me posting about it once before. Clicking on the tables button did nothing; the scroll bar seemed to be infinitely scrolled to the right; and if I drag the scroll tab all the way over; the parameters window would dissapear (as if I had scrolled) but the tab would return to the far right where it's seen in the pic. If I clicked on the tab and unclicked, it would get back to the section where I started showing the parameters window again. When I reloaded eCtune, the scroll bar was noticeable larger (the virtual desktop space smaller) and when I scrolled to the tables window, the sensors pane, and dash pane were re-arranged from where I normally keep them; the sensors list was on the left; not right where it normally is, and the dash with customizable readouts was shifted noticeably to the left upper portion of the parent window.

Epiphany: Calvin, see if you get the error when it hits the vacuum out of range \"trace jumping\" alert; I think this may be what causes it. I am still trying to get exact steps; but tis hard to remember when your making lots of changes to maps on the street!

try your best.. I'll look at the marker code again

Yeah; I will try and give it a shot tonight or tomorrow night.. been working 10 hr days. But my car with the SC and no PCV system connection to it; it hits the error all the time, and I just haven't bothered to touch the highest vacuum portions.