MS3X broken outputs

[Marek]

I have accidentally connected the Boost output to one side of a relay and the other side of the relay to 12v. The relay clicked at startup, but I find that now I have no programmable output from Boost, Nitrous1&2 and Idle.

It's not a software issue as MS3 commands the mainboard three LED output channels which still work as programmable outputs. The car appears to run fine (via MS3X outputs and inputs like tableswitch also appear fine).

My question is is it likely that these outputs on the MS3X are broken and is there an obvuious or easy way forward here.

kind regards
Marek

[grom_e30]

is it the boost output on the ms3x card? if so that is a ground switching output its capable of sinking 3a current. when you say to a relay was it coil of the relay?

[jacky4566]

I have accidentally connected the Boost output to one side of a relay and the other side of the relay to 12v.

Your not very clear on the mistake here what is "One side of the relay"? If your talking about pins 85 and 86 on a standard relay then that totally normal.

Do you have StimX you can check the outputs?

[Marek]

Dear Grom,

You are suggesting that it wasn't miswired at all, if the MS3X boost pin can sink 3amps. I still can't get any of those four ports to go high no matter what conditions I set.

On the bright side, the tacho output still works and that looks to be the same circuit in parallel to this from the MS3x schematic. I haven't checked VVT as that is used by my aircon.

kind regards
Marek

[grom_e30]

pretty much all the ms3 outputs are low side drivers, they provide ground to the circuit

[jacky4566]

Marek none of those outputs go high. You push in 12v and it switches between ground or not connected.

[jsmcortina]

See section 3.5.6 in the manual.
http://www.msextra.com/doc/pdf/html/MS3 ... .4-49.html

James

[Marek]

Thank you.
This is resolved.

I originally had MS3X Boost as the sink for a relay coil which had 12v on the other side of the relay coil. This appears to not work. MS3X Idle, however, wired the same way, does work, so I have rewired and reconfigured the software accordingly.

If I ever need more pins, I'll troubleshoot whether Boost and the other ports are working.

kind regards
Marek

[Marek]

The MS3X pins appear to be working, albeit they light an LED test light very weakly when "off" (and brightly when "on" of course) which slightly worries me.

One problem I seemed to have with TS3.0.05 and MS3 pre1.4b14 firmware was that no changes I made to the programmable outputs appeared to make any change, unless TS went through the difference report procedure. When alterations were picked up as having been made via this route, the programmable outputs took on and kept their new settings.

I'm not quite sure whether I was doing something wrong, but all of the right settings are in all of the right places and everything works as intended.

Many thanks for the assisitance.

kind regards
Marek

[jsmcortina]

Programmable on/off outputs will only take effect after a power-cycle.

You can test the outputs using the Output Test system.

James

[Marek]

I did power cycle.

What appeared to happen is that the effect of the condition change takes place immediately you tab out of the box where you set the conditions and this appeared to be "fixed" to the new setting as far as the software was concerned, but upon power cycling, it didn't appear to alter what the firmware was actually doing, even though TS appeared to have the new "correct" settings.

When doing the same offline, if a difference report is generated, then the new settings do indeed take effect. You can force it to generate a difference report by removing that particular programmable output, power cycling and then bringing it back with a different setting and power cycling.

kind regards
Marek

[jsmcortina]

You'll only get a difference report if TunerStudio hasn't actually sent and burned the data. There's nothing special going on with the firmware. Either the settings are in flash memory at boot or not.

James

[Marek]

I do appear to have a problem with this.
Firmware MS3pre1.4beta14

I think there are two issues:- one with TS updating the firware settings and one with the actual settings.

I have 5 programmable outputs set:-
3 LED outputs on the mainboard and two additional MS3X outputs.

PM3 (green LED) D14
power on value OFF Active value ON
coolant>72 AND coolant<90

PM4 (red LED) D16
power on value OFF Active value ON
coolant>90

PM5 (blue LED) D15
power on value OFF Active value ON
coolant<72

These three work fine and power a tri-colour LED on the temperature gauge which changes colour based on the coolant temperature

On the MS3X card, I have

PP2 Idle (Lambda sensor relay)
power on value OFF active value ON
rpm >250

This is connected to a 12v relay winding. The other side is connected to ignition fed 12v

PP4 Nirous1 (lpg fuel switchover)
power on value OFF active value ON
engine>0 AND fual_press2<170

When changing the setting of the conditions for the PP2 Idle, TS doesn't go through the difference report procedure and the only way to make it take the new settings is to uncheck the "Enabled" box, power cycle and then recheck the box with new settings and go through the difference report again.

From datalogs, portp=4 at or below 72'C and is 0 above 72'C. If it is doing something right, then portp ought to have a "4" in it based obn whether I am above or below my cranking speed of 250. (The intention is to have the lambda sensors powered if the engine is running (rpm>0) but not when cranking (cranking rpm is set elesewhere to 250rpm).

Portjm appears to be 160 or 164 below 72'c and 136 or 140 above 72'c, i.e. the blue/geen/red LEDs are behaving as advertised.

One way or another the lambda sensor power relay shouldn't be switching dependent on the 72'c temperature threshold.

kind regards
Marek

[jsmcortina]

I'm still totally baffled by your problem report

As a test, could you go to the options in TunerStudio and disable anything to do with Difference Report and CurrentTune.

Then make changes to the on/off outputs when online only. Powercycle after enabling or disabling channels.

Please report anything you find.

James