Adamw

As far as I know the TPS connection on the pigtail connects to the transmission, not to the ECU. So you will need to swap the signal wire from the old idle switch (I dont know what colour it is but it goes back to pin 18 on the ecu) into the other plug - I assume the center position.

Yes, I can give you instructions. However, before we go that far, be aware the CAN is very basic in these old ecu's, you cant configure much of the format - for instance all channels will be sent as full 16bit values, always Intel format, you cant change any scaling or how the data is fitted into the frame. What TCU do you have, and is its CAN configuration very flexible?

Yes, that CAN ID field used to work a bit weird in these. You need to hit the enter key after typing the ID number in for the ID to be applied to the channel.

So did you cut the original wires from the old TPS connector on the housing and connect to the new pig tail plug? Where did you get the sensor ground from?

Is it the auto tps? The manual one isn’t a tps, only a idle switch.

You need to set up a custom 0-5V sensor first in RS3, assign volume units, then go to your dash config and double click on the channel you want to use a assign the fuel level sensor to the channel. You can choose lowpass filter. The 32sec one will probably do it.

It is not relevant in this case, the DI wont consume anything.

Mostly looks ok. It looks like the throttle may be a little too closed now, adjust that until it idles at a suitable RPM. Have you checked base timing? Flex sensor is working and showing 53% in this log.

It will work when cranking

No, negative 85. But rather than just put random numbers in there, you should put a timing light on it and adjust the offset until the timing light matches whatever you have in the "lock timing to" box.

Did you check base timing? Pretty odd to have the offset at 0, I think normally around -85 on an RB. Also, your old fuel table is not suitable as a VE table in modelled mode. Highlight the whole table and multiply by 2 will be closer. Also in modelled mode you should turn of the IAT trim table and zero out warm-up enrichment. Also, at the time you saved that map, your MAP sensor was reading 164Kpa, which doesnt seem right, and you have a 100% fuel cut active for the boost cut.

I havent come across what you have above but it seems like maybe a permissions issue. Do you have admin rights on that PC? Here's the Link support numbers: https://www.linkecu.com/about/contact/

If you connect it direct to the dash analog input then you dont need the RC Filter as the dash software has filters built-in that are suitable for fuel level.

Your dropbox link doesnt work. Says I need a business account to access.

Your log file says unavailable.

That is something I just put together to show the relevant parameters only. You can do anything you want with the layout. Right click on any blank space (or create a new page if you dont have blank space), >new view>digital gauge, then chose the parameters you want.

What specific ecu do you have?

Cruise enable light works for me. Is your cruise status changing?

Im not sure what you are trying to achieve, as already stated the ignition output already outputs a 6.5V square wave. It doesnt sound like you have a duty cycle problem though. Speedos work by counting edges, the width of the pulse is irrelevant.

What are the error codes though and where are they displayed? That is just the help file that you are showing in your photo. The rotation direction is mostly only used on two stroke snow mobiles where you run the engine backwards to back up instead of having a reverse gear. It is not even possible to run a 4 stroke engine in reverse so I dont think this runtime would ever say reverse rotation on a four stroke.

99% of automotive hall effect sensors are happy on 8V, but I have never seen that one before and there is no data sheet that I can find. If the OEM used 5V, I think it would be safer to stick to that. It sounds like it is a variable resistance type. So the factory oil pressure gauge would have had a pull-up resistor in it, the sensor is effectively a resistor connected to ground. So between the gauge resistor and the sensor resistor you have what is know as a voltage divider circuit. When the resistance of the sensor changes, the gauge will see a varying voltage from the voltage divider. So you could make it work, but you will need to add a pull-up resistor to 5V like the pic below (ignore the fact this is a temp senor, they work in the same way). The problem with these sensors is they are very low resolution and their accuracy varys a lot with temperature. My favourite pressor sensor at the moment is the Bosch combined pressure/temp, or you can get one that is just pressure only for the same cost. The connectors are a bit horrible to work with but they are very reliable sensors which in the issue with many of the lower cost sensors: https://www.efihardware.com/products/3002/bosch-combination-145-psi-pressure-sensor-and-fluid-temperature-sensor Pressure only: https://www.efihardware.com/products/3000/bosch-150-psi-10-bar-gauge-pressure-sensor Your updated map attached. G4Thunder928 V0.1.pclr

Please do the triggerscope to confirm, but I suspect that will be it. If it was a GTR plug-in that would be no problem as there is an on-board jumper to swap trig 1/2, but no such feature on the 300Z plug-in. If you do the triggerscope and notice the waveform is showing on trigger 2 and trigger 1 is just a flat line, then you will have to move that pin.

No that shouldnt effect it. Trigger scope will show us what is wrong. I would guess air gap, but there are other possiblities such as it has been pinned wrong. I have also seen some aftermarket cams with lots of end float so the gap keeps changing.

It is not happy about something related to the trigger. RPM shows zero the whole time. Can you do a trigger scope while cranking and attach it here. Here is a video how to do it: https://1drv.ms/v/s!AiYbYlZQuRHPmidU5V2CmTcv6t2y?e=FGqZ0I

Use this map, I changed the cruise lights to virtual auxes as the CAN auxes are fully implemented yet. You can look at the Virtual aux states on the auxiliarty tab of the runtimes values screen. MitsubishiVR4Galant-LegnumG4XtremePlugin.pclrno2 new CANB.pclx