IÂ’m coming back with a few more questions :
1. I clearly missed some of your notes regarding this topic in your previous threads, but I understand your explanation, very interesting. Too bad there is not more GM calibration documentation floating around like you can find for the early EECIV Fords. Maybe one of these development ecus will show up on ebay one day...
Not sure if I detailed much of the interface or s/w that drives it. Ask for what info you need... I have worked through some of the cal. Limited by my knowledge of auto trans and so on.
Over the weekend I came across an add on board for the LS1 ecu called "
Real Time LS1" from a company in Australia which sounds similar to the interface you are describing. I may ask these guys if they ever offered (or considered offering) their interface for the LT1 as it would appear that they have been around for a while.
If you like I could put together a pinout of the interface for them to look at.
If the DLC can run at 40Kbps that sounds reasonable fast. Is this that standard protocol i.e. TECH2 class 2 interface at 4x, or would this involve some code modification in the ecu ? Also would this mode allow for specific memory addresses or PIDÂ’s or just those available in the TECH2 ?
The 40K (yup, class 2 at 4X) isn't always 40K *exactly*. To a small degree it depends on the distribution of ones and zeros because of the VPW pulse widths. If you want the automated repeat, that needs to be a PID. You could easily add a PID for whatever you need, but this would need a custom flash.
2. Let me clarify my question as my terminology may have not been correct. I meant to ask is there a way to log directly the RAM memory addresses as opposed to the receiving the preset message packets intended for the TECH2. Steveo mentioned in his post on this thread that he trimmed down the message on the $EE to improve the data rate using his software, I imaging you can also replace some of the standard parameters in that message on the ECU side ?
You can read/log ram. Looks like you can use Dynamically Define Diagnostic Data Packets (that's mode $2C). I have messed with this a bit, but not enough to give you details.
3. If I understand correctly the scanning side of the LT1 should work the same as it would with a LS1A or LS1B. I went back through your posts on the 1997 F-Body ECM thread pg. 29 which go over the 2A mode as well as some other addressing modes. Assuming this ecu should communicate with the LS1 logger in Universal Patcher, then I need to do a bit more homework to understand how that software works, i.e. are the PIDÂ’s common for all LS1 computers and if so are they also common for the LT1 i.e. LS1 PIDÂ’s same as LT1 PIDÂ’s ? If not, I need to figure out how to find them.
Can't help you here... I have not looked at LS1A/B, nor have I any experience with the Patcher. I do know that the '96/7 PCMs have complexity due to having two boards/cpus. There are two addresses used in class II. You can't directly converse with the ESide. All messages need to be processed by TSide.
To your last post, do you actually have that working on your bench? If so thatÂ’s pretty cool. A cruder way I suppose it could be done is using a pair of emulators like the Moates Ostrich at least for editing the ROMs.
I have not made hardware/written software to look at both E->T and T->E at the same time. The ideal would be to have a two line display. I have decoded the format, found the sequence info and looked at each direction separately.
Bookmarks