A terminal emulator to me, is just that, an emulation of a terminal, such as a VT100 or a Lear Sigler. This is where the communications failure occurs.
Since every command ends with a CR/LF pair, it naturally displays on alternate lines. The existing app sends all comms to a telnet app, along with ANSI controls to set the bold feature for one direction and not for the other. Heck, maybe I'm better off developing my own.
So the need for a way to directly interact with the com ports. I'm really trying to test the comms interface, which will have speed issues unless I can optimize the interface. In this case, I have a dumb device (that I'm designing) to receive commands, and provide replies. There are a few USB hubs that let you control power to the USB ports, but very few. But once I found the right tool, it worked well, other than not being able to reset the target since the com port was USB. The trick in that case was handling all the details of control characters, as to which were intercepted by whom. Trying to find a terminal emulator for Linux is nearly impossible, because they consider the command line to be a terminal emulator! lol I don't recall the setup I ended up with, but I had to run something on the PC to log into the rPi, (maybe Putty), then a different program on the rPi to connect to the target via the comm port. I had a different setup, where I was using something like SSH to log into an rPi which was connected via a serial port to an embedded target. One problem I have is that the term "terminal" seems to also be used for command line interfaces. Otherwise, it is a simple terminal application.
I just want it to show the transmitted and received data in different colors, or brightness or backgrounds. I need a terminal interface to a COM port.
0 kommentar(er)
