MicroSquirt.com read only forum (Jan.15,2018)

Gary,

If I understand correctly, you are wondering how the transition between the VE table points is handled.

The MS-II (and all MS codes) does what is called linear interpolation to get smoothly from one point to the other. Let's do a simple 1-D example, with an a VE of 10 at 1000 RPM and a VE of ...

Jonathan,

That last sequence indicates that either 1) the microSquirt isn't in boot mode, or 2) there's a hardware failure causing no communications. The fact that fuel pump output cycles (there is code running on the processor or it won't do that) plus portcheck can't connect (it wants the uS to ...

Ooh, maybe inadequate supply cable size??? How big are the wires supplying power to the MS?

Eric

Or maybe just good old hyperterm?

All Programs -> Accessories -> Communications -> HyperTerminal

You can tell if you are connected properly because "S" and "Q" typed into hyperterm should cause MS-II code to echo back their signature and version info, respectively. (That's basically all that ...

Justin,

You're way out of my area of expertise... Maybe try shielding the wire by wrapping it with aluminum foil? I remember Andy Whittle doing that on some MAF lines and it was a good diagnostic.

Eric

I just thought that the dialog box opens and removes the info, must have default settings for the dialog box, and when you cancel they are still =0 and it can't accept these values.

and then you get the error messages and bingo..
Ok, I'm not sure I'm following you here. What is the state of your ...

The port checker is looking specifically for MegaSquirt responses, so if you don't have one connected and running, it will say there's nothing there.

Eric

If the bootloaded utility can connect, that will narrow down the problem to Megatune configuration.
That's because I use exactly the same comm routines in both the Download utility and in MegaTune. :)

Try the portcheck.exe that's in the MegaTune installation directory. If that can't find anything ...

Oops, as usual I forgot to answer part of your question...

What version of MT are you running? The 2.25p1 version was recently updated to 2.25p3 by the addition of some better initialization in the comms section and that might help.

Eric

Justin,

If I'm reading this correctly, you do not have the problem when the cable is plugged in and MT is not running? That's very strange, usually these problems are due to the cable acting like an antenna and pumping noise back into the ground plane or something like that, so they occur ...