FORScan forum

Wild E Coyote wrote:I notice that OBD scanners get rather hot during operation. Is that normal? Perhaps they heat up to much, up to the point of affecting their performance?

Yes, it seems all china ELM327 WiFi become hot, but we didn't notice any influence to performance.

By the way, we are testing now OBDLink MX WiFi, it is much colder, although 3-4 times faster than any china WiFi adapter.

I am using a HP laptop with atom processor (1.6 MHz) and windows XP with all the patches (original, payed for windows XP instalation). It should be fast and strong enough for handling Forscan, shoudln't it?
When I get home, will do the logs as you requested

Wild E Coyote wrote:I am using a HP laptop with atom processor (1.6 MHz) and windows XP with all the patches (original, payed for windows XP instalation). It should be fast and strong enough for handling Forscan, shoudln't it?

Yes, it should work fine in this configuration.

Anyone know the username/pass for a wifi obd2 adapter with "CLKDevices" as wifi name? Tried standard admin/admin etc but none work

So helpful!

There are so many ELM 327,they all support WIFI functions. What's the difference among Vgate elm 327 and other elm 327s?

Tony Back wrote:There are so many ELM 327,they all support WIFI functions. What's the difference among Vgate elm 327 and other elm 327s?

Unfortunately, a cheap china adapter is always a lottery. We purchased Vgate bluetooth a year ago and it worked just great. Vgate WiFi purchased a half of year ago works ok as well. But in the past we got complaints from user who purchased adapters with label Vgate and had problems with them.

This is why in the past we recommend to purchase while label solutions like OBDLink MX. They are more expensive, but have good stability and performance. They are also better suit to Ford because of built-in MS-CAN support.

I just broke my piggy bank for a new sweet mini elm 327 with switch to play with. cheap $12 and much small previous elm327. Plug it into the vehicle's 16 pin socket, turn on the power, wait for the LEDs illuminates, attach the WIFI community of iOS system, and go to the App’s main program, start your first scan and enjoy seeing your engine’s available parameters like Vehicle speed, PRM, fuel pressure, mass air flow, EVAP System Vapor Pressure, Fuel Consumption,etc. The biggest advantages of this new super mini elm327 is that it comes with a built-in power switch to prevent the need for having to constantly disconnect your unit from the OBDII port.

I have made some comparison and found a most cheap one. Other may cause 10$ more than the price

<URL removed by moderator. Advertisement is not allowed on this forum>

Have you guys had any luck with Vgate's iCar2 adapter? I mean this one:



I've been using that to read my dad's Ford fault codes using Forscan. However, when I read my own BMW's fault codes using BMWhat app I started to suspect whether or not it finding all the ECUs. I contacted app's developer and he confirmed from the logs that adapter is not catching all responses from the car.

Unfortunately adapter settings are different than iCar1's settings - there is no setting for TCP-serial timeout. All the settings I can find are as shown below.



Or should I just go with OBDlink MX? Another option that I'm thinking which is a bit cheaper is BMWhat's own adapter (http://www.ivini-tech.de/en/adapter/ios ... mw/a-1003/). Do you guys have any experience with that using Forscan?

Yes we have one (purchased recently as many of our iOS users have it). Purchased here:

http://www.aliexpress.com/snapshot/6418 ... 6201211767

What can we say about it:

Good:
1. Nice looking device
2. Relatively good quality (comparing with some other clones), works quite stable.
3. Although reported as ELM327 v2.1, it is in fact seems to be old good china ELM327 v1.5 (so it is the only china v2.1 adapter that has no problem described here http://forscan.org/forum/viewtopic.php?f=4&t=22#p840)

Bad:
1. Still china clone (we had a hope such a nice looking device will have real v2.1 inside)
2. Quite slow (average ping 50 ms, in fact varies between 40 and 60 ms) - like on slowest Bluetooth clones. It has no serial timeout setting, so cannot be
adjusted. Such a delay is acceptable (means the whole FORScan functionality should work), but overal performance will be low.

As far as we can see, it works ok with all protocols, but we really tested only CAN. Ford SCP and Ford ISO seem to work, but we didn't test them on real vehicle.

So, we consider this device quite "average" - yes, it has enough quality to work with FORScan but quite slow. We would recommend to buy another Vgate WiFi adapter, one of our users recently posted: http://forscan.org/forum/viewtopic.php?f=4&t=897. We have such device and use it for iOS testing, it has 20 ms of ping (after changing TCP timeout in control panel to 1 ms).

As for OBDLink MX WiFi, we noticed some problems with it as discussed here http://forscan.org/forum/viewtopic.php?f=4&t=855, and so far are unable to understand nature of this problem and find a workaround. So for now we cannot recommend it.