MarcusP
Members-
Posts
70 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
MarcusP's Achievements
-
I get a bunch of error messages. It’s a 4 or 5 message rotation on mine.
-
MarcusP reacted to a post in a topic: G4X Fury to AEM Dash
-
Does the X and the + have identical can output? They don’t have the X in the software
-
Is there a DBC file available than I can load into the dash software so I have all the available CAN channels that are available to be displayed?
-
koracing reacted to a post in a topic: upgrade from + to X
-
Makes sense. E0 isn’t available here and e85+ can only be bought as race fuel. Neven e85 from the pump is hard to find. I would think that if your e10-e85 tune was on point the ecu can handle corrections for e0 and e90 without a hiccup.
-
I figured you should set table 1 at the lowest E and table 2 at the highest E you plan to run and let it blend between them. I’m never going to run e100
-
I’ll try that in the morning. Thank you!
-
This is still very rough on the e80 side but you will get an idea.
-
I’m running the older ID 1700x injectors. I only find one flow number on their site and it’s not fuel specific that I can tell. I have both fuels set to the same number
-
So the fuel charging coefficient for 91 octane which is e10 here is set to 10. On the flex side we are at e80 and the fcc is set to 30. the 91 tune is petty set, should I change the fcc for flex to 10 to get the numbers to line up?
-
Im in the middle of doing the same thing, unfortunately no someone has to manually move everything over.
-
Is it normal that the e85 map actually has less VE than the 91 map? Seems backwards to me, but we keep pulling fuel and the e85 map is still rich.
-
I have mine wired into DI7 but you can put it to any digital input. Set up depends on the sensor you are using. PC Link has good info on the set up in the program
-
Correct. The vehicle runs. I am getting random glitches like the O2 sensor and flex fuel sensor disconnecting. Otherwise I’d never know there was an issue unless I opened the firmware update tool
-
6.22.8 went back into safe mode 6.21.14 is in normal mode