54
Docklight V2.2 User Manual 07/2016 Copyright 2016 Flachmann und Heggelbacher GbR
Reference
8.8
Dialog: Project Settings - Flow Control
Menu Tools >
Project Settings... | Flow Control
Used to specify additional hardware or software flow control settings for serial
communications in Docklight
Flow Control Support
Off
No hardware or software
mechanism is used. RTS and DTR are enabled
when the COM port is opened.
Manual
Use this mode to control the RTS and DTR signals manually and display the current
state of the CTS, DSR, DCD and RI lines. If flow control is set to "Manual", an additional
status element is displayed in the Docklight main window. You may toggle the RTS and
DTR lines by double clicking on the corresponding indicator.
NOTE: Flow control signals are not treated as communication data and will not be
displayed in the communication window or logged to a file.
Hardware Handshaking, Software Handshaking
Support for RTS/CTS hardware flow control and XON/XOFF software flow control. These
are expert settings rarely required for recent communication applications.
RS485 Transceiver Control
Some RS232-to-RS485 converters require manual RTS control, i.e. the RS232 device
(PC) tells the converter when it should enable its RS485 driver for transmission. If you
choose "RS485 Transceiver Control", the COM port sets RTS to High before transmitting
the first character of a
, and resets it to Low after the last character has
been transmitted.
NOTE: Many USB-to-Serial converters or virtual COM port drivers do not implement the
Windows
RTS_CONTROL_TOGGLE mode properly. If you experience problems with
RS485 Transceiver Control, try using a PC with an on-board COM interface or a standard
PCI COM card.
8.9
Dialog: Project Settings - Communication Filter
Menu Tools >
Project Settings... | Communication Filter
Contents Filter
Use this option if you do not need to see the original communication data on the serial
line and only require the additional comments inserted by a Receive Sequence. This is
useful for applications with high data throughput, where most of the data is irrelevant for
testing and you only need to watch for very specific events. These events (and related
display output) can be defined using
Channel Alias
This allows you to re-label the two Docklight data directions according to your specific
use case. E.g. [Docklight] / [Device] instead of [TX] / [RX]. Or [Master] / [Slave] instead
of [TAP0] / [TAP1].
Содержание Docklight V2.2
Страница 1: ...Docklight V2 2 User Manual 07 2016 Copyright 2016 Flachmann und Heggelbacher GbR...
Страница 5: ...Copyright...
Страница 7: ...Introduction...
Страница 11: ...User Interface...
Страница 14: ...Features and Functions...
Страница 17: ...Working with Docklight...
Страница 28: ...Working with Docklight Advanced...
Страница 41: ...Examples and Tutorials...
Страница 46: ...Reference...
Страница 62: ...Support...
Страница 64: ...Appendix...
Страница 76: ...76 Docklight V2 2 User Manual 07 2016 Copyright 2016 Flachmann und Heggelbacher GbR Appendix...
Страница 77: ...Glossary Terms Used...