Steve1436215419

Yeah stuff are logged. Its just the number of logs thats screwed up for me. Files attached...

When i open 'ECU log file download' only some of the 10 spots are populated. Sometimes maybe the 3 first are ok then spot 4,5 and 6 are blank while 7and 8 are ok and the last two are blank. I use the latest FW. Feel free to fix this. And its about time you implement loop logging...

Im using KPA on my car but that doesnt matter i assume. I use that sensor to. My calibration table starts at 0 to and ends at 345 kpa. 0 is really 100 kpa vacum so 100 kpa is actually atmospheric pressure. In your case 0 psi is 14.7 psi of vacum and 14.7 is atmosphere. We are dealing with absolute pressure here not gauge pressure.

Update! I just shorted 2 wires and did 3 backflips while singing cumbaya in a high tone, and behold! Contact! Well actually i decided to try me XP machine once more and the updater got contact with the ecu. So now im golden again. I did see some with issues like this on the vipec forum too so the problem seems to be 'real'

Hi Simon. No i do not. If you got a secret hard reset function on theese, now is the time to reveal it. Like: Short 2 wires and do 3 backflips while singing cumbaya in a high tone or something like that.

'unable to connect to the ECU. Please check....' Its the same message you get when you try to connect without the usb cable connected The firmware update says the same thing. 'Error. Could not connect to the ECU. Solutions....' Its a G4 Extreme

Bringing this old thread up again (i`m the OP) as it now seems this bug have bricked my ecu for good. Today i was to start the car up for the first time since october. Got snowy winters where i live. But i figured i would build some oilpressure before start, so i disabled the injectors in the software and saved the change, then toggled the power. The thing when i run into theese problems is that my fuelpump is on the whole time my ignition is on. Not just priming for a few secs as it usually does. This happend at this point but i was still able to connect. Then i tried to upgrade the FW but it failed at the end and im pretty sure it did cause it was in this 'faulty condition' (dont remember the fail message) Now it acts the same but im not able to connect with my laptop. ECU is on and i am able to see it in the device manager. From dev mangr it looks ok. Changing any settings here doesnt help. The fuelpump starts (and keeps going) when i turn on the IGN and my tacho needle does its dance as usual. I tried my crappy old XP machine this time too but that wont connect either. Tried to disconnect the battery for an hour but no luck. So now im stuck To adress you latest questions: Tried different versions of PC link. Yes Its 64 bit W7. No there is no hold power function in use. And just saying: this is NOT a problem with my wiering. Car has run for years with it as it is.

Its listed at COM3, so 'in range' I can try a different pc some other day but there is apparently something fishy. I found that other thread i read on the Vipec forum. Same problem as mine.

So it is a hardware problem after all?

I saw this mentioned in another thread a while ago and wanted to put this there, but could not find it again. So here is a new one. Since 4.9.1 (if i recall correctly) i have not ben able to update the fw with my W7 machine. Al that happends is the 'searching for ECU' message and it stops there. The wery first time i encountered this i fought it until i actually got to the point where you cycle the power. Thats where it stoped up again. I was afraid i had bricked the ECU as i had no chance of connecting to it again after that. That is until i dug up an old crappy XP machine i have laying around and installed PCLink on it. Then i was able to update everything as usual. The update between that and the newest i did not dare to perform incase something simlar happend and i kinda hoped something would have been done to the problem by now. Tried to update to 493 yesterday and its stil the same. Still have to use my old XP machine to update it. I have simlar problems when i want to load a new map to the ECU. Going through some dark places before i have to break out the XP again. For everything else W7 works fine for me. Whats up whit this? Is there some kind of regional settings on my laptop that may be screwing stuff up for me? Im in Norway.

Yeah im doing it that way myself. Running a v6 with one knock table for each bank.

We can only hope they hear our prayers but i wouldn't hold my breath. They have not so far so..... But yeah i agree completely. The tables get filled up very fast and if you want to run a 6 cylinder car with say individual cylinder knock control. 2 fuel and ignition maps. 2-3 boostmaps .... Well in the end you need to choose what means the most to you.... Its like i have to choose whether i want my car to run safe or fast. Cant do both.

Figured it out. Had to change my 'region and language' settings to english to get it to work. Which leads me to my next wish for the software...

Been waiting for this feature so that i could open my logs in other programs. Anyone actually tried to open one of these files in Excel? How did that turn out? Cause mine is rubbish.

Oh. And my 'table allocation' has suddenly filled up all 12 tables and shows as a big red announcement on tom of the screen... NEED more tables folks! this has been requested before by others. 12 tables fills up fast when you start to customize things. And again; Can we please have a edit button?

And why cant this forum have a EDIT button so that i can go back and get rid of all these embarrassing typos?

1 Upgrading the FW you need to take a stand on what frequency you want your CAN channels to run at. You cant select 'NONE' or something like that if you do not run CAN. So i selected 50Hz just to choose something. So now when i connect my laptop to the ecu it runs at 100% prosessorpower. Its an old laptop yes but it has been sufficient up until this upgrade. Wonder if the 50Hz CAN selection i made demands higher CPU effort? God knows cause i CANT go back and change it to say 2Hz (that was the lowest available option. So no i apparently ned a new laptop. 2 Who came up with the brilliant idea of the tree structure in the layout? I find it horrible! And buggy. I like to have a tab for every section. One for boost, one for idle and so on. On every tab i put all the relevant tables. Like on the Idle tab i put up the PID tables cause i run closed loop idle. Now if i want to swap it to open loop for some tuning the PID tables go blank. No problem. They are not used in open loop anyways. Swap it back to Closed loop when tuning is done. PID tables are.... STILL blank! To get it back i have to load the Layout again. Also if i set a table into a tab i want it to look like when i put it up there the next time i go to that tab. I dont want to scroll and do a bunch of clicks to get the table visible again.Terrible... What was wrong with how the old software looked anyways? Here is an example of how a tab ends up looking

Nope.. No limit.

Got a link to the DBW unit? cant find it...

Got a link to this DBW uinit? I cant for the life of me seem to find it

Just be aware that there are some differences between the wiring on the gtr vs gts. Things must be configured correctly for your car here (obviously). You could always use the input that was used for the NB lambda you are not using anymore. But it doesnt matter. That looks linear to me, so you could have used the other table type. Just remember that you only got 3 of each calibration table. So use them wisely.

Ah.. Now i understand where your coming from on the matter. Yes you can/should hook up your wideband to your ecu. You just pick one of the Analog inputs you have not used yet, and select 'wideband' from the dropdown menu. Now, as your WB is not listed in the software you will need to use one of the calibration tables. I dont know the WB you got so i cant tell if it gives a linear output. But i guess it does. As you probably have noticed Calibration table 1-3 difffers from cal 4-6. 4-6 are the ones to use with a linear signal. ie. 0V=10AFR, 2.5V=15AFR, 5V=20AFR. That would be a linear output. Now if it was 0V=10AFR, 2.5V=13AFR, 3V=16AFR, 5V=20AFR this would be unlinear output so you would need to use tables 1-3. Personally i have Cal 4 table configured as follows: output values = AFR Output value a = 10 AFR output value b = 20 AFR Input value a = 0.00 V Input value b = 5.0 V Again, this is MY settings with MY particular WB Once hooked up you need to verify that your gauge reads the same value as the ECU does. If not you need to sceew the cal numbers a bit until it matches My widebands reads 14,7 if i unplug the sensor from the controlbox, so its easy from me to check this. Dont know if its the same for the AEM. Read the manual i guess No you do not need the narrowband lambda if you hook up your WB.

Hi A. Welcome to the forum. Seems like your having fun with your project. Now. Im not sure i follow what your problem is. Or what it is you cant figure out. You ringed the analog input section in picture 3. Thats where you configure what inputpin your mapsensor is hooked up to. Here you also select what sensor it is. If your sensor is not listed you need to configure one of the calibration tables (at the bottom of this section) to fit the sensor you got. Then you click at the 'options tab at the very left top of your screen . Between the 'File' tab and the 'ECU Controls' tab. There at option 9 from the top you got 'MAP sensor calibration' (Right below 'TPS setup' which i can tell you also need to do)

As it is explained in the changelog the limiters work a little different now. If you have a limit at 8000 and a limit control range at 500 then your limiter will start kicking in at 7500 rpm. I bet this is what you are experiensing

Aha. That explains. Glad im not THAT blind.... Well..In that case, forget i brought it up fellas!