pgmfi.org

That sounds like a behavior of the ECU not the simulator. I designed the board to not go above 190, however I purposely used thru hole resistors for guys that may want to change it.





There was a little bit of a fubar on the first run, half have holes and half do not. Future boards will all have holes.



I'll consider it for future revisions.





I hadn't noticed a significant voltage drop like that on my test unit, but if you are experiencing that, I find that the power cords from Linksys routers work well and can supply up to 1A of current.



Yeah I've been thinking about that also. I know that the VSS requirement is easily disabled in programs like CROME so that's why I didn't include it.



Check the other parameters. If MAP and TPS are below a certain threshold the injectors shut off prematurely.

Hope this helps!

Unfortunately, I initially thought the same thing, so I tried 3 more known good ecu's, running both Neptune software and Hondata S300, same problem with the ECT pot not working properly, unless the SCS switch is on..

[quote]Quote:
I found that the ECT pot does not properly work if the SCS switch is off.. If I turn on the SCS switch, the ECT pot works normally.. Odd..


That sounds like a behavior of the ECU not the simulator.
[/quote]

Oh, one other thing to add, I occasionally get an IACV and CYP sensor error for no apparent reason.. Could most of these issues be related? Should I send the unit in?

IACV is to be expected. There is a way to disable this code with CROME, I'm not so sure about other systems.

CYP I've had come up if I do erratic things with the RPM, but overall its been pretty solid.

Might want to add that to the information people see when they are about to purchase the unit, lol.. "IACV error codes are to be expected, we haven't figured that out yet" "CYP error codes are to be expected if you change the rpm erratically?".

Not trying to be a pain in the ass here, but it would be helpful if you included the list of problems with the units when they ship to the customers, so people like me don't bother asking why things don't work as expected.. Would the IACV issue be remedied if an IACV were wired up? The CYP error should probably have been addressed before release, no?

For $200, I'd expect most of these issues to be worked out, or at least the ability to update the firmware as you figure out the way to solve the problems..

Is this like buying a multimeter that doesn't read dc voltage above 9 volts, because I have one of those in my trash pile right now, lol..

It may be hard to see that I'm trying to make light of the issues, so don't assume that I'm mad, I'm just concerned..

I think you're missing the point of the engine simulator on the CYP, it happens because the ECU knows that the engine can't physically change the RPM that fast so therefore it throws a code.

You have to understand that this thing is adjustable but as the user you do have to realize what is physically accepted by the ECU...

No harm taken, and as far as the IACV and VSS and Power switch and things of that nature, all of this was preconceived. But as I started approaching completion I experienced a high level of "feature creep" kicking in. Originally the design didn't have injectors, VTEC, EGR, FPR, VTP or anything like that. But it was like the old motto "It can always take one more pound" in the turbo world, on my design it was, "Well it can always handle one more LED". Of course with each additional LED, its another wire that needs to be soldered, or an additional switch, etc. etc.

I drew the line at stuff that I knew for certain could be disabled using free software like CROME.

Using feedback from you guys I'll be able to further refine the design.

For the IACV, if somebody knows the resistance the ECU expects, I can probably insert a resistor to simulate that.

Some of us are too picky to use software like Crome, especially if we already tune with Neptune and Hondata systems.. I figure the simulator will help me track down odd software related issues without putting a car back on my dyno, as well as testing ecu's.. The more features the better! Honestly, with a bit more refinement, you could sell the hell out of these things at a lower price point, (due to higher production runs to reduce cost), and help a lot of people in the process. I still have no idea why people didn't make these years ago..

I plan on making a nice clear acrylic top with laser etched text for this thing, once I get it to work the way I need it to.. So, about that ECT issue, got any other ideas? Should I steal the unit from HRTuning, and put mine in its place?

The ECT thing, I mean really the SCS has nothing to do with the ECT circuit. I mean you can see the circuit yourself, so that has to be something going on inside the ECU. I know that unless you are feeding an RPM into the ECU, TPS doesn't read right, maybe it is a similar behavior...

Na, I tested with mine using both NepTune and Hondata and it works fine for me. I don't see how the circuit could be effected either, but it must be something with his unit. I'll stop by sometime soon and bring mine along. Test his unit, and test his ECUs with my unit to help you figure this out.

Sweet thanks!

I haven't had any issues with the simulator it works as expected. This makes v-tec conversions a lot easier to test. Props to Darren for creating this Simulator. Once you set the knobs to the proper settings you are good to go.

Peace!

Received mine last week and just am wondering if the CEL LED ever shuts off? It seems to be either dim or bright but never off. I get a code 14 using the VTEC check .bin and VTEC engages, but want to make sure I'm using it right.

i observed the same as Dweezil about the CEL being dim all time, even with no CEL present... maybe we need to up the resistor in series a bit more!

another nice feature is that now you can test the FPR relay. I have some ECUs that do not turn off the FPR at very low revs, being that the culprit for mysteriously flooded engines...