wastegate

Know this might be a popular one, but a wheel speed to CAN interface would be a huge welcome. A lot of the Link products can't take a raw ABS wheel speed sensor input without a divider and a lot of customers would love to have all 4 wheels input without using 4x DI's. Couple of products already out there from KMS and ECUmaster but they seems to be extra ordinary expensive for a 4xDI to CAN converter. https://kms.vankronenburg.nl/kms-producten/accessories/kms-speed-sensor-can-converter-4-channel https://ecumasterusa.com/products/wheel-speed-to-can-module?variant=13733653839933 The ECUmaster one even requires more hardware just to program it..

Set a AN for the rotary switch. 5V from ECU. Set the AN as a GP Input, give it a clear label. Set Calibration to a unused Cal. The Calibration table should have a input units as volts, can set table increments to 1, most rotary switches you can lockout the other unused steps on the switch itself. Create a table with the steps eg 1..2..3 and the voltage for each in the table. You can workout what each step if using Ohms law or put on a multimeter. Once you have a Cal table and a AN mapped tot he switch, you can then create a boost table or Wastegate DC% 1 - Active table with RPM on the X-axis and the AN input on the Y-Axis. Then map it out with higher duty with the higher rotary position.

Thanks Adam, will have a play.

Hi Adam, Sorry for Zombie posting this but had a question regarding the CAN structure and CAN IDs. My friend makes a Gauge that was made for the Haltech originally. Uses a CAN ID+N similar to the Race Tech above. My question was, is there a way to address different CAN ID eg +1 +2 etc without needing to use a separate channel for each to specify the new CAN ID? At the moment we are using 3 channels with separate CAN IDs and a user stream on each, then they have a single frame on each stream with the parameters. We tried it with multiple frames on the one stream but the frames seemed to mix. So had to do above. We managed to get this working with minor changes to his code but would be nice to get all the streams onto one channel, without needing to completely rewrite the audrino code. Here is the gauge working with the multiple channels for a example. Regards Nick

Enable PC logging on your laptop and save it. Attach to this forum. There are a few 2JZ maps around in these forums you can download and compare. But can be a number of things, if it's almost starting then I'd be looking at your cranking cold start map. Also are you piggy back off the stock ECU? Is the stock ecu still controlling the throttle?

Heads up, will need at least a log. That way can see the difference between the Throttle Position (TP) and Accelerator Pedal Position. (AP). Also the map is handy too to see the settings.

Depending on the number of teeth the ABS hub wheel has, it might be too high for most ECUs, only Thunder would have a high enough HZ rating to count that quick. There are converters that will change the frequency from say 1200Hz to under 600Hz that would then be usable in most ECUs. This has been covered a few times in other threads. Mostly using ABS sensors for traction control etc. Now, looking at the 2004 WRX/STI wiring diagram, it relies on the gearbox speed sensor for at least the stock cluster. So if you don't have one, the speedo won't work as well. I looked to see if the ABS computer has a SPD output (like some Toyota units) but you are out of luck there. My best advise, chase up a sped sensor and install it into your new gearbox.

Thanks blokes! Managed a little bit of both and seems to have settled it down. Still a small about of wavey (2 corrections) at the transition but quickly aligns and follows the target. Will fine tune the PID tomorrow to get it even better but will do for now. Cheers Nick

Hi Guys, Hopefully can get some guidenence here in regards to the VVTI config for my Link G4+. I currently getting what looks like pulsed Inlet cam control, but sometimes it seems steady. Attached screenshot of what I'm seeing. I'm currently using a TALT+ Altezza PnP on a 2JZGTE VVTI from a Aristo in a IS300. Loom has been repinned to suit Altezza plugin and IO reassigned etc. Just wanted to get an idea on the config for the VVTI control on the 2JZ. I've set it up with the defaults as far as PCLink is concerned in VVT setup, selected Toyota 2JZ as Cam control (tried 1JZ too). PID is default (have not been game enough to try this yet). VVT solenoid is on AUX1, 300HZ (tried 100HZ too), CAM type is Inlet /LH. Trigger 2 VVT is reluctor, offset to 175 ATDC. Confirmed offset with Cam Angle test. Scott's Map 07052019 - Flex Tune - Nick edit 03082019 - cold start better - new VVTI map WIP.pclr Log 2019-08-5 1;36;11 pm.llg

Ok, thanks Adam

Thanks on question one Adam. Question two, while I was aware that Toyota use BEAN, the Link itself uses CAN and relies on a CAN to BEAN convertor (coded by Zac as part of his Uni degree) which is special to this ECU. If there is no way to find out what address to put into the Link then that is fine I might hack the dash itself and run a wire out so the ECU can use a output to light it. Cheers Nick

Hi Guys, On the Altezza PnP, the manual says that DI7 goes to AC Pressure Switch (N6-"PRE") and DI8 goes to AC Clutch Lock (O8-"LCK1") Yet on the base map supplied (and online) these digital inputs are unmapped. If this correct? Can these DI's be re-purposed if not needed? Are those functions needed? Also while I have this open, I'm also configuring Cruise Control, do you guys know the CAN address to set the cruise control light on the dash? So it can light this if cruise control is set?