Adamw

It looks like trigger error to me, there are spikes in RPM and dwell gets pretty erratic around that area. So does it have a custom 36-1 wheel fitted on the crank? A couple of settings I suggest changing as yours arent normal: Change trig 1 filtering to level 1. Change trig 1 arming threshold to match this example:

In the runtimes screen, what does Lambda 1 status and Lambda 1 error show?

Usually the easiest option is via the TVS diode if its in an accessable area. As per my pic below, find the big barrel shaped component on the bottom PCB, with a couple of small aligator clip leads or similar, connect +12V to the striped end and ground to the other end.

It can be upgraded to G4 firmware so you will use the G4 PC Link. It is a very worthwhile upgrade. G4 PC Link is much better, especially the logging side. You will get internal ECU logging. Many more options for inputs and outputs, virtual auxilaries and timers etc. Many more configurable 2D & 3D tables. Closed loop boost control Quick tune Many general code improvements, performance improvements and bug fixes. Probably lots Ive forgotten about.

Try this. BRIO RALLY MXS Strada LINK FURY 3MO Reverse fixed.zconfig

Here's a video showing how to use the triggerscope with a G4+ ecu, you will find G4X is a little different but I think you will work it out with this: https://1drv.ms/v/s!AiYbYlZQuRHPmidU5V2CmTcv6t2y?e=FIxeSC So with idle speed control mode set to closed loop you get this stumble whether or not idle ignition control is on or not? But with idle speed control mode set to open loop, you dont get this stumble?

So is this a G4+ or G4X? And is it a JZX100 ecu fitted in an altezza?

Thats the first time I've heard this reported, but yeah, I suspect they must have the enumeration for reverse set up incorrect - possibly expecting "-1" or something. Can you attach your dash config and I will set up a custom enumeration to see if we can make it work that way. It may be something that is hard coded in the background that I cant get around so may need help from AiM to sort.

Can you do a triggerscope at idle please. Save it and attach the file here. Can you explain the "cut out" in a bit more detail too. Does the engine completely stop or is it just a short stumble and it recovers? Does the laptop disconnect when it "cuts out"? And are you saying with idle ignition turned off, it will idle forever, not cut out?

It appears the engine was not turning when you done that triggerscope. Please do it again, make sure you only hit capture when the engine is cranking.

I dont see any evidence of that. How reproducable is this? How long does it idle for before it will stop? Can you set up ecu logging like below, and next time it stops then download the ecu log and give us a look at that. Maybe add battery voltage to that logged list too.

I dont see anything caused by the ecu, The engine was still running stable at 850RPM at the point it lost comms with PC Link. This suggests power was lost.

Can you attach some pics of the oscilloscope captures. Make sure it has resistor sparkplugs evo's get bad trigger errors with non-resistor plugs. No the RPM limit count should increment everytime the RPM limit status goes active. This will likely co-incide with trigger errors as the error will create an artificially high RPM, but it should increment whenever you reach the normal limit as well.

Did you mess with the dashpot offset setting when you were doing any of those logs? In one log im trying to undersatnd why we didnt get the 7% dashpot in one place? It looks not far off to me now. You will need to experiment with the 3 dash pot settings to get rid of the undershoot after a blip. I suspect you will need shorter hold and decay and possibly more offset but its but just to play with it live.

Did you reboot the ecu after changing the comms settings? Have you tried some other device in your OTG cable (like a USB mouse or similar) to confirm the OTG adapter is working?

So does it not run with my map? It will likely be very lean that one you attached. The RPM looks fairly stable at 850-900 in that log, it wont get much better until it is tuned. For the temp sensor, can you set up ANT4 like my pic below, then tell me what IAT is reported with the sensor unplugged and then with the two sensor wires shorted together. If wiring is correct it will show high temp when shorted together and low temp when not connected.

Sorry, I must have been distracted with another job when I was adjusting your file, I had changed the trigger mode to Harley Davidson. Here is a new version with the trigger fixed. 1.9Kohm for the temp sensor is correct so it just seems like it must be wired to the wrong input or not set up correctly. Basemap350zG4 fuel fixed V1.1.pclr

Ok, I think the main problem will be someone has changed it to modelled fuel equation but the fuel table only has numbers in it suitable for traditional equation. A couple of other factors such as the IAT sensor not connected (reading -50°C) and IAT trim enabled would have further messed up the fuel volume. So try the attached file, I have updated the fuel table to something that should work and turned off the IAT. If it still doesnt run then please do a log. Basemap350zG4 fuel fixed.pclr

The idle ign not working correctly is due to a bug. I will PM you a new version of PCLink and firmware with this fixed. Please install it and update the firmware to V6.16.52 that is included in this install. After that load in the "New Idle" map that I attached earlier. Do us another log, include some just general idling and a couple of throttle blips and the AC switching on.

Please attach a log and the tune.

Correct, the Altezza plug-in ECU has a CAN to BEAN converter onboard to communicate with the rest of the car. There are plans to offer a version of this as a standalone module for wire-in ECU's in the future but it is still some time away - possibly a year at a guess. As far as I know the factory TRC button and light wont work with our Altezza plug-in.

Yeah, just load your original map back in.

Let me take another look tomorrow and will get back to you. For some reason in that config I gave you idle ignition control isnt working and I cant see why. I think I want to take a look with fresh eyes tomorrow.

The VVT trigger mode already uses rising on the trig 2 but you can try falling as well if you wish. I cant actually test it on the bench as my simulator doesnt give me enough movement of the cam signal to generate a pattern that matches yours. But from the testing I could do, it appeared that the OBD2 mode with cam set to rising was the option that I think will give the biggest margin from edges that could cause an error.

Yes, you will need access to the map to turn on the correct input, assign a calibration and set up any safety or protection strategies.