Makes And Models > Zero Motorcycles Forum | 2013+

Using Putty to connect to MBB

<< < (2/3) > >>

2020_SRS_Commuter:
This project is taking forever. First I waited for an OBD2 conn to arrive from China, then I found out I had to order the correct cable, it showed up damaged, I had to order a replacement cable, and FINALLY, I hook it all up and.... nothing.


Things I believe are ok:
1) The cable is a "Dtech USB to UART TTL Cable" My UART is shown functioning normally in device manager, and I set its parameters there. The driver is up to date. Parameters COM1 Baud 115200  Data bits 8 / Parity None / Stop bits 1 / Flow control None

2) The laptop is a budget but functional HP I5 running windows10. I use it every day. It works. Using Putty 64bit.

3) The OBD2 port on the bike works; I can connect my scanner, see the VIN and it ids as a ZeroMainBikeBoard or some such, and I can watch throttle position in real time.

4) I am certain I have the correct wires connected to the correct pins. My OBD2 shell has the numbers printed on it, reversed to correspond to an OBD2 port. I've double and triple checked.

5) I set putty to serial, Com1, baud 115200, and open a session. This shows a black command line box with a green square as a typing prompt, and nothing can be entered. Ok.

But what actually happens:
I connect the cable to my laptop, launch putty, connect the OBD2 end to the bike, power on the bike, then open a session with putty. What I see is exactly the same as if I had not connected to the bike... a green square for a cursor, not blinking, and no response to any keys, no menu, words, nothing.

Any ideas? I tried switching to Flow Control XON/XOFF, and tried reducing to Baud 9600 on both then gave up. I left everything else in putty as defaults, the Terminal Settings and stuff. 

atomicdog:
I would try a different terminal emulator like Tera-tem.
I just tried again to get putty to work and changed a bunch of settings but still couldn't get it to work.
It does receive data from the MBB though, so if your not even seeing that I would triple check that the TX and RX lines aren't swapped.

Before you connect to the bike; you can do a loopback test of the OBDII cable you made by connecting pins 8 and 9 together. Then you should see what you type in the terminal.

You shouldn't need to key-on the bike either. The MBB will wake up when it detects a connection on the serial port.

2020_SRS_Commuter:
#1 Thanks for all your continued assistance. Last time I dealt with UARTs was in tech school and that was way back in prehistory, a decade before the internet was even a thing.

#2 Loop back worked.

#3 I checked the pinout and wire colors of the UART cable in its datasheet, then compared that to your pinout of OBD on the bike from your Github. Based on that, I had UART TX connected to bike RX, bike TX to UART RX. I assume that is the way it should be.

#4 I switched RX and TX on the soldered UART wires in my OBD2 adapter and badabing... text is there. Why? Because reality hates me, I guess. Or is it because RX should go to RX and TX to TX? Dunno.

Time for some coffee and I'll go play around with it.

LeverCommaJohn:
Yeah, welcome to world of confusing nomenclature when it comes to SERIAL communications. Some devices actually label their PINS as to what THEY do (which is the way it *should* be done, IMHO), and other devices label their PINS as to what they should be plugged into on the other end. Thereby, leading to TX-TX and RX-RX connections. It's stupid. Glad you got it sorted!

Specter:
wanna have some real fun?
plug in a serial cable when you should have used a null modem cable.

Aaron

Navigation

[0] Message Index

[#] Next page

[*] Previous page