|
RomRaider
Documentation
Community
Developers
|
| Author |
Message |
|
nobundo
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Mon Feb 10, 2020 1:02 pm |
|
 |
| Newbie |
Joined: Fri Jan 04, 2019 1:28 pm Posts: 12 Location: Latvia, Riga
|
janithdg wrote: ba114 wrote: janithdg wrote: After I did the conversion I started getting the dtc 244 (Segment timing faulty, flywheel adaptation) and and I reverted to MS41.0 and no errors afterwards, am I missing out something in the conversion, And I did disable misfire detection i have put in a new CPS for the error, still the error was there Did you clear adaptions after you flashed to ms41.2? Yep, after every flash I clear adaptations Hello, I've met the same error after similar conversion, but with misfire detection turned on. After few days of diagnosis I've checked the TDC and timing marks and discovered, that vibration damper (which also has trigger wheel for crankshaft position sensor) TDC mark couldn't be sinchronised with a mark on the timing case when 1st cylinder is blocked in TDC using flywheel tool. The root was a part called "Woodruff key"in ETK, which positions vibration damper hub on the crankshaft (picture added). Probably, it was damaged due not completely tightened central bolt (TIS says 410NM). Now I'm assembling the engine, but I'm pretty sure this DTC 244 should be gone.
You do not have the required permissions to view the files attached to this post.
_________________ If there is a spark and fuel - you can start even a stick.
|
|
| Top |
|
 |
|
smallspeed
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Mon Feb 10, 2020 1:35 pm |
|
 |
| Newbie |
Joined: Fri Mar 08, 2019 9:34 am Posts: 38
|
That must be an intentional misalignment key? I can't imagine there's enough torque applied through the drive pulley to "smear" a hardened steel key like that..?! 
|
|
| Top |
|
 |
|
nobundo
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Mon Feb 10, 2020 2:23 pm |
|
 |
| Newbie |
Joined: Fri Jan 04, 2019 1:28 pm Posts: 12 Location: Latvia, Riga
|
smallspeed wrote: That must be an intentional misalignment key? I can't imagine there's enough torque applied through the drive pulley to "smear" a hardened steel key like that..?!  Engine is from AT E39, I doubt someone could do something like this for "tuning". As I said, crankshaft central bolt wasn't tightened to torque, because I loosened it with hand tools, I can't say there was more than 100nm by feeling.
_________________ If there is a spark and fuel - you can start even a stick.
|
|
| Top |
|
 |
|
dx4picco
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Mon Feb 10, 2020 7:32 pm |
|
 |
| Experienced |
Joined: Thu Nov 15, 2018 3:00 pm Posts: 718 Location: Europe, France (French/English)
|
smallspeed wrote: That must be an intentional misalignment key? I can't imagine there's enough torque applied through the drive pulley to "smear" a hardened steel key like that..?!  Vibrations and harmonics can do a lot of damage. ALOT like splitting a crankshaft in half. so matting a keyway like this is peanuts.
|
|
| Top |
|
 |
|
nobundo
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Sun Feb 16, 2020 5:23 pm |
|
 |
| Newbie |
Joined: Fri Jan 04, 2019 1:28 pm Posts: 12 Location: Latvia, Riga
|
dx4picco wrote: smallspeed wrote: That must be an intentional misalignment key? I can't imagine there's enough torque applied through the drive pulley to "smear" a hardened steel key like that..?!  Vibrations and harmonics can do a lot of damage. ALOT like splitting a crankshaft in half. so matting a keyway like this is peanuts. Engine assembled, works significantly better, no DTC 244 anymore, knock detection working correctly!
_________________ If there is a spark and fuel - you can start even a stick.
|
|
| Top |
|
 |
|
gadziuWLKP
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Wed Mar 18, 2020 8:57 am |
|
 |
| Experienced |
Joined: Sat Jan 06, 2018 9:15 pm Posts: 233 Location: Europe/Poland
|
|
I noticed one problem when I wanted to connect the AFR probe to the second off channel because I have only used one O2 for a long time. Namely, despite the off channel, you can see in the logs for the integrator of the second O2 before the catalyst certain values. they appear to be the average correction values from the O2 probe reading on the first channel. So, I think - using a second unused channel is not possible in MS41.2?
You do not have the required permissions to view the files attached to this post.
_________________ E36 Compact M50B28NV + V, turbo, 352hp 485Nm. 0-100 6.1s, 0-200 14s. MS41 Powered by Romraider.
|
|
| Top |
|
 |
|
ba114
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Wed Mar 18, 2020 8:32 pm |
|
 |
| Experienced |
Joined: Wed Oct 21, 2015 6:36 am Posts: 980
|
|
You have to connect to a rear o2 sensor, not the front
|
|
| Top |
|
 |
|
gadziuWLKP
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Tue Apr 14, 2020 11:43 am |
|
 |
| Experienced |
Joined: Sat Jan 06, 2018 9:15 pm Posts: 233 Location: Europe/Poland
|
ba114 wrote: You have to connect to a rear o2 sensor, not the front rear o2, with the rest all o2 inputs I set have some values. Either max scaling value or changing values. It is probably illogical to connect an analog input to the inputs where MS41 is already reading some voltage. I have the MS41.0 861 ECU with mrf582's MS41.3 custom code. Only when TPS is ticked as input. Has anyone managed to connect the analog input on the 861 controller? By default there were two probes in front of the catalyst in the 861 controller and none after the catalyst. The engine did not have an EGR and an air pump. EDITED (mrf582) - Clarified that you are using MS41.0 HW with MS41.2 base code with MS41.3 custom code patched in.
_________________ E36 Compact M50B28NV + V, turbo, 352hp 485Nm. 0-100 6.1s, 0-200 14s. MS41 Powered by Romraider.
|
|
| Top |
|
 |
|
ba114
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Tue Apr 14, 2020 11:25 pm |
|
 |
| Experienced |
Joined: Wed Oct 21, 2015 6:36 am Posts: 980
|
|
I'm struggling to understand your post. Why do you keep mentioning front o2 sensors if you're using the post cat inputs?
|
|
| Top |
|
 |
|
tjwasiak
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Tue Apr 14, 2020 11:56 pm |
|
 |
| Experienced |
Joined: Tue Nov 07, 2017 1:46 am Posts: 153 Location: Warsaw, Poland, (Polish, English)
|
|
He was trying to use bank 2 front sensor as he is using single bank tune. European MS41.0 based cars does not have wiring for post-cat sensors so it is easier to use what is already wired... Unfortunately it seems this could not be done as ECU still uses trims for both banks at least partially storing some data obtained from bank 1 sensor as bank 2 fuel trims.
|
|
| Top |
|
 |
|
ba114
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Wed Apr 15, 2020 1:57 am |
|
 |
| Experienced |
Joined: Wed Oct 21, 2015 6:36 am Posts: 980
|
|
if you use pre-cat o2 inputs, regardless of if you have it set to single bank, it will continue to read whatever voltage is input and interpret that as a narrowband input and adjust trims accordingly.
Do not attempt to use front (pre-cat) o2 sensors as a voltage input.
Only rear o2 inputs can be used.
|
|
| Top |
|
 |
|
mrf582
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Fri Apr 17, 2020 3:41 pm |
|
 |
| Senior Member |
Joined: Fri Feb 10, 2006 11:04 pm Posts: 2661 Location: RIP
|
|
Without checking this empirically, my thought was:
if Single Channel O2 mode is set, then Bank 2 Front O2 is not contributing to fuel calcs. So I thought, maybe we could connect something else there and repurpose it.
But, not sure how the HW and SW react to this:
If an analog input is left floating, the HW might pull it high as default? During gadziu's test, he hadn't yet connected an aux. 0-5V sensor.
I'll have to check the code to see where I'm taking the variable from. Maybe the ECU 'copies' the data from Bank 1 into the Bank 2 data when Single Channel is selected? But I thought I tried to get the 'raw voltage' in my custom code.
_________________ MS41 Project Leader & Co-Developer (2012 - 2023) MS41.3 https://sites.google.com/site/openms41/custom-code---ms41-3 MS41 ECU Portal https://sites.google.com/site/openms41/ms41-ecu-portal
|
|
| Top |
|
 |
|
gadziuWLKP
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Fri Apr 17, 2020 8:39 pm |
|
 |
| Experienced |
Joined: Sat Jan 06, 2018 9:15 pm Posts: 233 Location: Europe/Poland
|
Hello. Your suggestions are correct. At the beginning I will add that I currently drive one O2 collective, set as a single channel. There is no additional analog input connected yet. I made logs of my behavior today in a few cases. 1. My existing BIN, where the analogue inputs are switched off as soon as possible. WidebandO2 - disabled Ethanol - disabled MAP - disabled Oil Presure - TPS Fuel Presure - TPS Log with description A. 2. Logs after uploading BIN with attached analog inputs The engine won't start, the fuel pump works, doesn't start. WidebandO2 - front O2 bank2 Ethanol - rear O2 bank1 MAP - Evap presure (I don't have this sensor) Oil Presure - TPS Fuel Presure - TPS Log with description B 3. Logs after uploading the BIN with only the O2 bank2 input connected. The engine is operating normally - it took a while for the O2 probe to work - it cooled down. As you can see, I still have a voltage <5V at the O2 bank 2 input. It is a bit strange, because this input is empty and according to my electrical knowledge I should rather not give additional voltage from the AFR controller, which in the external device displays the AFR value after the same output. WidebandO2 - front O2 bank2 Ethanol - disabled MAP - disabled Oil Presure - TPS Fuel Presure - TPS Log with description C. As can be seen in the logs, some of the inputs display the values on the engine not running. As for the O2 inputs behind the catalyst, my car has no beam prepared for them. Originally, the 861 controller worked with two O2 upstream of the catalyst. The ECU itself has only one electronics system dps926748-r7004 as shown in the topic viewtopic.php?f=42&t=12913In MS41.2 we have 4 systems. My 861 doesn't even have a way out of the MIL led. Now i have to try on MS41.3 but on MS41.2 also O2 front1 have the same behavior.
You do not have the required permissions to view the files attached to this post.
_________________ E36 Compact M50B28NV + V, turbo, 352hp 485Nm. 0-100 6.1s, 0-200 14s. MS41 Powered by Romraider.
|
|
| Top |
|
 |
|
gadziuWLKP
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Wed Apr 22, 2020 8:08 pm |
|
 |
| Experienced |
Joined: Sat Jan 06, 2018 9:15 pm Posts: 233 Location: Europe/Poland
|
gadziuWLKP wrote: Hello. Your suggestions are correct. At the beginning I will add that I currently drive one O2 collective, set as a single channel. There is no additional analog input connected yet. I made logs of my behavior today in a few cases. 1. My existing BIN, where the analogue inputs are switched off as soon as possible. WidebandO2 - disabled Ethanol - disabled MAP - disabled Oil Presure - TPS Fuel Presure - TPS Log with description A. 2. Logs after uploading BIN with attached analog inputs The engine won't start, the fuel pump works, doesn't start. WidebandO2 - front O2 bank2 Ethanol - rear O2 bank1 MAP - Evap presure (I don't have this sensor) Oil Presure - TPS Fuel Presure - TPS Log with description B 3. Logs after uploading the BIN with only the O2 bank2 input connected. The engine is operating normally - it took a while for the O2 probe to work - it cooled down. As you can see, I still have a voltage <5V at the O2 bank 2 input. It is a bit strange, because this input is empty and according to my electrical knowledge I should rather not give additional voltage from the AFR controller, which in the external device displays the AFR value after the same output. WidebandO2 - front O2 bank2 Ethanol - disabled MAP - disabled Oil Presure - TPS Fuel Presure - TPS Log with description C. As can be seen in the logs, some of the inputs display the values on the engine not running. As for the O2 inputs behind the catalyst, my car has no beam prepared for them. Originally, the 861 controller worked with two O2 upstream of the catalyst. The ECU itself has only one electronics system dps926748-r7004 as shown in the topic viewtopic.php?f=42&t=12913In MS41.2 we have 4 systems. My 861 doesn't even have a way out of the MIL led. Now i have to try on MS41.3 but on MS41.2 also O2 front1 have the same behavior. I pay honor. My doubt was unnecessary. Today I dared to connect MAP and AFR to the inputs. The inputs work properly, after calibration the sensor values show the same as my external device - I log in to both. The values are in line with reality. So it works. By the way I looked at my engine harness and it turned out that the ECU plug lacks pins for the probes behind the catalyst, MIL lights and the Evap presure sensor. Therefore, using these inputs is not possible at the moment.
_________________ E36 Compact M50B28NV + V, turbo, 352hp 485Nm. 0-100 6.1s, 0-200 14s. MS41 Powered by Romraider.
|
|
| Top |
|
 |
|
mrf582
|
Post subject: Re: DEVELOPMENT : MS41.0 to MS41.2 Conversion Posted: Wed Apr 22, 2020 10:30 pm |
|
 |
| Senior Member |
Joined: Fri Feb 10, 2006 11:04 pm Posts: 2661 Location: RIP
|
Your engine didn't start during Log # 2 because you selected this: Ethanol - rear O2 bank1 : without connecting an actual Ethanol sensor. The Ethanol logic gets enabled as soon as you tell the ECU you have connected something as Ethanol input. I have put in a default Fuel Trim for Eth in there so people should be able to just install the hardware, flip one table in the tune and run the engine on Ethanol as a base tune. By not connecting the proper sensor, the code still ran and generated a really high Fuel Trim to add to your cranking tables. This flooded the engine and 'cooled off' your existing O2 sensor. No big deal though, just nice to know what/why/how something happened  Thanks for posting such detailed data on the topic of custom 0-5V inputs. If I understand you correctly: Once you selected the correct inputs and set them to their correct scalings, you were able to log the correct values as expected? Did you say you connected your external wideband to the front O2 sensor wiring and selected that as input in the Wideband setup tables? And also tried to 'spoof' the MAP table into using the front O2 as input and with the 'correct' scalings, it also showed the correct value? Also, in 'psi or kpa' instead of AFR? If so, that's good to know. I had only run these tests on my car using TPS voltage. That validated 90% of it especially the code that does the y=mx+b calculation. I actually use two different function types: : one for MAP that uses full 2 byte precision (for future Speed Density use) : the rest for AFR, Oil/Fuel Pressure, Ethanol use half 1 byte precision since there is enough resolution there. The MS41 Wiki on Custom Code has the actual resolution values posted. Your additional testing proved out that the actual variable I've selected for repurposing is correct for Front O2 sensor. So that can now also be classified as confirmed.
_________________ MS41 Project Leader & Co-Developer (2012 - 2023) MS41.3 https://sites.google.com/site/openms41/custom-code---ms41-3 MS41 ECU Portal https://sites.google.com/site/openms41/ms41-ecu-portal
|
|
| Top |
|
 |
Who is online |
Users browsing this forum: No registered users and 1 guest |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|
|