Adamw

A video showing how to set up and the stream template attached below. Zeitronix ZT3.mp4 Zeitronix ZT3 ID 90.lcs

We havent been able to reproduce this on any of the laptops or PC's at Link, but one thing we found on one of the higher end laptops was it was laggy on battery power but ok on AC. It was caused by a setting in the windows power plan for the graphics card which was switching it into low power mode when on battery. Setting it to "max performance" or similar on battery power solved it.

Do you have a trigger issue? To correctly set your arming threshold you need to do several different trigger scopes at the various different RPM's as the OP above done. But I would only bother if there is some problem, you appear to have good voltage so probably doesnt need to be any different than the default values.

You don’t need to turn advanced mode off. The limiter settings will remain, just the table will need to be set up.

Yeah one relay for the pair would do. I think they are rated at max 4.4A continuous each, so 10A should do it. Can you attach a pic of the factory switch schematic, because yours doesnt show any switch elements at all. If I were to hazard a guess I would say it is 1 common wire and 3 switch outputs, so you would connect the common to either ground or +12V (either is fine) and the other 3 to digital inputs.

What is the part number on the current Bosch sensors that arent working?

IAT Fuel correction should be turned off for modelled fuel equation. The air density change due to charge temperature is already taken care of in the fuel model.

That is not correct. Changing cam timing will affect the VE, MAP, overlap, reversion, scavenging, charge robbing, and many other factors. Whichever of those factors combined has the strongest influence will determine if the mixture changes and what direction it goes. There is no blanket rule that says AFR will go lean when you advance a cam. In fact it will usually be significantly different from one RPM band to the next. You need to tune valve timing the same way you tune ignition timing and injector timing, adjust the cam while monitoring the torque output.

I suspect even if I got a basic explanation from the firmware engineer I wouldnt have enough understanding of the system to pass that info on accurately.

From what you have tried so far I can only conclude it seems there is a hardware problem. I suggest you contact [email protected] to arrange return for inspection.

You will have to contact tech support ([email protected]) to arrange repair.

The speed lockout is working fine in your log "speed.llg". But what is the question? Was there any hunting in these logs - because I dont really see it? It looks like there is a little dip when entering idle which is probably settings related but nothing I would call hunting. You also need to attach your map.

The map that is already in the ecu will be fine for that engine. The same map is also available in PC Link base maps folder "Audi TT G4+ Xtreme Plugin.pclr"

Pins B5 and D1 are the DBW supplies, ideally they would come from their own relay/PDM output that the ECU can shut off in the event of a safety concern. See the diagram in the help file page: Wiring Information > Output Wiring > E-Throttle > Generic Internal E-Throttle Wiring for more info. For the cruise switch, do you have a "schematic" type diagram of it? How many buttons/switches does it have and how many wires? The VDO settings in the help file usually work ok with most Bosch throttles.

For the speed calibration you could jack the back wheels up, hold it at say 2000RPM in 4th gear and note down speed displayed in PC Link. Then go to something like this: https://spicerparts.com/calc/transratio/index.html to calculate the actual speed that should have been displayed at 2000RPM. Then you can multiply the DI calibration in the ECU by the same factor as your displayed vs actual speed difference. For the speed in the dash, are you looking at the LF wheel speed channel?

As far as I know the 2NZ and 1ZZ vvt modes are the same, only the triggermode is different. As above that is due to trigger error. If the ecu gets a tooth event from the crank at a time that doesnt match the predicted crankshaft angle then the ecu either needs to stretch or shrink the dwell time to ensure the spark happens at the updated crank angle.

If the ECU is correctly showing speed when the car is moving then there should be no further config needed. What is not working?

Yes the Atom is fine. As for connection you can just connect using the normal USB tuning cable, this is the most simple option. Or CAN is the other option (CAN is more configurable) . I wouldnt bother with OBD2 as there is noticable lag. There is a Bluetooth CAN option that looks like an OBD2 dongle (OBDLink MX+) but it is actually capable of direct CAN (no lag).

Your trigger settings look like they should be ok for that trigger pattern. Can you do a triggerscope at about 6500RPM and attach the actual log file here.

I believe under some conditions they can pull as much as 8A for a very short time, but typically <2A. Just try a temporary new 12V wire with a jumper lead or similar, as it would be pretty unusual to have two bad sensors unless they are fakes.

I would say your arming thresholds are a bit borderline too high. Try set like below. Im not confident this is your misfire issue, but possibly the reason for the trigger error and VVT issue.

So was that scope done at about 4000RPM?

So are you saying there is no longer error 36, but you have 16 instead? Typically error 16 is lack of adequate current on the 12V wire. Maybe try a new temporary 12V wire to see if that changes anything.

No idea sorry. We never intended it to work with a mac, have never tested or investigated using it on a mac, and none of us have a mac to try. The G4X ECU comms with windows is via a FTDI VCP and it runs at quite high speed, so I assume this would be the most likely area a VM would fall over. Have you tried reducing the baudrate in PC Link? Have you tried adjusting any of the advanced port settings like latency etc in windows device manager?