Damn Dave, can I send my car to you to have everything set up right!? :biggrin::smile:
-Steve
Yes
Damn Dave, can I send my car to you to have everything set up right!? :biggrin::smile:
-Steve
If you go with the F/IC you can make whatever changes you want to the fuel system and still pass emmisions as long as the end effect is an engine that can be tuned to run very close to OEM design while in closed loop operation. Once the engine goes open loop the ECU stops looking at the O2 sensors and stops monitoring for efficiency, the onboard emmisions test do not run, so there is less to worry about causing a CEL.
The F/IC allows the OEM ECU to think it is in charge of everything, it does this by intercepting the incomming sensors (O2's, MAP) to the ECU altering them to get the ECU to act the way you want, it then looks at the outputs for fuel and ignition from the OEM ECU and modifies the outputs to the fuel injectors and ignition system to alter the way the engine runs. If you add larger injectors the F/IC will intercept the fuel injector pulse sent by the OEM ECU and shorten the pulse to allow less fuel to be injected into the engine. Then when you need more fuel it can also add to the pulse sent by the OEM ECU. There are limitations to the F/IC as far as injector size, I have had good luck with 550cc injectors others have run larger, but the farther you go from the factory injector size the less control you have over the new injector. Since this device was designed to work with OBDII OEM ECU's in most cases the OEM ECU has no idea the F/IC is there and will never throw a code if the tune for closed loop operation is correct.
The other limitation of the F/IC is that it has to modify the OEM ECU's signals and cannot generate its own signals like a stand-a-lone can. It has to react to what the OEM ECU is doing so it cannot be proactive. If you use it in the application it was designed for it is a great option, if you try to do to much like large amounts of boost and really large injectors you will not have an ideal setup to tune and may have issues that can not be worked out.
Dave
Dave, does the DashDaq have the ability to set of audible or visual alerts especially for sensors running in the background?
So I could keep my base CTSC system, add a FIC, Meth, injectors and pump... with a good tune hopefully have more accuracy of AF and timing than the base system, cool AIT's down with meth on the track, and possibly up the boost to say 9PSI and be fine. That sounds like it can net quite a bit more power, and it would pass emissions. The CEL system of the factory ECU would still be functional for the most part, and it would be fairly cost effective compared to installing an intercooler/aftercooler, water pump, lines, heat exchanger, fans.
Add a DashDaq with a NAVpod, setup some warning parameters, and be good to go.
Is this right? Or is my math wrong... LOL
Wouldn't this setup even be able to pass in CA?
You are correct that is what the F/IC was designed to do, it will pass the plug in test for CA, but will not pass a visual test, so as long as you have the F/IC installed in a location were it will not be seen you should have no issues in CA.
Just when I thought I was done with mods...
Honestly Dave... Holy Sh*T! This is the gauge setup i've been looking for. I don't mind the initial setup time. A guy like me actually welcome's it but I can see how some folks would like a plug'n'play solution.You can setup the DashDaq to do just about anything, it has an audible warning and a visual warning, you can even set it up to look a a specific signal and when it goes out of range you can have the DashDaq play a .wav file of your choice, so oil temps to high the DashDaq can actually say "OIL temp to high" or whatever you want to to say or just play a sound, or just flash a "WARNING" on the screen. You can change gauge color as a warning. If you go to YouTube and do a search for DashDaq there are lots of vids to see them in use.
This one is from a guy going over some of the features and show the audible warning and visual warning feature.
http://www.youtube.com/watch?v=hoHaLTvXKHs&feature=related
There is a feature for monitoring gauges in the background, they work but you have to think outside the box to make them work correctly, it was really put in place to allow a default set of parrameters to be datalogged reguardless of what you see on the screen. The only bad thing about the DashDaq and OBDII NSX ECU is the update speeds from the ECU is not very fast, but the limitation is the OBDII standard not the DashDaq and any other scanner will have the same limitation. I use the OBDII data for things I cannot get any other way, like calculated load, fuel trims, or commanded spark. I use the Zeitronixs ZX2 to gather all the other signals I want to have a more real time responce from (60/sec), like RPM, Boost, Wideband O2, Throttle Possition, and Fuel Pressure.
Another thing you can do with the DashDaq is you can look at a sensor and apply a formula/calculation to the signal and then display the resulting calculated number in any form you want. You can almost do anything you can think of as long as you can do the math. It is sort of limitless.
Here is the bad thing about the DashDaq, becuase you can do just about anything, you have to do almost everything, there are some pre-installed themes to get you started, you can download their graphic editor and make any screen image and gauge style you want, but it will require lots of time and it is not what I would call point and click easy, you have to do the work to make it work. There is some good people using the DashDaq and they are willing to help/share their work. There are even a couple of guys that will design what you want and charge you for a completed product.
Dave
Np! I think we're at a point in this thread where people need to start data logging so perhaps we're still moving forwardDashdaq looks good but the screen is small. Dave did you look into these at all:
http://www.plxdevices.com/
It's the best I have seen so far. Ryu, sorry if I am derailing the thread a bit.
Honestly Dave... Holy Sh*T! This is the gauge setup i've been looking for. I don't mind the initial setup time. A guy like me actually welcome's it but I can see how some folks would like a plug'n'play solution.
One last question... I do see the harness for the AEM+DashDaq but is there a F/IC+DashDaq solution? I'm not sure if that's even possible since i'm still trying to get a grasp of exactly what sensors can one read from the OBD1 ECU and what does one need to add to get the F/IC (or AEM for that matter) running properly.
On an OBDI-F/IC setup you will have to add all the sensors you want to display,... If my car was OBDI I would consider the stand-a-lone and Dashdaq as the prefered setup, but you have to have a good tuner near by to get the AEM ECU tuned right.
Dave
Dashdaq looks good but the screen is small. Dave did you look into these at all:
http://www.plxdevices.com/
It's the best I have seen so far. Ryu, sorry if I am derailing the thread a bit.
Exactly my thoughts. After all this education I can see why the experts skip directly to an AEM standalone. You'll be getting a PM from againOn an OBDI-F/IC setup you will have to add all the sensors you want to display, there is no way to get any sensor data from the OEM OBDI ECU and no way to get data from an AEM F/IC to a gauge. You can get some data from the F/IC with a windows based PC/Laptop via a USB connection.
If you do a stand-a-lone AEM ECU and a DashDaq you will have full access to all the factory sensors via the AEM data stream. If my car was OBDI I would consider the stand-a-lone and Dashdaq as the prefered setup, but you have to have a good tuner near by to get the AEM ECU tuned right.
Dave
Exactly my thoughts. After all this education I can see why the experts skip directly to an AEM standalone. You'll be getting a PM from again
I wish I did. I do know 12 friends who have 12 friends and one of those friends can help me out but i'm too old for that. I can take the risk of possibly sliding the visual portion of the test as long as the car passes the sniffer. If I recall, on OBD1 cars there is no OBD2 ECU plug the smog machine plugs into to check for internal CELs. So it's the old visual + load bearing "dyno" + sniffer parameters. I think a good AEM tune can pass with proper Cats. Is it worth the risk? I don't know. Is it worth the hassle? That's a decision i'll have to make at some point.Ryu, you have a secret plan come inspection time? Enlighten me because I prefer the EMS over a FIC.
I'm looking at this list of OBDII parameters available on these devices... what is useful here? Not that much if you ask me.
Dave what are you using off the OBDII port that is useful?
just saw your video. Will it not fit in the factory NAVpod? Can you list what parameters you are using off OBDII and what you have the xyltronics or whatever for? You sell this stuff?
Dave,
What brand external sensors do you use? All Zeitronix? It doesn't appear DashDaq sells individual external sensors and wondering what other sensors are compatible with their setup. Hoping to put together a grab bag of sorts to choose from.
By the way, agree with your philosophy on the 12v world. Much props to SoS, DA, AW, LF, and the other folks who are able to make it work. Oh, and thanks for the video!
I was lost looking for sensors on their site too. Got a link on what we can pick from?