Jump to content

Dandeman

Members
  • Posts

    12
  • Joined

  • Last visited

Dandeman's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hello Adam! I turned off a bunch of settings or set them to open loop or off (thanks koracing - this helped). Idle, lambda control, etc. Car is now basically in open loop. Checked base timing at high idle - this was off 10 degrees and now corrected to -318*. Changed / calculated master fuel and fuel mixtures based on what I was getting before for a mixture number and adapted the base file mixture. Unfortunately I do not have data from Bosch for my injectors which would have helped. Even though, I did get pretty close - within a couple percent at idle. Car now idles at a good set point and I can actuate the throttle without it wanting to die, though it still wants to go lean. I now feel like it is mixture / timing as I can adjust this and get differing results. Also I feel like I can now get it into the trailer to get to the dyno and be productive there. Trigger scope is attached. Also attached the main file again. Please provide any feedback if you see something interesting. FYI - I believe the back fire thing is related to actuating the ignition switch from run (position 2) back to position 1. US cars need to do this, which resets the ability to engage the starter from the switch, but also cycles the ecu as you go back to position 2. I'm guessing there is a signal sent from the ecu at initial start up, and this may ignite fuel in a cylinder if it was just previously running. This was solved by using a remote starter switch. TriggerScopeLog_DanBMW-12-28-20.llgx BMW E36 G4X Dan Initial Set up.pclx
  2. Hello Adam! Yes - running the M50 harness and components. Sorry - the "US S52" if converted back to OBDI, or M50/S50 will run just fine - all single vanos. Apologies for the confusion - I should have been more specific. Adding or subtracting master fuel did not change this condition. Also, I feel like when you first started the car hot, it took a few seconds for the idle to come up to set point from being very low - like 600 rpm. I will try and get a triggerscope to you at some point. I do need to check timing, even at idle. Also need to check all lines in the intake as the backfire thing may have popped a line off - though I would not think this would change the MAP readings.
  3. Feeling super new ... Initial start up this weekend. The car will idle but as soon as you touch the throttle it will die. Looks like it will go way lean. It also does not sound right - but obviously not able to check base timing. Also I have the back fire issue when you cycle the key and restart the ecu. I do need to check to see if there is a vacuum leak caused by this misfire. I feel like I have not turned something off, and there is a conflict in the software. This car does have mild cams and bigger injectors than stock. I have attached the file I was using. Any additional direction would be helpful. Thx!! BMW E36 G4X Dan Initial Set up.pclx
  4. Knock Control -- I would like to have knock sensor inputs from the on board sensors - 2x. I see there are pins 69 and 70 on the pin out list. I am unable to find how to connect to these in PCLink and I do not see them used for any inputs. Wondering how to do this so I can set up knock conditions. Thx!
  5. Hello All! Sending this ecu back to the point of sale vendor - you should see this from them as an issue to fix. Through a alternate dealer, we have also identified that there is a hardware issue. I have since received an alternate G4X that is up and running. Thank you for all the help!!
  6. Tried this - With power to the ecu, I hover over the "ECU Controls" tab, and I clicked the <update firmware> tab. Please see the results below. Please advise - appears that it need some communication. Or I am not clicking the correct tabs. Thx, Dan
  7. 12v power at pin 54 and ground at pin 34 - no communication still - get the error message "unable to connect ... cycle ecu" Checking for power and ground at the connector side - I have ground at 34, but also have a ground at 54 - both without the ecu connected to the connector. With the ecu connected I have 12v at 54 and ground at 34
  8. okay - so different computer and a fresh install of G4+ I get this error when powering on the ecu And I get these settings in device manager I have these settings in <connections> in PCLink Thoughts? This is pretty much same as before.
  9. No Can devices. I had an expansion loom installed (nothing there connected yet) but have since removed it. The connection settings have been the parameters above - I have moved them around to see if there was any different results. I will put them back to this. Will try a different computer today to see if we can get a different result there. Any other thoughts? Only thing that seems weird is that when the ecu is powered, it will run the fuel pump circuit for an extended period of time, not the typical 3-4 seconds for priming. Also - the ecu came with the communication cable attached to the ecu - is this normal, or could there be an issue with this connection? Just as a sanity check yesterday, reconnected the old dme to the car, and it stated and ran - albeit it was flooded. May have an additional issue with a leaking injector, but also see above for the pumps running and something else maybe happening as well. Also checked battery power before starting - 12.2v. Thank you in advance!
  10. Thank you for the quick reply Here you go - Let me know if you need more.
  11. Hello! I have a new ecu in the bmw and it will not connect to my pc. The PC does see the usb in device manager, and the ecu has a green light - and is cycling the fuel pump. I have looked at other forum posts, and tried a few of the potential fixes for similar issues. Usb driver, using what I believe is the correct software. I did yesterday get the note that the usb was connected but to cycle the ecu. I do not have this today after removing the xsl harness and trying again. Thank you in advance for help. Dan
×
×
  • Create New...