-
10th July 2016, 04:53 PM
#1
IIDTool Bluetooth & USB wont communicate
got a Bluetooth IIDTool in March last year and used it succesfully to reflash the Disco 3 EAS ECU and clear faults, read live data etc.
Went to use it today on same car and having major issues getting it to communicate. I have the IIDTool app loaded on a Samsung Galaxy S5 and it wont read live values. there are 2 ways to view the data, one mimics the up down left right buttons of the car ( very clunky on an android phone) and the other is a more intuitive menu / display system. In my case the expanded menu system wont work but I can read live data in the up down left right button style display.
I am also having problems connecting my laptop using a USB cable.
Also having issues with the Bluetooth pairing with the app on the phone freezing and just being a brick.
Does it have flash memory onboard that loses its marbles if not used for a while?
Does this sound familiar to anyone?
Experienced guidance would be good.
thanks.
-
10th July 2016, 05:01 PM
#2
I've heard of a couple of people having similar Bluetooth & freezing issues as you. And there's a couple of reviews on the Play store saying the same.
What versions of the app and android do you have on your phone?
-
10th July 2016, 05:25 PM
#3
latest version of the app as downloaded yesterday. Android is 5.0.
Whats changed is that it no longer works on the the laptop and the phone that I used successfully in the past.
-
10th July 2016, 05:28 PM
#4
Does sound like it's reached end of life. I think your only hope is contacting GAP Diagnostics support now.
-
10th July 2016, 06:46 PM
#5
So if anyone has got one of these and has had similar problems I would be interested to hear what has been going on.
thanks.
-
10th July 2016, 08:45 PM
#6
Ok, had a breakthrough.
i was supecting that I needed to update the IIDTool but I couldnt connect to the IIDTool using the Updater Software, it wouldnt get past the 'Find Device' step.
I got it to update eventually as I was trying to 'find device' while the tool was connected to the OBD2 port. My mistake as I was already in the car trying everything. Doh!
Once I connected just the IIDTool to the computer on the bench ( in the kitchen with the wine & cheese) the 'find device' sequence went fine.
After that the tool did everything normally.
So, the root cause of the problem is that not having used the device for at least 6 or 8 months it wouldnt communicate with the mobile phone which had the latest app loaded.
So, whats the implications of that? Well if you have a IIDTool and you plan on using it or will be depending on it as a resource on a trip then you better keep it updated...... thats what it means.
cheers.
-
27th July 2016, 08:11 PM
#7
There is also a problem with some BT units where the BT daughtercard gets shaken out of the mainboard socket. Just open it up, and push it back in, or contact GAP, and they will send you rubber piece to help keep it there. This is for v2 BT (I had an early BT unit, and that had to be sent back).
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Search AULRO.com ONLY!
|
Search All the Web!
|
Bookmarks