RealTerm – это одна из тех утилит, пользоваться которыми смогут лишь настоящие профессионалы своего дела, обладающие исчерпывающими знаниями о TCP-терминалах и способах их эксплуатации. Да и за счет своей узкой направленности тем, кто ни разу не слышал о дебаггинге, настройке терминалов и всем, что с ними связано, смысла скачивать данное ПО попросту нет.
О функционале
Основным направлением применения функционала RealTerm является работа с контроллерами, а вернее с теми данными, которые они отправляют клиентам (другим устройствам) и получают от них. Это необходимо для отладки и настройки терминалов, но в большинстве случаев все же для управления ними. Использование подобных решений может существенно автоматизировать работу на предприятии любого типа.
Терминалы также используют в процессе дебаггинга данных для устранения всех возникших ошибок при передаче. Это в разы повышает стабильность работы группы устройств и снижает риск внезапных вылетов и остановки работы систем. Программа отлично “дружит” как с бинарными, так и со всеми остальными потоками данных, что уже само по себе делает ее универсальной и расширяет области применения основного инструментария. Стоит отметить тот факт, что в процессе создания RealTerm разработчики не предусмотрели возможность использования модемов DialUp и BBS.
Об интерфейсе
Графическая оболочка этого программного обеспечения оставляет двоякое ощущение. С одной стороны, она будет интуитивной для тех, кто уже ранее работал с контроллерами и сетевыми терминалами, но с другой – ни одну из имеющихся в программе функций новичок в этой сфере не поймет. А посему начинающим пользователям придется довольно долго и упорно разбираться в функционале, чтобы вскоре ориентироваться хотя бы в базовом инструментарии.
RealTerm has been created mostly to represent a better alternative to the ubiquitous HyperTerminal application, especially when it comes to debugging microcontrollers. It allows capturing, controlling and debugging binary data as well as other types of data streams.
The most impressive part of this application for me is the fact that it can emulate almost any kind of terminal used for serial communication. It’s a very complex, feature-rich and comprehensive application that offers a huge number of settings, options and functions. Anyway, it doesn’t support only physical serial communication ports but also Telnet, TCP, and other protocols.
I also like a lot its handy right click context menu and the fact that the popup hints (the mouse-over tooltips) provide clear and comprehensive explanations. Furthermore, RealTerm comes with a directory containing example files that allow seeing how RealTerm works and how it can be used in conjunction with various types of scripts and other programs.
In an end note, RealTerm is one of the most comprehensive and effective terminal applications for Windows serial communications. Simply put, the fact that it is also open-source makes me recommend it with all my heart.
Perform network administration operations by capturing data streams and processing them in the special environment for optional debugging, analysis or creation of logs. ASCII, Ansi, Hex, binary, Int8, ASCII+Hex and other types of visualization are available.
Realterm 3.0.1.45 может быть загружена с нашего сайта бесплатно. Эта бесплатная программа была разработана Simon Bridger. ПО относится к категории Разработчикам.
Realterm.exe — распространенное имя файла для установщика этого ПО. Самые популярные версии Realterm это 3.0 и 2.0. Это ПО для ПК может быть установлена на 32-бит Windows XP/Vista/7/8/10.
Realterm is a terminal program specially designed for capturing, controlling and debugging binary and other difficult data streams.
— Serial Ports, USB Serial and TCP/IP & Telnet — I2C, SPI, 1Wire chip control via BL233 / I2C2PC — Binary viewed as hex, 8 bit, 16 bit, little/big ndian, signed, unsigned, float, special fonts — Fullscreen, MiniTerminal, Screen Scaling, Global Hotkeys — colorised: rx and tx data are different colors — ansi/VT100 terminal or plain text or binary modes — protocol analyser / «portspying» mode — fixed frame sizes/line lengths — sync patterns with masks and xors, and display only match data — Timestamps on pattern match or newlines — data inversion & bit mask — full remote control through activeX/COM — extensive command-line control for batch files and INI files
Мы предлагаем вам также рассмотреть другие программы, такие как Fiddler, которые часто используются вместе с Realterm.
Realterm is an engineers terminal program specially designed for capturing, controlling and debugging binary and other difficult data streams. It is the best tool for debugging comms.
§ Contents
V3 Beta version under development (3.0.0.30). See Latest News
Help & Hints:
Press F1 to bring up the help screen. Amongst other things you get a list of the actual commandline parameters that version supports.
Tool Tips are the primary source of help and explanation when using Realterm. Take the time to move the mouse over every control, and read the hints that pop up. If you doubleclick on the status bar at the bottom it will toggle to a longer hint string.
The Popup hints are also displayed (and don’t timeout) on the status bar. Double click the status bar to show them the full screen width.
ENTER send CR, +ENTER sends LF, +ENTER sends CRLF
§ Installing Realterm
If you are using an FTDI usb adaptor you need to install the FTDI driver first
To use Spy mode, or PicProg functions, install the separate drivers required.
Read all the Tool Tips carefully. Check the examples directory for programming examples.
§ Display Formatting
Reaterm displays data in different ways to suit. «Display As» selects the display emulator:
This gives a traditional terminal with extensive control codes that navigate the cursor around and clear selected parts of the screen. If you need to format the display use this emulation, not ASCII. [The ASCII emulator displays all 256 characters, and so will not even act on backspace or formfeed. It does not properly act on CR and LF, so as to display them best ]
§ Terminal Colors
Colors can be set from the commandline (V2.0.0.64+), or on the Misc tab. Colors are set by a string of color chars below. The sequence is: Kbd,Port,SendStr,SpyTX,SpyRX,Background Default is ‘RYLRYK’
The Tray Icon and main icon changes to show a red dot when it is capturing. The dot rotates as data bytes are actually being received. The dot is Green for normal chars, Red when capturing,
Yellow when Data Triggers or Binary Sync Matches occur.
Small tablets, high resolutions screens etc, can make the default screen difficult to use. There are several ways to change the size of Realterm
Scaling:
The whole UI can be scaled to make all text and controls bigger. See Misc
FullScreen Mode:
For small tablets, the app can be run in fullscreen mode. See Misc tab, and right click menu, or command line WINDOWSTATE param. You can increase the COLS to fill the screen by double-clicking COLS. Use the Hotkey to toggle screen mode
MiniTerminal:
Sets up a small Realterm, hides the controls and sets StayOnTop. Both Rows and Cols are changed when you drag resize the MiniTerminal. Use the Hotkey to toggle screen mode
§ Hiding Controls / FullTerminal
Hide Controls either from the popup menu, or the commandline or activeX interfaces. This is ideal for making a shortcut that sets up Realterm for your field staff or users, then hides all the controls, to make it less confusing. Use the Hotkey to toggle screen mode
Show / Hiding Everything
Visibleoption that will completely hide Realterm. Unlike minimising, it disappears from the taskbar. Only the Tray Icon is left.
If you want it to be totally hidden the activeX interface lets you hide even the Tray Icon. This is ideal if (like us) you have 16 Realterms running in the background at once, all the time.
mechanism uses the window name, and this disappears when the window is hidden.
Setting Rows and Columns
Rows sets the min number of rows.
Drag resizing will increase the actual number of rows (but not change the setting).
Cols are not changed by dragging, except in MiniTerminal mode. Double Click in COLS will set number of cols to fill the screen width. The status bar will show the actual Rows & Cols during resizing.
Bytesand check «Single». Realterm tries to set the actual number of Cols, to be multiples of Data Frame sizes.
You can set the display rows from the commandline to launch it the size you want.
The example shown will be a 80×16 window.
§ Frame Sync
Binary data is arranged in frames. These frames are either
A count of sync matches is shown on the Binary Sync Chars panel. When a sync match occurs, the tray icon square changes to yellow for a few seconds.
Fixed size frames are self evident. You will notice that theterminal resizes to always have a whole number of frames across, unless «Single» is checked.
Unfortunately frames will randomly begin somewhere on the line.GULP swallows a character each time it is pressed. Press it until the frames correctly start at the beginning of a line.
Delimited frames start a new line when they detect the sync sequence. A sync sequence can be any number of bytes long
Here sync is detected when 2 bytes match 0xA55A, or moreaccurately, when 0xA55A XOR 0x0000 AND 0xFFFF > 0. [«SyncIs»should be set to «Number»]. If you are syncing off ASCIIchars, then select «Synch is: ASCII» and put the chars in the top editbox.
You can have as many bytes as you want in the sync word.
§ Baud Rates & Ports
Baudrates depend on the exact hardware port. Realterm accepts anything. Some ports complain about invalid baud rates, others just ignore them, some coerce to the nearest rate.
Most PC ports accept non-standard values that the chips divider is capable of generating.
Realterm can connect to both SERIAL ports (real uarts, as well as USB, and network virtual uarts) or TCP/Telnet ports.
server:port eg «server:telnet» or «server:9876»
USB Virtual Comports
USB serial ports appear at some port number. Look under «my computer->properties->hardware->ports» to find where they are. Unfortunately the same device will often appear at different comport numbers when it is on different USB hub ports.
The currently present devices and associated ports are also listed in the registry at HKLM\HARDWARE\DEVICEMAP\SERIALCOMM. You can use these device names directly in the port selection eg «\VCP0» or «\Serial0»
For example when you plug in an I2C2PC adaptor it will normally appear as \VCP0, regardless of the comport# that it is assigned, or which usb hub port it is connected to.
On Win9X there don’t seem to be any special names for devices, and this won’t help you.
§ Scanning for Ports, Startup Delay, and Bluetooth
Version 2.0.0.70 onwards
Realterm now uses the registry to find ports rather than trying to open them all. Note if you get a registry key error when starting, this is because you do not have any serial ports installed. Install one.
Exhaustive Search by Opening
Versions Before 2.0.0.70 (and Win 9X)
Realterm scans by trying to open every comport number.
Realterm will scan for ports at startup if an explicit port is not given on the commandline. This can cause long delays where Bluetooth is running. The SCANPORTS commandline option sets the highest port that will be tried.When starting normally, Realterm will try to open the first existent port that it finds. (V2.0.0.57+)
When started as an ActiveX automation server, it does not open the port until explicitly requested.
§ What Baud Rates does Realterm support?
Realterm will pass any requested baud rate through to Windows. Many other applications have a list of baud rates, but Realterm does not, it will request anything.
Microsoft says this : «For all other cases, as long as the requested baud rate is within 1 percent of the nearest baud rate that can be found with an integer divisor, the baud rate request will succeed»
The most basic PC uart has a maximum baud rate of 115,200. Any frequency of 115,200 / N, can usually be requested. More modern PC’s and laptops, usually have a higher maximum baud rate of 230,400, or 460,800, or 921,600. Actual serial ports usually have a maxium that is a multiple of 115,200. Once you have found the maximum, any baud rate of /N should work.
USB-Serial adaptors usually have higher clock rates, and support a wider range of different rates. FTDI’s usb-serial adaptors have high maximum rates, and many possible rates. See FTDI info:
If the actual PC baud rate is within 3% of your actual device baud rate, it will usually work OK. If you are using RS232 connections, modern drivers will usually work at 230kbd for short cable lengths, but are less likely to work at 460kbd, or 921kbd
Baud Rate Multiplier and 16C95X Uarts
The16C95X family of advanced uarts are able to support very high baud rates. They have 64byte FIFO’s, which is a give away that they are in your serial card. When trying to get very high baud rates, there is an option in the hardware configuration of the uart to enable the «baud rate multiplier». This will result in higher than requested baud rates. ie the actual baud rate = requested rate * multiplier
§ RS485
For all versions of Windows > NT AsyncPro handles the toggling of RTS via the RTS_CONTROL_TOGGLE flag and the Windows SetCommState function. I have found other people complaining about a «significant lag» when using this flag to control RS485 devices from non-ASyncPro programs. This seems to be a problem with Windows in general and not AsyncPro in particular.
«I tested the RTS_CONTROL_TOGGLE mode with RS485 devices, and I noticed that Windows has a significant delay between the end of transmission and the control of the RTS line, so this mode does not work properly with a RS485 equipment that replies «too fast» for Windows, due to a conflict between the RS422 amplifiers simultaneously active on the RS485 line. Your best bet might be to get an actual RS485 card for your windows system that handles the RTS toggle in hardware.
§ TCP/IP: Telnet and Raw modes: Missing FF’s
The TCP connections default to using Telnet protocol. However if you are connecting to a socket with raw data, you might notice that some characters (eg 0xFF) are missing or doubled up. You need to change between Telnet and Raw modes. This is not a bug!
The telnet connection lets two copies of Realterm talk to each other on the same machine. Just set the first to «server:telnet» and the second to «127.0.0.1:telnet». This is very useful for testing and experimentation.
§ Fonts
By defualt Realterm should be using the Hex fonts (below). The terminal can be changed from Terminal Font button. Only fixed pitch fonts show, and only some of these seem to be satisfactory. Lucidas Console and Fixedsys are good starts. Commandline options FONTNAME and FONTSIZE allow you to make a permanent change.
e.g. realterm.exe FONTNAME=»lucida console» fontsize=11
§ Hex Font
Our Hex fonts are included. The Installer should install the fonts for you automatically. You can also go to the windows font installer in Control Panel to install it.
The hex font contains all 8 bit values. The non-ascii values
§ Pins & Status
Handshake Pins and comms status can be monitored.
Handshake outputs can be controlled directly (and from the command-line, and via activeX)
The error cause is displayed when you hover the mouse over the error light.
Pin states can be set manually. Set means data flow is enabled. Note that if CTS/RTS or DTR/DSR handshaking is enabled, then you cannot control that pin from the buttons.
§ Capture
This provides a very easy way to (say) collect serial data, and graph it live using Matlab.
It can either capture «direct» or via the terminal window. When you use DIRECT capture, the terminal window is turned off, and the echo port operation will cease. This means less processor load, screen draws etc. This is best for embedded type uses. (V3.0.0.28+ Display checkbox enables terminal in Direct mode to check data)
If you want to capture what you are seeing in the terminal, don’t use Direct Capture.
Capture As HEX
Sometimes it is easier to look at binary data when it is saved as hex. So each received char is converted to two hex chars and saved to file. This option only works with Direct Capture. For best speed don’t do this: capture normally, and use a binary/hex editor to examine the file
Restarting, AutoName, and Long Captures
Some users leave Realterm capturing for long periods. Files can grow very large, or be unwieldy to find data in.
Restart and AutoName (V3.0.0.28+), lets Realterm begin a new file, after N secs or bytes, with the DateTime appended to the filename. Previously this was done via a batch file.
eg to capture temperature data, with a new data file automatically created every day, and the datetime suffix in filename.
(V3.0.0.24+) Timestamps can be shown in the terminal, or added into capture file.
§ Terminal Display Mode Timestamps
Custom timestamp format can be set by right-click on Timestamp checkbox. (V3.0.0.30+)
Capture File Timestamps
Timestamping is very useful for data logging, or where you want to know when an occaisional string arrived. This is most useful for comma separated (CSV) type text data. Timestamp is triggered by CR or LF.
Unix timestamps are the number of seconds from 1/1/1970.
Matlab timestamps are floating point days since 0 Jan 0. Matlab timestamps are given to the PC’s clock resolution, this should be 10ms for NT and later and 55ms for Win98 and earlier. Using Matlab timestamps should give you finer resolution than 1 second.
UnixHex is provided for convenience when all the data being captured is in hex. In this case the whole file including timestamps can be converted to decimal by the HEXCSV2DEC utility that is bundled with Realterm.
System Format (labelled YMDHS before v3.0.0.30) timestamps display the time using the system locale formatting function. This means that it varies with your preferences and place to place (month and day will swap with country). (It also has some slightly odd behavious like not including the HMS value what it is 00:00:00)
§ Custom Timestamp Format
Note that Unix, Matlab, and format yymmddhhnnss will sort (in data analysis). System and other customary date formats do not sort.
Timestamping also slows down file capture somewhat, so it is probably not ideal for very fast and dense data streams.
§ Sending Char Sequences
Read the popup Hints carefully. They give lots of information especially in the Send tab!
Often you want to send special chars strings or strings repeatedly, or send them quickly.
Both ascii and binary strings can be sent. Ascii strings include python escape sequences eg \n for LF. See table below. Literal disables the escape sequences and send just the string. Sent chars aren’t echoed to the terminal.
(V2) If half-duplex is set, then sent strings will be shown on the terminal. This also applies to strings/chars sent via the ActiveX interface.
When Sending ASCII, you can optionally end the line with CR and/or LF. You can also strip spaces from sent data. This is useful for the I2CChip adaptor. While it ignores spaces, they take time, and buffer space, and won’t be used in the final application. (but they make it much easier to read!)
Python Escape sequences:
Escape Sequence
Meaning
\\
Backslash ( \ )
\’
Single quote ( ‘ )
\»
Double quote ( » )
\a
ASCII Bell (BEL)
\b
ASCII Backspace (BS)
\f
ASCII Formfeed (FF)
\n
ASCII Linefeed (LF)
\r
ASCII Carriage Return (CR)
\t
ASCII Horizontal Tab (TAB)
\v
ASCII Vertical Tab (VT)
\ ooo
ASCII character with octal value ooo
\x hh.
ASCII character with hex value hh.
Hotkeys
(V3.0.0.25+) Local hotkeys work throughout now. Look at the popup menu to see what local Hotkeys exist.
From the ActiveX interface you can prepopulate the Send dropdowns with strings by using the “AddCannedString” function.
The String1, String2 commandline options load strings into the dropdowns. If you want to preload lots of strings, or long strings, then use an INIFILE. (3.0.0.24+) Previous versions used SendStr, this is now used to send strings.
Sending ASCII with special/non-printable values
When you press «SendASCII » any valid backslash sequences are converted to special values in the style of Python.
If Literal is checked, then the string is sent raw. Note that the special chars must be lower case
hex value. Also accepts \0xXX
Octal value like Python /C. 1-3 digits can be used. (Before V3.0.0.30, was decimal, NOT octal like python)
Sending Non-printable binary chars
You can do this in several ways.
CRC and Checksum
You can add a variety of CRC’s and Checksums to the end of the send string. See the drop down list.
Modbus binary packets end with a 16bit CRC. This can be appended to each string sent.
§ Sending Files
Padding File Dump with Delays
Two delay settings are provided to add delays after each char, and at the end of each line. (EOL is denoted by CR at present). This affects file dump, but not sending char sequences above.
Sending Repeatedly
These are particularly useful from the commandline for data logging, when combined with capture.
For example you can make a simple, one line file that commands a multimeter to read a voltage. Set repeats to 0, so it will loop for ever, and delay to 1000ms, and Capture. Now the data will be read to file every 1 second.
§ Data Logging
Using Capture and SendFile from the commandline, you can log data and control intruments directly from the commandline, without extra software.
This will send «commands.txt» endlessly, with a 10sec pause between sends, and capture the replies to «results.txt». This is all you need to do to turn (say) and RS232 multimeter into a datalogger.
(V2.0.0.46) The TIMESTAMP option can be used to prepend a timestamp to each line. This is most useful for CSV type text data. See capture section
§ I2C & SPI & 1-Wire Bus
I2C, SPI, 1-Wire and other Serial buses can be read using the I2CChip products «I2C2PC» and the «BL233B» IC. Realterm cannot read I2C without these external devices. It cannot use printer ports, the PC’s SMBUS interface etc.
The provides a USB/RS232 interface to 3 I2C buses. Realterm is an easy way to use it. Using the ActiveX interface you can easily send strings from excel or other apps. Using the Echo port provides a way to make hardware devices that can be controlled over the internet.
Common commands you want to send to play with the adaptor are provided by the controls. Using this you can quickly try out an I2C adaptor or 1-wire device.
Control various special I2C chips: BL301, PCA9544, PCA9545,MAX127,
The main I2C tab has controls to select one of the serial buses.
Refer to the datasheet for the BL233B chip used, where its commands are detailed.
Note that you can use it with SPI, Dallas 1-wire, and other serial IC’s, as well as I2C
The I2C-2 tab has controls to support a number of common IC’s. The MAX127 12Bit Precision ADC and PCA9545 Bus Switch/multiplexor are available as standard modules fromI2CChip
The tab has support for non-I2C devices:
§ Echo Port: Redirect Ports across Network
The main port can be passed through or echoed to the Echo Port. This is partcularly useful when the echoport is a TCP port. This allows a real serial port to be aliased across the network. (the echo port can be a real comm port too)
Lets say the remote (unattended) machine (192.168.0.99) has a datalogger connected to COM1. It runs Realterm at startup with a command line like this:
ie realterm connects to the datalogger on COM1 at 9600 bd, and presents a telnet server on port 9876 (or any other suitable number).
On the local (attended) machine run a copy of Realterm like this:
This makes a telnet connection to the remote machine. Now you can sit at your desk, and control and monitor the remote serial device.
Note that as Realterm has a full ActiveX interface, you can use Windows remote DCOM to start,stop and control the remote Realterm, as well as the local copy.
When there is a connection, chars are echoed. When the connection is broken, or the buffers are full for some reason, it simply stops attempting to echo chars. When the connection is broken, the server end just waits for another connection. At the client end, the port need to be manully restarted.
If you are using the activeX interface you can check the open property to see if the link is up, and use it to re-establish a dropped link.
The Monitor checkbox lets the terminal window display both sides of the conversation (ie both the data received through the ain port, and the echo port)
Signalling Winsock Connection state to Comport
When a telnet/winsock connection is being echoed to a physical comport, we can use one of the comports handshake output lines (DTR,RTS) to signal a remote system whether winsock is connected. You must make sure that this doesn’t interfere with the operation of the handshake lines. (ie use DTR for signalling if you are using RTS/CTS handshaking for flow control)
Com0Com, Com2TCP: Virtual Comports
§ Monitor RX and TX data: Protocol Analyser
Realterm has two ways to monitor serial communications, and let you see the RXD and TXD data interleaved in the same terminal window:
Spy mode allows you to monitor the communications between a program running on your PC and the com device, by installing a device driver to intercept the port messages, Spy mode must be activated before opening the comport, and the comport must be closed before spy mode can be released. Spy button is on the port tab.
Note that you cannot currently capture the spy mode. However you can copy and paste from the terminal window.
Monitor Mode
Monitor mode is useful to monitor communications between external devices by connecting to the RS232 cable.
The Echo port can be used to give you a second receiver. The data is put into the terminal screen, in a different color. Now you can see both sides of the conversation.
The interleaving on screen, only shows you when the data arrived at Realterms handlers. The indeterminate delays in Windows mean that you can’t rely on the sequence being exactly as it happened. Obviously with slow data, or decent gaps between send and receive, it will work better than with very fast data streams.
Special Monitor Cable
You need a special adaptor with 2 plugs for the PC’s 2 serial ports. Only connect RXD and GND on those plugs at the PC end.
§ Monitor and Echoing
You can select both Echo and Monitor. Now Realterm echos as normal, but the terminal window displays the data from both directions.
§ Command Line Parameters
The command line is morphing into a general purpose Command system. You can run INIFILEs, send commands to running isntances with first, and execute commands from ActiveX/COM using DoCommands. Future versions will allow command strings and hotkeys.
Realterm doesn’t save its settings. Instead it is set up from either the command line, for basic setups, or using its extensive ActiveX interface. It is also possible to send commands to a running instance of Realterm from the commandline. (fix 3.0.0.25+)
These examples show the command-line params you can use. Generally they set the corresponding widgets. For radiobuttons and checkboxes, a number selects the state. For booleans (eg visible) use either 1 or 0. (n.b. No «/» or «-» before parameters). Double-quotes enclose values with spaces or other control characters eg \. Double quotes inside strings are possible (V3.0.0.30+) eg send1=»abc=»»def»»»
For complicated settings, a file of parameters can be loaded using INIFILE, and settings generated and saved from the «INI File» button on the Misc tab. (V3.0.0.18+). When debugging problems, the View Params button will show what Realterm actually received on its commandline.
§ INIFile Dialog:
Example Command Lines
§ Table of Commandline Parameters
Set the baud rate. Non standard baudrates are fine
Sets the port, exits if port does not exist or can’t open
Sets DataBits,Parity,StopBits. eg DATA=7E1 DataBits is 8-5, Parity is None,Even,Odd,Mark,Space, StopBits 1-2
terminal frame size. Interacts with COLS. Use one or other
name of the capture file to use
Length of capture in bytes (either CAPCOUNT or CAPSECS)
Time of capture in SECS. (-ve values makes it quit as soon as idle or until timeout).
If using SENDQUIT, then waits this time after send finishes, before stopping capture. See SENDQUIT. (V3.0.0.17+)
Capture starts immediately. Stops at count OR secs. Can use CAPTURE=filename
Capture=0 is off; 1 is ON; 2 is APPEND; 3 is RESTART
§ CAPAUTONAME
0/1/2
Append DateTime to filenames. Used with RESTART for logging (V3.0.0.28+)
§ CAPPROCESS
0/
Set Capture Post-Processing batch file (V3.0.0.28+)
§ CAPQUIT, CQ
Capture (as above), but program quits when capture ends. If you manually stop capture, then Autoquit is cancelled. Can use CAPQUIT=filename
Capture as Hex ie turns all chars to a 2 char hex value.
Capture Direct checkbox
Set timestamp delimiter eg TSDELIMITER=%
During capture, Prepends a timestamp to each line. Only works in text files with EOL character. A custom format string can be used (v3.0.0.30+)
starts hidden, only tray-icon is visible. 0=Hidden,1=Visible
sets the display format (ascii, hex,int etc). eg DISPLAY=5
Put before other display params such as COLS
set big-endian checkbox
Sets hardware flow control mode. FLOW=X to enable XON/XOFF mode or Flow=N+8 for RX-XOn, +4 for TX XON or use flow twice FLOW=1 FLOW=X. Xon/off: +8=TX, +4=RX. eg FLOW=10 is RTS/CTS+RX-Xon/off. Also you can use R or RTSCTS or D or DTSDSR
Starts with port closed (default is open)
Selects the opening tabsheet by name or tab number (case in-sensitive)
Sets the echo port, and enables echoing
Set the baud rate for echo port.
Sets Echoport DataBits,Parity,StopBits. (not working properly yet)
Sets window caption (can’t accept spaces, use underscores). See caution below if using with FIRST
Hints: Parameters that put a string into a drop down (eg SendStr, SendNum, HexCSV), can be called multiple times to push more than a single value into the drop down.
eg realterm.exe hexcsv=uv hexcsv=st hexcsv=ab
If you are doing batch file automation, you will often want Realterm to do something (e.g. send a file), then quit.
Realterm has SENDQUIT, CAPQUIT, and PORTQUIT commands.
CAPQUIT can capture either CAPSECS seconds of data, or CAPCOUNT characters, then quit.
SENDQUIT sends files then quit. When capturing Realterm will continue the capture after the file send for up to 1 second if chars are still coming in.
So below, the capture will remain open, until the flow stops, (for a max of 5 seconds open):
And here capture will remain open for 20 seconds regardless:
When you are calling Realterm within a batch file, you will normally want the batch file to pause until Realterm exits. You must use the batch command START with the /WAIT parameter for this to happen.
When you look at the examples, you will see that I tend to set environment variables for the names of the files, ports, and Realterm itself. So it looks more like this.
PORTQUIT: Waiting for USB Ports
When testing USB devices via batch file, there are two problems that arise.
PORTQUIT quits the program with an error code, if the port is not able to be opened. This allows your batch file to retry until the port is open or timeout. See examples
Exit Codes and Errors
In batch files you may need to check for error exits (using errorlevel)
§ Controlling a Running Instance
(V3.0.0.24+). The first instance must be started with FIRST=1 now [security improvement].
If the sending instance shows an error message that it is blocked the try starting the first instance with realterm.exe first=2. This unblocks the UIPI protection.(V3.0.0.24+)
Realterm: Serial Terminal
Realterm: Serial Terminal
when it is capturing. The dot rotates as data bytes are actually being received. The dot is Green for normal chars, Red when capturing,
Pin states can be set manually. Set means data flow is enabled. Note that if CTS/RTS or DTR/DSR handshaking is enabled, then you cannot control that pin from the buttons.
