mpscan trouble shooting

[wowzer]

so is the ecu in the 92 spirit an sbec1 t1 or an sbec2 t1? are you able to send me the bin for that or is it one of rob's Turbonator cals?

[Shadow]

so is the ecu in the 92 spirit an sbec1 t1 or an sbec2 t1? are you able to send me the bin for that or is it one of rob's Turbonator cals?

The 92 Spirit is a T1 (original 2.5l turbo car) and we believe SBEC1. We tried the SBEC2 first and it would no connect at all. Changed to the SBEC1 and it worked, but RPM was 1400 at idle, just like Nicks was doing before this last round.

I could get you the bin, but I would have to remove the chip and read it to do so.

We were meaning to go out one more time in Nicks car and verify #'s with DRB2, see if we could record the DRB2 for playback, but it was getting late and we totally forgot to. lol

[wowzer]

i was thinking the 92 was an sbec2 t1. i need to load up a few of these cals on my bench and do some checking. i relying on some old (10yrs) data on the various protocols and i now see that it may not be correct. also, i can now use both the drb2 and a saleae to watch the info flow. i'm gone this weekend but PROMISE to work on it next week to iron out some of this stuff.

looking at the sbec2 t1 the connection protocol was set up differently than the sbec1 t1. whether that is correct i am uncertain now at this point.

- - - Updated - - -

don't remove the chip, btw. let me do some testing with the stock cals that rob has already posted.

[Shadow]

i was thinking the 92 was an sbec2 t1. i need to load up a few of these cals on my bench and do some checking. i relying on some old (10yrs) data on the various protocols and i now see that it may not be correct. also, i can now use both the drb2 and a saleae to watch the info flow. i'm gone this weekend but PROMISE to work on it next week to iron out some of this stuff.

looking at the sbec2 t1 the connection protocol was set up differently than the sbec1 t1. whether that is correct i am uncertain now at this point.

- - - Updated - - -

don't remove the chip, btw. let me do some testing with the stock cals that rob has already posted.

Sounds good!

[ShelGame]

i was thinking the 92 was an sbec2 t1. i need to load up a few of these cals on my bench and do some checking. i relying on some old (10yrs) data on the various protocols and i now see that it may not be correct. also, i can now use both the drb2 and a saleae to watch the info flow. i'm gone this weekend but PROMISE to work on it next week to iron out some of this stuff.

looking at the sbec2 t1 the connection protocol was set up differently than the sbec1 t1. whether that is correct i am uncertain now at this point.

- - - Updated - - -

don't remove the chip, btw. let me do some testing with the stock cals that rob has already posted.

I'm pretty sure the SBECI and SBECII protocols are the same...

[2POINT5TURBO]

I'm pretty sure the SBECI and SBECII protocols are the same...

Hey guys, I have a bit of work left to do here today but I promise to go back out and do another Log tonight with the smec t1



Rob I created an sbec2 t1 for Shadow and his spirit last night when we plug it in it would get the same error as the original post in this thread. I proceded to create a second gauge layout for his spirit using the sbec t1 and it allowed the laptop to communicate with the spirit, most of the data coming in tho was not accurate at all.

I believe I can upload the log from the spirit as well.



PS. hopefully we have enough cars here to be able to trouble shoot a bunch of stuff


Peace out until later

Nick

[wowzer]

I'm pretty sure the SBECI and SBECII protocols are the same...

that explains part of the issue then. i'll switch it and get a new version uploaded in a couple days.

- - - Updated - - -

Hey guys, I have a bit of work left to do here today but I promise to go back out and do another Log tonight with the smec t1



Rob I created an sbec2 t1 for Shadow and his spirit last night when we plug it in it would get the same error as the original post in this thread. I proceded to create a second gauge layout for his spirit using the sbec t1 and it allowed the laptop to communicate with the spirit, most of the data coming in tho was not accurate at all.

I believe I can upload the log from the spirit as well.



PS. hopefully we have enough cars here to be able to trouble shoot a bunch of stuff


Peace out until later

Nick

well, using the sbec1 t1 protocol in mpscan to communicate with the sbec2 t2 cal won't work since the addresses are in different spots. i need to switch the sbec2 t1 protocol and get you a test version to use.

[wowzer]

nick - pm me your email address so i can send you a test version.

[2POINT5TURBO]

okay in case this is relevant i have my radiator fan hooked up to my climate control fan switch so if the alternator draw is a higher its because i had that on lol opps!


https://dl.dropboxusercontent.com/u/...MPScanPort.txt

https://dl.dropboxusercontent.com/u/...s/mpt2coms.txt

https://dl.dropboxusercontent.com/u/...slogsmect2.MPl

and tonight i happened to find this nice ride cruzing the streets

and yup those are shackles to jack up the rear end for more traction at the track

[wowzer]

nick - if you could get try it with the new version of mpscan i sent you i'ld appreciate it. thx.

[wowzer]

nick - were you able to get any new info with the test version i sent you? (not trying to be tooooo pushy )

[2POINT5TURBO]

nick - were you able to get any new info with the test version i sent you? (not trying to be tooooo pushy )

i'll make sure to get you one by tonight i promise

[wowzer]

any luck?

[2POINT5TURBO]

any luck?

okay so just so you know I put my high timing cal back in so don't get alarmed by it lol

https://dl.dropboxusercontent.com/u/...MPScanPort.txt

https://dl.dropboxusercontent.com/u/...s/mpt2coms.txt

https://dl.dropboxusercontent.com/u/...alscannick.MPl

if you need another test make it soon as i am not sure how many days i have left before it snows

[2POINT5TURBO]

hi guys, I'm trying to use a windows tablet to use mpscan all is well the tablet recognizes the ftdi cable but mp scan does not


here is the error i am getting

https://dl.dropboxusercontent.com/u/...s/mpt2coms.txt

https://dl.dropboxusercontent.com/u/...%2046%20PM.jpg

[wowzer]

the ftdi cable is not being properly recognized by the tablet.
a) did you install the ftdi drivers from the ftdichip.com site?
b) did you make sure the vcp option is checked in the windows driver settings?

-make sure the usb serial port is recognized in the device manager under ports. and when you click on the properties and go to the driver tab it should say ftdi driver is used.
-again in the device manager under universal serial bus controllers the "usb serial converter" needs to be there. click on properties and go to the advanced tab and make sure the "load vcp" is checked.
-lastly, if you still don't have any luck run the ftdi ft_prog.exe program, scan for devices, go to the hardware specific group and see if the d2xx "only" options is checked. i think windows may override this option anyway but see what it says.

[2POINT5TURBO]

the ftdi cable is not being properly recognized by the tablet.
a) did you install the ftdi drivers from the ftdichip.com site?
b) did you make sure the vcp option is checked in the windows driver settings?

-make sure the usb serial port is recognized in the device manager under ports. and when you click on the properties and go to the driver tab it should say ftdi driver is used.
-again in the device manager under universal serial bus controllers the "usb serial converter" needs to be there. click on properties and go to the advanced tab and make sure the "load vcp" is checked.
-lastly, if you still don't have any luck run the ftdi ft_prog.exe program, scan for devices, go to the hardware specific group and see if the d2xx "only" options is checked. i think windows may override this option anyway but see what it says.

a) is done
b) check it right after dinner

thanks for the feed back

[2POINT5TURBO]

the ftdi cable is not being properly recognized by the tablet.
a) did you install the ftdi drivers from the ftdichip.com site?
b) did you make sure the vcp option is checked in the windows driver settings?

-make sure the usb serial port is recognized in the device manager under ports. and when you click on the properties and go to the driver tab it should say ftdi driver is used.
-again in the device manager under universal serial bus controllers the "usb serial converter" needs to be there. click on properties and go to the advanced tab and make sure the "load vcp" is checked.
-lastly, if you still don't have any luck run the ftdi ft_prog.exe program, scan for devices, go to the hardware specific group and see if the d2xx "only" options is checked. i think windows may override this option anyway but see what it says.

I uninstalled the drivers, for all USB. and let windows reinstall everything. Just managed to get it all working again.

Big thanks for looking into this thread again, glad me and Shadow could be a help in figuring out the smec t2 & mpscan connection issues.

[Shadow]

glad I could be a help in figuring out the smec t2 & mpscan connection issues.

Fixed it for you

Not sure why you mentioned me as I had Zero to do with any troubleshooting on this............