Adamw

MAP sensor calibration is wrong, you have a MAP of zero (impossible) so no fuel is being injected.

If your car is right hand drive then the right hand cam would be drivers side.

I said "Xtreme and higher". That means Xtreme, Fury, Force & Thunder have the automode.

I dont see why the normal VL base map wouldnt work. Only the ignition mode will need to be changed if you get rid of the distributor.

You can use 2 external modules or the one internal and one exturnal. You will need to confirm you have enough inputs/outputs as two throttles and a pedal will need a lot of IO.

You are right about the Daihatsu is 4+1. 6-1-1 would be a different pattern than 3+1. The two gaps will be 360 deg apart. In the pic below 3+1 would give a signal like the green teeth. 6-1-1 would be the red teeth.

If its got clean uncontaminated fuel in it then its output frequency should be between 50 and 150Hz. If it is not outputing that then either the fuel is contaminated or the sensor is faulty. The ecu cant influence the frequency it outputs.

The toyota single wire resonant frequency sensors typically dont work with most aftermarket ECU's. Their output voltage is very high and you will find even with low gain the signal saturates the input and it starts clipping the signal. I have seen them work on some low power/stock engine but usually no. Automode CLL is an advanced feature that was only available in the Xtreme and higher.

I will attach a map from a running engine. This was done in an early beta firmware and I think (not 100% sure) that the trigger offset was eventually written into the code. So trigger offset may be zero or 142. Trigger 2 must be connected to LH inlet cam, and RH inlet must be connected to a DI (the RH inlet is also used for quick syncing the trigger). VVT needs to use user defined mode, instructions for setting up offsets etc are in the help file but these should be working in this map. VQ35HR.pclr

Still the same, no signal. The sensor signal isnt reaching the ecu. A wiring issue.

The throttle system is going into fault mode due to the reported fault "AP(Main) CAN Timeout". Maybe the device that you have sending the APS data is slow to bootup and the ecu times out waiting? Can youy attach your current map as well. I will give it a quick test on the bench here. When the ecu thinks there is a safety concern with the throttle system it shuts off the E-throttle relay (Aux 9/10 supply). With no voltage holding the throttle blade closed the spring inside the throttle body will push the throttle to its neutral balance point, this is usually aroud 7-10% on most common throttles.

Try this one. R and N wont work but it may give us an idea what is going on. I dont have a dash with me to test at the moment. Brad Foreman V3.zconfig

Any ground is fine, it is a digital signal so ground offset won’t influence it. Shielding is not needed, it is only 150Hz.

New update is available here: https://linkecu.com/software-support/pc-link-downloads/ Release notes: https://www.linkecu.com/pclink/Link Engine Management PC Link G4X Updates 21042021.pdf Important notes: This firmware changes the sync point in some triggermodes so base timing must be checked after doing this update. There is a new "Slow Comms" setting added, this may help those with communication problems that are due to some laptops with USB ports that are slow to respond. This a an ECU setting so the ecu needs the latest firmware instaled before you will have this setting available, you will find it in the main configuration menu (where you set number of cylinders and engine type etc). Any new issues related to this update can be reported here.

yes.

Looks like it is a match

As I said above it looks like you have something shorting out the 5V rail. A log would have confirmed this as I originally requested. I dont even know what ecu you have since you have given no relevant info at all except for a video, but assuming it is a wire-in ecu the next step would be to pull the 5V wire out and see if the error disappears.

CAN1 needs to be ON and with no errors if you have APS connected via CAN. It is obviously not going to work with CAN1 turned off...

Can you try temporarily turning off the channel with the AEM on it as a test. Your wiring looks fine.

The settings wont prevent a signal showing on the scope. If you still get a scope capture like above and it was definately cranking while the capture button was clicked that that would suggest there is no connection between the sensors and the ecu.

I dont see any way to support that trigger pattern presently, it will likely need a new trigger decoder written. With 3+1 on the cam it shouldnt need the trigger 2 signal at all. You could try Daihatsu copen trigger mode which is also 3+1 on the cam but the "+1" tooth is much closer to the normal tooth so Im not sure if it will work.

But did you click the capture button while the engine was cranking? Not click capture, then crank.

Your scope and settings look fine. What makes you think the trigger offset is meant to be -5? The trigger offset is the angular distance from the sync tooth to TDC#1. In your case the sync tooth set to 1 means the sync tooth is the first tooth after the gap. You need to check this with a timing light and also if you are running leading wasted ign mode you need to confirm timing on the trailing plugs as well, because it will still run with the trailing 180 out.

That is just 0.15V of static noise, it is not a trigger signal. Was the engine cranking when you clicked the capture button?

There is a pre-defined Hella 6PT calibration built in, it is expecting about 6600ohm @ 20deg C so that sounds like it is close. Did you try that?