Frequently Asked Questions
All FAQ
Select a category to view related FAQ:
Select a product to view related FAQ:
Suggestions
The main reason is that Win32 API's device naming convention for COM ports uses the form "\\.\COMx". For example, if the device name of COM10 is "\\.\COM10", then COM11 will be "\\.\COM11".
Under the Visual C++ environment:
You need to use the format "\\\\.\\COMx" as the COM port device name when using Win32 API to develop your program.
For example, the device name of COM10 is "\\\\.\\COM10"
Under the Borland C++ Builder:
You need to use the format "\\.\COMx" as the COM port device name when using Win32 API to develop your program.
For example, the device name of COM10 is
"\\.\COM10"
Close
Suggestions
[Description]
I logged into Windows Vista (Windows 7) as Administrator, and received
the following error message when running the COM Mapping utility:
How can I get around this problem?
[Solution]
"Run as administrator" is a security concept introduced into Windows
Vista (Windows 7) in an effort to limit the ability of
non-administrative programs to compromise computer security. Programs
not running as administrator are not allowed to modify system folders or
portions of the Windows Registry, add routing entries, etc. Because of
this, some of the NPort COM Mapping operations will not function
normally.
A program can be "run as administrator" by right-clicking its icon or
shortcut, and selecting "Run as administrator" from the pop-up menu, as
shown in the figure below. Note that double clicking on the icon will
not have the desired effect.
If you want to solve this problem once and for all, right click on the
NPort Administartor Suite icon, select Properties, click on Advanced,
and then click "Run as Administrator."
Suggestions
Actually, the FIFO size is depend on the what UART type that Moxa use. And there are several UART types that Moxa MSB, NPort and Async Server use.
|
|
UART Type |
FIFO Size (Bytes) |
Model |
Windows Driver Setting |
||||
|
MSB |
Smartio / Industio |
16C550C |
16 |
C168H Series, C104H Series,
|
|
High |
Middle |
Low(Disable) |
|
TX FIFO |
16 |
8 |
1 |
|||||
|
RX FIFO |
14 |
8 |
1 |
|||||
|
MU-150 |
64 |
CA-104, CA-132/132I,
CP-104UL, CP-104JU, CP-134U/CP-134U-I, CP-132UL/CP-132UL-I |
High |
Middle |
Low(Disable) |
|||
|
TX FIFO |
64 |
32 |
1 |
|||||
|
RX FIFO |
56 |
28 |
1 |
|||||
|
MU-860 |
128 |
CP-118U, CP-168U V2, CP-104UL V2, CP-104JU V2, CP-102U/CP-102UL, CP-134U/CP-134U-I V2, CP-132UL/CP-132UL-I V2 |
High |
Middle |
Low(Disable) |
|||
|
TX FIFO |
128 |
64 |
1 |
|||||
|
RX FIFO |
120 |
60 |
1 |
|||||
|
Intelligent |
16C550C |
16 |
C320 Turbo Series, C218 Turbo Series |
Enable / Disable |
||||
|
NPort |
16C550C |
16 |
NPort 5110,
NPort Express DE-211/311 |
Enable / Disable |
||||
|
16954 |
128 |
NPort Pro DE-303/308 |
Enable / Disable |
|||||
|
MU-150 |
64 |
NPort 5400/5600 Series, NPort Server Lite DE301/302/304/331/332/334 |
Enable / Disable |
|||||
|
MU-860 |
128 |
NPort W2250/2150, NPort W2004 |
Enable / Disable |
|||||
|
Async Server |
16954 |
128 |
CN2500/2600 |
Enable / Disable |
||||
|
MU-150 |
64 |
CN2510/2610 |
Enable / Disable |
|||||
Suggestions
[POSSIBILITIES]
1. Improper IP configuration.
2. Improper OP_mode .
3. DHCP issue.
4. Access authorization.
5. COM port No. conflicts with other devices.
6. Your firewall filter rule discards the specific TCP packet.
7. DE-311/211 has a DIP SW1 setting error.
8. Port is occupied.
9. Forget to click 'Apply' and 'Save' button.
[SOLUTIONS]
- Make sure that your Host is able to PING the NPort.
- Your operation mode must be [ Host Based / Driver Mode] or [Real COM Mode].
- If your Host and NPort are in DHCP environment :
a) You have to assign a fixed IP address to NPort & your Host.
b) Under DHCP environment, you can map a specific IP address to your NPort's & Host's MAC address. - Use NPort Configurator or Administrator to check the NPort's access control list; your Host IP must exist in NPort's access control list.
- Check if there is any other installation using the same COM port number,
e.g., internal modem on COM3. - Check filter rules to open TCP port # 950(to 965) & # 966(to 981).
- The DE-311/211's DIP SW1 must be OFF for data communication.
- Telnet NPort's IP address, and check the 'Conn. Status' message under [Monitor]. It must be set to 'listen' before you open the port.
- Please remember click 'Apply' button after setting COM Mapping with NPort5000/NE series. And click 'Save' button after installing Driver with NPort Server Family .
Close
Suggestions
[POSSIBILITIES]
1. Improper operation mode.
2. NPort's UDP port is not correct.
3. DHCP issue.
4. Improper [Desti. IP] setting.
5. Firewall filtering rules.
6. Improper DIP switch settings on DE-311/211.
7. Data loss.
[SOLUTIONS]
- Your operation mode must be [UDP mode].
- The NPort's UDP Port must match your own UDP program.
- If your Host and NPort are in a DHCP environment :
a) You have to assign a fixed IP address to NPort & your Host.
b) In a DHCP environment, you can map a specific IP address to your NPort's & Host's MAC address. - Your [Desti.IP] must be the same as your host’s current IP.
- Make sure that your firewall can open the TCP port.
- The DE-311/211's DIP SW1 must be OFF for data communication.
- Initially, UDP can NOT guarantee data won’t be lost. But we still can do something for this problem. That is,
a) Purify your network traffic as best as you can.
b) Your program should be able to handle a resending mechanism when the data is lost.
c) Change to use TCP Server / Client architecture.
Close
