Trying to do some logs on my 7.3 X.

Surprisingly the first time I connected the VCI to the computer and then to the X everything worked. I was able to select sensors to watch and even did a short log of cold start and run for a short time. Then all the sensors I was watching in live data started to drop to 0. In short time all of the sensors only showed 0 even though the connection was still there. Re-selecting the sensors or anything I did wouldn't make it work again. SO I closed it down and tried to reconnect and now I can't get the connection to work again. I tried unplugging and waiting and plugging everything in again about 10 times now. I tried shutting the X off and restarting and all.

I have had this same problem before while trying to log our work truck as well.

Reading I found the "heartbeat" option and have selected it and will try it out to see if that helps but I still can't connect to the vehicle.

This thing is so frustrating.

 

Oh yeah, and every time I click to open the AE program it pops up a warning "Failed to create new session". It has done this since I got it and on two separate computers.

 

Oh yeah, and when I plug the VCI usb into the computer all three lights light up, red, amber, blue and stay lit.

 

Ok I tried some stuff.

I used the J185PWM and the "non-obd2" connect and it worked great for like three times. Then all of a sudden that didn't want to connect any more like the problem I was having before.

So then I tried CAN and "non-obd2" and that worked again great for a few few connects. But then I was doing a log and all the sensor values dropped to 0 again like the one problem I was having before.

So right now I am trying CAN (28? bit) and "Non-obd2" and all seems to be working like it should. It connects right away and it is still up and showing sensor values as I type this with the X running. Hope this works out!

If I save session all this stuff should save and work the next time I bring out AE yes?

 

That's the one. Is the Auto-connect box empty or checked? That automatic stuff can make a mess if you start in the wrong sequence.

Your version of the software may have a bug, or your computer may need a reboot.

As to the boost dilemma, I am reluctant to mention this because it's not as common as leaks: Who's to say the turbo is at the top of its game? I'm not saying shot... I'm saying diminished performance. Looking at about 10 PSI spread between MAP and EBP, that's about normal for a stock turbo at WOT- depending on other air mods. As far as testing a turbo goes, all we have is our eyes and fingers. Feel the turbo shaft in-out play and really look closely at the compressor blades.

 

I unchecked the auto-connect long ago. But just yesterday I actually tried the manual settings instead of the auto-detect. After making the last post I was having a problem again connecting and ended up using the second to the bottom selection for the connection. I forget what the letters and numbers were. It seems as you go down the list of "connect options" the refresh rate of the "live data" gets slower and slower.

After getting a log and watching some numbers I did a leak test and didn't find anything. I have to get the mirror out and check around the baby butt to make sure it is all sealed up good after I did "the work" a few years ago.

I do have a log graph I would like to post up but am unsure how you guys get those big clear pics of just the graph itself.

 

Can someone see this? lol The last WOT on the graph was up to 95mph. Max is 16psi boost.

 

This is where many people think I'm just being ****. When I set up my sessions, I put sensible maximums on each PID. AE is made for all vehicles, so it has generic maximums as default for each PID. 8000 RPM? That's an interesting maximum that we're never gunna see on a 7.3L. Even if one fails to put a max 3500 RPM while setting up the logging, you can change the scale every time you open that log - but you can't save the scale setting after the log is recorded. If you open the CSV file with Notepad, you can permanently change the maximums that way, but be careful in there - changing the format will render the log unreadable by AE.

So... you can open the log, and a PID selection menu will pop up. This is where you check the box for each PID you want to display, and this is also where you type a new maximum of 3500 for RPM and 50 for EBP and MAP.

 

Sorry for the delay, been in the shop.

Turn on Windows, connect vci, wait for it to connect.

Then open giotto.

If you're using v13, use the help update email to get the update. The shipping version 2 months ago had the problems you mention.

Try to open aa logged session. If it crashes...update.

What year 7.3?

02 is manual, pwm1850, non-obdii only
03 6.0 is autodetect, obdii

Hope this helps.

 

Hey Camper, Did V13.2 cough up any surprises beyond the "Save Sessions" Issue?? I looked thru the Crib notes on the update, but as usual, pretty cryptic......Hows the stability?
Thanks.

 

I got mime around a year ago or so now. I have heard of a couple problems with the update so I have been holding off. But if it would fix these connection issues I would be willing to do it. I have have the email saved for the update.

 

What Version are you using right Now?

 

I'm using version 13.1.0

It came with 13.0.1

If you have 13.0.1, go ahead and upgrade. It was FULL of bugs! Connection issues, layout, crashing, failure to open, couldn't open a logged session for playback, etc.

I don't know where, but at least v13.x removed the ability to save the session configuration (PIDs to monitor, scales, etc)

I still get the occasional startup problems, such as not activating the enhanced Ford bundle, can't find adapter or adapter not compatible, etc.

I simply close the program, cycle the key, maybe remove the adapter with key off and start over. Plugging it in after windows is completely started and not opening Giotto until the 'New Hardware da-ding" is heard and then waiting a few seconds is the repeatable way to consistently correct the problem.

The interface is funky, not sure if just this version or what

1. I have to maximize the screen, and even then on my notebook the bottom PID selection boxes are barely visible/clickable

2. If you open the drop down box on a PID to monitor (live data tab) and your mouse is over the selection box (ie using touchscreen), it immediately takes that row as the selection.

3. If you have a dialog or selection open and hit ESC, Giotto disconnects from the vehicle

All in all, okay. But I really expected a higher level of refinement and clean and stable functionality from a program on V13 that has been in widespread use for many years and at $450.

 

Cool, I just requested V13.2. They just released it 6/9. At this point, I'm just hoping its stable...They fixed a few more bugs and added a few more lost sensors and supposedly fixed the crashes. We'll see. They also stated that some of the issue of it working with Win 8.1 was because Giotto was not playing well with IE V9. When I get the update on my Laptop I will violate it vigorously and report in on the results.

Peace Out!

P.S. Don't forget about the proper start up sequence( Win,/Giotto/plug in VCI/ go to help-Activate, in case it didn't already discover./Hit connect..).Should auto-run after that and push a few buttons.

 

New version, eh? If we're lucky, I may need to edit the AE fail thread.