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

Noobie alert. Finally got around to fighting with the serial/usb deal. Got it to work on the XP after trying different drivers. Sort of.
The "detect" feature can't find anything. It's there on 14 so I manually get it going. After successful connection the "detect" still can't locate the port.

On my win7 sp1 machine it's a more severe problem.
Any time I try to use the "detect" option it goes about 25% and crashes TS totally out.
Anyone got a tip/hint/fix for this? Using the DIY adapter, ts version is 1.004

Thanks

That happens sometimes, odd you are getting it twice.. Maybe the computers have a common point.

But anyway, the problem with detect is that it goes through all the ports in order looking for a megasquirt. However, sometimes there seem to be devices that don't like being queried. In these cases 1 of 2 things can happen, it can hang or report false signatures so the detect never gets to the port with the MS, in other cases as soon as TS tries to open the port it just kills it.

In this case, you really should just not use detect. Especially if you know the port it is on, just set it manually.

This does remind me though that I wanted to try to capture known bad ports in a future release so I can skip them during detect.

common points? Windows and USB adapters!!
FYI, the same thing happens if one tries the ECU detect which is a little more bothersome if you don't know what is in there.

Excellent point.
If you know your com port and baud, there should be a detect that just looks at that

What you can do there; open the mini-term.
Open the port
Then type a Q

You should be able to see what firmware is in there

Fueler wrote:common points? Windows and USB adapters!!
FYI, the same thing happens if one tries the ECU detect which is a little more bothersome if you don't know what is in there.

Had the same problem on my desktop with a serial port running Win7. TS freezes when asked to detect. Same computer has an XP partition - that worked fine.

Phil,
The mini term/Q thing works but only shows the signature. No sign of the definition. Another step needed?

The signature is what you need.
What is it?
Then if it is a common firmware it will be in the ECU Definition drop down, if not you will need to get the ini.

Looking, looking. Where is the ecu definition dropdown?

In the New Project Dialog, or in Project Properties if you already have a project setup.

If you are just starting with a new controller, you should create a new Project from the File menu.

ahh hah. thanks