DSM Chips

[9D9X]

My 2.0 cable is the mail. I can not wait to get it and use the evoscan and evoflash. I will let everyone know how it goes. Thanks Again Jeff.
_________________
Black 1999 GSX-Fp Green, fic 850, short route FMIC, type-s bov, 3" intake pipe with k&n, adj. fpr, 255 fp, N-1 turbo back, 2.0 cable, evoscan, evoflash, 3.2 fidanza clutch and flywheel

[9D9X]

Hey Jeff,

As soon as I get everything up and running I want to maybe get some patches and tuning from you. Being able to flash these ecu's are the best thing that happened to the 2g dsm community.
_________________
Black 1999 GSX-Fp Green, fic 850, short route FMIC, type-s bov, 3" intake pipe with k&n, adj. fpr, 255 fp, N-1 turbo back, 2.0 cable, evoscan, evoflash, 3.2 fidanza clutch and flywheel

[keydiver]

Ceddy's 1.8b definition file is a good place to start. He's coming out with a v1.9 soon. You won't get my good custom maps, but he is adding lots of features. We have worked out a good knock gauge conversion, which I am shipping now. His version will probably be in v1.9.
Jeff
_________________
GVR-4 #1886/2000
http://www.dsmchips.com

[keydiver]

BTW, be sure to install ECUFlash first. It has the proper drivers for the cable.
Jeff O.
_________________
GVR-4 #1886/2000
http://www.dsmchips.com

[9D9X]

Yea, I already downloaded the ceddy's 1.8 and evoflash. Do your maps and gauge conversion work with his rom.
_________________
Black 1999 GSX-Fp Green, fic 850, short route FMIC, type-s bov, 3" intake pipe with k&n, adj. fpr, 255 fp, N-1 turbo back, 2.0 cable, evoscan, evoflash, 3.2 fidanza clutch and flywheel

[keydiver]

Yes, sort of. His 1.8b ROM and xdf do have access to the gauge values used. There are actually 4 things that need changed to make the guage diplay something else:
1) You of course need to change it from displaying LOAD to something else, like knock, so you need to know the address from the MUT table that is for knocksum. In this ECU the address is F4B6.
2) You need to determine how many divisions you are going to display. Like my 1G and 2G knock gauges, I decided to have the gauge sit on the 2nd tick up from the bottom, and go up 3 more ticks from there, so that's a total of 4 divisions. You can actually scale it with more divisions if you wanted, up to the maximum 9 that I think there is room for in the original scaling for the boost gauge. But, I thought 4 divisions was accurate enough. I think Ceddy's new 1.9 will have a knock gauge with 8 or 9 divisions.
3) You need to scale whatever the value range is that you want to display. My gauge is setup for 5 knocksum per division, so I have 4 divisions: 0, 5, 10, and 15.
4) You need to know what the corresponding value needs to be to make the gauge move to the corresponding tick on the gauge for each of the above values. Ceddy sat up a gauge cluster on the bench and determined that the 5 bars on the boost gauge represent (in hex): 00, 30, 7E, BE, and FF.
Ceddy's 1.8b gives you the access to change all of the above values.
Jeff
_________________
GVR-4 #1886/2000
http://www.dsmchips.com

[9D9X]

Great thanks Jeff. Also my cable came in the mail today can not wait to use it this weekend. Thanks again.
Joe
_________________
Black 1999 GSX-Fp Green, fic 850, short route FMIC, type-s bov, 3" intake pipe with k&n, adj. fpr, 255 fp, N-1 turbo back, 2.0 cable, evoscan, evoflash, 3.2 fidanza clutch and flywheel

[9D9X]

Hey Jeff,

What are all the files on the CD. Just wanted to install everything correct.
_________________
Black 1999 GSX-Fp Green, fic 850, short route FMIC, type-s bov, 3" intake pipe with k&n, adj. fpr, 255 fp, N-1 turbo back, 2.0 cable, evoscan, evoflash, 3.2 fidanza clutch and flywheel

[keydiver]

The first program to install is ECUFlash, as it has the drivers for the Openport 2.0 cable. The setup.exe is for EVOSCAN 2.5. There are also backup copies of EVOSCAN 2.5 on the disk, zipped and in the folder. The Scantech, if I included it, is a program to check your Readiness Tests, but I don't believe it works with the Openport 2.0 cable. It works fine with my cheaper logging cables though, and older Tactrix cables.
Jeff
_________________
GVR-4 #1886/2000
http://www.dsmchips.com

[9D9X]

Hey Jeff thank you so much for the cable and evoscan. I love it and think everyone should get it, you can see everything your car is doing. Few things though.. Evoscan will not stay connected for a long time cuts off and reconnects. also my anti-lock light comes on and stays on. Do I just turn it off in the logging menu? Also do you know what the (apply CPU Timer Fix and logger superspeed) in the toolbar under logging is. I am Logging in MUT III is that right.
Thanks
_________________
Black 1999 GSX-Fp Green, fic 850, short route FMIC, type-s bov, 3" intake pipe with k&n, adj. fpr, 255 fp, N-1 turbo back, 2.0 cable, evoscan, evoflash, 3.2 fidanza clutch and flywheel

[keydiver]

1) I wasn't aware of any issues for guys logging the 1997+ ECU's with MUT protocol. Perhaps that is what the "CPU timer fix" is for? Do you have superspeed turned on or off? What baud rate are you using?
2) I think you need to cut out pin #9 of the OBDII plug if you don't want the ABS going into diagnostic mode.
Jeff
_________________
GVR-4 #1886/2000
http://www.dsmchips.com

[9D9X]

Baudrate is 15625. I have superspeed turned on. I think it came that way. Is there any reason to have the anti-lock brakes go into diagnostic mode, that you can think of. If not Ill just cut it like you said. Hey one more thing. What select DTC Method/ECU should I have it on? Right now its on OBDII EFI.
Joe
_________________
Black 1999 GSX-Fp Green, fic 850, short route FMIC, type-s bov, 3" intake pipe with k&n, adj. fpr, 255 fp, N-1 turbo back, 2.0 cable, evoscan, evoflash, 3.2 fidanza clutch and flywheel

[keydiver]

I *think* the OBDII DTC's are the only ones that work. Sometimes you have to try several times to get an answer for some reason.
Jeff
_________________
GVR-4 #1886/2000
http://www.dsmchips.com