Mitsubishi Forums banner
21 - 40 of 59 Posts
I know the mut 2 protocol is used in the version 1 outlanders, its a big pain to find something that will communicate with it.
What would be nice if you could use that Mut3 software ( readily available on the net) via a pass thru driver, I think some of the mut3 software of mitsubishi
does have the older mut2 in it but its how to connect to the software is an issue for me...........I"m a novice never tried to do it.
If that were possible it would open up all the bells and whistles of the software for any version of mut.
 
Well I had a look at the ebay add, I'm not sure if the latest mut3 software covers mut2 ( is there a mut1 also, not familiar with that one), but you can download different free versions of that software that does cover the older mut protocol. If this is a way to connect the older mut version cars to that software package then its what I've been wanting for a long time. I have no experience with taxtrix etc or pass thru drivers only with obd11 ( a guy in canada makes a box that converts the mut2 to canbus which I use but it doesn't communicate with all the ecus, its limited, he does make another device which does communicate with all the ecus, but using the mitsubishi software is really the way to go. ...very interested in this.
 
FWIW.
The computer communication system is quite generic for the 2wire system bus used in cars, including what is used internationally.
I believe the problem in using 'generic' scan tools is that there are differences between any particular 'address' and what that particular function is named.
The US system required a basic set of addresses and names to be established for the US industry "OBDx". That is, most generic systems can work on Magna, but asking for say 'P0102' my not relate to what it is P0102 in the US standards.
'I think'!
rumpfy
 
A couple of years ago, I bought a Foxwell ET2530 (NT530 outside of Oz) through Repco for $375 (via Australian distributor Endeavour Tools - ET2530 Foxwell Multi System Scan Tool Enthusiast ) to use with my OBD1 Hyundais. It comes complimentary with one manufacturer's software, so obviously I got the Hyundai/Kia with mine, but this morning I paid the ~AUD$100 to install the Mitsi software so I can also use it to work on my Mum's KF Verada. My first experience of using it to scan seems satisfactory, although I'm still getting used to understanding the Mitsi system of OBD1 coding (see my other post from earlier today - (15) Unknown OBD1 Codes '98 KF Verada | Mitsubishi Forums ).

It's not the most user-friendly scanner I've ever used in terms of setting it up with the new software (I had to have a conversation with their helpline), but in short, it seems to scan all systems on my Mum's '98 Verada Ei well enough, and it's sure cheaper than other OBD1 options, which all seem to be well over $1K (see screenshot examples in my other thread just posted above). Seems to give me clear-codes functionality as well, at the very least. If you happen to live in Perth, you're welcome to drop by and try mine on your Mitsi before you actually outlay any money. I think it would still be the same if you bought the Foxwell NT530 through Ebay or whatever for a cheaper price because all the downloading etc I've done has been through the global/US Foxwell website anyway...

Now I just need to better understand the coding system in terms of which error codes mean what (it's certainly quite different to what I get from Hyundai/Kia)...
 
that is really good info, can you say what was the basic process to update the scanner? Have to connect to the internet or via a memory card or some other method?
Here are some videos that demonstrate the actual scanner, how to set it up initially, and how to add additional vehicle software. In my case, the only thing I did wrong was assume that, because I already had the FoxAssist application open (from buying and downloading the additional software) it would then update my scanner/SD card, but apparently it will only do that when you have plugged your scanner/SD card into your PC BEFORE you open the application to update with the additional software. In other words, I had to:

1. Go into FoxAssist to buy/download the additional (Mitsubishi OE) software;
2. Once the download has completed, close the FoxAssist App;
3. Insert my SD card reader into the USB port of my PC;
4. Open the FoxAssist App again;
5. Click on update;
6. Eject my SD card/reader and insert back into my NT530 scanner.

Step 1-2 was the longest stage, taking a few (<5?) mins. Steps 3-6 took only a minute or two, if that....

Hope this clarifies.

Foxwell NT530 Unboxing - YouTube
Foxwell NT530 - An Affordable Bi-Directional Scan Tool Less Than $200
Foxwell scanner Activation and Software install Set up
How to Activate and Update the Foxwell NT530 For Extra Software?
Foxwell Scan Tools Software Update - YouTube
Foxwell NT530 - adding a new car brand (PayPal only)
 
A question for you guys down under...Where were the Mitsubishi models you are driving built ? ...In the U.S. there is a federal emissions standard [OBD-2] in place for all vehicles sold new here. The Mitsubishis we have here were either built in the U.S. [factory now close], or in Japan. Do you have something like that down there ? ...J.D.
Australia's automotive industry did not adopt OBD2 until 2006, so it's pot-luck as to whether any new car sold here prior to that can be scanned using an OBD2 diagnostic tool. As some examples:

1. My Hyundai Sonata EF V6s (1998-2002) are OBD1 systems, but some OBD2 scanners will read them, with the right software. For example, my OBDLink LX Bluetooth scanner will read the EMS with the free "CarScanner" app available from Google Play Store, but not with the software that came with the unit itself. Nonetheless, it also won't scan other systems, like transmission etc. That's the main reason I bought my Foxwell NT530 diagnostic tool - because it communicates with every Hyundai ever produced, not just the OBD2/2006+ models, and it does so multi-directionally with all systems (i.e. Engines/EMS, transmission, SRS etc.).

2. All systems on my Nephew's Honda CRV 2002 can be read/cleared etc using my OBD2 Bluetooth (OBDLink LX) scanner. Same for my friend's 1994 Ford (Australia) Fairlane V8 (go figure!).

3. My friend's 1&2 Gen Toyota Prius are most reliably read using the OBDLink MX+ scanner, with added Toyota module.

4. My Mum's '98 Mitsubishi Verada (Diamante in O/seas language) isn't even visible to any OBD2 scanner/reader that I've tried, but seemed to cooperate fully with my Foxwell NT530 that I bought a couple of years ago, once I paid the additional ~AUD$100 a few days ago to add the Mitsubishi OE (OBD1/"MUT") software to it.

5. My daughter's '98 Hyundai Excel (Accent) - invisible to OBD2 tools, but fully interactive with my Foxwell NT530 with OE (OBD1) software.

6. Neice's 2002 Ford Fiesta 100% OBD2.

Anything sold new from 2006 onwards in Australia is 100% OBD2 (i.e. same as USA & Europe).
 
thanks Kimp for all the details on updating and getting mitsubishi software, its so easy to do fords with forscan software, suprised that someone has not figured out how to do same for mitsubishi obd1 and obd2. The guy who designed the forscan software made an absolute fortune from app downloads, massive number. That should be incentive enough for some software guru to do same for mitsubishi, I've been waiting a long time for it.

anyhow thanks again for going to trouble to post those details, very good to know the process
 
Putting aside the fact that we can't open the page in which you've attached their response, was that Foxwell or Endeavour Tools (Foxwell's Australian Distributor) that you contacted?
I have received recommendations from Foxwell indicating that the following scantools will function on 2005 and earlier Mitsubishi Motors Australia Limited vehicles: NT510 Elite, NT624 Elite, NT710 and NT726. The NT530 is still available but the first 2 models I listed are upgraded versions. Foxwell are having a sale at the moment and these scanners are discounted. So, you need to purchase a single vehicle scanner plus the Mitsubishi vehicle software add-on and the Mitsubishi adapter lead.
The prices are in USD and as usual the conversion rate doesn't help. Apart from that you can get a scanner(US$159) plus Mitsubishi software(US$80), Lead(US$29) and delivery appears to be US$20.
I think it's viable if you want to keep your vehicles for a few years.
 
I have received recommendations from Foxwell indicating that the following scantools will function on 2005 and earlier Mitsubishi Motors Australia Limited vehicles: NT510 Elite, NT624 Elite, NT710 and NT726. The NT530 is still available but the first 2 models I listed are upgraded versions. Foxwell are having a sale at the moment and these scanners are discounted. So, you need to purchase a single vehicle scanner plus the Mitsubishi vehicle software add-on and the Mitsubishi adapter lead.
The prices are in USD and as usual the conversion rate doesn't help. Apart from that you can get a scanner(US$159) plus Mitsubishi software(US$80), Lead(US$29) and delivery appears to be US$20.
I think it's viable if you want to keep your vehicles for a few years.
Great. Thanks for the update.

My mum's '98 Verada didn't need an adapter because it already had the OBD2 port, albeit communicating in OBD1/MUT language through it. They used to include one manufacturer's software in the price and still do include it for the USD$159 (Foxwell NT510 Elite All System ABS SRS OBD2 Diagnostic Scanner ). BTW, Foxwell says on their website that the NT530 is an upgrade on the NT510 Elite (Foxwell NT510 Elite VS Foxwell NT530) rather than the other way around, so I'm not sure who's right on that one, but reviews seem to corroborate that (eg. Bing Videos). The NT530 was supposedly still considered new to the market when I bought it a couple of years ago from Repco for AUD$375, and from memory, the NT510 Elite had already been out for a while by then. There didn't seem to be a great difference in capability between them at the time, but the NT530 seemed to be considered the later-developed of the two (which is why I chose that one over the NT510 Elite). When I added the Mitsubishi software to the Hyundai/Kia software already on my NT530 last week, it cost me USD$60 via FoxAssist. If I was to do it all again, I wouldn't bother going through Repco/Endeavour Tools and just save myself AUD$100-$150 by buying it online. The warranty isn't so long to make the local-return convenience worth it, and Endeavour Tools doesn't seem to offer any significant improvement from a customer service perspective, that I've noticed (certainly you get the exact same software for diagnosing our Australian OBD1 cars regardless of who you buy it from).

The only disappointment I have so far with my NT530 is that the VIN identification function doesn't work (I suspect it only works on US vehicles as this often happens when I try to check part compatibility using my VINs on non-Australian sites online). Likewise, I don't seem to be able to save my vehicles into memory, so I have to manually enter them each time I scan. Apart from that, so far, it seems to work very well on my old OBD1 Hyundais (90s Sonatas & Excel) & Mitsubishi ('98 Verada). Those two issues (i.e. VIN identification & Saving vehicles) seem to be a common problem for people in Australia and Britain, from what I've seen so far...

EDIT: Here's the link to the thread back when I was investigating what scanner to buy in order to diagnose my Australian OBD1 vehicles:

(1) Best diagnostic code reader tool recommendations please? | Page 2 | Hyundai Forums
 
When someone does a new reading with the Foxwell on a Magna/Verada, could they please post an image to the forum?

Thanks.
Good idea. I'll start with these from my earlier thread last week, just for the collection. In short, they all seem to have something to do with the immobilzer system, which ironically seems to work just fine on my Mum's Verada...

(1) Unknown OBD1 Codes '98 KF Verada | Mitsubishi Forums

Initial scan reveals a total of four error/fault codes from two systems (i.e. 1x MFI - Fuel injection system faults; and 3x Immobilzer system faults)

Image


Drilling down into the MFI system fault - some kind of Communications thing with the Immobilser computer??...
Image


Drilling down into the 3 Immobilser faults/codes - still trying to work out what these specifically mean in the real world...
Image



And then these two codes, which I have no idea what they mean...
Image

Image
 
Just a point of interest for members, I just purchased a FOXWELL NT710 from OBD STORE on eBay.au and when I queried compatibility with MMAL manufactured Magna's I have been told it may not work.
Leaves you wondering about the reliability of information from companies or are they just after the dollar!!
 
This is a disappointing saga. I ended up cancelling the purchase of Foxwell NT710 from ebay australia after talking to a rep from Endeavour Tools in Melbourne. He recommended their ET2530 as it will read OBD1 and OBD2 but you still need to purchase 2 adapter leads in order get the scan tool to communicate with the vehicle system.
The problem I have experienced in trying to find a scan tool to work on Magna's is that people overseas appear to be oblivious to Mitsubishi's MUT protocol that we had in Australia.
Maybe some of the diagnosis issues KIMP is experiencing with his ET2530 coud be due to not having the adapter cables(?), just a thought
 
Maybe some of the diagnosis issues KIMP is experiencing with his ET2530 coud be due to not having the adapter cables(?), just a thought
The '98 Verada I'm connecting to uses the normal 16pin OBD2 port, so any adapters would be pointless anyway... My recommendation from personal experience is to get the NT530 (or "ET2530", if you want to pay a commission to the Australian distributor - Endeavour Toos, because the actual product you'll receive in the box is the NT530 anyway). The software I downloaded from FoxAssist obviously communicates with my Verada's OBD1 system & ECUs, so for those who don't have the 16pin OBD2 shaped port, you'd also need to buy the necessary adaptor for your particular car (no real way around that, that I can see?). There may be other options out there, I just don't have personal experience of them so I obviously can't vouch for them.

For me, the biggest challenge is learning what the codes actually mean. I think Leadfoot6's intention is that together, we can gradually put together a reference chart of what the codes mean in real life part/connections/symptoms etc - to the point where it will eventually be as easy for us as googling an OBD2 code / video etc. Or, in short, "if it ain't out there, let's compile our own" ;)(y):unsure:
 
21 - 40 of 59 Posts