wastegate

6 years on, still would love to be able to change this. The crosshairs are hard to see if you have gradient cells. Also G4X

Certainly some things to try. In regards to vacuum, it's only an issue with me for the first time after startup with minimal brake asset. I'll have a look at those misfires. Change plugs etc. Running pretty low gap at 0.3 as I'm still running the stock coils. R35 coils are on the plate so i can increase gap again at the power end. Will have a look at those misfires, what time stamps are they? I do have a ignition retard on gear change. Will give it a go Adam cheers

Trans is controlled by a Compushift Sport TCU. TC is not locked up at that point. I log the TC lockup as well. It seems to be repeatable at that speed. Can certainly feel it, at first I thought it was going lean as that was what I was seeing on the dash, but it's going rich then closed loop catching it, then whatever is causing it to go rich stops and CL has to add fuel again. I have pretty low vacuum anyway even at idle due to my cams 272, 9.9mm lift. To a point I'm putting a vacuum pump on for my brakes to help. Just seems puzzling that during that low speed cruise it happens pretty consistently. If it is a driveline issue and something in the trans binding up causing a little extra load I should see that extra load in the logs?

Have a weird little issue that has been tickling my annoyance. When cruising on the street, normal 50-60kph light throttle, sometimes I would feel the engine drop off in torque or labour just a tiny bit. I'd look at the Lambda and it would be pretty lean at 1.15 etc. Then restores back to around 1.0 and feels normal. I've tried to work out what is causing it for a while now and from what I can see in my tune and ecu logs, really nothing is a smoking gun. It just seems to go rich, then Lambda Fuel Correction kicks in, leans it out a bit back to 1.0 then about a couple secs later, bam, leans out where CL Lambda takes out all the fuel it put in. All this while same throttle input, speed and engine speeds. Eg just cruising down a 60kph road. Engine is a 2JZGTE, 272 Cams, Turbo etc with a A340e Auto. I'm kinda starting to lean on a failing auto maybe putting load on the engine while cruising? I can't find anything in the log to say the ECU is doing it. Just weird it goes mega rich. Here is a link to the tune file. https://drive.google.com/file/d/13siHUU6E5GH92eacB36jkLJ6z8c5IkyZ/view?usp=share_link Here is a link to the ECU log (example of what I'm looking at is at 1:10) https://drive.google.com/file/d/1TOzDgf1oI7hnyDx7mhaMa7fmD05d8uqt/view?usp=share_link Any advice is appreciated.

Hey Adam, Looks like this is hardware failure, the solenoid was stuck open a little bit each time it happened. It did it when the engine was at operating temp too so pulled it out and probed it with a precision stick, sure enough it popped shut. Ordered new one. Updating this for knowledge. Thankyou! Attached the startup scope anyway. https://drive.google.com/file/d/1NCrJrswFH6V9LzAXFyassQBRORKaujWV/view?usp=sharing

Hey Link, Need some ideas or analysis on why my Inlet cam is advancing 60 degrees while cold... It was a pain in the arse to start this morning and pulled the logs and found this. I managed to get it to start and after it got some temp it smoothed out and ran fine. Then logged a warm start and the inlet advance was normal.. Engine is 2JZGTE VVTi Tune file https://drive.google.com/file/d/1O_l6TosSkdAE9xCGwFW2b0s8qfxLEU_w/view?usp=share_link Cold Start ECU Log https://drive.google.com/file/d/13MluEyzjDLFPl4dy8isEyS6MiZNgkLxW/view?usp=share_link Warm Start ECU Log https://drive.google.com/file/d/10wsMmyoo7lOEbET41Sd2mjmsdaKYFaPa/view?usp=share_link

The Altezza PnP uses a CAN to MPX convertor. However the JZS171 might or might not use 100% the same frame structure as the XE10. But I'd be checking MPX pins on the ECU header are around the right way. On the PnP the pins for MPX are; E5 - MPX1 E12 - MPX2 I don't have the JZS171 wiring diagram but I do have JZX110 ewd. JZX110 shows MPX1 wire colour is R-L (Red-Blue) while MPX2 is Y (Yellow)

Not sure what I did wrong Adam on why it rounded so much, no of course not 0.02 :D. But thanks for the help!

If anything, I want it to goto GP Temp 3 so I can log it, and also push it to my dash. At the moment it's going there but only via a math block to get the correct result. Raw CAN value example is 9881 (as stated in OP) How would you ingest this data into the ECU? Given it has a 0.03125/bit and -273c offset?

So using 32 as the divider certainly works, but rounds to the whole number. Expected Result = 35.78 result using /32 = 35

Hi Link, I asked this question on the FB group but seems it was a stupid question and got usual Toxic replies. It might be a simple one but I feel like I'm doing it wrong or it's the limits of what the CAN calculation can do.. I have a J1939 CAN message coming into the G4X. CAN ID 419362819 (Extended) J1939 Transmission Oil Temperature 0.03125/unit with -273 offset. Link CAN Start Position 39 Width 16 LS First Unsigned. Raw CAN message = 9881 9881 x 0.03125 - 273 = 35.78c which is 100% what I want (Cold Transmission). However I can not put in <1 numbers in the multiplier So I'd need to multiple 9881 x 3125 / 100000 - 273 but I can't have a divider >10000. Doing 9881 x 312.5 would be ok but I can't have a decimal in the multiplier so I'd need to round up to 313 which results in a inaccurate final temp. For now I'm just piping the Raw CAN to a Math Block and doing the required math then outputting to a GP Temp but I'd really like if there is a simple way to get the CAN itself to do the math right?

I had this a while ago, contacted Haltech and they corrected the map. It should have been rolled up in the newest ICC firmware. Basically they changed the ecuchannels.json to correctly show the Generic Dash Gear Position numeration. { "unitGroup": 12, "unitSelection": 0, "ID": 40, "Name": "Gear", "DefaultLabel": "Gear", "DefaultUnit": null, "MinimumValue": 0.0, "MaximumValue": 15.0, "Shortname": "", "Function": "Gear Position", "Unit": "Gear", "PullupPosition": "", "PullupStatus": 0, "ThresholdValue": 2.5, "SensorIndex": -1, "MuxValue": -1, "MuxByteOrder": "", "EcuCanID": 1404, "EcuByteOrder": "3-2", "OBDIICanId": 0, "OBDIIByteOrder": null },

Looks like this little annoying bug is still in 6.22.25

Hey, I can only go off experience with calibrating fuel level on a IC7. But works the same. I had to use a 220ohm resister pullup (change it to suit the range you want). As I had a saddle tank, I drained the fuel out as much as the pump can grab on a level ground. Then syphoned the other side out via the level sender access hole on the other side. I then measured the voltage reading and marked that as "you're walking to the servo", put 10L in the tank and measured again. Noted this 10L as Empty voltage. I then filled the tank at the servo and measured the full voltage. It's a slight pain in the ass with a saddle tank but worked ok. I don't recommend reading the voltages with the sender out of the car as the intank full and empty ranges can vary. I also had two senders in serial. I do still have some variance in voltage, so I'm going to run new wiring to my senders as I'm currently using the stock OEM wiring which seems to be causing voltage irregular readings.

Hmm so that is not the first time I've noticed PCLink replace the ID... Usually when clicking on different streams it would randomly change the ID. To check, I reloaded the map, sure enough, it's changed back to the way it suppose to be 996.. Adam, Just replicated it changing the ID on me. PCLink_jYvjnZzZDJ.mp4

Not really a request for help, just sharing knowledge for others too. If you currently have a g4x and a IC7 dash, you will likely see some icons on the dash that just don't trigger with the Link protocol (Displaydash). A lot of these status fields are not in the standard Displaydash CAN package. And Haltech did not include them in the Link CAN protocol on their dash when you choose it. But don't worry, we can still get them working with a little text editing and CAN setup. There are quite a few options for flag/status on the IC7, a lot that is currently not integrated, like cruise control status etc. But for this setup, I wanted to get the Battery Light, Oil Light and Check Engine light on the dash. Prerequisites; Setup the IC7 in PCLink like normal, using Displaylink and ID Load the IC7 with the Link CAN protocol like normal. Check that your Link ECU is communicating to the IC7 ok. Save your IC7 .map config to a file. A good Text editor (Notepad++ is fine, vim if you are elite) A good zip utility (7zip is great, Unregistered Winzip if fine, ) Here is the full Haltech CAN schema as of late last year. It's the latest I got from Haltech. https://drive.google.com/file/d/1aHkwiXcw1WpFAPQFni7nCmqO_iwTeuIh/view?usp=sharing note: I'm going to use the Haltech can IDs and byte addresses here, only purely for ease of reference. But there is nothing stopping you changing the addresses, certainly if you have two status fields over two different IDs.. you can change the address in PCLink and also in the IC7 config. The status for CE Light and Oil Light used below, are at Haltech CAN ID 0x3E4 7:7 and 1:0 respectively. Secondary, we need to add the status fields to output to CAN in the Link ECU. 1. For the CE Light, I had to change the output from a DI it was assigned to originally to a CAN Aux 1. Go to "Auxiliary Outputs" -> "CE Light", change the Output to CAN Aux 1. You will need to change the GP Output 1 - CE Light to trigger CAN Aux 1 for SW Parameter 2. It isn't needed in my instance as the IC7 has alerts anyway for ECT etc. 2. For Oil Pressure Light, I setup a new GP Output 2, Labelled it "Oil Pressure Low" Output was CAN Aux 2, SW Parameter 1 = Oil Pressure < 15.0psi. No other conditions. So this will trigger CAN Aux 2 if oil pressure is below 15psi. The pressure value, you can change yourself, by my idle pressure when hot was 25 and I knew it got below 15, there is a serous issue (this is linked into engine protection not covered here). Now that we have what we want to send setup to send it on CAN, lets setup the stream. 3. In PCLink's CAN setup, add a new stream and put CAN Aux 1 (CE Light) as the parameter with a start position of 56 and only 1 bit wide. Then add any others you you may want, like I did adding the Oil Pressure Low. 4. Then assign the stream to a Channel, with a Transmit rate of 5 hz, it's only a status, doesn't need to be quick. And give it the correct ID, remember, Link uses Decimal, Haltech use Hex. 0x3E4 = 2047 6. Now we are setup to send the messages over CAN. We can move to the IC7 to configure it to receive the CAN messages and assign the correct status. 7. Now since the IC7 ICC software does not have any direct way to configure CAN messages, we need to do this old school and edit text files, or more correctly JSON files, which are a structured file for configurations used on a lot of things. You need to extract the .map config file as a zip file to your drive. Sometimes it's easy just to rename the extension of the config file from .map to .zip remember to backup your file before editing it. 8. Once the config file is extracted, it should have a new directory with the same name as your map name. You can then browse to the data directory, you should see a bunch of json file in there. You need to open the file called ecuchannels.json in Notepad++ or any other good text editor. If it looks messed up or everything is on one line, change your editor. 9. This is where we need to add in the new status fields. Scroll all the way to the bottom, now if you started with a Link setup in IC7, the last one would be Speed Pulse Rate. The config is enclosed in parent [] brackets and each Function is closed in child {} brackets and comma separated. This is VERY important, because if your commas and brackets are not right, the map will fail to load. Each new function needs to start with a { and end with a }, including the comma except for the last one. Example; [ { "Function1" : data, }, { "Function2" : data, } ] Here is the edits I made to mine. Which are enclosed within the main [] brackets { "unitGroup": 20, "unitSelection": 0, "ID": 88, "Name": "Check Engine Light", "DefaultLabel": "CHECK ENGINE", "DefaultUnit": null, "MinimumValue": 0.0, "MaximumValue": 1.0, "Shortname": "CEL,MIL,Diagnostic Light", "Function": "Check Engine Light", "Unit": "enum", "PullupPosition": "", "PullupStatus": 0, "ThresholdValue": 2.5, "SensorIndex": -1, "EcuCanID": 996, "EcuByteOrder": "7:7", "OBDIICanId": 0, "OBDIIByteOrder": null }, { "unitGroup": 20, "unitSelection": 0, "ID": 143, "Name": "Oil Pressure Light", "DefaultLabel": "OIL PRESSURE LIGHT", "DefaultUnit": null, "MinimumValue": 0.0, "MaximumValue": 1.0, "Shortname": "OilLight", "Function": "Oil Pressure Light", "Unit": "enum", "PullupPosition": "", "PullupStatus": 0, "ThresholdValue": 2.5, "SensorIndex": -1, "EcuCanID": 996, "EcuByteOrder": "1:0", "OBDIICanId": 0, "OBDIIByteOrder": null } 10. Now that the file is edited, save it. Now we need to compress this back to a zip file. You need to ZIP up the main directory with the data, images, qml, styles etc directories. You can name it something different if you like. Once zipped up, rename the extension from .zip to .map. 11. Load the config to IC7, make sure it loads ok. If there is a error, or crashes, you have failed at formatting the JSON correctly or fiddled what you should not have fiddled. 12. Once loaded to your dash, you should see at lease CE light and Oil Pressure light working, giving a little more OEM look. Hopefully that helps some people.

Cheers mate, makes sense.

Thanks Adam, seems to have helped! Idle settles on target nicely (as much as cams can). I have a side question. Should my Throttle be resting at 5% while at speed under decel (or <5% APS). Idle I understand but no matter what the car is doing, cruising at 100kph or around the street, the TPS always shows minimum of ~5%. I would have thought during a decel event, TPS should be fully closed?

New Map https://drive.google.com/file/d/1Ud05ODTCVPjJLFeana5_2_wK-5VSMb9x/view?usp=sharing New Log https://drive.google.com/file/d/1V4-xEe0wK_cSdj9azU1slZBJZCBa62NA/view?usp=sharing

Hi Everybody, I'm in need of a little advice, trying to get my cold start and idle sorted. Engine is a 2JZGTE VVTI with 272 Cams. Starts okish, just takes a few cranks, when it starts, the idle settles to 700-800rpm and is a bit cranky. Until the engine get warmer (over 40c) where it smooths out. However, I have set the target RPM to 1300 for colder temps, but it never get to that. I have Closed Loop enabled, I also have IGN control turned on with max advance 20 degrees. After start, the idle goes to 800rpm, and IGN is at 12 degrees, then about a couple of seconds, IGN control kicks in and pushes the IGN to 20 degrees to try and meet target, however all this does is drops the rpm about 100rpm then kinda goes up then down. Starts to smooth out once engine starts warming up. I've captured a PC log of the cold start and tune file. Log https://drive.google.com/file/d/1ULMaLkHUhJiwwCnNxeLiLMFNIS-v-wfo/view?usp=sharing MAP https://drive.google.com/file/d/1Ud05ODTCVPjJLFeana5_2_wK-5VSMb9x/view?usp=sharing I've tried to change the base position table from say 5 to 7.5 but doesn't seem to do anything. What am I missing here? Is it a fueling thing? Too much fuel during startup? Lambda is not enabled until 15 secs or so after and it's very rich. But if it's not rich, the idle is very lumpy.

Hi Adam, The Toyota shop manual states that STP should be below 1.5V with no brake applied. This is same for Altezza (just in japanese and with the correct pin on the ECU This is the Altezza wiring diagram, I'm unsure where that voltage is coming from. But will pull the pin and check. EDIT: Just pulled the pin from the ECU header and same voltages. 1.27v no brake and 12.4 with brake. I guess there is no way to change the DI falling edge? I noticed also that the STP also goes to the Skid Control/ABS ECU. The IS300 also runs a NC brake switch (ST-) as well. I might see what I did with that wire in the loom... might be a better one to use since it doesn't go to the ABS ECU. EDIT 2: Using ST1- into DI6 instead of STA from the IS300 loom worked 100%. Now have cruise control back working. Cheers

Hi Guys, Currently have an issue with the Brake switch. At the moment it's configured as per the Altezza base map for DI6 as Brake NC with a Pull Up and set to High. I have this in a IS300 which is identical. It was working fine like this with my G4+ and the G4+ was getting the signal from the brake switch. However with the G4X, it seems to trigger the Brake NC but then doesn't turn off. Latch is not enabled but it's acting like it. I have tried with a pull up, without it, set it to high, set it to low.. Only High with no pull up will sense anything and only the one time. Probing the pin, I get 1.27v and 12.8v with brake depressed. Looking at the wiring diagram for both Altezza and IS300, they are identical with 12v source from battery, to the brake switch then to the ECU to ground. From the diagram, it should be a Normally Open circuit until the pedal is pressed and closes the circuit. However the base map has a Brake NC as DI6 not NO. Seems I'm getting the right voltages to DI6 but for some weird reason, Brake is not triggering correctly. Map https://drive.google.com/file/d/1IFgz0CCCq9Erbu2caBoS-G188oSagFRz/view?usp=sharing

Thanks Guys, I tested the 3d idle out just now and certainly an improvement, not perfect as it oscillates once or twice before settling so will keep at it with your suggestions too Adam! Thankyou

Cheers mate, that makes sense now. Will give the idle base position table a play. Thanks for your help!

Thanks Vaughan, That is what is confusing me as the Overrun Fuel Cut status is ON the entire time. Yes, idles fine, you should be able to see in the ECU log, the Idle control has a speed lockout of 2kph. So surely Idle control should not be kicking in here?