|
|
|
Contents
|
|
Read the popup hints carefully. They give a lot of information
Right mouse context menu has some extra functions
Popup Hints (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 F1 Key will bring up an about dialog with an up-to-date list of commandline parameters for Realterm.
DownloadDownload and run the installer
Active X should be registered automatically.
Special TermHex Fonts should be installed automatically. If you need to, install the font file TERM_HEX.FON from control panel -> fonts. This font is also useful in editors etc.
Make shortcuts with all the configurations you need. (see commandline options) eg "Port=2 baud=9600 flow=2"
Monitor
New File Releases to be notified of updates.
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.
Project Page on is the place to
find all up-to-date information, make bug reports etc.
Help is Here
|
|
Reaterm displays data in meaningful forms
|
Right mouse click on the main window or on the Tray Icon 
will bring up the popup menu. You can doubleclick the tray icon to
hide/show Realterm (ie make it disappear from the taskbar)
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 occur.
If you don't want the control panel visible, or you want a bigger screen, then you can 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.
The popup menu (and ActiveX and Commandline) have a Show option that will completely hide Realterm. Unlike minimising, it disappears from the taskbar. Only the Tray Icon is left.
This is ideal where Realterm is being used by another program to work in the background, eg capturing data to a file, echoing a port to a remote machine.
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.
|
|
To force the number of columns across the terminal window, set Bytes and check "Single" You can set the display rows from the commandline to launch it the size you want. The example shown will be a 40x16 window. |
Binary data is arranged in frames. These frames are either
Fixed size N byte frames
variable length, delimited by a trailing byte sequence
(of course Text is arranged as lines ending with LF or CR)
|
|
Fixed size frames are self evident. You will notice that the terminal 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 more accurately, when 0xA55A XOR 0x0000 AND 0xFFFF > 0. ["SyncIs" should be set to "Number"]. If you are syncing off ASCII chars, 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. The XOR term allows you to invert some or all data bits. ($00 is normal $FF is inverted). If you don't need the XOR and AND fields, just leave them empty to get the defaults. The AND term lets you ignore some of the bits. For example you could use this to use bit 7 as a sync bit, by setting the AND term to $80 $80. (Note hex numbers are preceded by $) Errata: Versions <1.99.31 the XOR and AND fields are mislabelled (swapped). The middle field is AND, the bottom is XOR |
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.
Windows Serial Port# eg "2"
ip_address:port eg 192.168.20.1:23
port can be a number or service name eg "telnet"
server:port eg "server:telnet" or "server:9876"
USB serial ports appear at some port number. Look under "my computer->properties->hardware->ports" to find where they are.
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 restricts scanning.
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.
Enables hardware direction control by the RTS line.
Note that some specialist serial cards and USB-Serial adaptors can handle this in hardware, and don't require this to be set. They may also get around the limitations that windows imposes on this, as described by Stephen Boyd below:
“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. Here is a quote from a user in a different forum:
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.”
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.
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 <32 are shown as either HEX or CONTROL chars, depending on the font you select. (There are 3 different fonts in the .FNT file)
|
|
|
|
This is very useful for seeing control codes, invalid hidden codes and errors, in serial comms. It's equally useful in a programmers editor.
(Note that you won't see them in ANSI mode, as the control codes will be processed)
You can now get just the fonts from the downloads page. If you can convert these fonts for use with Linux or another OS, please do! If you would like to add a larger size to the font, please do.
|
|
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.
Incoming data can be captured to file. The capture can automatically stop after a certain time or number of chars. Realterm can be hidden, and capture controlled from the tray icon, popupmenu, and automation interfaces. Combine capture with filesend to make simple datalogging applications
Capture can be fully controlled through the ActiveX interface. Well behaved applications can read and process the files whilst RealTerm is writing them. (beware: Microsoft apps often try to lock the file, eg excel, notepad, word.)
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.
If you want to capture what you are seeing in the terminal, don't use Direct Capture.
RealTerm can also write LOG and TRACE files to help debugging difficult serial problems. For more information see the Async documentation.
Char Count and CPS (chars per sec) are displayed 
during capture.
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
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, normally 15ms.
Timestamping also slows down file capture somewhat, so it is probably not ideal for very fast and dense data streams.
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. 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!)
From the ActiveX interface you can prepopulate the Send dropdowns with strings by using the “AddCannedString” function
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
|
\n |
LF (0x0A) |
|
\r |
CR |
|
\a |
BEL |
|
\b |
BS |
|
\f |
FF |
|
\v |
VT |
|
\t |
HT |
|
\xXX |
hex value |
|
\NNN |
decimal (NOT octal like python) |
|
\\ |
\ (backslash) |
You can do this in several ways.
In the terminal window you can send most control chars by holding the control key down eg ctrl+m = CR. (You cannot send 0x00 or 0x03 this way)
You can send special chars NUL (0x00) and ^C (0x03) using the buttons
You can enter a string of hex or decimal numbers in the Send comboboxes eg "51 0x31 $32" and press "Send Numbers". (Note that they must be separated by spaces)
To send a series of binary numbers use the unmarked edit box. Type in numeric values here, separated by spaces. When you hit SPACE, each char will be sent. Chars can be decimal, or hex eg "13" "$1A" or "0x1A". Just keep typing out numbers.
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.
You can dump a file directly to the port. This has no "protocol" and just sends everything. (versions before 1.14 swallowed ^Z / 0x1A).
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.
You can set the number of repeats, and the delay after sending.
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.
Using Capture and SendFile from the commandline, you can log data and control intruments directly from the commandline, without extra software.
realterm.exe senddly=10000 sendrep=0 sendfile=commands.txt capture=results.txt
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
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:
realterm -port=1 -baud=9600 -echo=server:9876 -caption=Mirror_Multimeter_To_Internet
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:
realterm -port=192.168.0.99:9876
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)
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)
Sometimes you just want to watch or spy on a conversation on a serial cable. Normally the terminal screen only shows you the RXD half of the conversation. You could just run a second copy of Realterm, but wouldn't it be nice to see the RXD and TXD data interleaved in the same terminal window?
The Echo port can be used to give you a second reciever. 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.
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.
You can select both Echo and Monitor. Now Realterm echos as normal, but the terminal window displays the data from both directions.
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.
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)
Errata V2.0.0.60 and below: Quoted strings are not working properly, and may not work if you need spaces in parameters and filenames
Check the Help (F1) to see a list of the commandline parameters which has been automatically generated. It may be more complete than the one below...
realterm.exe baud=9600 port=1 flow=2 capfile=c:\temp\junk.dat visible=0 display=5 bigend=1 capcount=9876 framesize=7
realterm.exe port=server:telnet
realterm.exe port=127.0.0.1:21
realterm.exe RTS=1 DTR=0
realterm.exe tab=Send
realterm.exe echo=server:9876
realterm.exe capfile=junk.txt capsecs=10 capture
realterm.exe sendfile=junk.txt chardly=3 linedly=50
realterm.exe baud=1200 data=7E1
realterm.exe capture=in.txt sendrep=10 senddly=10000 sendquit=out.txt
|
BAUD |
# |
Set the baud rate. Non standard baudrates are fine |
|
PORT |
|
sets the port |
|
DATA |
7E1 |
Sets DataBits,Parity,StopBits. eg DATA=7E1 DataBits is 8-5, Parity is None,Even,Odd,Mark,Space, StopBits 1-2 |
|
FRAMESIZE |
|
terminal frame size |
|
CAPFILE |
|
name of the capture file to use |
|
CAPCOUNT |
|
Length of capture in bytes (either CAPCOUNT or CAPSECS) |
|
CAPSECS |
|
Time of capture in SECS |
|
CAPTURE |
0/1/2 filename |
Capture starts immediately. Stops at count OR secs. Can use CAPTURE=filename Capture=0 is off; Capture=1 is ON; Capture=2 is APPEND |
|
CAPQUIT |
|
Capture (as above), but program quits when capture ends. If you manually stop capture, then Autoquit is cancelled. Can use CAPQUIT=filename |
|
CAPHEX |
|
Capture as Hex ie turns all chars to a 2 char hex value. |
|
TIMESTAMP |
0-4 |
During capture, Prepends a timestamp to each line. |
|
VISIBLE |
0/1 |
starts hidden, only tray-icon is visible |
|
DISPLAY |
# |
sets the display format (ascii, hex,int etc). eg DISPLAY=5 |
|
BIGEND |
|
set big-endian checkbox |
|
FLOW |
0,1,2,3 |
sets hardware flow control mode |
|
RTS |
1/0 |
sets RTS pin |
|
DTR |
1/0 |
sets DTR pin |
|
CLOSED |
1/0 |
Starts with port closed (default is open) |
|
TAB |
|
Selects the opening tabsheet by name |
|
ECHO |
|
Sets the echo port, and enables echoing |
|
EBAUD |
n |
Set the baud rate for echo port. |
|
EDATA |
7E1 |
Sets Echoport DataBits,Parity,StopBits. (not working properly yet) |
|
HALF |
|
Sets HALF Duplex |
|
CAPTION |
|
Sets window caption (can't accept spaces, use underscores) |
|
SENDFILE |
|
Sends the file immediately. (capture started before sending starts) |
|
CONTROLS |
1/0 |
Hide Controls and expand terminal window to full screen |
|
MONITOR |
1/0 |
Monitor Echo port RX onto terminal |
|
CHARDLY |
# |
Sets delay (in ms) after each character when sending files and strings |
|
LINEDLY |
# |
Sets delay (in ms) after each line when sending files and strings |
|
ROWS |
# |
Set number of rows in terminal window. |
|
SENDDLY |
# |
set delay (in ms) after file is sent, until next send begins. If Send Delay is set, SENDREP will be set to 0. |
|
SENDREP |
# |
set number of times file will be sent. 0 sends for ever. Should follow after SENDDLY |
|
SENDQUIT |
|
quit when sendfile ends.If you manually stop send, then Autoquit is cancelled. Can use SENDQUIT=filename |
| SENDSTR | "string" | Loads "string" into the Send String comboboxes. Can be called more than once to load more strings. Does not send the string unless sent to a running instance using FIRST (see below) |
| SENDNUM | "string" | as SENDSTR above |
|
FIRST |
|
Sends commands to running (FIRST) instance of Realterm or stops more than one instance running. Brings FIRST instance of realterm to front, and quits. Should be first param. |
|
LFNL |
1/0 |
sets Newline Mode checkbox |
|
SPY |
1/0 |
Spy mode. Port you are spying on must be closed when starting |
|
SCANPORTS |
1/0 |
realterm scans for actual comports by trying to open them all. This can cause problems with Bluetooth serial devices, because it takes a while before the OS can say that a port is not there. This option can be sued to suppress scanning |
|
I2CADD |
set the I2C Address. Should be hex string eg "0x40" |
|
| HELP | ||
| SCROLLBACK | # | Enable Scrollback. =0 disables; =N Sets SCROLLBACK lines=N |
When you begin a line with the FIRST parameter, the parameters will be sent to the existing (first) running instance, and the second instance will terminate. This allows you to pass many of the above parameters (not all will do anything), and some special ones below. Note that Windows Scripting/ActiveX is a better way to do complicated tasks.
realterm.exe first LF sendstr="S42F0"
|
QUIT |
|
Quits Realterm |
|
EXIT |
|
same as Quit |
|
CAPTURE |
0/1/filename |
Start/stop capture. 1 starts capture; 0 stops; filename starts and sets filename |
|
SENDFILE |
0/1/filename |
start/stop send file |
|
SENDSTR |
"string" |
send string. (only when sent to a running instance) |
|
CR |
0/1 |
send CR after string (sets for following strings) |
|
LF |
0/1 |
send LF after string |
|
SENDNUM |
"numeric string" |
send numeric string as binary (only when sent to a running instance) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The best idea is to create a special shortcut for each setup you want to use, and set the params in its properties. If you need other parameters added, contact us.
RealTerm is an out-of-process server. The active interface is more extensive than the command line. Use a property browser (eg from excel or delphi) to see what it can do. (must be registered first run: REALTERM /REGSERVER)
You can launch Realterm from another application, eg matlab, excel, VB,OpenOffice, delphi. Alternatively use windows scripting, and write a simple .SCP file to launch and control it. You could even launch it from a web page to use as telnet client!
This should be done automatically when you run the installer. Sometimes this fails, or perhaps you don't have the right permissions under XP or Vista.
To register the ActiveX (only needed if you want to use activex) run: REALTERM.EXE /regserver
When the type library changes (ie we extend it) you may need to unregisterm then register it. Run: REALTERM.EXE /unregserver
It has many problems. The best thing about using RealTerm is that you can see exactly what is happening when you want. Save yourself time and headaches. If you don't want people to see RealTerm, you can completely hide it.
Windows has one big problem for users of binary data. Strings are null-terminated. ie they end with 0x00. Amazing as it seems, you can't pass a string containing char 0 (0x00) through the activeX interface.
Putstring can send any 8 bit chars except 0. If you need to send char 0 to an application use the Putchar function.
(V2.0.0.46+) Realterm can send events to an application. From the Events tab you can manually trigger events, to make it easier to test your software interface. The Events tab is only visible when started as an ActiveX.
Events usually have an associated property to enable them. By default they are disabled, so you will need to explicitly enable them before anything happens.
The Timer is a utility. It does nothing within Realterm, ie it only provides callbacks to your application. This exists as some languages do not have a convenient timer arrangement.
DataTrigger is new, and a work in progress, so the interface will change in future. Note that when you are capturing a lot of data, or the data rate is high, using the a capture file is probably a better approach than Data Triggers.
procedure OnTimer; dispid 1;
procedure OnCaptureCount;
dispid 2;
procedure OnCaptureStop; dispid 3;
procedure
OnDataTrigger(Index: Integer; Timeout: WordBool; Data: OleVariant;
Size: Integer; Reenable: WordBool); dispid 201;
Open Realterm using a property editor/browser. Or open the typelibrary (.tlb) or the realterm_tlb.pas file, which are in the source directory.
property
TimerPeriod: Integer
dispid 1;
property EnableTimerCallbacks: WordBool dispid
2;
property CaptureFile: WideString dispid 3;
property Capture:
EnumCaptureMode dispid 4;
property baud: Integer dispid
5;
property Port: WideString dispid 6;
property PortOpen:
WordBool dispid 7;
property CaptureCountForCallback: Integer
dispid 8;
property EnableCaptureCallbacks: WordBool dispid
9;
procedure Close; dispid 10;
procedure StartCapture; dispid
11;
procedure StartCaptureAppend; dispid 12;
procedure
StopCapture; dispid 13;
property FrameSize: Integer dispid
14;
property DisplayAs: Integer dispid 15;
property CharCount:
Integer dispid 16;
property CPS: Integer dispid 17;
property
WindowState: EnumWindowState dispid 18;
property Caption:
WideString dispid 19;
property Visible: WordBool dispid
20;
property CaptureEnd: Integer dispid 21;
property
CaptureEndUnits: EnumUnits dispid 23;
procedure PutString(const S:
WideString); dispid 22;
function SelectTabSheet(const TabCaption:
WideString): WordBool; dispid 25;
function DiskFree(Drive:
Integer): Double; dispid 24;
property CaptureTimeLeft: Integer
readonly dispid 26;
procedure PutChar(C: Byte); dispid
27;
property TrayIconActive: WordBool dispid 28;
function
DiskSize(Drive: Integer): Double; dispid 29;
property BigEndian:
WordBool dispid 30;
property EchoPort: WideString dispid
31;
property EchoPortOpen: WordBool dispid 32;
property
HalfDuplex: WordBool dispid 33;
property HideControls: WordBool
dispid 34;
property Parity: WideString dispid 35;
property
DataBits: Integer dispid 36;
property StopBits: Integer dispid
37;
property EchoBaud: Integer dispid 38;
property EchoParity:
WideString dispid 39;
property EchoDataBits: Integer dispid
40;
property EchoStopBits: Integer dispid 41;
property
FlowControl: Integer dispid 42;
property EchoFlowControl: Integer
dispid 43;
property CharDelay: Integer dispid 44;
property
LineDelay: Integer dispid 45;
property Rows: Integer dispid
46;
property SendFileDelay: Integer dispid 47;
property
SendFileRepeats: Integer dispid 48;
property SendFile: WideString
dispid 49;
property Send: WordBool dispid 50;
procedure
ClearTerminal; dispid 51;
property MonitorOn: WordBool dispid
52;
property LinefeedIsNewline: WordBool dispid 53;
procedure
NewlineTerminal; dispid 54;
property RTS: WordBool dispid 55;
property DTR: WordBool dispid 56;
property CaptureDirect:
WordBool dispid 57;
function AddCannedSendString(const
SendString: WideString; ControlNum:Integer): WordBool; dispid 58;
property Version: WideString readonly dispid 59;
procedure
TimeStamp(Style: Integer; Delimiter: Byte); dispid 201;
procedure
EnableDataTrigger(Index: Integer); dispid 202;
procedure
DisableDataTrigger(Index: Integer);dispid 203;
function WaitforDataTrigger(Timeout: Integer): WideString; dispid 204;
Don't rely on the defaults when using ActiveX (eg baud rate). These may change with different revisions.
This is only a snapshot when this web page was written. Always check your actual version, as new functions are always being added. If you need other parameters added, contact us.
The I2CChip Host adaptor 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.
Read a Dallas 1-Wire ID chip
Write to 4 Digit LED Display
Read/write I2C Bus chips
Read SMBus Alert register
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
|
|
Realterm can has buttons for RESET and POWER if you are using the BEL Dual PIC Programmer. Its watches the RB7 line. This makes it easy to control a serial PIC when you are using ICP. If you are using NT/2K/XP you need to install the DLPORTIO driver using its install program. |
Version 1.x was compiled with Delphi 3 and used the turbopower Async 2.11 library.
The translation component is not currently working, however if you would like to volunteer, I keep a list for the day it is working. Translators are wanted for all languages. I am not sure if this version will work with non-european languages.
Email
if you can help:
crun@users.sourceforge.net
If
you are using Realterm in
your company, please drop me a line
so I can include your company below...
Rakon, NZ. Test machinery runs 16 copies per PC, 24hr/7days, automatically testing Quartz crystals for most of the worlds GPS receivers
Macfab Mfg, Canada: Upload and Download programs to its CNC mills and lathes, and troubleshoot cable runs for new machines.
C.P. Bourg, Printing Machinery: Used to support field technicians
Novell: Debugging Telnet connections to mainframe through gateway
CNC, Netherlands: Used in laboratory with INOLAB Conductivity Meter
JASMIN Plc, UK: Collecting data from a Seimens SCOOT UTC (Urban Traffic Control) system for offline processing.
Institute for Lasertechnologies at Univerity of ULM: Controlling 2 spectrometers and stepper motor control in a spectral reflection interferometer
Escort Memory Systems, USA: RFID tags. Send intel-hex files to thier systems
Thrane & Thrane, Denmark: Remote debugging
Oculex: Collects data from phone system
Omitec: Test and confirgure bluetooth modules
EZ_ARM: Serial terminal used for debugging and development with ARM7 EV kit
MCSi: Setting up custom control systems for very large A/V and Presentation systems
Thorlabs: test nanopositioning controllers during product development
Woehler: Debugging Pressure measuring instruments and flue gas analysers
SmartHome: SDK tool for protocol development
Ditchwitch
Cinetech: Discovering serial strings used in equipment control to develop automation
Sparklike: debugging GassGlass devices and automated calibration
Grand River Rubber: Monitoring and debugging Production line scale systems
I2C: Chips, Modules, I2C-USB/RS232 Host Adaptor
PIC Programmer Windows/Linux:
BeyondLogic:RS232 Info, and info on most any hardware port on your PC
Serial Port Central: Heaps of serial port related links
MultiEdit: Programmers editor for Windows
FTDI: These make an easy way to convert your serial products to USB
Borland: who make it all possible, and whos generosity with Kylix, will soon make a linux version possible!
The latest version of a program isn't always the one you want. Sometimes it works differently, or isn't as stable as an older one.
Some of the older documentation can be found here:
|
|
