monya

thanks for the reply , correct i have it set to run when stalled to log the first start, confirms what i was thinking i just have never seen a number that high and thought maybe i had something wrong,, not having to calibrate it is messin with me lmao

getting ready to do first start and i just got the canlambda set up in ecu it connects but reads reaaly high! 148.75 ?? i havnt started the car yet but ive never seen a wideband go above 22-24, so im not sure if something is off or not or if i just need get some exhaust to pass by it

I’ve wired to the above diagram and all is working 100% as intended, thank you

Thanks for the edited diagram, I have a better work around than my original idea Regarding the chassis relay, it doesn’t tbh I’m just going off the factory wiring diagrams while trying to use the relays how the factory Intended, while trying not to modify the cars factory electrical system, only making modifications to my jumper harness adding a relay for key on + to - to control chassis relay, should do the trick, thanks much!

It’s way more complicated than it needs to be but I think I’ve come up with a solution, I just want to clarify if it might cause an issue, more info idk if needed but I’m wiring to a 2016 Scion frs using a kpower pnp jumper for a haltech I’ve re-pinned for the link, & all the relays are wired hot so I can’t change that, I also want to keep keyless entry so I can’t add a relay on battery cable after melting my brain and taking a nap, I’ve come up with the idea to put a relay inline with aux1 at my jumper board/harness to connect/disconnect the vtc solenoid with key, cutting off that feed back, While running other aux channels through ign/inj aux @Adamw does this sound like a feasible solution? thanks

Here is a super simplified version,

Yeah sorry xtreme wire in, I think my issue is 12v feedback from main relay e throttle relay and chassis relay are also wired for low side drive, when set to low side i get error on the aux channel with vtc and vtec solenoids , when set to high the errors go away but car doesn’t turn off,

I have configured the e throttle relay and still getting some feedback or something, have error with low side, and error gone but car won’t power off when set on high side

I found a hiccup with e-throttle wiring/relay, first I had e throttle +/- backwards, fixed that and then did the set up e-throttle and added the e-throttle relay & the error went away but car didn’t turn off with key so sorting out relay, should be fine after that tho,

Link xtreme g4x k24 I have wired the vtc and vtec solenoids to low side, feeding them 12v & the aux 1&2 are red showing error? Doesn’t actuate when testing either, When I set to high side drive the error goes away, Any ideas ? Thanks much!

i would appreciate that, as i havnt found to much info on it, so im hoping to get a little head start if possible

is anyone willing to share a file for 86/frs/brz, for the can data TIA!

thanks brad! i didnt think to look at the supra base file ill start with that

does anyone have a good 2jzge vvti na/nat/gte file i can use to compare what ive got ? i built my maps from a buddies g4+ monsoon 1jz vvti file on old firmware, i upgraded everything and moved to my monsoon g4x 2jzge vvti with turbo ive had the car running for a while doing my 500mile break in for my new transmission and it drives well, afr are ok, but ign and vvt i have no clue so i was wondering if anyone had a file i can compare/reference my file with just to get an ide where im at? thanks

UPDATE ive got it sorted out im 90% sure the fix for me was deleting contents of %appdata% back up your maps/logs before you do anything.... just incase anyone else runs into this issue,, this is what i did when uninstalling and reinstalling didnt fix it type %appdata% in the toolbar at bottom of home screen hit enter,, find the PClink folder open it and then delete the contents inside, restart computer open PClink then close it and the next time you open it should have a new appdata file saved, back to normal

its in the proper file location and i replaced the file, i also gave the computer full permission of the file, and still the same

i have a log file open, here is a screenshot, as you can see the range is very small i have tried changing this in parameters but when i click ok, it doesn't change, its locked like that on every parameter

i cant figure out how to fix my issueim not sure how it got this way, but im not able to adjust the range or color line for graphs of my time plots in parameters , when i input the changes and when i click ok it doesnt change anything, all my time plots are white cubes and zero for the min and max values making a bit difficult to read logs

ok then all is good, my ignition switch is probably on its way out most likely why it didnt turn off yesterday

update: so i went out to car this morning and started it up again see if it was still staying on before i start messing with things and to my surprise it shuts off when i turned the key off, but now for some reason it turns off and doesnt hold the power on, it just stops engine right away and then the relays can be heard clicking off in roughly time its set for after engine is off,, weird part is it was functioning properly before updating, im thinking my ignition might be faulty that could explain the car staying on, when key out/off but that wouldnt explain why it turns off right when turning key off, only thing ignition is wired to is starter and di #3 with diode to ecu power

monsoonx i just updated to the most recent udate and i have had power hold configured and properly functioning previously , have been driving the car for a few weeks no problem,, after update car stays on with key out and i have to uplug power to kill the car none of my settings seemed to have changed during update so im not sure whats going on 8-29.pclx

the device paired to my phone, tablet and laptop just fine, its just not communicating with the ecu, on any of the devices,, i tested it on my friends 2019 tundra and it worked no problem getting a buss error and receive error counter to 105

so i tried setting bit rate to 500, 250, 125 & 100. Also, i did turn the generic dash to off and double checked wiring at port and still not making connection with ecu tried with obdlink app and realdash app both with same result

monsoon g4x and ive wired as diagram shows in the communications wiring, obd2 port to ecu 8-20-tune.pclx

yes just updated this morning