I can tell from the cable serial number that it's one of mine, programmed with my template. So, it will have the correct settings for the Rx/Tx and D2XX driver.
Looks like it's doing everything correctly. It's just not getting back the confirmation byte from the ECU when trying to initiate the logger mode.
I'll look at the other T2 cals I have. Maybe they use a different baud rate in '88 vs. 89?
EDIT: Every T2 cal that I have (like 9 of them) has the baud set to 976 for commands, and 62500 for logging mode.
Last edited by ShelGame; 09-04-2015 at 01:50 PM.
Originally Posted by ShelGame
I have not been able to reach Cindy to ask her about what smec they use for their stage 5 I'm running 88 89 electronics
I just re-confirmed - the baud rates for all of the T2 cals are 0x01 and 0x25 --> which give a 976 baud for the command processing and 62500 baud for the logging mode.
Nick, bring it with you to the shop this wknd. I have a Stock running 88 TII Daytona here that you can try it on.
Robert Mclellan
http://www.youtube.com/watch?v=wambNdfnu5M
10.04 @ 143.28mph (144.82 highest mph)
Worlds fastest 8v MTX Shelby Charger
Manitoba's Fastest 4cyl!
8 valve, No Nitrous!
New clutch combo is the SH!T!
Thanks Rob, I'll call Ron in lockport and see if he is around as i'm storing the Minivan out there * aka poohbox * I might be able to throw it on there too. At least at that point I'll know for sure if its this damn laptop.
- - - Updated - - -
Thanks for checking Rob, I toasted my last motor and from here on out especially with this Holset I want to be able to datalog the car. Thanks for going out of your way to help me out, I'll make sure to update this thread when I have more results.
Nick
Not sure if it makes a difference, but I think something is funny with 88 SMECs, my 89 works fine, 88 won't connect.
I put a T2 SMEC and a T1 SMEC on my bench tonight; and I can confirm that the T2 simply doesn't work. A stock T1 will receive data just fine, but the T2 gets the same error you do. I'll try to hook up my logic analyzer and figure out what's going on.
So, you're totally justified in your frustration - the T2 isn't working they way I think it should. WHich is odd; other than the hi-speed logger baud rate, it looks identical to the LM code. Though, I guess the LM's have issues, too.
Aww no way
this will be interesting....
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Just throwing this out there; I was under the impression that all 88-89 SMEC T1 And T2 boards were compatible. Is this Not the case? ie. you can socket any T1 or T2 SMEC board and whatever cal you use in it (T1 or T2) will work properly for its application.
So are we talking about a difference in the board, or just in the eprom cal itself?
Robert Mclellan
http://www.youtube.com/watch?v=wambNdfnu5M
10.04 @ 143.28mph (144.82 highest mph)
Worlds fastest 8v MTX Shelby Charger
Manitoba's Fastest 4cyl!
8 valve, No Nitrous!
New clutch combo is the SH!T!
No, the boards are the same. The difference is due to changes in the DRB service routines in the code. The T2 is really a DRB1 era system. While the SMEC is DRB2.
Found this this morning:
This is of course for the LM. The baud rate for the '88 SMEC's are 976 and 62500. I'll hook up my T2 SMEC on the bench and see if it also spits out this 'status' byte every 11ms.> The "initial" baud rate is about 976 or that is the nearest compatible PC baud rate. The LM spits out a "Status" byte that means something. I don't have a "factory" protocol on my desk presently but I believe the
> LM spits this out every 11mS unless you have put it into "Fast" mode per below.
>
>
> By sending it a 0x12 at 976 it tells the LM to goto "fast" mode where you request information from it. This baud rate is 7812.5 according to the Motorola datasheets
Please let me know if you come up with a solution Rob, I've really been looking forward to being able to use mpscan.
OK, got some good logic analyzer traces. I think I'm onto something; I sent it to Wowzer to confirm.
I hope hopes he can shed some light.
based on testing so far mpscan will NOT support the t2 cals. the logging protocol and output is different then what was originally thought (at least by me!!). might be a while before it is completely sorted out. sorry.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
i've done quite a bit of analysis using my logic analyzer and drb2 on the t2. based on that i modified mpscan to use some new protocols and logging techniques as well as having to change some of the ecu ram addresses currently set up. it works like a charm!!! woohoo. i'll do some more testing this weekend when i can and issue a new release soon. i unfortunately updated my visual studio software to a newer version to support the arduino testing i'm doing and it foobar'd a few things i do to create the mpscan/mptune updates. gotta love microsoft!!!
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Man you guys are the bomb ! Big thanks to rob and wowzer. I promise to load all my no scans here if you guys need it. Let me know when we are good to go !
Wowzer will ill I be able to use 3 bar map, knock voltage, airfuel, timing advance as those are currently not aviable on the smec t2 ?
i've asked rob to take a look at some of the t2 ecu addresses currently defined so i'm not sure what we'll end up with. may need to be a work in progress. also, the t2 logging speed won't be near as fast as the regular smec/sbec since the addresses have to be sent twice with the first byte returned thrown out, also needs some delays programmed in.
what cal are you using for sure? hopefully the ecu addresses are the same as the one i'm testing with (89 t2 cal 553).
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Posting Permissions
Reply With Quote
