Page 1 of 1

Launch Problem on 3.2.1 (SOLVED)

Posted: Mon Apr 16, 2012 3:50 am
by Paul_VR6
I can't get launch to work on 3.2.1

Circuit verified by using another processor using 3.1.1 - works
Loading known good msq on 3.2.1 - no luck
Loading 'problem' 3.2.1 msq on 3.1.1 - works
Verified circuit using scope
Base msq from 3.2.1 and only updated launch pin to JS4 - no luck

I am out of time for the moment but the next step will be a 3.2.1msq on 3.1.1 and see what happens.

Datalog and various msq's attached.

Re: Launch Problem on 3.2.1

Posted: Mon Apr 16, 2012 3:51 am
by Paul_VR6
Ran out of attachments, log attached.

Re: Launch Problem on 3.2.1

Posted: Mon Apr 16, 2012 3:59 am
by Paul_VR6
Using both 3.2.1 msq's on 3.1.1 firmware shows launch working. :|

Re: Launch Problem on 3.2.1

Posted: Mon Apr 16, 2012 4:55 am
by jsmcortina
It works ok on a Microsquirt module using the "FLEX" input.

James

Re: Launch Problem on 3.2.1

Posted: Mon Apr 16, 2012 5:17 am
by jsmcortina
Tested on an MS2, works ok?
When I ground DIP40-pin30 (JS4) the launch in is active and the timing retards to 1BTDC. (With other conditions met.)

James

Re: Launch Problem on 3.2.1

Posted: Mon Apr 16, 2012 1:44 pm
by Paul_VR6
Even using the dated msq? Its almost like there is a pin conflict as I can see it go low on the scope.

Re: Launch Problem on 3.2.1

Posted: Mon Apr 16, 2012 3:42 pm
by jsmcortina
Paul_VR6 wrote:Even using the dated msq? Its almost like there is a pin conflict as I can see it go low on the scope.
I concurr. That particular MSQ is triggering a problem in the code.
Entering those launch settings from scratch works ok. Using PE0/JS7 with that MSQ instead works too.

James

Re: Launch Problem on 3.2.1

Posted: Mon Apr 16, 2012 4:03 pm
by jsmcortina
Far simpler than all that...

User level needs to be set to "Advanced"

James

Re: Launch Problem on 3.2.1

Posted: Tue Apr 17, 2012 2:20 am
by Paul_VR6
Set to Advanced, power cycled and it works.

Any rhyme or reason for that happening?

Thanks for the help James! Feel free to update the title to *SOLVED*