Are you trying to load software or just use it in the car?
Printable View
Are you trying to load software or just use it in the car?
Did you make sure everything is plugged in correctly and securely?
Not sure if MUT works for you USDM guys, but shouldn't you connect via OBD2 instead of MUT (selected in the main menu by holding the switch in when powering on)?
The rear trim just gets disabled. The front trim acts normally.Quote:
Originally Posted by Jesters Deadd
MUT for the hybrids, ODB2 for the 96 up...Quote:
Originally Posted by GTOX
I'm back now. :)
I was trying to use it in the car.Quote:
Originally Posted by green-lantern
Triple checked prior to unhooking it.Quote:
Originally Posted by Jesters Deadd
The directions say to use MUT for '94 - '99 3S cars.Quote:
Originally Posted by GTOX
Though now that I am looking at it again it says to use MUToverOBD2 if you have an issue communicating as MUT. So it may have been a simple setting issue on my part.
That is what I get for rushing. I now have time to do everything right. My next track event is not until March or May.
-John
Hrmm yeah I use MUT because it's all I can use with my JDM ECU. Hopefully it's a simple fix and you get it working, let us know how you go.
So if I got a Montero ECU or a flashable 3/S ECU, could I use this to view realtime/control boost then export as CSV file to log on my computer? Could I log on my Palm without buying HHH or some expensive program?
status on obd2 simulation?
Yes use MUT for 94-99 3S Vehicles. OBD2overMUT is just another option available to 96+ vehicles that does the same thing but more slowly. On DSM cars, their 95 ECU only communicate OBD2overMUT.
J-Groove: If you're having trouble connecting, go to the Factory Calibration screen in the setup config and add +4. ie, if it says 150, make it 154. I assumed the microprocessor manufacturer would have done a good job, but their tolerances vary a lot. What is happening is the cold temperature is slowing down the heart beat of the microprocessor, and serial communications will get picky if the calibration is off too much.
HLxDrummer: I'm using a flashable 99 ECU, and yes to everything you said. You can datalog as CSV, or use a palm logger if you like.
OBD2 simulation is stuck at the moment. The software is written, but apparently there is some hardware differences between a real ECU OBD2 port and that of a datalogger OBD2 port (other than male/female connections). My guess is the resistance or impedance differs. I don't have an oscilloscope to measure volts/current on OBD2 waveforms to determine the input circuit resistance. I've spent a few days searching on the internet on electrical schematics for OBD2 on the ECU side, but all I find is OBD2 circuits for dataloggers.