User Manual
Table Of Contents
- Chapter 1 Introduction
- Chapter 2 Getting Started
- Chapter 3 Initial IP Configuration
- Chapter 4 Choosing the Proper Operation Mode
- Chapter 5 Web Console Configuration
- Chapter 6 Installing and Configuring the Software
- Appendix A SNMP Agents with MIB II & RS-232 Like Groups
- Appendix B Well Known Port Numbers
- Appendix C Federal Communication Commission Interference Statement
- Appendix D FCC Warning Statement
- Appendix E Service Information
NPort W2250/2150 Plus User’s Manual Installing and Configuring the Software
6-11
Click on the Advanced Setting tab to modify Tx Mode, FIFO, and Flash Flush.
Tx Mode
Hi-performance mode is the default for Tx mode. When the driver finishes sending data to
the NPort W2250/W2150, the driver will issue a “Tx Empty” response to the program.
Under classical mode, the driver will not notify the user’s program that Tx transmission is
finished until all Tx data has been sent out from the NPort W2250/W2150. This ODE will
cause lower throughput. Classical mode is recommended if you want to ensure that all data is
sent out before further processing.
FIFO
If the FIFO is Disabled, NPort W2250/2150 will transmit one byte each time the Tx FIFO
becomes empty, and an Rx interrupt will be generated for each incoming byte. This will
result in a faster response and lower throughput. If you want to use XON/XOFF flow control,
we recommend setting the FIFO to Disable.
Fast Flush (only flushes the local buffer)
a. We have added one optional Fast Flush function to Moxa’s new NPort Real COM
driver.
b. For some applications, the user’s program will use the Win32 “PurgeComm()” function
before it reads or writes data. With our design, after the program uses this Purge Comm()
function, the NPort driver will keep querying NPort’s firmware several times to make
sure no data is queued in the NPort firmware buffer, rather than just flushing the local
buffer. This kind of design is used to satisfy some special considerations. However, it
might take more time (about several hundred milliseconds) than a native COM1,
because it needs to work via Ethernet. That’s why the native COM ports on the
motherboard can work fast with this function call, but NPort requires much more time.
In order to accommodate other applications that require a faster response time, the new
NPort driver implements a new “Fast Flush” option. Note that by default, this function
is disabled.
c. To begin with, make sure there are some “PurgeComm()” functions being used in your
application program. In this kind of situation, you might find that your NPort exhibits a