T300+ key coder and ECU diagnostic reader: MEMS1.9 and 2J
Posted: Sun Apr 15, 2012 9:26 pm
This arrived in the post for the weekend - a bit of shame that I haven't had the time to really play with it so far:
This is the T300+ - a diagnostic tool and key code programmer. Big thanks to Julian and Paul for pointing me in its direction - it's going to be quite useful for me I think - especially as I currently have two MGFs. Not yet sure whether it'll talk to my ZTT CDTi - not tried it yet. You don't get a MEMS1.9 or Lucas 5AS with the reader BTW - they're there for artistic effect 
The T300+'s forte is programming key fobs to your Lucas 5AS - and I think may also have the capacity to sync an 'alien' 5AS to the MEMS. It can also be used to retrieve the EKA - or indeed edit and change it. All of which is hugely useful, but it can also interogate your MEMS unit in a similar way to the plethora of OBD2 compliant readers can... so now yes you can read your pre-EOBD/OBD2 MEMS in much the same way as you can MEMS3 - which is very nice
MEMS1.9 and MEMS2J use an OBD2 style port, which is located on the fuse board - shown here:
As mentioned above, I haven't had a great deal of time to really explore the functions, not helped by the fact that my car's battery is on its last legs and was nearly flat (grrr!) - but here's what the screens look like:
On start up - it asks you to adjust screen brightness:
Then you enter the security code - which helpfully is printed below the main screen (d'oh!):
The device is compatible with a range of vehicles, so enter the manufacturer (Rover):
It then tells you which version of engine management you've got on your car (in my case, MEMS1.9):
You can then enter the diagnostic menu:
You can then read the fault codes, and also clear them:
I read mine, and I found a few faults listed, including the throttle position sensor - which wasn't massively surprising, as I'd fitted a 52mm throttle body over 10 years ago, and the car hasn't been anywhere near a Testbook for over 12...
I'll not bore you with the other codes - but there were two other sensor faults listed as current. Something to look into. I haven't tried the live menu yet, so I don't know whether I can correct the calibration issues out? Something for another day!
Anyway, I cleared the fault codes to see what would recur later - which gives you this screen when completed:
So plenty of other areas to explore here - the instruction manual is largely generic, other than the key programming procedure which is specific to each manufacturer - but I'll report back once I've had a chance to look in more detail 
- T300+ and OBD lead
The T300+'s forte is programming key fobs to your Lucas 5AS - and I think may also have the capacity to sync an 'alien' 5AS to the MEMS. It can also be used to retrieve the EKA - or indeed edit and change it. All of which is hugely useful, but it can also interogate your MEMS unit in a similar way to the plethora of OBD2 compliant readers can... so now yes you can read your pre-EOBD/OBD2 MEMS in much the same way as you can MEMS3 - which is very nice
MEMS1.9 and MEMS2J use an OBD2 style port, which is located on the fuse board - shown here:
- Location of OBD socket
- Connect lead to OBD2 socket
- It's in the fuse box, in case you needed to know ;)
On start up - it asks you to adjust screen brightness:
- Start up: adjust brightness
- Enter security code
- Enter vehicle manufacturer
- MEMS1.9
- Diagnostic menu
- Fault codes
- Throttle potentiometer
Anyway, I cleared the fault codes to see what would recur later - which gives you this screen when completed:
- Procedure complete
). But the communication from the exporter I used was exemplary - and they used DHL as their delivery agent, so no compliants. I see that there are quite a few listings on the website I used: 
