Results 1 to 4 of 4

Thread: Communication Error

  1. #1
    Newbie
    Join Date
    Apr 2011
    Posts
    2

    Communication Error

    Hey Vitaliy,
    I didn't want to start a new thread, but my problems are almost identical to Ned's, although in my case I do see the LEDs cycle once I first plug in the unit.. when I try to Connect to the device, I get a quick flash of the two PC LEDs but nothing else.. then I get the Communication Error prompt..


    any advice?


    04-14-2011 11:48:17.875 Comm Port 3 successfully opened.
    04-14-2011 11:48:17.875 Tx: ATZ
    04-14-2011 11:48:23.046 Rx: Request Timed Out. (ATZ)

  2. #2
    VENDOR - ScanTool Vitaliy's Avatar
    Join Date
    Dec 2006
    Location
    Phoenix, AZ
    Posts
    624
    Different problem, Ned's tool wasn't flashing LEDs (it was dead, and MCS sent him a replacement).

    Since your LEDs are flashing, the unit is alive. The log says that the software opened COM3, sent "ATZ" (=software reset) but never received a reply.

    Is OBDwiz doing an automatic search, or did you hard-set the COM port and/or baud rate?

    Vitaliy
    OBDLink MX: world's smallest, fastest, most advanced OBD/Bluetooth adapter with SW and MS CAN support. Read the review to learn more.
    Need to look up a diagnostic trouble code? Try the most up-to-date, free DTCsearch.com!

    You cannot send me a private message using this forum. Use my email instead: vitaliy[@]scantool.net.

  3. #3
    Newbie
    Join Date
    Apr 2011
    Posts
    2
    Vitaliy:

    I tried setting the communication to pretty much every option... when I try to 'connect', initially the green light comes on on the interface and before I get the time out error on the laptop...

    so, it seems as though I'm communicating with the device properly but it isn't working out from there... I'm not really sure what to do...

    what do you reckon?

  4. #4
    VENDOR - ScanTool Vitaliy's Avatar
    Join Date
    Dec 2006
    Location
    Phoenix, AZ
    Posts
    624
    Green LED means the software opens the correct port, but can't get a response from the interface. Try updating the firmware:

    http://www.scantool.net/downloads/updates/obdlink/

    If the update is successful, it will tell us that the problem has to do with the software. Otherwise, request an RMA# from [email protected] (include a link to this thread).

    Sorry for all the trouble,

    Vitaliy
    OBDLink MX: world's smallest, fastest, most advanced OBD/Bluetooth adapter with SW and MS CAN support. Read the review to learn more.
    Need to look up a diagnostic trouble code? Try the most up-to-date, free DTCsearch.com!

    You cannot send me a private message using this forum. Use my email instead: vitaliy[@]scantool.net.

Similar Threads

  1. OBD2 communication
    By Anand in forum Coders Corner
    Replies: 1
    Last Post: 02-07-2011, 03:02 PM
  2. Serial Communication over usb
    By QuagmireMan in forum Road Runner
    Replies: 5
    Last Post: 04-07-2008, 12:50 PM
  3. communication
    By scuba_steve_wrx in forum Newbie
    Replies: 0
    Last Post: 10-23-2007, 06:29 PM
  4. Special OBD communication
    By banshee in forum Engine Management, OBD-II, Engine Diagnostics, etc.
    Replies: 2
    Last Post: 03-14-2007, 11:14 AM
  5. Interesting New Way Of Communication
    By Rafster in forum Wireless Communications
    Replies: 0
    Last Post: 08-07-2005, 03:48 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •