89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
No, the 'sensor test' RAM locations should all be the same, regardless of the DRB generation. When they add new sensors, they add them to the end of the list. So, the Jeep may have some sensors in that test function that the earlier SMEC DRB function doesn't have, but everything in the SMEC will be carried over to the Jeep; and in the same order.
Gents, is it possible to read the cals from the two SBEC-IIs I have that are not socketed with a FTDI cable?
3LV6 cals? and if yes which partnumber(s) they have?
yep, just have way too many irons in the fire at this point. got about 5 major things i am working on and that will be one of them.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
No worries at all! Just let me know when ready. No rush
Figured out what was wrong with why this was happening. It was a bad read of my original 56028310 chip thanks to the crappy willem burner I had. I replaced with a much better burner, read the cal again, burned it to a blank chip and viola, fires right up.
If anyone wants a copy of the working 56028310 cal that I just read, let me know.
i'll take it.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
wowzer,
One thing Im trying to understand (and Im still a n00b for sure), are DRB access to sensor data different than how the guages menu would use? (I am assuming ram locations) I ask because in MPScan, I can pull back all the live sensor data under "sensor" diagnostics, the menu is titled "DRB Diagnositics" I am assuming that sensor data is coming back with a different method than working guages do? Forgive my ignorance here...
Could we not use the same, and default RAM Locations used in the sensor diagnostics menu to build working gauges for the jeep? it seems like we already have what we need in MPscan and don't need to go hunting for ram locations... unless Im missing something. I'm able to read back every sensor that's available in the DRB through this menu in MPscan.
Id really love to be able to get data logging working with mpscan for jeeps, I've been away from this stuff for a while due to work and family. Still would love to get this all figured out.
Last edited by sev80; 05-31-2017 at 10:37 PM.
alot of the data is there for you to start scanning. just need to put some work in up front to do it.
1) make sure you have the latest version of mpscan2 (2.0.4.0 or greater)
2) download all the layout csv files using menu settings/layout files/update
3) go into the menu settings/layout files/xref settings
4) make sure you have the latest version of mptune
5) download the latest jeep 781 cal from here https://dl.dropboxusercontent.com/u/.../jeep1_781.zip
6) compile the cal and exit mptune
7) open up the .lst file that is created from 6) in an editor and go to the ram locations (0x00 - 0xff)
8) enter the address values (IN DECIMAL, NOT HEX) into the appropriate rows in the xref settings file using one of the 2 custom columns
9) save it and create a layout file and give it a shot. make sure you select the correct custom ecu type in the display layout form BEFORE you start adding gauges by clicking the dropdown box and selecting custom1 or custom2 (as appropriate) and then click the new button to start adding gauges.
10) the only other thing i can think of is - when you create the "profile" where you link the gauge layout with the ecu type make sure you select sbecii t1. that should use the correct protocols unless the jeep stuff is different then the 4 cyl stuff.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)