96530006 Live Map download
Mar 30, 2009 | 02:27 PM
#31
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 5
From: UK
I don't want you to live with it if I've messed something up, but the things I've done tend not to work at all, or work fine... I haven't gone anywhere near cold start stuff. Only if there was some erasing of learned idle data or the wrong ignition timing would this happen. If learned idle data was being overwritten, it would also overwrite our RAM maps. If the wrong ignition timing, you'd see it in the maps you read from RAM, if the map was offset it wouldn't run at all because the header would be trashed. I'm not saying it is definitely placebo, but I'm suspicious or not something I've done to the code 
I'm using Tephra 5.10 download. Maybe there is stuff in there to explain?
I'm using Tephra 5.10 download. Maybe there is stuff in there to explain?
Mar 30, 2009 | 02:48 PM
#33
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 5
From: UK
The 8 does weird things after a reflash with parts of the idle learning still in memory. You might need a while idling and driving around for it to sort out? 9 just clears the log but behaves better after a battery disconnect for example.
Mar 30, 2009 | 09:20 PM
#36
Finally, I managed to find a few minutes to get everything copied over to your modified 5.10 ROM, so I should be able to get this flashed in the morning and see if everything is behaving correctly on the drive to work.
One comment about the PC app: you have a nice 15" screen on your laptop, don't you?
On my tablet with an 800x600 screen, the interface elements don't fit very well; that's not a big deal, since I can usually just resize windows like that and scroll it around to find what I'm looking for, but it appears that the main window of the PC app isn't resizable (at least, it isn't on Win2k), so I can't get at any of the right-most buttons. 
(The only reason I know where all the buttons are is because I've been messing around with it on my Linux laptop. I'm still amazed that it "just worked" under Mono.)
On the other hand, the fact that all your common operations are "tappable" is fantastic for those of us without keyboards regularly attached to our loggers.
(Next up: figure out why the OBDII/MUT code I wrote months ago doesn't seem to be initializing properly, so I can look at doing something a little more Linux-friendly with this. I need to spend a little more time reading your code (and the PC app source) to see what the protocol looks like from the client side.)
One comment about the PC app: you have a nice 15" screen on your laptop, don't you?
On my tablet with an 800x600 screen, the interface elements don't fit very well; that's not a big deal, since I can usually just resize windows like that and scroll it around to find what I'm looking for, but it appears that the main window of the PC app isn't resizable (at least, it isn't on Win2k), so I can't get at any of the right-most buttons. (The only reason I know where all the buttons are is because I've been messing around with it on my Linux laptop. I'm still amazed that it "just worked" under Mono.)On the other hand, the fact that all your common operations are "tappable" is fantastic for those of us without keyboards regularly attached to our loggers.
(Next up: figure out why the OBDII/MUT code I wrote months ago doesn't seem to be initializing properly, so I can look at doing something a little more Linux-friendly with this. I need to spend a little more time reading your code (and the PC app source) to see what the protocol looks like from the client side.)
Mar 31, 2009 | 01:14 AM
#37
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 5
From: UK
You can always edit the PC source if you want to change the behaviour of the windows. Just use the xml files that I posted for your ROM and change the default baud rate in the PC app.
Mar 31, 2009 | 06:45 AM
#38
No visual studio here. (I'm assuming that's what you developed it in? I haven't been successful at getting mono to recompile it yet, working on that. )
Er, nevermind, I just noticed that VB.NET Express is free; I'll pull that down and see if I can get it working on my Windows VM. At the very least, that should give me a few clues about what I'm doing wrong with trying to get Mono to build it.
(I'm assuming that's what you developed it in? I haven't been successful at getting mono to recompile it yet, working on that. )Er, nevermind, I just noticed that VB.NET Express is free; I'll pull that down and see if I can get it working on my Windows VM. At the very least, that should give me a few clues about what I'm doing wrong with trying to get Mono to build it.
Mar 31, 2009 | 06:50 AM
#39
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 5
From: UK
Yes it is in VB Express 2005 Freebie. I only used VS 2005 to do the Pocket PC - for this you can download a trial that will work if the system clock is not more than 90 days after the installation date.
Mar 31, 2009 | 08:28 AM
#40
For the eventual SD patch, we need to have MAT and boost logging. The MAT patch is available for this ROM, but the boost logging is not (that I could find from the main thread on it by mrfred).
I would like to do everything at once, if possible, since I have my ECU pin connectors handy. This way I will be ready for the SD patch when mrfred gets enough time to code it up. I may as well use that time to install a switching harness as well.
I already have a GM 3.3 bar map sensor and a GM AIT sensor installed and working in the car for quite some time, but not wired into the ECU. They are both wired into my SSi-4 for now. So, on my todo shoulld be:
1. Wire in AIT to ECU and apply mrfred MAT patch to 96530006.
2. Wire in GM 3.3 bar to ECU and apply boost logging patch for 96530006 (is this available yet?)
3. Buy or build a map switching harness and wire in to ECU.
4. Download John's livemap 96530006 ROM and xml and apply all of mrfred's tables and patches to the XML and make necessary changes to ROM.
5. Hope that everything is up and working and flash into my car.
That's a lot of changes at once to do, but I would like to do it all at the same time, if possible. I have all of the info that I need for all patches, except my #2 because I don't think it exists.
If #2 doesn't exist, I suppose I can still do the rest and leave #2 and the eventual SD patch for round 2.
Eric
Mar 31, 2009 | 08:42 AM
#42
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 5
From: UK
I've left off doing SD patches for US cars, not least because of time, but also because I don't have a clue what addresses all these sensors are going to appear on. On the 8MR JDM (not tested yet) I've ignored temperature and just expect the user to wire their manifold or UICP temperature sensor into the MAF IAT wire, then it works as stock.
I still believe you guys could use 96260009 with a lot less hassles, as a guy on the MLR says he got this code working in a US Evo 8 ECU running his JDM Evo 6 IIRC http://www.lancerregister.com/showthread.php?t=253391
I still believe you guys could use 96260009 with a lot less hassles, as a guy on the MLR says he got this code working in a US Evo 8 ECU running his JDM Evo 6 IIRC
http://www.lancerregister.com/showthread.php?t=253391
Last edited by jcsbanks; Mar 31, 2009 at 08:45 AM.
Mar 31, 2009 | 08:57 AM
#43
Mar 31, 2009 | 08:57 AM
#44
Code:
<!-- direct boost control modifications --> <table name="Variable for Boost Control" category="Turbo" address="2025e" type="1D" level="1" scaling="Hex16"/> <table name="Boost Error RAM Address" category="Turbo" address="20252" type="1D" level="1" scaling="Hex16"/> <table name="Boost Error RAM Address in Boost Error Table" category="Turbo" address="6bfa" type="1D" level="1" scaling="Hex16"/> <table name="WGDC Correction interval #1" category="Turbo" address="1a54" type="1D" level="1" scaling="uint16"/> <table name="WGDC Correction interval #2" category="Turbo" address="1a56" type="1D" level="1" scaling="uint16"/> <table name="MUT8A" category="MUT" address="3642a" type="1D" level="1" scaling="Hex16"/> <table name="MUT8B" category="MUT" address="3642e" type="1D" level="1" scaling="Hex16"/> <table name="Max Total Upward WGDC Correction vs TPS" category="Turbo" address="448a" type="2D" level="1" scaling="DynamicBoost"> <table name="TPS" address="6c2a" type="Y Axis" elements="9" scaling="ThrottlePercentage"/> </table> <table name="Max WGDC vs Coolant Temp" category="Turbo" address="604e" type="2D" level="1" scaling="WGDuty"> <table name="Coolant Temp" address="6ad6" type="Y Axis" elements="8" scaling="Temp"/> </table> <table name="SHLR->SHLL for EBC" category="Turbo" address="1ffd6" type="1D" level="1" scaling="Hex16"/> <table name="Boost Error Correction" category="Turbo" address="449a" type="2D" level="1" scaling="OffsetWGDC"> <table name="Boost Error" address="6bfe" type="Y Axis" elements="17" scaling="BoostErrorPsi"/> </table> <table name="Boost Adder" category="Turbo" address="1a70" type="1D" level="1" scaling="psia16"/> <table name="Baseline Boost #1" category="Turbo" address="450a" type="2D" level="1" scaling="psia8"> <table name="RPM" address="6bd4" type="Y Axis" elements="16" scaling="RPM"/> </table> <table name="Baseline Boost #3 (BCLS)" category="Turbo" address="454c" type="2D" level="1" scaling="psia8"> <table name="RPM" address="6bd4" type="Y Axis" elements="16" scaling="RPM"/> </table> <table name="Max WGDC cold engine / CEL" address="2201"/> <table name="Max WGDC before full temp or CEL" category="Turbo" address="2201" type="1D" level="1" scaling="WGDuty"/>
Mar 31, 2009 | 08:58 AM
#45
I still believe you guys could use 96260009 with a lot less hassles, as a guy on the MLR says he got this code working in a US Evo 8 ECU running his JDM Evo 6 IIRC http://www.lancerregister.com/showthread.php?t=253391
http://www.lancerregister.com/showthread.php?t=253391