Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
31 Software / failure to install Bluesoliel software
« Last post by rmatuszak on March 26, 2015, 02:14:19 PM »
First time user of the ELM 327 and the software. When I try to install the bluesoleil software I receive an error 183 and it won't install.
Not sure what to do.
Our scan tools and software only read diagnostics from emissions data on vehicles that are OBDII complaint. Unfortunately, the ScanXL software with the GM Enhanced add-on will not be able to command the EVAP to turn on and off.

I apologize for the inconvenience.

Best Regards,

Would it be able to read the EVAP system pressure sensor and display a readout?
OBDLink / Re: failing to connect on japanese vehicles
« Last post by STN-Brian on March 26, 2015, 12:30:23 PM »
What country were they bought new in?  Are they gas(petrol) or diesel? Different vehicle types were OBD II compliant at different years in different countries around the world.
OBDLink LX / Re: OBD link LX
« Last post by Chris Fincher on March 26, 2015, 12:25:48 PM »
It makes sense that you were able to communicate with the VW since EU adopted the OBD standard for petrol vehicles in 2001 and for diesel in 2004.  Unfortunately, an MX or any of our other tools probably won't be able to work better than the LX in the Subaru.  I apologize for the inconvenience.

OBDLink MX WiFi / Re: Client Mode
« Last post by macduff on March 26, 2015, 12:23:09 PM »
Ok, let me know what happens.

Sorry, been busy at work but I'll try this soon as I'm heading to the track in two weeks!
General OBD Questions / Re: OBDlink MX wifi
« Last post by Chris Fincher on March 26, 2015, 12:06:20 PM »
The OBDLink MX WiFi only uses WiFi so you can't pair it using Bluetooth.

The need to turn off mobile data is actually an Android restriction, specifically one that Lollipop utilizes.  It'll do the same thing if your wireless router doesn't have internet access.

Developer Forum / Re: Inconsistent result to repeated 0100 OBD commands
« Last post by Chris Fincher on March 26, 2015, 12:03:22 PM »
The most helpful thing right now would be turning on headers and trying again to find out where each response is coming from.  Send ATH1 and then try to reproduce what you are seeing.  I can tell you that the responses that are the same as you expected are all probably coming from the same ECU though.

Do the lights on the Elmscan light up when it is only plugged into the car and not the PC?
Also, please post a log from OBDWiz of a connection attempt. You can do this by going to the Diagnostics tab->Raw Data tab, verify there is a green check next to Always Collect, connect to the tool and run it until it fails and click the save button in the Raw Data tab.  Then either attach the file here or paste the file into your post.
DashCommand / Re: [ECUsim master]Waiting for 5 baud init
« Last post by Chris Fincher on March 26, 2015, 11:59:56 AM »
That means it's set ISO 9141-2 or ISO 14230-4 5 baud init and is waiting for the initialization sequence.  This will usually happen automatically once the scan tool establishes a connection with it.  Without a scan tool that connects to it, you will never get past that prompt.

OBDLink SX / Re: OGBLink SX upgrade firmare failed
« Last post by Chris Fincher on March 26, 2015, 11:55:51 AM »
Your SX has the most updated firmware version so there is no need to update it.  The message you are getting, "Bootloader version not supported" is usually an indicator of this.  What it means is that the SX is newer than the updater will allow and in most cases this indicates that there is no need to update.  You happen to be in one of these cases.

Pages: 1 2 3 [4] 5 6 ... 10