Welcome, Guest. Please login or register.
Did you miss your activation email?
April 24, 2014, 02:04:39 PM
Home Help Search Login Register
News: Added OBDLink MX forum board.

ScanTool.net Forum  |  Recent Posts
Pages: 1 ... 8 9 [10]

 on: April 18, 2014, 12:26:46 AM 
Started by Rocknrollnightmare - Last post by callforfire
I am having a similar issue with my 2001 Ford Excursion 7.3l.  I can read codes, but immediately after reading it disconnects. So if I try to clear the DTCs it will say not connected to ecu. I tried the OBDLink MX with other apps (OBDlink, DashCommand) thinking it might have been an issue with torque, then tried it on 2011 ford escape thinking it might have been a diesel issue, but the problem is the same.  Pretty much limited to doing one thing at a time and then the MX stops talking to the vehicle.
The Bluetooth connection is stable, I have not had that drop out...yet.

 on: April 18, 2014, 12:01:53 AM 
Started by qoboosh - Last post by qoboosh
This OBDLink was ordered strictly for use with iPads, iPods, and iPhones.  I was really surprised that the "Quick Start" guide ran through multiple steps to "install drivers", "connect tool to a PC", or even "watch a video" which wasn't even a generic video but a Windows program too.   We don't even have a Windows PC at home so I was deep in Linux WINE configuration before realizing the video just gave directions for...Windows wifi connections!

This was going nowhere fast so next I was hoping for simplicity in trying a basic connection with the OBDLink WiFi in a 2001 BMW 3 series.  I just went ahead and plugged it in, noted the green LED came right on.  I was hoping the iPad or iPhone could see a new WiFi network, but they could not. 

If you've nodded your head with me so far, you probably agree that we are in search of very easy steps, like:
1) Plug your new OBDLink WiFi into your car's OBD2 port.
2) Scan for new networks on your iPod, iPad, or iPhone.
3) Connect to the OBDLink network.
4) Download and "ScanToolWifiConfig" "myfreeOBD" both free from iTunes.
5) Confirm you can see your car's basic data on your IOS device; spot check engine revs for example.
6) Download more advanced OBD apps from iTunes if you need them.
7) If desired "ScanToolWifiConfig" allows you to modify your ESSID, WiFi password, IP address, port speed.  It doesn't have any OBD functions except to show that it is communicating with a car.

This doesn't seem like too much to ask, does it?  If not I can wait a little bit, but otherwise this unit is going straight back to Amazon with my clearly-worded complaint that buyers should beware that they will be doing quite a few MANDATORY things on their PC, or a borrowed PC ( Shocked)  before they get anywhere near being able to use their target Apple IOS device with the ScanTool OBDLink WiFi.

 on: April 17, 2014, 06:57:45 PM 
Started by Rocknrollnightmare - Last post by Rocknrollnightmare
So just purchased a new OBDlink MX to use in conjuction with Torque Pro for my 2003 Ford F350 Powerstroke Diesel, and while I love the idea of being able to track the PID's & vitals of my truck, I have had nothing but problems with this stuff? I am a bit of newbee, so forgive me....but basically I have tried using the device with my HTC ONE, and with a SAMSUNG GALAXY TAB both running different versions of android, and still having the same issue?? the issue is that the bluetooth connection is esentially dropping out? example: I activate a device, ensure that it is connected, and all is going well....then all of a sudden the gauges freeze? so I reboot the torque app, and then only half of the gauges work while the other half stop working? I haven't changed anything....so one moment the gauge works....then everything freezes....reboot, and now only half of the gauges work....any ideas? would love to be able to utilize this setup, however this is very unrelible at this point....I haven't returned the device yet in the hopes that this thread may help...?


 on: April 17, 2014, 10:15:05 AM 
Started by LaurentGom - Last post by Chris Fincher
We have a programming manual that I will link below.  It will have all the commands that you can send to customize the ECUs on the sim.  To send those commands, just connect to the ECUsim via USB.

CAN is only slightly different than the others, as far as formatting goes, since it has the DLC which is not displayed normally but is usually 8, and the PCI byte which gives you frame information.  A CAN response will have [ $id, $dlc, $pci, $mode, $pid, $data1, ...] but the DLC part of it won't be displayed unless you send the command ATD1.

ECUsim Programming Manual


 on: April 17, 2014, 07:57:39 AM 
Started by kodl - Last post by kodl
So, simple Kiwi MPG for $60 is outperforming Scan XL Pro! Sorry, but this is crap software. I have my money back, but my friends is still trying and trying and trying.....and still nothing. Just some reading..........

 on: April 17, 2014, 12:06:38 AM 
Started by LaurentGom - Last post by LaurentGom
Thanks for your reply.

If the simulator outputs predefined datasets it's fine. But what do you mean by "you can set custom values for all PIDs" ? How do you do it, since there's no configuration software? And can you set a single constant value, or a complete dataset?

You answered my question about the STN1110, it sends the ECU response directly with no intermediate formatting. So if it's an OBD-II protocol, I'll get byte sequences such as [$length, $mode, $pid, $data1, ...], right?
But for example, in case of CAN, how is the CAN ID (the ECU index) transmitted? Is it prepended to the data?

 on: April 16, 2014, 10:35:30 AM 
Started by jdub1981 - Last post by Chris Fincher

I apologize for the delay.  Unfortunately, the information you want to access is most likely on another bus like you guessed but I don't think you can get to it on Torque.  I've tried messing around with it before and wasn't able to find a setting that did that.  Also, you can't access both busses at the same time.  This is a limitation in the chip in the OBDLink MX so there's not much we can do about it.


 on: April 16, 2014, 10:22:27 AM 
Started by scuderiaferrari - Last post by Chris Fincher

I went to the site for the app and saw the same thing.  It states that the WiFi device has to have an IP address of and port of 35000.  If that's the case then the OBDLink WiFi won't work with it.  Those settings do happen to match what the OBDLink MX WiFi will have but that device won't be available until August.

You can change the IP address and port of the OBDLink WiFi but it's not something we encourage because you can mess up other settings that would make it so you can't connect on WiFi at all.


 on: April 16, 2014, 09:13:20 AM 
Started by LaurentGom - Last post by Chris Fincher

The PIDs can be manually changed with commands or the knobs can control them.  This is true for both the ECUsim 2000 and ECUsim 5100.  Currently, remappable knobs and signal generators aren't available but as the page stated, it is planned functionality.  If you buy the professional version, it comes with 3 ECUs that all have predefined data sets and will revert to those data sets when the sim is either power cycled or reset.  In the Professional version, you can set custom values for all PIDs up to 0x4F.

It is not shipped with software to configure the ECUs and PIDs but that is something that is planned, too.  Unfortunately, I don't have an ETA for that.

About your question on the STN1110, what do you mean by the format of UART frames?  Other than the AT and ST commands, the frame formatting is determined by the protocol you're communicating on.


 on: April 16, 2014, 03:45:08 AM 
Started by holden_2004 - Last post by Shawnf350
See if the SX powers up when connected to the OBD port without the USB connected to the computer on one of the 03 Yukons.

 If possible, you could also see if a handheld scanner could connect.  This could help to rule out whether it's the Yukon or the tool.


Pages: 1 ... 8 9 [10]
ScanTool.net Forum  |  Recent Posts

Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.8 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!