Roll Posted June 28 Report Share Posted June 28 On 6/24/2021 at 8:48 PM, Chuck W said: Motronic Suite has the bins for the 0261204444 and 0261204446, which are shown as the ECUs for the B5204T3. I double checked and I have ending with 446, which is great! Looking forward to start tuning it! Quote Link to comment Share on other sites More sharing options...
bmkamill Posted July 5 Report Share Posted July 5 (edited) hey my setup is b5234t 2001 on motronic 4.4. cop update, 0.7mm BKR7E spark plugs, turbo gtx2867r ar0.83, Japanese exhaust manifold r. 3 "throttle, engine forged connecting rods, intake system 550x230x65, exhaust system dp3" -> 2.75 "-> 2x2.5" boost 1.4-1.5bar the problem is with the ignition I put logs. Do you think the problem is with the car, or is the ignition just too aggressive for the load? fuel is pb 98.maf 3 "multiplied by 1.64 logi 3b 4b.xdl 12345.xdl Edited July 5 by bmkamill I added information about the update of the maf Quote Link to comment Share on other sites More sharing options...
Buddy-T5 Posted August 24 Report Share Posted August 24 Who can share 609.bin? It was available for downloading on m44.wikia several years ago but now only 607 and 608. Thank you. Quote Link to comment Share on other sites More sharing options...
Turboforslund Posted August 24 Report Share Posted August 24 I have it, let me know all the last digits. Is it 0261204609_1037359880.bin or the 0261204609_1037357528.bin? // Turboforslund Quote Link to comment Share on other sites More sharing options...
Buddy-T5 Posted August 24 Report Share Posted August 24 880 Quote Link to comment Share on other sites More sharing options...
Turboforslund Posted August 24 Report Share Posted August 24 Hope this works fine: https://www.dropbox.com/s/ul288xcbcmqpzqr/0261204609_1037359880_1.bin?dl=0 // Turboforslund 1 Quote Link to comment Share on other sites More sharing options...
ItalianT5 Posted September 7 Report Share Posted September 7 Hi guys, I am currently trying to get data logging fully working on my '98 V70 2.0 T5 AWD. I can log all the original values, but when it comes to connecting my AEM UEGO WB to either the rear O2 or the tank pressure sensor channel, all I get is some wrong ADC values. I've connected the white AEM wire (0-5V analog output) to either B31 (tank pressure channel) or A34 (rear O2 channel) and the brown wire (signal ground) to A18 (the main ground of the ECU). The resulting voltage displayed in TunerPro is a constant zero for the rear O2 channel and a fluctuating voltage for the tank pressure channel, which depends on RPM and not on the voltage which is supplied by the analog output of the AEM UEGO. Maybe there is some problem regarding my ADX or XDF file, so I will upload them. In my BIN file data logging for both channels is activated (non-zero value) and the diagnostics are disabled, so this should not lead to my problem. If someone has installed the same WB and has got a working ADX file, let me know, maybe you could share this file with me. Thanks for your help in advance, Joel rev5.adx rev5b.xdf Quote Link to comment Share on other sites More sharing options...
Turboforslund Posted September 7 Report Share Posted September 7 (edited) Hi, My WB installation: Comments from a post in 2015: "Just wanted to add some ground-info regarding my installation of spartan wb. My wb uses pin A13 (power ground) as the only ground source, no extra grounding needed. My spartan pinout: Red = A27 (power supply from the main relay) White + Black = A13 (power ground) Green = B31 (tank pressure 0-5V signal) ADX formula: (X/375)+0.68 (gives a lambda value in the range 0.68-1.36) If you want it in AFR then put *14.7 in the end. Example: ((X/375)+0.68)*14.7 Lambda values x 14.7 should be more accurate then using the AFR formula from 10 to 20 AFR." Mine is a Spartan WB controller but the pinout and adx tips might give you a hint. Best of luck. // Turboforslund Edited September 7 by Turboforslund Quote Link to comment Share on other sites More sharing options...
ItalianT5 Posted September 7 Report Share Posted September 7 Thank you for your help @Turboforslund. In the end it turned out that my .bin did not work in combination with the .adx file. If someone has similar problems, first check that you are using .bin and .adx files that fit to each other! Quote Link to comment Share on other sites More sharing options...
ItalianT5 Posted September 9 Report Share Posted September 9 Now that I am able to log all the important data, I recognized that at high loads the actual fuel correction does not match with the programmed fuel correction in the VE table. Values up to 1.5 are used instead of the programmed 1.3x while WOT enrichment is 1.0 for all RPM values, which leads to way too low AFR's. Can someone tell me which table has also an effect on the actual fuel correction? Quote Link to comment Share on other sites More sharing options...
versus Posted Monday at 11:28 AM Report Share Posted Monday at 11:28 AM (edited) There was some fan function discussion 10 pages back. Has anybody made some investigation in these? I discovered that one of the cars i have uses speed 2 postition which is 115C by default, its 98 LPT. All the other cars i have touched use speed 1 102C. Thats very weird seeing car running at 115C degrees. It also blowed one of the coolant hoses recenly. I reduced speed 2 and now fan kicks in before. But still i can't understand how this can be. Was the same with original ecu and the remapped custom 608 bin. Edit: It was bad fan relay. Speed 1 not operating. Had one spare and now its good. I always thought low speed is for AC and high speed for engine cooling. But Speed 1 corresponds to lower speed fan and speed 2 kicks in when things are getting out of hands at high temps Maybe when AC is active and fan is at low speed, then on ecu command speed 1 acts as high fan speed. Because im almost sure it will spin faster then. Edited 15 hours ago by versus Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.