IDS TRANSIT CONNECTION PROBLEM

[digi-dash]

hi all, i have ids china v67. working on 05 fiesta tdci, 01 mondeo 1.8 petrol and 3 focuses but wont connect and diagnose 3x 01-03 transit duratorq 2.0 and 2.4s. i have firewall turned off and running on a fresh xp sp3 install. NO other programs on this laptop. date on laptop set to allow module programming so i am puzzled. on an ids trouble shooter it gave an ip address to use so i set that and still the same. i also installed ids on a dell d600 and same results, any advice appreciated, thanks steve

[sowczas]

I've v67 and i did 04 no bother i think i did 03 can't remember now we should have on yard something between 01-03 i will check tomorrow and let you know

[digi-dash]

thanks i'd appreciate that, thanks steve

[digi-dash]

update, tried 04 transit 2.0 today. tried to connect, gave me choice 2.0 or 2.4...when selected 2.0 ran network test and just kept trying until it gave a testman error. as always any help/advice appreciated, thanks steve

[tomtom0785]

have a look guys - maybe it's a problem because of building date - i know diesel Engines had to have from year 2004 onwards to confirm with the EOBD System (Industrial vehicles from 2006 on) - so sometimes the vehicles build before don't plugged K-Lines for all modules into 16pin OBD Connector n(sometimes there's a second connector somewhere else)
just have a quick check and look if on the OBD Plug on pin 16 are 12 Volt and on pin 4 and 5 ground - had a similar problem with a Landrover Date 2002 Diesel Engine - had no ground on pin 4 - so no communication over VDM/IDS , and fault errors,....

[digi-dash]

hi tomtom, thanks but ids support 1996 on...landrover supported from 2005 so your 2002 not supported. thanks but i feel transits maybe different protocol and my prob may be ip address, lan, network, or driver such conflicts, thanks steve

[sowczas]

Checked on '01 2.0 FWD self test, datalogger , vp44 programing all went ok

[digi-dash]

thanks for that, could i ask another favour...please. could you plug in and check the ip address and network settings yours is using. if you dont know how to do this i can email you ids trouble shooter with instructions please pm me your email address, once again, thanks steve

[digi-dash]

thanks sowcsaz for ip address but i am still not connecting to transits....the furthest i get is choose 2.0 or 2.4 then it starts testing network, goes accross bar loads of times then says testman error. any suggestions it connects to other models ok but failed on 6 transits now...thanks steve

[nutloose]

it is a faulty clone.

[digi-dash]

are you sure as it connects to other cars fine. i thought it may be transits are a different protocol but not sure??? thanks steve

[Dzltec]

It should identify the vehicle fully, vin details etc. Then allow you to go and do all the tests you need.

i don't think it shpould be giving you choices.


Andy

[digi-dash]

it does id vin but on a fiesta ive been working on it gives choice of fiesta...fiesta 3 door or mazda 2???? surely it wouldn't be part of the program if it wasn't supposed to give choices???? thanks steve

[donsmith249]

I use non clone and it gives me a choice of year model and type of vehicle. Example. Explore or mountaineer And then 2000-2001-2002. As for the transit connect problem. I have a gna600 I use on ids when my real vcm is in for service and it will not communicate on may body modules. Like the GEM radio and park assist. Good luck.

[digi-dash]

ok my thoughts are to try v68 instead of 67. i will reinstall windows first. can anyone say if i need to change date and if so what date should i put? also will i need to update vcm? if so is there no going back to v67? will vcm update be on v68 dvd? all and any advice appreciated, thanks steve

[digi-dash]

update...i got v68 dvd but the patch says its for mini ids and the vcm.bcf file is less than 1 meg where the v67 file is over 2 meg so i am reluctant to try it incase it screws it up my vcm. i see china is doing v69 now so i might wait to try and get a copy of that. i have since managed to connect to a couple of trannys but manually and choosing 2.4 only. this method will do for diagnostics but i would prefer the software to id van to avoid any programming errors. thanks all, steve