Adamw

I think it would be best to get advice from M&W in this case. We dont know what the limitations of the hardware are.

Roughly if we forget about deadtime and all the other compensations, Injector PW is calculated as Master x fuel table x (MAP/100), this PW assumes a single injector. The PW then gets divided up by the staging table & sec flow ratio and the appropriate proportion sent to each injector. So an example, 10ms master, 80% fuel table, 200kpa MAP. Total PW = 10 x 0.8 x 2.0 = 16ms. In your case the sec flow ratio is 1:1 and your staging table will have 50% in it, so half that 16ms goes to primary(8ms) and half goes to secondary (8ms).

It is very unlikely hall effect if it has only two pins. Is it the white marelli sensor they show in the pic on there website?

Our FD test car has the stock 550 primaries and 1600 something in the secondaries (roughly 2150cc total per rotor), so I would expect your 2 x 1050's to be in the same ballpark. Master fuel around 12ms should do it.

You could do a virtual aux like below so if any of them go above say 750°C you take action. That action could be anything from flashing a warning light, add extra fuel, lower boost, or activate a GP limit, etc.

correct. I think its going to be wise.

E-throttle PID is always hard to guess without experimentation, but based on the numbers in the help file for the LS throttle I would start by dropping the Integral back to 0.05. If that doesnt help try dropping proportional back to 6.5

I wouldnt think there would need to be many changes except for setting up all the IO to match you wiring. What problem do you have?

Do you have any old triggerscopes saved on your laptop? The position of the cam doesnt look too far away from where our internal documentation says it should be, but the cam signal is inverted to what our reference pattern shows. So Im not confident if the cam has moved - or maybe just the sensor is starting to die and is somehow given an inverted signal. It would be nice if you had an old scope to confirm if the cam waveform has always been that way up or not... Since both intake and exhaust are giving errors Im leaning more towards it being the timing has shifted but not 100% on that.

I dont see much wrong in your ECU set-up. Can you give us some pics of the CAN wiring just in case there is something obvious there.

Unfortunately no. There is this type of functionality coming in G4X, but not possible in G4+. The dash doesnt have the advanced math required either at this time.

I have passed some questions on to engineering, I will hopefully feedback tomorrow what they think.

Why did you change it back? I already set up wheel speed in the last file.

What do you mean by you are not getting DTC's? Do you mean via an OBD2 port? The OBD2 port isnt even connected to the ECU.

Have you got another laptop you can try? It sounds more like a comms issue than an ecu issue.

It should just work, your settings are all correct. The map shows there is no signal being received on DI8. The flash of green when you turn on the pull-up means the DI is working. So, either there is a sensor problem or a wiring problem. I have seen some sellers giving incorrect pinout info for the flex sensors. Is yours wired like below?

Here is the custom CAN I done for your dash. LINK_Kungfuice_@20190316_075205_007515.xc1

Yeah, ok this is just a PID/tune issue. You can see in this log under certain conditions the E-throttle gets an unstable oscilation in it, which causes the TP/Target error accumulator to count up with no time to recover. Once it reaches 100% it shuts down the E-throttle relay. If you attach your tune I might be able to suggest a change.

Can you attach a copy of your tune please. Your voltages and waveform looks fine to me but the "not starting" scope capture shows the ECU is not happy so I want to pass this on to engineering to take a look.

Ok it all looks happy in that log. But things might be different when the engine is running and there is boost etc. So my next suggestion is to set up ECU logging like below and next time it plays up, down load the log out of the ecu as soon as you can. The ECU will have enough memory to hold about the last 1.5hrs of running set up like this. This may give us more clues. Set up like below except for aux 8 status - replace that with whichever aux controls your DBW relay.

Can you try changing the transmit rate to 20Hz and turn the OBD2 off and see if that makes any difference.

Were you driving when you done that triggerscope? There is no signal showing on DI3. I want you to do the triggerscope while driving so we can try to capture what is wrong with the speed signal.

Can you tell me what firmware version you are using. >help>ecu information. It looks like there was a change to MX5 triggering in 6.17.8 so if your firmware is older than that then that would be the first thing to try.

I made many changes as it had some pretty odd settings in your tune. Can you do a couple more logs using the tune below. Since ive changed quite a bit it may still not be right so dont freak out if it is worse not better initially. We should be closer after the next log. Idle tweaks .pclr

I havent seen the odd blank screen like you show there before. But yeah, make sure the power supply is goo is the first thing I would look at. If you attach your ecu tune an the dash config I will take a quick look at your software setup too.