If you haven’t, please read the Article here. All visitors to read, especially, you must read before making the Platinum contribution or joining The Honda NSX Owners Club (separate body from NSXCB). Thank you.
So, received the package and started to install it.
There are lots of different Bluetooth models available from cheap version to the high end ones on the Amazon, ebay, etc.
If you want just a simple and cheap Bluetooth OBD-II adaptor, search the web for ‘ELM327 Bluetooth’ but beware of the fact that some people had no issues at all while others had big problem with them.
As I wanted to have the capability of both the USB connection to my PC as well as the Bluetooth for my Android phone (Samsung Galaxy S-II) in one package, I went for the ScanTool.net ‘OBDLink Bluetooth Scan Tool’.
I was hoping to find some discount code through their Facebook but not available and then found their UK distributor.
At the end, it was cheaper and faster to buy it from this UK distributor than buying it from US considering the delivery/tax.
Addition to this, the person (Robert) who supported me for all the email enquiries were very helpful and quick to respond so very pleased in buying it from them.
I bought it through http://www.scantool-direct.co.uk .
The actual link to the product is as follows;
The package contains the followings;
Starting from the top left of this photo in anti-clockwise order, the OBD-II connector cable with serial connector, the OBDLink with Bluetooth feature + USB interface, the USB cable and CD for the hardware driver file, OBDwiz software, etc.
There is also brief installation manuals included in the package but these are also on the CD.
The PC setup is very easy and simple.
Just need to install the driver and the monitor software.
For the Android phone, there is a software called ‘Torque’ on the android market site.
It’s free and if you are happy with it, there is also a paid version with extra features.
For my background, the PC software was nothing new and not much to comment in this post.
I may touch on it in another post while diagnosing the issue on one of the NSX.
The Bluetooth interface with Torque on the Android phone is useful for both the DIYer as well as the owners who are not so keen on working on their NSX.
Having said this, there are not many UK owners with full OBD-II spec NSX.....
I think there are similar app for iPhone but since I don’t have one, can’t comment on them.
There are lots of nice features even for the free version of the Torque software and if you have full OBD-II NSX, it may help you in diagnosing some of the issues.
For UK spec NSX, you will find the OBD-II connector just below the glove box in front of the passenger seat above the right side knee area.
There is a small plastic cover and the connector is behind there and looks like this.
Reading the stored error code on the ECU.
I on purposely disconnected the Front Primary O2 sensor on this NSX and the Torque displayed the code and description correctly. ‘Front’ is ‘Bank 2’ and ‘Primary’ is ‘Sensor 1’.
You can also erase this error code using your mobile phone so no need to pull the Clock fuse.
Haven’t tried it yet as I must keep this sensor disconnected for a while.
There are several display method available but haven’t tried them all yet.
Just an example of numeric display and graph mode.
There is also logging capability but will leave it for the PC software as I don’t have all the time playing with the mobile phone.
Does this simply allow for easier reading of error codes, or does it allow you any tuning capability for the ECU?
My understanding is that the OBDII version on the 3.2 are not easy to tune?
The frame rate on any communication protocols over OBD-II port will randomly vary within the protocol spec so the update rate on a certain PID (Parameter ID) is not consistent. Also, the comm. speed is not fast enough (depending on what you want) so you can’t use it for any timing critical control.
This is why you need external sensors, emulator, logger, software , etc for detailed timing related tuning.
Initially, you will need to break into the CPU socket and use emulator to understand what is happening with each control module.
Sometimes, it’s quicker and easier to understand some of the output by using oscilloscope due to high sampling rate that can’t be achieved through the OBD-II protocol.
The difficulty in tuning the later model is around the DBW, idle control + LEV.
While non-DBW ECU software is almost fully analysed by the aftermarket ECU companies, I don’t think it is the same for some of the areas on the DBW model. For example, the idle control, LEV and so on.
Still, the information over OBD-II port is useful to understand the 'tendency' of the certain sensor output and PIDs by using the user friendly software.
Some of the software/hardware is quite user friendly so good for even non-technical oriented owners.
Ofcourse, having extra knowledge on your specific vehicle will also help in understanding a certain issue. For example, there are three coolant temperature sensors on our NSX but not many owners know which one is used for fuel timer control.
From the software point of view, reading and erasing the error code is just a basic.
You can log the PID while you are driving and play it back after stopped driving.
If used with video and GPS features on the mobile device, some of the software will even let you not only log the PIDs but also record the video coverage while you are driving.
Then, you can play it back with the PID displayed in the foreground while the video in the background.
If you have enabled the GPS, it will even show your movement on the Google map. Scary…