Dangerous Dave

  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Feedback


Everything posted by Dangerous Dave

  1. You should be able to add four new scalars in tunerpro (right click parameter list and click "insert new XDF parameter") and set the addresses to 0xF3AB, 0xF3AC, 0x1F3AB and 0x1F3AC and name them IAC open fault, IAC close fault, IAC open fault (upper bank), IAC close fault (upper bank) respectively. They should all be set to 1, change them to 0 to disable the MIL coming on.
  2. There is not a diagnostic disable in tunerpro for the idle control valve. I've had a look through the damos and unfortunately I can't see a diagnostic disable for the IAC. So it maybe possible to be do in the code somehow
  3. Don't worry, I made the same mistake years ago when I tried to hook up an AFR gauge to my narrowband. It's just part of the learning curve. I guess that back in the 90s wideband sensors were expensive and possibly not as reliable or available as a narrowband? or maybe the control technology was too expensive? Would need to research it for better clarification. The wideband sensor uses a different heater control method to the narrowband hence why a controller is needed (where if you hooked up the wideband direct to the ecu it wouldn't work properly and may even cause some damage).
  4. On our cars the O2 sensors are narrowband so can only read approx. 14 to 15 AFR (hence why your readings are going between 12 and 17 using your equation). You would need to fit a wideband sensor and controller to read a wider AFR range (to a separate gauge, you would need to modify the ecu binary to add it to the logging).
  5. What values are you trying to change from and to? It could be an issue with the step size as the injector opening voltages go in 0.0195V steps.
  6. Are you saving the binary as well (File>Save Bin)?
  7. You can add it manually in tunerpro, it's not listed in the XDF normally. Just add a new flag parameter and point it to 0xC8ED. Then you can change it to 1 or 0 for manual or auto. Fingers crossed it works
  8. Ok, had a quick look at both files. Your BMW MAF file looks ok apart from the alternative maps (used for map switching) are not the same as the normal maps. It could be these are being used for some reason. Plus, as you know, you've got it set to TCV Duty Cycle control only. The 80lbinjector file is a bit of a mess. It seems to be a 608 file (set for manual gearbox) but is missing the first 16 bytes so the whole binary is at an offset of -10hex and does not match a 607 file at all. It also appears to be the launch control version (maybe Rev6?). What I would do for both ECUs is start again with a base 608rev5b bin from HERE and copy all your modified values over. Set the hardware config (at 0xC8ED) to 0 for the auto car. That way you are ruling out the binary as an issue.
  9. Hmm. Upload your bin via dropbox and we'll have a look see if anything stands out
  10. Is it running the stock wastegate actuator? An old/weak (or even incorrectly adjusted) actuator can cause issues. Also check the "max TCV duty cycle" is set to 100% Have you checked the logging to see what the TCV duty cycle maxes out at when running? You'll need to upload via another hosting platform as attachments don't work on here work some reason so we can't download it. Maybe try dropbox?
  11. There used to be a signal description list for each pin but I can't find it any more. Fortunately I've got my own copy: https://www.dropbox.com/s/z0avaurxii29vth/Motronic44-1.jpg?dl=0
  12. Was the harness new or was it from another car? Sounds like you have it sorted Nice work dude! I guess comparing with other auto binaries may give us more info on that difference.
  13. Part numbers and flow rates need adding to the wikia then
  14. So the plot thickens. Like you say best to get flow tested to make sure you know the flow.
  15. According to the datasheets Greens should flow 453cc at 3 bar on N-Heptane but on petrol/gasoline they flow 413cc. How were yours tested?
  16. I wouldn't bother going back to oranges. Just tune the injector constant and the dead times to the greens. Greens flow approx. 413cc at 3bar. The injector constant for this should be 0.7656250. Then you will have to tune the dead times but for this you'll need a wideband O2 sensor. Some people have posted their dead times for greens on this thread, but they all differ for various reasons so be wary of using them. More info on tuning injectors here https://m44.fandom.com/wiki/Tuning_the_Injector_constant_and_dead_times Definitely get this sorted as the wrong fuelling can cause issues especially when the engine is under load
  17. Aaargh, I can't open the file. IDA says the database format is too old. What version are you using to view it?
  18. As far as I know the 'download Bin from Ostrich' feature doesn't work properly with default settings in tunerpro, I don't know if there is a workaround as I've never had the need to download the current bin. I save the current bin in a version/date order whenever I make changes, plus tunerpro saves a log of changes made. As for why the changes aren't having any effect, have you made sure you are changing the right map? As don't forget there are the alternative maps (unless you are making changes to them all) Also have you tried using the emulation feature of tunerpro?
  19. Anything is possible 🙂 It's just getting the code written and working that is the problem. Correct me if I'm wrong but as I understand it the mapswitching is in the pre-start routine so would need something setting up to run in the running engine routine. The problem then is when a map is switched would this affect the program and/or cause issues with the engine. Or maybe I'm just overthinking it.
  20. There are a few posts about the Spartan controller and the issue with output impedance, someone had an issue and built a low pass filter to condition the signal. The wiki also doesn't state anything about the issue with the Spartan controller, I'll add something. Though from how quiet this thread is nowadays it seems people have moved on? In the end it was a post I found from Venderbroeck saying that the tank pressure input had the best result for the Spartan controller as the non-linearity was non existent on that channel. Yeah I knew A19 had an offset (0.7V if I recall) so I was using the accelerometer ground as the connector was already wired in and my 850 doesn't have the accelerometer, then I tried A18, then I swapped the pin to the tank pressure input which worked. Yes the accelerometer channel does work for logging, just needs some code adding to the binary. I've also got the barometric sensor channel working as some code is needed to switch the channel
  21. So I've been having an issue with my wideband values being out by 0.2V (using a Spartan controller) I was using the accelerometer input. Tried using different grounds to no avail. Today I switched the pin in the ecu socket to use the tank pressure input (from B32 to B31 as my car does not have that pin populated) and the wideband values are now spot on (my Spartan controller has a display built in). Took me a while to get to this point as there is a lot of conflicting info in this thread about grounds and filters, etc.
  22. I can only see just the two fan speeds in the 98MY wiring diagrams. There's only two pins allocated on the ecu one for high speed and one for low speed. Maybe the different modes share run times and speed thresholds.
  23. No worries. Coolant temp is the temp in degreesC that the different fan speeds kick in. The speed threshold is in km/h and I guess stops the fan mode kicking in over that speed. The fan runtime is in seconds and each step is 3.06 seconds. Not sure why there are 5 speeds for the Coolant temp and less for the speed threshold and run time. These are all the values listed in the damos.
  24. There isn't any documentation as far as I know but it's pretty self explanatory. Fan mode 1 is the most common one that kicks in at 102degC. The values are stock as they are in the damos file and the values are the same for other bins too. The only value I'm not sure is the 4th fan mode, as the speed and run time is a lot lower than the others.
  25. Have you tried changing the allocated Com port number in device manager? Maybe try COM9 and change the settings to match in tunerpro