Jump to content

Base timing offset difference between G4+ and G4X


Shedley

Recommended Posts

So i've done a bunch of BMW S54's on G4+ Fury ecus, base trigger offseet is always arround the suggested 276 degrees.

Yesterday started one up with the G4X Fury, but car wouldn't start, so checked with timing light and now with base timing at -15 degrees, the engine runs, but does seems weird to mee as crank patern isn't changed at al so why is base timing suddenly different. Also if you look in the help file, on G4+ there was a lot of parameters for the S54 included in the engine specific section, but on the G4X help file they seem to have deleted a lot of the base value sugestions.

 

Someone experienced similar problems?

Link to comment
Share on other sites

On engine where we had good reliable information on the normal trigger offset, this has been built into the trigger mode.  So in most cases you can set it to zero and it will run.  

As for the info removed from the help file, we have only removed the stuff that is no longer needed in G4X.  The Aux setup have been removed as you can now use any Aux for the solenoids.  The VVT offsets were removed as the calibration is all done automatically.

Link to comment
Share on other sites

3 hours ago, Adamw said:

On engine where we had good reliable information on the normal trigger offset, this has been built into the trigger mode.  So in most cases you can set it to zero and it will run.  

As for the info removed from the help file, we have only removed the stuff that is no longer needed in G4X.  The Aux setup have been removed as you can now use any Aux for the solenoids.  The VVT offsets were removed as the calibration is all done automatically.

Ah ok, didn't know about the offsets being implemented in the base trigger setup.

 

Also encountering another weird one ont his particular car. 

So on e throttle we have much more configuration options compared to g4+. I copied pid values ect but keep getting issues wutht he ethrottle controll, can't run the automatrd tps calibration as well, but that didn't work ok s54 and g4+ to.

But what i have now, so i configured all the sensors manually, but for example throttle is at 6% due to idle control, and ethrottle dc is arround -85%, but that does not make any sense because there's a spring on the e throttle motor, so it goes to zero on itself. And if you pull of the connector throttle shuts immediately so there's no resistance at all. Also if you gently press aps, tps goes open as it should, if you pump aps, tps goes shut instead of open. Also if you keep for example aps at 50%, tps follows, but you can press throttle open or shut with your hand, but on g4+ it was really not possible to do so. It seems as there's no current enough supplied to the ethrottle motor.

Another issue is, sometimes out of the blue when you restart the ecu trottle blade goes al crazy, open shut open shut open shut ect. If you put them completely shut with your hands, ethrottle dc goes to 100% but throttle plates stay shut and aren't moving at all

The only thing i can imagine being a problem is that tps sub and main go in opposite direction, so one 0-5v and the other one 5-0v

Link to comment
Share on other sites

1 minute ago, Adamw said:

The PID will be different but that doesnt sound like your only problem.  It sounds almost like it might be working backwards, is the aux 9 active edge set to high?

Yes it does, and also wired aux 9 to the + side of the ethrottle motor.

Also worth mentioning, if i set it to low, throttle plate goes immediately full open without aps

Link to comment
Share on other sites

9 hours ago, Adamw said:

Give us a log and tune then please.

herre you go

First log is trying with tps cal. Second log is with setting tps limits manually en actuating aps. On TPS calibrating i get error 6, but i think tps movement is reversed. neverthless if i set aux 9 to low i get error 5.

basefile.pclx limited tps movement log calibrating.llgx reverse movement.llgx

Link to comment
Share on other sites

Ok, that is weird, it definitely looks like it is having a hardtime getting it closed.  

To confirm what the software is showing, can you put a voltmeter on the E-throttle motor (Red to aux 9, black to aux 10) and see what voltage it is showing when the throttle is closed and the Motor DC is showing -80% or whatever.  If the volt meter shows about -10V then that will back-up what the software is showing.  

Link to comment
Share on other sites

36 minutes ago, Adamw said:

Ok, that is weird, it definitely looks like it is having a hardtime getting it closed.  

To confirm what the software is showing, can you put a voltmeter on the E-throttle motor (Red to aux 9, black to aux 10) and see what voltage it is showing when the throttle is closed and the Motor DC is showing -80% or whatever.  If the volt meter shows about -10V then that will back-up what the software is showing.  

I'll do in a minute, but can say this, if i put a bench power supply on the ethrottle motor, 12v 2,5a, the throttle kicks open immediately and you can't move it with your hands, if i reverse polarity, you can't open it

Link to comment
Share on other sites

I can confirm there appears to be something weird going on in your map.  I just done a quick bench test in an ecu here and the outputs are definitely not behaving as expected.  When I load a map in from my car the outputs behave correctly.  Ive tried adjusting a few things but havent spotted what is causing it yet.  I will have to get back to it tomorrow and have a closer look as its 10:30pm here now.   

 

Edit, added later:

Ok, update, I played a little more.  I think there is some bug in the initialization of the auxes.  With your map in an ecu I changed the E-throttle PWM output to "Aux1/2", then back to Aux 9/10 and suddenly the auxes started working in phase correctly.  Try loading your map below, it should be fixed in this map.

 

 

basefile fixed.pclx

Link to comment
Share on other sites

21 hours ago, Adamw said:

I can confirm there appears to be something weird going on in your map.  I just done a quick bench test in an ecu here and the outputs are definitely not behaving as expected.  When I load a map in from my car the outputs behave correctly.  Ive tried adjusting a few things but havent spotted what is causing it yet.  I will have to get back to it tomorrow and have a closer look as its 10:30pm here now.   

 

Edit, added later:

Ok, update, I played a little more.  I think there is some bug in the initialization of the auxes.  With your map in an ecu I changed the E-throttle PWM output to "Aux1/2", then back to Aux 9/10 and suddenly the auxes started working in phase correctly.  Try loading your map below, it should be fixed in this map.

 

 

basefile fixed.pclx 430.05 kB · 1 download

E-throttle works now, but to report, tps call doesn't, calibrate sensor manual does the job, just as in g4+

I think has to do by how the system is constructed, one tps on the ethrottle motor and one on de itb's themselves, with a linkage between them

Thanks

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...