Syvecs Forums

Hi,

I am building a custom 3D table to implement a meth injection failsafe. I am using FP2 as the Y axis to monitor meth pressure and MAP in the X Axis and the table itself is WGMapLimitAdd where I can reduce boost pressure if low or no meth pressure is detected on certain MAP levels i.e. 2 bar of boost and low FP2 pressure will trigger a -1000 mMap limit.

However I run into an issue where I want to turn meth injection off on some cal settings however this failsafe table will likely be triggered preventing me from increasing boost.

The only option I can think of right now is to target 1000Mbar above what boost I want (with meth off) i.e. target 3000mbar when I want 2000mbar and let the failsafe table remove 1000mbar. Is there a better way of doing this by any chance?

Why do you need MAP on the X axis, as you could just swap that for CAL position?

I'm spraying meth progressively, so I have a similar situation as the OP where I need to have duty on one axis.

Mark the one you created as "Raw Value Computation only" (it's at the bottom of the list of when you open CMXXX Use) and then use another 3D table which is used for whatever you want to correct (WGMapLimitAdd), where the X axis is the Cal and the Y axis is the output of the first table (it will be called rawComp_CMXXX). Then in that map, set the output = Y where X is the Cal you're spraying meth in and 0 in all the others.

You need at least 1.680 firmware for this.

MReilly wrote: ↑Tue Jun 08, 2021 12:46 pm Why do you need MAP on the X axis, as you could just swap that for CAL position?

MAP axis to allow meth to run correctly if theirs pressure on boost and drop boost if no or low meth pressure.

nmerdan wrote: ↑Tue Jun 08, 2021 5:57 pm I'm spraying meth progressively, so I have a similar situation as the OP where I need to have duty on one axis.

Mark the one you created as "Raw Value Computation only" (it's at the bottom of the list of when you open CMXXX Use) and then use another 3D table which is used for whatever you want to correct (WGMapLimitAdd), where the X axis is the Cal and the Y axis is the output of the first table (it will be called rawComp_CMXXX). Then in that map, set the output = Y where X is the Cal you're spraying meth in and 0 in all the others.

You need at least 1.680 firmware for this.

Will upgrade firmware tomorrow and give this a go. Another option I was exploring is using Nitrous functionality for meth, just need to see if the new firmware will allow me achieve the same result as above with Nitrous as opposed to a custom fan PWM table that I currently have running to control meth pump and solenoid.

Meth

you don't necessarily need to reduce boost, just ensure tuning is safe at all boost levels with or without meth.

Use a custom input for meth pressure so it makes sense, and add timing and alter fueling as needed based on this pressure.

Or I guess you could also add a table to alter boost target or wg duty based on meth pressure, but that's getting messier.

RICE RACING wrote: ↑Mon Jun 14, 2021 4:04 am Meth

onmeth.jpg

Yes sir

stevieturbo wrote: ↑Mon Jun 14, 2021 6:29 pm you don't necessarily need to reduce boost, just ensure tuning is safe at all boost levels with or without meth.

Use a custom input for meth pressure so it makes sense, and add timing and alter fueling as needed based on this pressure.

Or I guess you could also add a table to alter boost target or wg duty based on meth pressure, but that's getting messier.

That's actually a brilliant idea, I just set up 2 tables to tweak ignition timing and global fuel based on meth pressure.