Serial Port for Diagnostic SW with MBE ECU ?

Serial Port for Diagnostic SW with MBE ECU ?

Author
Discussion

crypto

Original Poster:

232 posts

242 months

Tuesday 12th June 2012
quotequote all
Trying to get the (old) diagnostic software running on my pc. What is the required com-port number and settings to get it running ? Are the general PC requirements ? WinXP ? USB-to-Serial-Port converter or physical Com Port ?

Tanguero

4,535 posts

202 months

Tuesday 12th June 2012
quotequote all
Windows XP and COM1 regardless of if you are using a USB-COM adaptor or a physical RS232 port

scotty_d

6,795 posts

195 months

Wednesday 13th June 2012
quotequote all
You can use windows 7 it makes no odds. Com port 1 as said and if using usb to serial converter get one with chip set pl2303, The one maplins do works, don't bother with cheap e-bay ones.

ukkid35

6,188 posts

174 months

Wednesday 13th June 2012
quotequote all
eBay 370464905270 - £2.45 works perfectly for me with WinXP.

scotty_d

6,795 posts

195 months

Wednesday 13th June 2012
quotequote all
Fair enough if you found one that works, I tried 3 different one's from the bay before i went to maplins and paid 15 quid for one frown

ukkid35

6,188 posts

174 months

Wednesday 13th June 2012
quotequote all
scotty_d said:
Fair enough if you found one that works, I tried 3 different one's from the bay before i went to maplins and paid 15 quid for one frown
I think it is PL2303 as you recommended.

Gray_101

1,118 posts

191 months

Wednesday 13th June 2012
quotequote all
ukkid35 said:
eBay 370464905270 - £2.45 works perfectly for me with WinXP.
Bin it and get a maplins one.

when my cheapo burnt out it buggered up the cam timing and played havco with the ECU.


Tanguero

4,535 posts

202 months

Wednesday 13th June 2012
quotequote all
Gray_101 said:
Bin it and get a maplins one.

when my cheapo burnt out it buggered up the cam timing and played havco with the ECU.
Neither the software nor the ECU (nor any USB-COM adaptor connected to them) can change the cam timing, you have to undo bolts to change that.

scotty_d

6,795 posts

195 months

Wednesday 13th June 2012
quotequote all
Might have messed with the fueling? or in my case when my heater hose came off gave the ECU a unwanted shower made the Lamda's go full scale?

Gray_101

1,118 posts

191 months

Wednesday 13th June 2012
quotequote all
Tanguero said:
Neither the software nor the ECU (nor any USB-COM adaptor connected to them) can change the cam timing, you have to undo bolts to change that.
That's what I thought... But it can when the lead shorts out.

http://mobile.pistonheads.com/gassing/topic.asp?h=...

Edited by Gray_101 on Wednesday 13th June 10:46

cerbfan

1,159 posts

228 months

Wednesday 13th June 2012
quotequote all
scotty_d said:
You can use windows 7 it makes no odds. Com port 1 as said and if using usb to serial converter get one with chip set pl2303, The one maplins do works, don't bother with cheap e-bay ones.
Would not work on Windows 7 for me as its 64 bit and won'r run 16bit programs. I has to install Virtual Machine and then a copy of XP and run it through that, worked eventually though. If you have Windows 7 Enterprise than you can just download and run XP mode for free from Microsoft.

Tanguero

4,535 posts

202 months

Wednesday 13th June 2012
quotequote all
Gray_101 said:
That's what I thought... But it can when the lead shorts out.

http://mobile.pistonheads.com/gassing/topic.asp?h=...

Edited by Gray_101 on Wednesday 13th June 10:46
It can not under any circumstances change the cam timing - the cam pulleys are bolted to the cams. To change the cam timing you have to loosen those bolts. Whatever it did - it didn't change the cam timing.

The ECU can change the ignition timing - and could quite possibly have problems due to a dodgy USB-COM convertor - but not the cam timing!

scotty_d

6,795 posts

195 months

Wednesday 13th June 2012
quotequote all
The beauty of Windows 7 is it can run anything. If you right Click on you application File and go down to Properties, Then in to compatibility, compatibility mode, you can then select it to run on any Operating system from win 95 right through to 7. I run on xp service pack 3 that is 16 bit and that works fine. smile

It does work as i only have this little net book that i use for everthing.

cerbfan

1,159 posts

228 months

Wednesday 13th June 2012
quotequote all
Not on Windows 7 64bit home premium it won't the 64 bit version will not run 16bit programs regardless what you set the compatibility mode to. Maybe you have the 32bit version which will let you run 16 bit programs I believe.

crypto

Original Poster:

232 posts

242 months

Wednesday 13th June 2012
quotequote all
Hi folks, thanks for all the feedback ! I'll try this evening with 2 cables I already have and on COM1 (only).
Some more questions :
1) will the ECU only respond while ignition is on or also when off ?
2) can I use a (standard) 9 pin cable or do I really have to modify it according the wireing diagram picture (with the resistors) ?
3) coming out of the ECU there are 4 pins (on the big black connector) to control a stepper motor, what are they used for ?

Peter


Tanguero

4,535 posts

202 months

Wednesday 13th June 2012
quotequote all
crypto said:
Hi folks, thanks for all the feedback ! I'll try this evening with 2 cables I already have and on COM1 (only).
Some more questions :
1) will the ECU only respond while ignition is on or also when off ?
2) can I use a (standard) 9 pin cable or do I really have to modify it according the wireing diagram picture (with the resistors) ?
3) coming out of the ECU there are 4 pins (on the big black connector) to control a stepper motor, what are they used for ?

Peter
1) The ignition must be on and the immobiliser off. i.e. if you were to press the black button it would start.

2) You can use a standard cable - the resistors are to protect the ECU in the mapping mode I believe. I certainly use a standard cable with just rx,tx and ground connected.

3) Nothing as far as I know!

Gray_101

1,118 posts

191 months

Wednesday 13th June 2012
quotequote all
Tanguero said:
It can not under any circumstances change the cam timing - the cam pulleys are bolted to the cams. To change the cam timing you have to loosen those bolts. Whatever it did - it didn't change the cam timing.

The ECU can change the ignition timing - and could quite possibly have problems due to a dodgy USB-COM convertor - but not the cam timing!
Yes I see what ive written now.. My mistake... I ment ignition timing.

Any ways the point I was trying to make.. Is a cheap lead caused me a load of problems

scotty_d

6,795 posts

195 months

Wednesday 13th June 2012
quotequote all
cerbfan said:
Not on Windows 7 64bit home premium it won't the 64 bit version will not run 16bit programs regardless what you set the compatibility mode to. Maybe you have the 32bit version which will let you run 16 bit programs I believe.
Your right mine is the 32bit Win 7. Bit rubbish the 64 bit will not let you run programs on 16 bit. frown

S6PNJ

5,183 posts

282 months

Wednesday 17th August 2022
quotequote all
Bringing this old topic back from the dead (well, it has only been 10 years eek) I'm hoping to try and get some info on what works - I already know what doesn't!!

I've been using an old Win 7 (and Win XP) laptops with serial ports and the TVR MBE ECU software via a 'serial' cable and serial port on the laptop to get access to my SP6 Tuscan data but would like to 'play' with the RS-AJP app and also use the software on my newer Win 10 laptops and tablets.

Now before you all say - but the TVR software won't run on a Win 10 machine - I'll say - oh yes it does yes but only if you have the 32bit software version loaded. First, you have to install NTVDM - oh and that's it!! Details here - https://docs.microsoft.com/en-us/windows/compatibi... or the command (via Command Shell as an admin) is DISM /online /enable-feature /all /featurename:NTVDM Don't forget, that when you exit the TVR Software, you need to hold Ctrl when you click the X, else it logs you out of Windows.

Right, so now we've got that out of the way - I'm stuck on finding a suitable USB to RS232 adaptor. I would prefer not to have it go to a 9 pin D cable/plug but instead would prefer that it simply ends in 'pins' so I can wire it into my 3 pin plug that directly interfaces with the Tuscan's wiring loom. I've read many a thread, old and new, and the Prolific chipsets seem to be the ones to go for - so I duly ordered a PL2303TX - which didn't work - but turned out to be a fake Prolific chipset, so I then ordered via another seller, a PL2303HX which is a genuine chipset (tested with Prolific's authenticity tool) but still won't connect to the ECU. I've made sure (via device manager) that the correct COM port is assigned, that the COM port settings match the old serial port settings and that everything else is the same etc. I've changed the input port in the TVR Software (via F10) and assigned it to the USB device's COM port but still no joy. I've tried swapping txd and rxd pins around in case they are wrong - still no joy!

I've now got a different USB-RS232 cable on order (Prolific chipset) but now one that terminates in a 9 pin D, which is clearly not what I want, but I'd like to get it working in some way shape or form (rather than use the old laptop whose battery is fairly shot etc).

So what do you lot use USB cable wise? If you are tech savy enough, please let me know the chipset of the device and any make/model/spec please.

If this new cable doesn't work, I'm going to try an FTDI FT232RL chipset device as I've also read they might work.

Edited by S6PNJ on Wednesday 17th August 16:59

DuncanM

6,210 posts

280 months

Wednesday 17th August 2022
quotequote all
Lots of good information here:

https://www.pistonheads.com/gassing/topic.asp?h=0&...

There's also a sticky subject at the top of this forum.

rs-ajp is the only thing I use now, however that was interesting to read re the TVR software working on Win 10, I'll probably try that at some point smile