JMP

what particular computer-specific items cause the glitches? As I've experienced them on all the different notebooks I tune with, and don't see the same issues on previous G4 stuff on the same systems. I've even done a fresh bare-metal windows install on one of them as a test with all Microsoft-supplied drivers through Windows Update and the issues persist

I'd be looking for noise on the signal wiring, what else is connected to sensor ground?

I'd wire it to INJ8

Feed one wire on the mac valve with ignition switched 12V, then connect the other wire to one of your spare Aux out's

you can remove it and use a spare Aux output to switch the supercharger clutch via a relay

Here's mine from a few of the systems I've experienced the glitches on DxDiag_surfacelaptop.txt DxDiag_X1Carbon.txt DxDiag_XPS15.txt

it's not scaling on any of my systems either they're all set to 100%

I've experienced similar Dell XPS15 running Win11 home build 22621, Intel Core i7-12700H, Intel Iris Xe Graphics and also GeForce RTX 3050 Ti mobile GPU Also on an older Win10 i5 Microsoft Surface Laptop

My Mine is the same, was doing my head in trying to figure out what thread it was meant to be

are the exhaust ports different lengths from the valves? I generally try to install the sensors with same difference from the valves which can mean different lengths from the head flange depending on the engine. I don't have an answer for your fueling at idle as the cars I've got EGT on are circuit cars and the readings are used to help trim the top end of things

Lots of good info there, racking my brain to think how similar can be done to address the internal lambda controllers

When using an exhaust pressure sensor, it looks like that reading is used for compensation on both lambda controllers. Is there a way currently or maybe future plans to be able to assign individual exhaust pressure sensors to each lambda controller, for a scenario where you're reading 2 different banks for instance

your tuner has read the help file right? I use the 2NZ VVT trigger mode and 1ZZ Cam control mode myself on all the 2zz's I do on Link ECU's, I've also had them work when using the 1ZZ VVTi trigger mode. Sounds like you need a different tuner that knows what they're doing

you set it up through AIM Racestudio configuring the dash directly

I'd be looking to identify the cause of the drop myself. Looking for correlation with other parts of your logs, checking the pump supply, sensor voltage supply, sensor type/location etc etc.

just set one of the switch conditions to your CAN DI in the same method as Adam has shown above

I'd be running a system file scan and then applying all pending windows updates as a start. If it persists after that analysis of the crash dump file will give more clues a) Press Windows key + X, select Command prompt (Admin) to bring up elevated command prompt. b) In the command prompt type the following command: sfc /scannow and press enter. c) After the scan, restart the computer and check if the issue persists. Once the scan is done, restart the computer and ensure that the computer is up to date with the latest Windows Updates.

Is anything recorded in Windows Event Logs when it crashes? I'd expect something to be logged in either the Application or System Event logs which will point you in the right direction

Thanks guys, working nicely

next thing I'd like to confirm, is the CAN ID in PCLink in Decimal or Hexadecimal format? With both PCLink and the Blackbox set to ID 400 it didn't work, the BlackBox uses a hex ID

awesome, I'll give it a shot and report back

Hi, I'm helping a friend finish off his project which involves a G4+ Xtreme and Moristech/Black Box P30 PDM. Final pieces of the puzzle is switching the thermofans and fuel pump over CAN. The documentation from Moristech is basically non-existent for their CAN Input so I'm hoping someone here could provide some guidance. My plan was to send Virtual Aux status' over CAN for the switching of the thermofan's and fuel pump, but would like some feedback on if this configuration looks right before I go back to the car for the final touches. Thoughts on Link CAN config: And an example of what I think might work in the PDM CAN Input section: Any feedback or examples of what others have done would be appreciated, here's a quick video of the car in question

E2 is the sensor ground that matters, connect that to the Link's sensor ground. E1 goes to the head so it can go to one of your Link Power grounds Here's a bit of a pinout I did for a Storm on a ZZE122 1zz Corolla a while ago which might be useful for you

you've got way too much dwell in there, this works well for the ZZE corollla coils:

you'll need to add a terminating resistor at the end of the bus as detailed in the CAN Lambda manual