SuperBCNR33

I think I'm on 6.19 or 6.20. I'll update the firmware and see if that fixes the device not found.

Here's another update: The CAN lambda device is sending the AFR signal, it's actually working, but the ECU still can not find the CAN device itself.... Im getting an actual AFR reading, but it still says device not found. Im puzzled.

So I have an addendum. I put retested today the CAN comm lines and there is a differential voltage between the two now. L=~2v and H=~3v Additionally the CAN errors are all gone. When my lambda connector is disconnected I get the CAN errors (obviously) but as soon as I connect them back errors go away and the error count down drops to 0. However, it still cant find the device. I have tried every bit rate as well. I even swapped to CAN 1 and the same issue exists. In the same way. I have done a continuity check from the lambda connector to the JST connector, and every point in betweem. I show to have good continuity on both comm lines. Every thing I can physically test or diagnose (aside from a logic analyzer) shows it should be able to find the device. Any thoughts? Images are of the inside the ECU. I am also going to attach a link to show the error counter when connected. https://drive.google.com/file/d/1n09AYsV18iwjpdQmVgr6-sgYcf-SyJfy/view?usp=sharing CAN Lambda p2.pclx

The connectors are sumitomo and yazaki connectors. I am getting HIGH LOW readings at both ends of the connectors of 2.4V there is something coming out of the ECU. And there is definitely a connection. Also, I think with me having a 120ohm resistor at the lambda end and reading 60 ohms would say I have a full CAN connection to the ECU. (The other resistor at the ECU being included in the reading) When you say connection at the ECU do you mean inside the ECU at the 5p JST connectors? If so, I'll have to get that to you at a later time. It's 330am here so I'll start again tomorrow. Also, the sensor is getting warm when IGN on yes.

Hey Adam, I figured I would piggy backoff this thread as I am having the same issue. I am set up using CAN 2 instead of CAN 1, using the appropriate set up configuration with the appropriate wiring. I am still getting CAN 2 errors and no device found. I have measured resistance at the termination (lambda end) and see 60 ohms so I know my termination is correct. However I am getting 2.4v at both HIGH and LOW com lines. I am reading 12V when switched on at power, and getting continuity at GND. Also, I have checked with all bit rates, same results. Would running on CAN 2 cause an issue? CAN Lambda.pclx

Im looking to understand how the Estimated torque parameter calculates its value. If it's what I think it is, I would like to use it as a reference for estimating avg HP per triggered window of time. However, when I look at the logs this parameter always returns 0. Is there a setup needed to enable this data capture? Also, what other parameters / sensors is it using to calculate this estimation? Using LINK G4X - NGTRX plug in ECU on code versions: Main 6.19.60, boot 6.19.32 and board 3.1

Happy to report that the issue was 100% the jumper being on the wrong setting. It should have been removed to put it in 1:1 scale mode. System is functioning 100% Thanks for the suggestion Adam.

So, when I popped open the ECU the jumper was installed. (Couldn't see the J1 designation so I assumed it's the only jumper on the bottom board aside from the switches) According to the NGTRX manual, this means it was in the "2:3" mode. I removed the jumper putting it into "1:1" mode. What the manual says is for it to be in 1:1 for factory manuals. Although in the paragraph above that it says the TPS is scaled for auto trans and 4WD controllers. This is not implying it does actually need to be in 2:3 mode does it?

Took this image of the ECU before I installed it. Looks like the TPS jumper might be on the 2:3. Hard to tell since I dont know what the jumper itself looks like. I'll pop the case open tomorrow if you can't tell from this image. I can say I did not adjust it when I installed it originally. So it would be in the shipping default. (If that is a thing) *Edit: Just re-read the manual. Looks like I might have never swapped the jumper to 1:1. Really hoping this is the issue. I'll gladly take the cone of shame for a simple fix! For anyone else that may come across this thread. I'll confirm in my next post if this was indeed the issue. However, I would like to mention I did not have any warning lights. (No AWD warning) likely because the pump system itself is in tact. It could be that there is no TPS signal check within the system for triggering the cluster light. Also, very much appreciate the quick response as always Adam.

Hoping to find some answers with the ETS System and the Link NGTRX G4X. I have read for the R32, you must wire in the TPS direct to the ETS module. Is this is the case with the G4x Plug in? I ask based on the fact that ever since I installed the Link ECU my torque meter stopped behaving normally. It no longer reports any torque distribution when you would expect there to be. (I.E. Hard driving in wet weather). I think its because at the same time I have lost functionality of the actual torque split controller (ATTESA). The car is mostly stock with the exception of the LINK G4x ECU, and injectors. I am trying to diagnose the stock components before I install the Full Race ETS system, so I'm not potentially chasing a phantom issue. Could my issue be the link ECU does require TPS wiring modification? (Sorry if this is mentioned on this form for the R33, but I can not find any information on the R33- only ever find info on the R32.

Thanks Adam, Ill look into async this weekend!

I have a G4X for an RB26 (NGTRX), and I am in the process of working through my accel enrichment and cant seem to find the accel hold or clamp tables like the G4+ used to have. G4+ used to have: - Accel hold - Accel clamp table - Accel load correction tables G4X has a bit of a different model. Is it possible to utilize the G4+ accel enrichment model instead of what is optioned in the G4X? Also, what was the driver for the change?