how to connect scale to putty and display scale in putty when pressing print on the scales?
I tried to connect the scales to putty and when the scales were pressed print the print results appeared on putty, is that possible?
Related
I want to log and display a stream of data arriving at a serial port in hex with timestamps and all non printable characters (particularly any XON XOFF characters). don't need to transmit anything on the Tx port, it is not connected.
Been trying to use stty to set port parameters and socat to log but having trouble.
using /dev/null socat just exits without any doing any thing, using -u and /dev/null as second address doesn't show or log anything, using a PTY as second address works for a while but then hangs - I guess the PTY fills up and block with nothing reading it.
Thanks for any help.
I have a HPLC pump connected via serial port to the computer. By using PuTTy I can send commands to it such as REMOTE to control it from PC (the display will change on the pump to show that it is indeed in remote mode. However when I use the same command from python the device does not respond.
import serial
pump = serial.Serial(port='COM2', baudrate=19200)
I have tried
pump.write('REMOTE\n'.encode())
and
pump.write(b'REMOTE\n')
and
pump.write(b'REMOTE')
I resolved the issue.
I needed to use
pump.write(b'REMOTE\r')
not
\n
I am trying to programmatically communicate with a device connected over a serial connection. When I send commands using PuTTY, I have no problems. But when I try to communicate using Plink, I get no response. What would cause that difference?
I connect to PuTTY through the command line using putty -serial com3 -sercfg 9600 and then send my commands from within the PuTTY window using Ctrl-J (to adjust for the line endings, I think? It works in any case).
And I connect to plink using plink -serial com3 -sercfg 9600, but then neither enter nor Ctrl-J or any combination seem to send my commands.
Just received my first ESP8266 wifi module with some excitement. However I've been unable to fully communicate with it. I have connected the module to my computer via a usb to serial cable and I'm power the module via a separate power supply (3.3v).
After powering the module up I receive the following information (via PuTTY or and Arduino serial monitor window):
[Vendor:www.ai-thinker.com Version:0.9.2.4]
ready
I have tried sending various AT commands e.g.
AT+RST
But I get no response. Using ctrl+m and ctrl+j in putty didn't help either.
Please see my youtube video if its helpful:
https://www.youtube.com/watch?v=RvasOuHuWDc
To get AT OK .
1.AT + PRESS ENTER + THEN CTRL +J WILL GIVE OK
2.Then Enter commands to execute
eg AT+GMR ->presss enter then ctrl+j
to get firmware
repeat step 1 for each command.
Make sure that you have putty or the Arduino serial console configured to send both a newline \n and a carriage return \r character. So AT+RST actually ends up being AT+RST\r\n. This took me a bit when I first received my ESP8266 modules. On the Arduino serial console this option is at the bottom of the window. I can see in your video you have it set to no line ending. Hopefully that does it for you.
I am successfully using GNU Screen as serial terminal to "talk" to my Altair 8800 clone (http://altairclone.com/) using serial line. The command I use is 'screen -istrip /dev/ttyUSB0'. Screen does the VT100 emulation, strips off MSB from output etc. - works perfect.
Now, I am also working on an emulator of Altair 8800 in Java and would like to use some terminal emulator to connect and talk to it, just like it was a real machine behind serial device. What is the best way to solve in in the Linux world? Is there a way to use Screen for that? Something tells me the solution is trivial, but I just don't know it yet ;) Thanks for any suggestions.
You emulator has to create a something called a "pseudoterminal". This is a pair of devices - the master side is used by the terminal emulator, writing bytes that are to be sent to the program on the computer and reading bytes that the computer sends. The slave side is on the other end: it is the device that the program being controlled by the pseudoterminal opens to get input and send output to. The slave device will appear in the filesystem with a name like "/dev/pts/9". See http://www.gnu.org/software/libc/manual/html_node/Pseudo_002dTerminals.html.
Also, to get the vt100 emulation in Linux make sure the terminfo package is installed and set TERM=vt100; export $TERM after opening your terminal window