Where can I find all of this information for a LM? Also what is the offical crappy baud rate of the LM? Thanks!
Where can I find all of this information for a LM? Also what is the offical crappy baud rate of the LM? Thanks!
Frank Katzenberger
Squirrel Performance - Home of the best turbo calc!!!
http://www.squirrelpf.com
91 Daytona Shelby - It is getting there
87 Shelby CSX #418 - Near stock is a good thing!
94 Bronco 302 XLT - Shorty Headers, 3" exhaust, cold air intake, & Soft top
"... to get the best out of it, you have to go beyond the line. Where bravery becomes insanity. Shall I turn into this hairpin bend at a 100mph? Why not!"
Visit the new Knowledge Center today!
Check out the one and only Shelby Dodge Registry!
Anyone? Rob?
Frank Katzenberger
Squirrel Performance - Home of the best turbo calc!!!
http://www.squirrelpf.com
91 Daytona Shelby - It is getting there
87 Shelby CSX #418 - Near stock is a good thing!
94 Bronco 302 XLT - Shorty Headers, 3" exhaust, cold air intake, & Soft top
"... to get the best out of it, you have to go beyond the line. Where bravery becomes insanity. Shall I turn into this hairpin bend at a 100mph? Why not!"
Visit the new Knowledge Center today!
Check out the one and only Shelby Dodge Registry!
DRB commands I don't know. I mapped out the SMEC and SBEC (DRB-II protocol). But, I can't follow the DRB-I protocol.
I think the baud rates are 976 and 7812.
Jeff Chojnaki(sp) had them all figured out. He made a DRB-I emulator for the PC that worked from the command line.
Those are the commands I need to request datalogging parameters correct?
Frank Katzenberger
Squirrel Performance - Home of the best turbo calc!!!
http://www.squirrelpf.com
91 Daytona Shelby - It is getting there
87 Shelby CSX #418 - Near stock is a good thing!
94 Bronco 302 XLT - Shorty Headers, 3" exhaust, cold air intake, & Soft top
"... to get the best out of it, you have to go beyond the line. Where bravery becomes insanity. Shall I turn into this hairpin bend at a 100mph? Why not!"
Visit the new Knowledge Center today!
Check out the one and only Shelby Dodge Registry!
Yep - but if that's all you want, it's pretty universal for all of our ECU's: wait until the startup datastream stops (only on the DRB-I ECU's; DRB-II's don't have a startup datastream), then send 0x12 until the ECU replys with 0x12, then switch to the hi-speed baud rate, then send the requested memory location (1-byte) and recive the data from that byte. In the DRB-I devices, there's no way to exit hi-speed mode short of powering the car off, though.
The later DRB-II computers do have a command (0xf2, IIRC) to exit hi-speed mode and go back to 'regular' DRB-II command processing.
Where do I acquire what memory locations contain what?
Frank Katzenberger
Squirrel Performance - Home of the best turbo calc!!!
http://www.squirrelpf.com
91 Daytona Shelby - It is getting there
87 Shelby CSX #418 - Near stock is a good thing!
94 Bronco 302 XLT - Shorty Headers, 3" exhaust, cold air intake, & Soft top
"... to get the best out of it, you have to go beyond the line. Where bravery becomes insanity. Shall I turn into this hairpin bend at a 100mph? Why not!"
Visit the new Knowledge Center today!
Check out the one and only Shelby Dodge Registry!
From a dis-assy or source listing. What you want are the ram locations. They'll have a definition like MAPValue == 0x7a. 0x7a is the address that you request. BB60 and Turbonator use the same memory map (stock 87 T2) so you can look at either of those for reference.
Ahhh! Gotcha!
Frank Katzenberger
Squirrel Performance - Home of the best turbo calc!!!
http://www.squirrelpf.com
91 Daytona Shelby - It is getting there
87 Shelby CSX #418 - Near stock is a good thing!
94 Bronco 302 XLT - Shorty Headers, 3" exhaust, cold air intake, & Soft top
"... to get the best out of it, you have to go beyond the line. Where bravery becomes insanity. Shall I turn into this hairpin bend at a 100mph? Why not!"
Visit the new Knowledge Center today!
Check out the one and only Shelby Dodge Registry!
Whatcha doin' ?
I am taking my Arduino (Atmel328 microprocessor - samething I used to build that knock board) to interface with the LM and my 24x8 serial display. I am basically creating the same thing as your minidash, but a little different. I will stagger the data requests so things like speed will be requested less in comparison to other important parameters. When datalogging is required, you can press a button and the display will turn off and I can then go fullout. With the ability have multiple serial sources, it works out nice.
http://www.pjrc.com/store/mp3_display.html
Frank Katzenberger
Squirrel Performance - Home of the best turbo calc!!!
http://www.squirrelpf.com
91 Daytona Shelby - It is getting there
87 Shelby CSX #418 - Near stock is a good thing!
94 Bronco 302 XLT - Shorty Headers, 3" exhaust, cold air intake, & Soft top
"... to get the best out of it, you have to go beyond the line. Where bravery becomes insanity. Shall I turn into this hairpin bend at a 100mph? Why not!"
Visit the new Knowledge Center today!
Check out the one and only Shelby Dodge Registry!
Cool.
Frank, this gonna show real time info or just to read it after logging?
Bryan
86 GLHS #161, 2016 Impala
SDAC National Member, SDAC Buckeye Chapter Member
A man has got to know his limitations.....
Not sure anymore. I have a copy I can post, but I don't think there's any documentation. Jeff is on the baord here from time to time. I forget his username now...
The DRB-II protocol isn't easy to follow either, and I haven't been able to find any document that definitively says what commands do what. But I took your turbonator source code and converted the DRB-II logic to pseudocode, and from that I came up with this:
Some of these commands were hard to figure out, because of all the spaghetti!Code:# Output error codes [ 0x10 ] -> code1, code2, ..., 0xfe # Output error bits [ 0x11 ] -> HB, LB # Setup hi speed data transfer [ 0x12 ] -> nothing # Setup ATM [ 0x13 ] [ arg ] -> depends on function? # Send diagnostic data to SCI [ 0x14 ] [ loc ] -> 1 byte # Send 16-bit memory location [ 0x15 ] [ arg1 ] [ arg2 ] -> 1 byte # Send ECU ID to SCI [ 0x16 ] [ arg1 ] -> ? # Clear error codes [ 0x17 ] -> 0xe0, 0xe0, 0xe0 # Control ASD relay [ 0x18 ] [ arg1 ] -> nothing? # Set min idle speed [ 0x19 ] [ arg1 ] -> nothing? # Switch test [ 0x1A ] [ arg1 ] -> ? # Init byte mode download [ 0x1B ] -> nothing # Reset EMR [ 0x1C ] [ arg1 ] [ arg2 ] -> 0xe2 or 0x00
I've attached the pseudocode and my notes on each specific command. Does any of this look right (or wrong)?
How different is DRB-I?
(I'm guessing I don't have to worry about that since I have an SMEC?)