BMW S50 trigger support in G4X

[link_user]

Hi,  in the old G4+ version there is support for the BMW S50 trigger pattern. In the new G4X there is no BMW S50 trigger type in the drop down list. I went with the latest G4X Ecu to enjoy all the new features and enhancements.

Frimware version installed on the ECU is 6.19.37

I found BMW S52,S54, M52 but no S50 trigger type.  Since this is the S50B30 engine with the single Vanos I need the S50 trigger type. The old G4+ works nicely with the S50 single Vanos. There are a bunch of topics regarding the S50 in the G4+ section of the forum.

I need some advice on how to solve this problem. 

 

[Adamw]

I suspect we left it out as we have very little info for it in our library.  Can you give us a triggerscope while cranking and I'll talk to the firmware team on Monday to see if there are any existing options that will work, or how quickly it can be added if not.

Also are we talking the Euro or US S50B30?

[dx4picco]

euro S50 has dual vanos, so I guess its not that one as he specifies single vanos.

maybe a m50 vanos like?

[Adamw]

I think it is only the S50B32 that got the double vanos.  

[Mustang]

Adamw is right, Euro S50B30 has single, stepless high-pressure inlet Vanos, Euro S50B32 has stepless high-pressure double Vanos.

 

[link_user]

Euro S50B30. single Vanos.   Please add this trigger pattern to the G4X.    I went with the G4X to support the new product line and use all the benefits of the new product.  The car is ready to go, just waiting for the trigger support.

Let me know if the information provided below is enough or I need to provide more triggerscope data?

 

Here are links to the G4+ forum, with all the info about triggerscope and wiring. You included even a basemap.

 

 

 

It was supported even in the old Vipec ECU

 

[Adamw]

2 hours ago, Adamw said:

Can you give us a triggerscope while cranking

 

[link_user]

Will do on Monday, thank you for quick reply.

 

[link_user]

Here are some logs and the calibration file.  How can I view the triggerscope logs once I save them? 
The DI2 input reads the additional sensor on the input camshat with the single Vanos.    DI1 is used for the VSS sensor with the E36X plugin.

I noticed the  G4X interface is a little bit different than the old G4+ when selecting the digital inputs.  I hope the settings in the calibration are correct.
If not I hope for some help to get them right. All sensors are reluctor style , I measured them at 1100 Ohm acrross the two wires.

 

bmw2TriggerScopeLog.llgx bmw3TriggerScopeLog.llgx bmwTriggerScopeLog.llgx m3_e36new.pclx

[Adamw]

You havent captured anything in any of those scopes.  Well, #2 does show a couple of teeth right at the end.

So this usually means you are clicking the capture button before cranking.  You need to click the capture button while the engine is already turning - and keep it turning for a couple of seconds after clicking capture.  

[link_user]

Thank you for the suggestion. Will do a few more. How can I view the logs in the tuning software? Loading  the trigger logs in the Logviewer does not show any data.   Only seeing the triggerscope logs while captuirng them. I'm sure I saw the trigger1 and Trigger 2 data. But I did not capture them and save them into the file as it seems.

Also the DI2 input has "inactive" status near it. Do i need and how to make it "active" ?

 

[Adamw]

You view the logs just like any other log, you probably havent added the relevant trigger parameters to your time plot.

DI1-4 will be captured in the triggerscope regardless of status.  

[link_user]

Here are the calibration and triggerscope files. I checked them in logviever and it seems DI2 , the VVT input signal has no data.  I connected one wire od the VVT cam sensor to DI2 and the other to trigger2 ground.  This is an E36X plugin. The manual for the wire in ECU says all ground for sensors are connected together.
Can you please checkif there is an error in the calibration file itself so it does not shows the DI2 input signal?

I think the polarity on the trigger1 and trigger2 is wrong. Please check.

 

bmw4TriggerScopeLog.llgx bmw5TriggerScopeLog.llgx m3_e36new.pclx

[Vaughan]

trigger 1 polarity looks correct, trigger 2 polarity looks to be the wrong way around.

Try something like this:

[Adamw]

As Vaughan has suggested, your engine doesnot need a special trigger mode, it only has a single tooth on trigger two.  

But you do need to swap the +/- wires on your cam sensor, the waveform is upside down at present.  

You are right there is no signal from the DI2 VVT cam sensor in this scope, but that could just be because it is not meeting the arming threshold at cranking speed - so get it running first and do another scope.  The DI cam sensor is not needed to make it run.

[link_user]

Will do as suggested and report back. Thank you.

 

[link_user]

Today i used a USB PC scope to sample the signals to be sure what signals are sent to the ECU.  All three sensors are giving a good signal. Measured at the ECU connector. Ground of the PC scope probe on the trigger 1 and trigger 2 ground, signal on the PC scope probe to the trigge1 , trigger 2 signal wires.
Ground for the DI2 is on the trigger2 ground, (also tried sensors ground pin 71 on the E36X plugin for the triggerscope - no difference)

I did not swap the +/- on the cam trigger2 - cam sensor when taking the measurement.  Can you please check the signal polarity on the PC scope pictures?

The DI2 sensor generates a visible signal. 10V peak, trigger 1 is 50V peak, trigger 2 has 30V peak at cranking speed.   All data is visible on the pictures from the PC scope. I also centered  the time intervals, so you have an idea how fast/long the trigger signals are. 
Before you ask. Yes, I should use both channels on the PC scope to measure both trig1 and 2 or trig1 and DI2 at once and had them on the same screen...
I cannot resize the measurement I saved  when using the PC-scope "logging display" to play them back. Should resize the horizontal axis when measuring. If needed I can do it next time.

Again I also tried triggerscope on the Link at it  does not see DI2 signal at cranking.  Log file and calibration files attached.

After that i started the car and tried to do a triggerscope while it runs at idle. Here a new bigger problem arises. USB connection is completely lost when the engine runs, Windows7 pops up a little window saying "unrecognized USB device".

Do you have any suggestion what can be the cause? Wiring harness is stock S50B30 only the E36X plugin installed. I checked both the M50 and S50 pinouts and wiring schematics, no differences apart from cam sensors and all the other sensors grounding. The car runs, respond to the throttle. Only the USB connection is completely lost when the engine runs. 

I used this laptop on e few other wire in and plug in Link Ecus and never had a problem.

Now I need some suggestions what to look for.  What could cause a complete USB blackout when the engine runs?  USB wire goes through a hole in the original Motronic case which is in the engine bay side. The USB wire than goes through a 2cm hole in the firewall (rubber tubing around the wire for protection) into the passenger side of the interior. The hole in the firewall in deep under the dash.

 

 

bmw8TriggerScopeLog.llgx m3_e36new.pclx

[Vaughan]

That 3rd image has the wrong polarity but I don't think that will affect active/inactive, to confirm you have connected the VANOS cam sensor to pin 65? If you set DI2 to a gp input with pullup on and tap that cam sensor wire against an earth does it go active and inactive?

[link_user]

First image is the VANOS cam sensor on the DI2, second image Trigger1, third imeage Trigger 2.

Yes, Vanos cam sensor is connected to pin 65. There i put the PC-scope probe to measure the signal.     The ECU connector was disconnected when i dis measure all the sensors.
I will test the DI2 input as you suggest. This one is easy to test.

Do you any suggestions what can I do to solve the USB connection going completely offline when the engine is running? I can not do anything with the ECU since
I get "USB device not recognized" from Windows7 when the engine runs.

[link_user]

"set DI2 to a gp input with pullup on and tap that cam sensor wire against an earth does it go active and inactive? "

I tried this and DI2 works fine as a GP input, goes to active when the wire touches ground.

I would like to take a triggercope of DI2 as a VVT input when the engine is running, but I have another more urgent problem. 
When the car runs the USB connection going completely offline, get "USB device not recognized" from Windows7 when the engine run.

Please give some advice to resolve this bigger problem. I pulled the USB wire from the firewall, opened the plugin ECU case (removed the cover). So the USB cable goes directly to the laptop computer.  No difference.

 

[Adamw]

USB comms dropping out when the engine is running suggest it is caused by EMI.  Does it have resistor spark plugs?  Possibly a bad ground somewhere?

Depending on the age of the G4X there may also be a small hardware change we can do to improve the USB EMI resistance also.  Contact tech support if spark plugs and grounds look ok and they may get you to return it for the mod if it is an older one.

[link_user]

Recommended spark plugs for the S50B30 engine - resistor spark plugs as all modern EFI equipped cars. Car ran fine on original ECU before the Link plug in install.  All the wiring is as it came from BMW factory, completely stock, no check engine lights, no error codes. 
I will contact the tech support as advised. An USB cable with ferite cores on it would also help. The one that comes with the Link does not have it.

At the moment the ECU can not be used to run and tune the car. BMW plug-in has built in high current ignitors for the 6 coils on the engine. I guess they can also be a source of EMI noise near the USB comms. Most other ECUs have external ignitors or smart coils with ignitors built into them.

Hopefully the tech support can put me back on track. Thank you. 

 

[link_user]

I managed to get the USB comms stable for a few minutes to take the triggerscope. More on USB comms later.

VVT input is now visible. Do you need any more information to make a decoder for the euro S50B30 engine?

Now to the USB comms falling out situtation.

I noticed the engine cover, that cover the ignition coils that are on every spark plug was not on. The cover is metallic.

We put the engine cover on and the car runs and the USB communication will hold on for a few minutes. I managed to make a trigger scope for the

euro S50B30 engine. I will post it on the forum. So you can add the S50 decoder, that was already in the G4+ ECU.

I think with a better USB cable, the USB comms would stay on longer. Where  I can get the Link USB cable with ferrite core noise protection?

In the E36 chassis the ECU is on the engine side of the firewall, near the engine and the ingnition coils.   This seems to be the main problem.

Thank you for all the suggestion to solve the problem. Now I need just a better Link USB cable. How to get one?

 

bmw9TriggerScopeLog.llgx

[Adamw]

As mentioned earlier, you dont need a specifc trigger decoder for this engine since you only have a single tooth on trigger 2.  Your trigger 2 is still wired wrong polarity though so you need to swap the wires there. Otherwise you should be good to go.

Contact [email protected] and tell them you are having connection issues and want to try the ferrite bead usb cable.  

[link_user]

OK, will correct the wiring for the trigger 2.

I'm asking about the VVT signal on DI2, what should I enter for VVT input, so the VANOS mechanism works?  There seem to be a number of tooth on the DI2 signal. Before on G4+ there was speficic S50 trigger decoder for this type of VVT input signal.

Will be in contact with the tech support for the ferite bead USB cable. Thank you.