Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Burton]

38200 was the first thing I tried. However that isn't a default baud rate option (see attached)

If you go to device manager and open the device you can find that screen.

[Burton]

Can someone who has got their USB : ODBII to work provide a similar screenshot to the one I did on the previous post? Also which driver is your USB using.

Don't want to take apart something I am near certain I wired correctly before confirming the screen options are identical. My cable still isn't working correctly :/

Go to Device manager > find the USB in COM# being used for the ODBII > go to tab in image and check bits per second

[Francois]

here is the setting i used

[evtricity]

Burton, I have the same setup in my Device Manager as per your screenshot. I only set the baud rate to 38200 when I connect using putty.

[Burton]

Lovely ... so now I have to take the cable apart :/

Let me see if I can find a way to check the pinout of the USB to the ODBII pinout to see if it is connected right. I really don't want to have to cut through three layers of heat shrink to find out it is wired right and something else is wrong lol

Thanks for the info guys.

[Burton]

Ok, for those who are wondering the best way to check your pinout on a usb ... take it apart (picture included)

Seriously. You cannot check the center pins at all less you do this. And when you test you test from where the wires come into the PCB not where the pins com in to the PCB.

My high / low are switched for some reason. >__<

So to fix it I am going to unsolder from the board and swap the wires since it is more trouble to strip down the wires at the connection to the OBDII connector.

UPDATE: was able to log in and started to dump logs then it stopped. Seemed all USB ports don't work now 0_0 restarting my laptop to hope they come back lol

UPDATE 2: restart worked to get ports functional again. Upon trying the dump all command the computer blue screened after a while and crashed >__< Tried another port on usb 2.0 and it locked up the ports just after pressing enter to get prompt. Restarting now for the fifth time ...

[Burton]

Update, the buad rate works at 38400, and since it is a stock buad rate that is what I am going to use.

Every time I do a dumpall or eventlogdump after about 30 seconds the terminal stops receiving text and the computer will blue screen. My computer never blue screens and hasn't since I have had it for the last 3 years.

I don't have another machine to test this with sadly. I might pick up a cheap laptop and install Linux on it to see if that fixes it. Wonder if I started up a VM Linux machine and tried that .... hmm.

[Christian Frankl]

I´d rather would try it with a different USB to Serial converter. Maybe the driver isnt´t very compatible to your Windows version. What´s the name of the IC on the little USB-PCB? Is it something with FT232?
If yes, you could get the drivers here: http://www.ftdichip.com/Drivers/VCP.htm


regards, Chris.

[Burton]

It is a prolific 2303 as far as I can tell.  http://www.amazon.com/gp/product/B008AGDTA4/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1

The drivers installed are current. Anyone else using the prolific chipset?

System Requirement:
  . USB 1.1/2.0/3.0 Host Controller
  . Device using PL2303HX/X/EA/RA/SA/TA/TB version chips
  . PL-2303 Windows Driver Installer v1.8.0 or above
  . Supports the following Windows OS Family:
   - Windows XP SP2 and above (32 & 64 bit)
   - Windows Vista (32 & 64 bit)
   - Windows 7 (32 & 64 bit)
   - Windows 8/8.1 (32 & 64 bit)
   NOTE:
     - Windows 8 is NOT supported in HXA/XA chip versions (will show yellow mark Error Code 10).
     - Windows 8 is supported only in following chip versions:
         - PL2303HXD (HX Rev D)
         - PL2303EA (ESD protection)
         - PL2303RA (Built-in transceiver)
         - PL2303SA (SOP8 package)
         - PL2303TA (PL2303HXA/XA replacement)
         - PL2303TB (12 GPIO)
 
Supported device ID and product strings:
  . VID_067B&PID_2303 for "Prolific USB-to-Serial Comm Port"
  . VID_067B&PID_2304 for "Prolific USB-to-Serial Comm Port" (PL2303TB chip)
  . Other VID/PID based on PL2303 chip.

[Justin Andrews]

Check to see if you are using FDTI drivers, myself I'd be VERY hesitant about using FDTI drivers with non FDTI chips, they have already proven that they cannot be trusted after their deliberate "bricking" incident last year.

[KrazyEd]

I have two OBDII connectors that I use for my cars. One is bluetooth that connects to the " Torque APP " on my phone.
The other has a USB end that I use with my laptop. Would the on with factory USB work on the Zeros, or, do I have
to " build " one similar to photos above?  I have a 2013 FX, and, a 2012 XU that I would like to look into.
Thanks
Ed

[evtricity]

Zero uses an uncommon pin layout for accessing the MBB as detailed earlier in this topic. You can try it out and you might be lucky but I suspect it won't match the Zero OBD pin configuration.

[KrazyEd]

Thanks for the quick reply. I must have missed the mention of Zero pin difference.
Is there a particular version of PUTTY to be used, or, would the most recent work.
I thought I read in a different thread about using an older version of software. Not
sure if it was for the same purpose.
Thanks again.
Ed

[evtricity]

Current version of putty works ok for accessing MBB

[DynoMutt]

First, thank you for posting on how to assemble a cable to connect OBD-II to a computer and access the onboard management tool via serial console.

Second, please see this re: bitrates

http://www.tldp.org/HOWTO/Modem-HOWTO-23.html