rusefi.com

What is the step by step procedure to connect to Hyper Terminal?

E4ODnut wrote:What is the step by step procedure to connect to Hyper Terminal?

why would you want to use HT and not the java console?

Good Morning Andre,
No particular reason. I would just like to get more familiar with how things work so I'd like to connect using Hyper Terminal, Tera Term and puTTY as well as the dev consol. My USB TTL device just arrived from China so I'd like to try connect to Tuner Studio as well.

The analog board hasn't arrived yet.

EDIT

Oops, just got a call, have to go to work. To be continued

the micro usb port is relatively easy - all you have to specify is which port you are using (COM4 or COM8 or smth)
For usb ttl you have to specify speed which is 115200 the rest is default

mind installing windows drivers (if needed) from st's site...

That was too easy, even for me, so I assume I must have the Windows drivers installed and working.

Hyper Terminal, TeraTerm and puTTY have no problem connecting. Discovery is running and the terminal windows are very busy reporting stuff, as is the Message Central window on the rusEFI Consol. How do I stop Discovery and just send it commands to get familiar with that end of things?

Excellent! Thanks.

When it comes to sniffing serial traffic with putty, I have had good success with com0com. I was trying to get a serial stream from a device in the field piped over TCP/IP, then I was connecting this single serial TCP/IP stream to several pieces of software on my PC via virtual COM ports. This com0com program allowed me to do that. I had a physical device theoretically in the field that had a TCP/IP serial stream. I then connected to that stream with my PC. I had one com0com session that grabbed the TCP/IP data and stuck it on a virtual COM port. I then had a second com0com session that would take that virtual comport and it would relay the data to two other virtual comports. One com port was then connected to with putty such that I could watch the stream, the other com port was connected to a piece of software on the PC. It worked great as I was tracing down a bug. In my situation, it turned out that this device in the field a SixNet gate way, was improperly handling MODBUS RTU packets. It was manipulating the signals and changing the packets before sending the TCP/IP stream. The tech support at SixNet confirmed the problem but refused to fix the issue. So that entire effort was all for naught, however I got to learn some cool stuff about com0com. I mention this as it can be a handy tool if you have a serial stream going to the java console, you can also get a log of that stream via putty, which might be handy.

I'd like to try to connect to Tuner Studio and see what happens. I have a USB/TTL device which looks the same as the photo that Andre posted. What do I connect to what and what is the procedure?

1) before connecting the TTL to the brain board, connect it to your desktop and install the drivers if it would ask for any
2) once the TTL is properly configured in windows, connect GND wire to GND on the brain board
connect RX wire of the TTL to pin PC10
connect TX wire of the TTL to pin PC11
3) connect to that new serial port @ 115200 using your favorite terminal
4) hit button 't' on the keyboard

It should tell you something. Once you tell us what it has told you we will tell you what the next step is

buzz click buzz click (or what ever robots make for noise)

I see content, must assimilate http://rusefi.com/wiki/index.php?title=Manual:Software#USB_TTL_cable assimilation complete.

buzz click buzz click (or what ever robots make for noise)

Windows couldn't find a driver but directed me to Silicon Labs where I downloaded a driver package and installed it. Now when I go to device manager, under "Ports (Com+LPT)" and the USB/TTL plugged in it shows "Silicon Labs CP210x USB to UART Bridge (Com5). So far so good (I think).

I have the gnd pin on the device plugged in to a ground pin on Discovery. I have the RX pin connected to PC10 and the TX pin connected to PC11.

When I try to connect with Hyper Terminal I get no response. Should Discovery be powered up with it's USB cable?

The USB TTL cable can not power the Discovery. The Discovery will need to be powered, probably from a secondary USB cable in your case.

E4ODnut wrote:Should Discovery be powered up with it's USB cable?

Yes, discovery has to be powered one way or another. The mini-USB (the one on top) is the simplest way to power discovery.

Discovery is plugged in via the mini-USB and is running. If I connect on com5 with the dev consol and in message central I type "t" > enter it returns a stream of "Command Queue: Sending [sec!1!t]"

If I connect with Hyper terminal it shows a data stream and will not respond when I type "t" > enter

You definitely should not be connecting to TTL with the dev console - dev console is for our own protocol, and the TTL is currently assigned to Tuner Studio protocol.

Can you please provide a screenshot of the data stream in Hyper terminal together with your hyper terminal settings?

just a reminder: you should have the latest firmware installed.

puff wrote:just a reminder: you should have the latest firmware installed.

Good point because pin assignment has changed recently

Here's my first attempt at screen shots.
http://i.imgur.com/j0ZE3gC.png
http://i.imgur.com/8PQ9ynQ.png

Can you please connect your microUSB cable, start the dev console and take a screenshot too?

So you would have three USB cables. If that's a problem you can disconnect the TTL for now. The point is to see what versions are you using?

What particular screen would you like me to try and capture for you?

I am interested in

How's this?
http://i.imgur.com/RKawK9D.png

@ is a genius - the problem is with


You need to upgrade to current version.

OK, I'll see if I can remember how to do that.

Latest screen shot. Is that what you want to see?
http://i.imgur.com/uz8i4Cz.png

Yes I am expecting this to make things better. Please disconnect the dev console, disconnect the microUSB and hit 't' in the TTL HyperDesktop session

Discovery up and running.
USB/TTL connected.
Hyper Terminal connected.
Com5
115200 Baud
8 data bits
Parity none
1 stop bit
flow control none
"t" returns "alive" ("enter" key not pressed)

Progress?

Progress!

We have confirmed that USB TTL is properly connected. You should now close HyperTerminal and create a new TunerStudio project using our rusefi.ini file and connect it using the TTL COM port