monkeywinky

Hi,

I'm sure Rev is getting tired of all my noobness so I just thought I'd inquire here to see if anyone has dealt with a similar situation and what worked for them.

Running the latest TS, created a new project using the ini file from Rev, set up the config as directed, when it gets to the connection settings window, the "test port" fails.

I've set the baud rate to 115200 both in TS and in device manager. I've tried com 1, 2, and 3. Tried two usb cables using the ftdi drivers, then I tried using two different keyspan usb/serial adapters. Still get a fail.

When I was using a serial adapter, I jumped pin 2/3 to test the "mini terminal" in TS and that worked.

I'm not really sure what else to try - Rev says the ECU is getting power since when I switch the key to "ON," the fuel pump runs. Rev's working to help me, I just wanted to get more ideas to try during down time.

Could it be that my car voltage is too low?

Thanks, everyone.

Reverant

iTrader: (10)

Stock TPS is disconnected?

monkeywinky

No, the TPS is not yet hooked up. Stock TPS is disconnected. In your instructions, calibrate TPS is after the "test port," so I thought it didn't matter.

I wasn't 100% sure which wires connected to which so was going to just hook them up temporarily and verify if they work before making the connection permanent after the ecu was connecting properly.

Do all the sensors need to be hooked up in order for the ECU to connect?

Reverant

iTrader: (10)

Just had a similar problem on the bench.

Created a new project, supplied the .ini file (no autodetect), selected the correct COM port, clicked Test, nothing.

Created the project anyway, and was put in offline mode. Waited, nothing.

Then went to Communications -> Settings, clicked Test again (I didn't change the COM port!) and bam - successful this time around.

Try that and let me know.

monkeywinky

I've tried going Communications -> Settings, and "test port" after creating a project in offline mode. In my last instance, this window would show a default of COM1 regardless of what I had setup the COM port to in the project creation screens. So just leave it as COM1 even if it's supposed to be COM2(3, etc)? It's worth a shot.

Reverant

iTrader: (10)

No, use the actual COM port as reported in Device Manager.

monkeywinky

oh, then yes, tried that. additionally, one of the last things I tried was changing the megasquirt baud rate under communications to 115200, not much happened, lol.

Ben

iTrader: (33)

What USB to serial adapter are you using? I very highly recommend using an FTDI based adapter. Also try installing the correct driver for your machine from the FTDI website:
FTDI Drivers

Remove the driver currently on your laptop before installing the new one.

monkeywinky

When I first tried using a usb cable, I installed the FTDI drivers per their website instructions. When I tried serial adapters, I have tried the keyspan serial adapters. I'll look for a ftdi based adapter.

Is this the one you recommend?
http://www.mouser.com/ProductDetail/...nzRp8XLQeQIA==

monkeywinky

update: i just bought the one of diyautotune's site - will update after it comes in and I give it a shot. Hopefully this is all that was wrong

Ben

iTrader: (33)

That would have been my recommendation. The adapter you linked to is FTDI based, so is *probably* fine, but the adapter that we carry is absolutely known to work. We tested numerous adapters before settling on the one we carry, and we are very happy with it. We've sold thousands, and I can only recall 1 DOA.

monkeywinky

Got the adapter from DIY today, works like a charm. Thanks!

Ben

iTrader: (33)

cyotani

iTrader: (8)

I'm having a similar problem so I'll add on to this rather than making a new thread.

My diypnp for a 1.6 is not connecting to tunerstudio anymore. I am using a r232 to usb adapter set up following msextra's COM connection write up. I was able to get my MS to auto detect and read the bar pressure and air temp correctly in Tunerstudio. Then when I tried to start the car it went offline and will not re-connect. I've tried making new projects, port diagnostics and nothing. I hope I didn't fry anything internal to the ECU. Also, I removed the 10A fuse form the engine bay fuse box as mentioned in the MSPNP write ups.

Any ideas for diagnosis? Thanks.

cyotani

iTrader: (8)

I just checked all fuses and they are good. I'm trying to find a ac adapter around the house to power the ecu on a bench to see if it will connect. All I can find is a 12v 1.0amp and an 8v 0.6 amp. Diyautotune sells a 12v 0.5 amp. Could either of these be used?

Chiburbian

iTrader: (1)

I have been having problems lately with tunerstudio occasionally losing contact with the megasquirt. I think it has to do with the vibration and the cable and/or usb port on the laptop. Anyone else have this problem over time?

FRT_Fun

iTrader: (19)

I have this problem on my older laptop. The USB slots are all loose. When I do a hard pull the acceleration pulls the laptop back and sometimes the cable will drop the connection for a second. Sucks when I'm trying to do a log. Thinking about getting a laptop mount.

hankclaussen

iTrader: (5)

So Ben, I have one of your cables on the way to me to solve another seemingly related issue (maybe?) - TS switches from gauges that show nothing to off line every 5 seconds or so even after "successful" port tests/changing latency in the device manager/matching baud of the device to that of the MS3.ini supplied by Reverent and using an FTDI cable (really hoping yours is the fix!)

I don't get it! Mine says it is connected but shows nothing and flashes on and off line with FTDI cable in windows 8 and just shows gauges with no information (seeming to stay 'online') when used with the other cable I have and Windows 7; which works fine with Windows 7 and the MS1 PNP on my other car... Wait for magic cable? Something wrong with MS3 unit?

Ben

iTrader: (33)

Make sure you have the right drivers from FTDI, but there's not a Win8 compatibility issue if using a genuine FTDI serial > USB adapter. The adapter we sell is a genuine one, not a cheap Chinese knock off.

I also recommend not using any USB extension cables. They let in a lot of noise. In general, USB is a terrible comms protocol for use in an automotive environment. Their existence is consumer driven, IE the false assumption that if a device does not have USB, it must be old and sucky. In reality, USB is sucky for this type of application.

monkeywinky

In your experience, do these adapters go bad?

I was driving, and suddenly lost power. When I pulled over, car cranks but wouldn't start. Got towed home.

Now my MS3 won't connect to the tunerstudio. I tried to flash the firmware, but my computer doesn't detect an ecu. I've replaced the main relay and verified that the fuel pump primes when the key turned to "on".

Do you think it could be the adapter or a problem with the ecu?

Thanks,