wastegate

e-throttle uses dual sensors for TPS and APS, they need to be matching, think of it as an agreement system. If one of the APS sensors fails, the system will flag an error. If you disable those check, and the APS sensor1 reads 100% while APS sensor2 is ready only 4%, it might use that 100% reading. There might be other things like integral limiters, remember a motor is driving the throttle blade, it requires PID control. If the integral limiter isn't there, the throttle might swing to far, giving too much or too little.. There are e-motor limiters too to stop the motor smashing the blade.. the motor might get a voltage spike from somewhere, jamming it open, with nothing to check the voltage of the supply, you have a motor being over driven.. I guess only Link engineers could tell you how the ethrottle works in setup mode and what sensors are read or ignored, but I don't think you will get that answer. Legally it's a mine field even on a race track or competition race car. Frankly, your tuner is risking themselves to a wrongful death lawsuit if something were to happen as he told you to do this. If he is willing to risk your son's safety, would you trust him? As for ABS, your brakes still work if ABS fails, there is built in redundancy and most modern cars even have multiple channels. Traction Control disable or failure won't cause you to loose control, it's meant for a simple job of maintaining as much traction as possible, it can be disabled in most cars. What is very difficult to disable in a almost all modern cars is stability control which is more of a safety feature than traction control is. You almost need to do a secret combo move to disable this in any modern car. But again, that is a safety feature that is about maintaining control. Disabling the safety features on a ethrottle is like disconnecting the SCRAM button on a Nuclear Reactor.

The two incidents I mentioned at QR were from cable throttle cars... a lot of keyboard experts after them always say "if it was me, I would have just turned off the engine" and I'm sure some have got away with doing just that. But you don't hear about those, only the ones where they don't..

So at QR raceway here in Brisbane, Australia, we have had a couple of fatalities from throttle issues being stuck or not closing. Not to say this was ethrottle but more the fact there was a couple of deaths because a throttle failed. Disabling safety features because you want to come first is the first way to the morgue. As a father of two, I hope for your son's sake you don't risk it. To put it in Australian, "Don't be a bloody idiot"

Unless I'm missing it, I'd love to see a feature where you can use a table for anything you want. Personally I'd love to use one to convert an input to what Link is expecting. For example, my Transmission controller outputs the gear position as Neutral: 0x00 Forward ranges: 0x01 to 0x0F Reverse ranges: 0x11 to 0x1F Park: 0x10 However, G4/G5 expect gear position as 0 (no gear) 1 2 3 4 5 6 7 8 9 ·P (Park) 10 ·R (Reverse) 11 ·N (Neutral) 12 ·D (Drive) 13 ·H (High) 14 ·L (Low) 15 ·M (Manual mode) 16 ·M- (Manual mode shift down) 17 ·M+ (Manual mode shift up) Ideally, I'd like to have a CAN Input from the TCU on one axis and the Shifter Position on the other as a 2D table.

Brilliant. Do you think this is normal and not worth mentioning and to just work around it? I don't care it doesn't log during sleep, what I care about is it looses all the data before it went to sleep and just flat-lines to entire log.

Anyone ran into an issue with logging on PC and sleep? For example, start logging a cold start on the laptop, can see the log going ok. Then go for drive and laptop will sleep. Come back to it, save the log and the log is then nothing, accept the last few minutes/seconds since sleep restore? flatlines the entire history before sleep. Log file attached https://drive.google.com/file/d/1Z9y3YRpPRO35OI0Gswdli5HkysobPx1U/view?usp=sharing Map in case it's needed https://drive.google.com/file/d/1xDkULkoVkVfWKjVtjBIxjRDHwBOi0-2n/view?usp=sharing

If you could get the AA80E CAN information, that would open the door for other Link ECUs to use this for conversions etc. There is quite a bit of interest in getting the AA80E behind JZs. Would be a real option if Link supported the CAN messaging to the TCM.

Vaughan, asking if possible you guys can look at a condition for turning on Overrun Fuel Cut? Or better still able to add a axis to the overrun Deactivation Table? Reason for this is some autos (like A340) free wheel in lower gears like 1st and 2nd if in D. This can cause the overrun to kick in and out, bouncing. Would be nice just to have overrun fuel cut on higher gears/speeds..

canchecked are also a good choice. They have a CAN based EGT amps now too.

Just an update, the DMCD works great with the Toyota ABS sensors. Only have the left side wheel speeds hooked up for now as I only had 2 wire shielded cable spare. RR is from the speed output from the ABS ecu itself. RF not connected currently.

Yeah Vaughan I was going to use a couple of those, but they don't tend to ship international to us in ANZ unless it's a bigger purchase. I ended up purchasing a Motec DMCD for $100AU that "should" do what I want.

Would love to be able to set the voltage thresholds on the DIs.. at the moment there is no way to change the trigger point. Background, using ABS wheel speed sensors, some sensors not picking up a trigger till 40kph.

Just do what Toyota do.

Which car? Most Toyota's (6 cylinder) run two sensors. Knock1 usually Black wire to ECU, then other pin to ground. Knock2 usually White wire to ECU, then other pin to ground. But some Toyota's use gray instead of white.. But Pin 1 on it goes to the ECU.

Of course, lots of people would love a Native Linux app, hell even an appimage. But it's a lot of support issues and development. I'd think Link would do a Mac one first if they ever did anything other than Windows. Only based on the user base. Really using QEMU with KVM and a Windows VM isn't such a pain.