Are you getting RPM? Does tunerstudio communicate with the firmware?

Can you post an msq?

Ken

i think the simple is no. if i recall, there was an impossible 5 digit number in the RPM field ... something over 60,000.
as far as i can tell, yes. a few messages aside, it seems to communicate with it just fine.
if i don't get it right now, i will keep trying. i have a couple i can post. i've been kind of having fun trying to come up with VE tables. :) if worse comes to worst, and i am unsuccessful in posting it here, would you be willing to let me email it?

Something over 60000 is a configuration error. You have a settings conflict. Try to find out what the actual number is.

Ken

when you say settings conflict, are you specifically talking about an input error on my part in Tuner Studio or does that include possible conflicts between Tuner Studio and the firmware? i ask simply because usually when i am using Tuner Studio online with the car, when they connect, it gives me a message referring to some fields (i forget which right now) and i pretty just OK and move on. the next time i go back to the car, i will pay closer attention though. for the record, i'm using version 3.0.3.

also, i've been going over some of the wiring instructions and something struck me. where it says the Ne- signal should go to pin 2 (MSII ground), should it matter if i grounded it by itself? considering i made a special ground harness and the MSII grounds were incorporated into it, i'd tend to think not, but i'm going to try to not take anything for granted. so that's why i'm asking.

There are some settings conflicts between the various settings in the MS that can't be prevented with the tuning software.

If you get RPM over 60000 one of these configuration conflicts has happened. It means that there is a conflict between 2 of the settings that are set in the firmware.

Ken

so should i try to wipe the firmware and load an older version or is there a way for me to rectify the conflicts within it?

You have to figure out what the actual problem is and then find the settings that are conflicting. Wiping the firmware or going to another version is not the proper fix.

You can use the mini-terminal feature of tunerstudio or megatune to see what the cause is.

Just turn off the MS, open the mini terminal (set to the proper comm port) and then turn the MS back on. It'll tell you what the problem is.

Ken

(from this THREAD)

would any of this apply to MSII?

it would, except if you're getting a config error, in which case you need to fix that before you do anything else.

Ken

I also had that 65535 rpm, in megatune 2.25 this happens strangely if you use in this menu 'every rotation of crank instead of cam

You probably have other settings that are incorrect causing an impossible configuration. Please post the whole msq.

Ken

okay, it took a few weeks, but i was finally able to get back to the car yesterday and try this. the message i got was, "trigger offset must be zero in EDIS and trigger wheel mode." so what i did was to go and set the ignition to EDIS and change it to zero, burned it, then went back and changed it back to toothed wheel. the car still doesn't spark when i crank it, but the message is gone when i bring up the Mini Terminal.

i think i'm going to go back, yet again, check the wiring for the coils and crank angle sensor. however, i think i'm at the point where i'm going to need a fresh pair of eyes for any true progress or new ideas to be made.

yep, that's the number. :) i actually had mine saying "crank" before, but i switched to "cam" (just in case) and tried it. the Tach needle (in Tuner Studio) stayed pinned on 8000 and it still showed the 65535 RPM.

there's probably nothing wrong in the wiring, there is a configuration error. Please post the whole msq.

Ken

here it is.

okay, let me try it this way. does anyone have a "working" *.msq that they could share? i see 1 view on the one that i posted, but no feedback thus far. i've spent the last couple of days going over my wiring (just in case) and i can say i'm satisfied at this point. mini terminal is now clear when i do the procedure muythaibxr described above.

on a sidenote, i've been so engrossed in all these spark issues that i had forgotten that i'd left the coolant temperature circuit undone because i was waiting to find the right pigtail for it. so, as soon as i get that and some loom, wiring will be 100% complete!

i don't know if configuration is dictated by what version MegaSquirt one has, but here are the cliff's note on this particular setup:
MS II 3.57 (using a self-made DB15 cable for CAS and coil trigger circuits)
Gen II ignition system

so anyone have complete file that fits this that they could share, please, by all means.

Here is the one I have now for the renesis, I had it running with the FC cas also, altough I did not save the msq,

I think i put all the setting back as they were.. so here oyu find it attached, hope it can help you..

Don't look at the rest of the file as it is only very basicly tuned..

I'll let him know you posted that. He's here. We were just working on the car and I think he's having a stroke. :lol:

I am on vacation now, so I am posting from my phone. When I get home I will post one of my old ms2 tunes. I have made a lot of drivability improvements since going to ms3 but it should still help.

Ken

i've been having other problems complicate my plight even more. i think my USB adapter cable (or it's driver) stopped playing nice with the computer, so now whenever i open Tuner Studio and bring the MegaSquirt online, the bloody computer goes dead with a stop error!

anyway, Rub20B, i was able to load your *.msq and burn it. i'm still not getting any spark or any signs of RPM in Tuner Studio. i did get 5 warnings though:

1. egoTarget not in current configuration. Value ignored.
2. mafOption not in current configuration. Value ignored.
3. mapsample_percent not in current configuration. Value ignored.
4. feature 413_dbg not in current configuration. Value ignored.
5. feature 413_missdbg not in current configuration. Value ignored.

i'm at my wit's end now.

EDIT: by the way, thanks for the file. :)

much appreciated. i hope you're having a good time wherever you are.

quick question: how does the MSII know when something is connected to it's DB15 port?

i'm starting to think my problems are in the DB15. i'm thinking since i am still not getting spark with an *.msq file/configuration that is known to work, then it must be a communication failure between the CAS and the MSII. my brother tested the hardware (the CAS and both coils) and everything spec'd out fine.

do you have any thoughts on this theory?

Have you verified the 2nd VR (LM1815) is working? ypou can easily do this by just using a led with a resistor on the output wire, you should see the led blink when you turn the CAS by hand

no. i did not think to do that, but i will. hopefully, i will be able to go over to the car tomorrow. thanks for the idea. just for clarification, when you say output wire, you're speaking of the wires that carry the MSII signal to each coil, right?

no I was referring to the wire that goes from the 2nd LM1815 circuit to the MS2, if you attach a led between ground and that wire (use a resisor or led will die) you should see the led blink a very sort time when you spin the CAS by hand. this proves that the 2 tooth VR circuit is working

OK, he just pulled it apart again. Is that between Gnd and SG or Gnd and Proto gnd? He realized that he may have reversed those two wires. So he fixed that as well.