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

Hi all,

I added a tinylOx to my system and I was informed that I should upgrade to the latest beta version of TS to make the setup easier. I installed 2.2.3 and now I have 0 communication with the ecu through TS and Megasquirt. "Test Port" fails on all settings. And the other symptom that I found to be strange was that my fuel pump is no longer cycling and the car won't start. I've uninstalled the serial driver and reinstalled it. I tried setting it to 115200 but every time i open it back up again it is at 9600. I've read a lot on here and I keep seeing disable CAN Commands and ensure that your main controller is set to 0. I've seen screen shots of the CAN Command Menu but I don't even see that in my software. My controller is set to 0. When I try to detect in the communications menu i get nothing back.

As of right now the CAN H and CAN L wires aren't hooked up to anything and the tinylOx only has the power and ground wires running to the 5v/ground connections on the proto area of the EEC-IV Board.

I'm running and MS2 v3.0. I'm at a loss at this point and don't know how to proceed. Any help would be greatly appreciated.

Do you mean 2.2.30 ? 2.2.03 would be from last March.

Either way, I don't _think_ that is the TS version or serial drivers are relevant problems here if your fuel pump isn't cycling and the car is no longer running. Ignoring the CAN device, it sounds like you can not talk to the MegaSquirt any longer. It seems there is problem with your MS not talking.

Are you getting any LED Activity from it?
When exactly did you loose contact with it, what was the last thing you did before the fuel pump stopped cycling?

I tried setting it to 115200 but every time i open it back up again it is at 9600.

Is this the baud in windows device settings you are looking at? That does generally revert back to 9600, but doesn't matter what it is set to. When TS opens the port it sets the baud to what you set in TS.

Phil! Thanks for responding!

TS 2.2.30 is the version I installed 2 days ago. Seemed like it was the most recent.

All 3 LED lights simply flash for a second when I turn the ignition on and then off. There are a few LED lights lit up on my EEC-IV board.
I lost contact with TS when I installed the newest version. If I remember correctly this is also when the fuel pump stopped cycling. It was only then that I tried to start the car and nothing happened. Prior to that I hadn't tried to start the car before making changes to the system.

Good to know about the baud in windows and yes that is what I was referring to.

I agree with you that MS is not talking anymore but I'm not sure why or what I did that could have caused this.

When you install the beta, it does not replace the 2.0.x stable version, it installs in parallel. So you can still try the old version.

But i don't think it will matter. It seems like the trouble is more related to the installation and the MS is not talking, changing the version of TS can't kill it.

In a terminal or TS's Mini-Term do you get any response to an S or Q command?

firmware reload?

It is semi-unclear to me what happened but essentially I screwed up the firmware on the ms2 when I opened the updated version of TS by attempting to communicate with the extender board before loading my tune. Now I have updated Tuner Studio and as well updated my Firmware version loaded in my MS2. I will hopefully be able to load my old settings in rather than manually entering all of them but we will see. Huge huge thanks to the guys at Tuner Studio for the support. Brian was a HUGE help and a great guy!