Problems with ms1 started in tunerstudio

[Kwirk]

Hello everybody..
Bought my self a megasquirted car (been a while since i messed with one, back then in megatune...)

Its a ms1 v2.2, running fuel and spark, triggered from a distributor.
Volvo b230 engine.

I launched the ignition and made new project in tunerstudio (huge misstake i guess)
Should have started in megatune...

So it seems like all my settings went all off, nothing of the settings seems to be right and it sends errors. (dont know where to read them ? )
Im on a vista with usb adapter, problem? (i use it for my other car with vems)
the whole config was really messed after i launched it in tunerstudio, it has written it all in ecu too.

i cant open the ecu in megatune eather, it says some error has occured.
i cant burn new cfg there.

Has anyone had similar problem?
What should i do now?

I try change settings on the ecu on the car, and suddenly it plots a error in tunerstudio and im stuck again with pulseting fuel pump. and it wants me to change something.
But nothing seems to make it work..
Bleh..

I hope someone can take some time to help me..please.

Best regards

[Matt Cramer]

Please start by posting a screen shot of the errors. That will give us more to go on.

[Kwirk]

Hello Matt

Errors i got was ignition outputs twice and etc etc
I managed to get it running on 2 cylinders? i cant get it to run on 4
it runs on 1 and 4 cyl.
Checked all i can, even timing belt and so on.

Sometimes when i start megasquirt it plots error again, and the ignition outputs have changed again..wtf ?!?!
And i need to reload the whole tune..
This feels very unstable and dangerous.

What it going on.

Cheers

[jsmcortina]

Help us to help you :
1. Please do what Matt asked.
2. Upload your tune (MSQ)

James

[Kwirk]

Hello
thanks guys for taking your time.
I triend work on it again abit this morning but no luck.
Re checked crank tdc and so on.

I am not sure how to check the trigger angle ?!?!
Its a block mounted distibutor with 4slots and hall sensor.

I found out that the engine starts on 1 and 4 one time, and next time on 2 and 3 cylinder.
Strange

Heres the msq, hopefully you find something'

super thanks guys

!!!!!!!!!! EDIT!
Wow. for some reason the spark map is all crazy in my first upload ? what the heck..
I have reloaded a new msq here..
I went back to some old savings and found the correct map again...
Well still no cigar.

[Kwirk]

Heres my box from inside .
Fidle for spark out a ?!?
It only start on that..

[Kwirk]

Heres my box from inside .
Fidle for spark out a ?!?
It only start on that..

So.... still no cigar.
Been messing with it and reading manual
More and more settings incorrect.
How could it become like this

So d17 is obvisoly spark a out
Thats what i use now.
I have put a spark plug directly to coil to check spark, it was there couple secs. Then go away. When fuel pump stops in sparks one time..(.zzzzzz grabbed it too quick once haha.)

So i tried a new bip in the box. Nothing.
Put the old back.. voila! Spark.
It started now and ran on all. All good.

Turned it off too hook up computer and tighten a belt.
No more sparky time for me.

So whats going on.
Any ideas ?
Its same again, sparks when you release key and fuel pump stops
Can send a occatianal spark here and there when cranking.

Cheers.

[Matt Cramer]

The MSQ looks like it's set OK for distributor based ignition. Can you post a data log of an attempted start and a tooth log of an attempted start? This will give us a feel for the quality of the sensor readings.

[Kwirk]

Thanks again..
I'm starting to think something is not right with the box...

Heres some logs
of trigger
normal log.
and one i tried to start (coil hooked up and injectors connected)

These datalogs wont say much eh?
I think the usb adapter is causing some serious errors?

[Kwirk]

Thanks again..
I'm starting to think something is not right with the box...

Heres some logs
of trigger
normal log.
and one i tried to start (coil hooked up and injectors connected)

These datalogs wont say much eh?
I think the usb adapter is causing some serious errors?

%%%Update..
so i send away the ecu to a guy who builds and repairs them.
I'm pretty sure something might be cooked.

But why??? Does it sometimes out of nowhere decide to reset>reboot>restart with a msq with changed settings> then error... and something like spark output have changed. Like fidle can be sparkout A.
I reload my old msq and its back again.

This feels like dangerous problem.
Meaby ot could be related to my hopefully fried ecu.

I'll keep you updated.

[jsmcortina]

Did you try with Megatune to compare?

James

[Kwirk]

Hello

With megatune i got a message with something like firmware not matching or newer and it would not work.

+ tons of errors...

I regret i didnt connect with megatune first

I wonder now, is it possible i have so old firmware in the box and tunerstudio couldnt match that somehow ?
I could have could have clicked past that without paying that much attention....doh...

[jsmcortina]

You are using the current (7 year old) firmware for Megasquirt-1. TunerStudio ought to be able to communicate with it just fine, but something sounds weird.

James

[slow_hemi6]

Your ecu has had coms issues before. Someone has wire jumperd the traces from the U6 max232 to the cpu. If the coms are bad you can get incomplete/partial burns of data that cause the issues like you have.

[Kwirk]

Yeah
Hoping its just the box so i dont need to redo the whole installation. Haha

I mean in has started before i connected with computer..


Lets hope for best expect the worst.

[Kwirk]

Hey

So, i sent the box away to a bloke who builds and repairs them

The firmware had been messed up!
So i guess thats caused by me and tunerstudio somehow
I dont know what happend ? Anyone?

So he loaded new firmware and its ok.
No hardware faults

Cheers.

[slow_hemi6]

A bad burn caused corruption. Has to be unstable coms. Maybe a bad usb to serial converter?

[Kwirk]

Could be
It works in my other car with vems.
+ other vems cars...
And with dta.

I will go for bluetooth in this.

[Kwirk]

Car runs again and connects with no problem.
Must have gotten corrupt in the config or something.

So problem solved.

Thanks for support guys.