Connect serial equipment to an Ethernet network with a device server selected for electrical interfaces, application mode and host support. Compare transparent transport, virtual ports and security requirements separately from protocol conversion, then test timing and recovery with the actual legacy device. Prioritize application, electrical, settings. Use the checkpoints to build a consistent equipment scope and confirm the intended trial or installation evidence. The official image is a product reference; it does not establish availability or an authorized supplier relationship. Submit OEM/ODM changes for application-specific feasibility review.
Connect serial equipment to an Ethernet network with a device server selected for electrical interfaces, application mode and host support. Compare transparent transport, virtual ports and security requirements separately from protocol conversion, then test timing and recovery with the actual legacy device.
Shown as a configuration reference. Availability and the equipment offered for your project are confirmed separately.
Define what the serial application expects
A serial device server transports serial communication across a network. It does not automatically translate the connected application’s protocol. Identify the serial device, host software and the desired arrangement: a virtual serial port, network socket or another supported mode. The Moxa NPort 6100/6200 reference offers defined terminal-server modes, but the correct choice depends on the application. A successful cable connection alone cannot establish that legacy software behaves correctly through the network.
Match the electrical serial connection
Specify RS-232, RS-422 or RS-485, connector pinout and the actual wiring. Include baud rate, data bits, parity, stop bits and any flow-control requirements. Similar connectors do not guarantee matching pin assignments or electrical standards. Check termination, isolation and other requirements through the responsible installation design. List adapters and leads explicitly so an otherwise suitable device server is not delivered without the interface needed to connect the field equipment.
Confirm operating mode and host drivers
Virtual COM or other driver-based operation needs compatible host operating systems and software versions. Socket modes introduce a different application interface. Identify who configures the host and whether the existing application can use the chosen method. Where several clients or paired servers are involved, confirm supported behavior for the exact model. Do not assume every serial application accepts shared access or that all control signals are reproduced in the same way.
| Selection issue | Information to specify |
|---|---|
| Application | Serial device, host software and desired transport mode. |
| Electrical | Standard, pinout, wiring and required isolation or termination. |
| Settings | Baud, framing, flow control and control-signal behavior. |
| Host | Drivers, operating system and application compatibility. |
| Recovery | Timeouts, buffering and reconnection expectations. |
| Acceptance | Real transactions through the complete supplied arrangement. |
Assess timing and interruption behavior
Network transport can change timing compared with a direct local serial connection. Describe timeouts, message boundaries and the application’s response expectations. Test the actual device and software rather than relying only on a generic throughput figure. Discuss buffering, reconnect behavior and what happens after power or network loss. A system can transmit normal messages yet still fail during startup, a long idle period or a recovery sequence important to the legacy application.
Specify network protection and management
If encrypted transport or secure administration is required, identify compatible modes, peers and software. Security depends on the selected configuration and supporting systems, not merely a secure product label. Define credentials, management access and updates within the site policy. Retain addressing and port assignments and decide who restores them after replacement. The device server should expose only the intended serial service, with management and production access organized deliberately.
Accept through the real application workflow
Commission the supplied server, cables and host setup with representative transactions from the actual application. Include agreed restart and interruption cases and any control-signal behavior the device uses. Retain driver versions, serial settings, firmware and configuration. A changing byte counter or a successful network ping does not establish useful operation. The acceptance should demonstrate that the intended legacy process communicates and recovers as specified through the complete networked arrangement.
Scope OEM/ODM as a documented connection package
Preconfiguration, connector organization, labels and panel integration can be reviewed. Changes to serial electronics, firmware or protocol behavior need engineering and ongoing support. Provide application and wiring details with the brief. A customized package should preserve component identification and a reproducible host setup. Reference photographs do not imply private-label rights or guarantee compatibility with a legacy program that has not been tested using the proposed mode and configuration.
What should your serial device server RFQ include?
- Application: Serial device, host software and desired transport mode.
- Electrical: Standard, pinout, wiring and required isolation or termination.
- Settings: Baud, framing, flow control and control-signal behavior.
- Host: Drivers, operating system and application compatibility.
- Recovery: Timeouts, buffering and reconnection expectations.
- Acceptance: Real transactions through the complete supplied arrangement.
- Destination, site conditions and delivery access
- Installation boundary, utilities and connection drawings
- Acceptance procedure, documentation and training scope
- OEM/ODM changes: interface, material, branding or new design; written engineering feasibility required
Need OEM / ODM customization?
Submit branding, packaging, configuration or engineering requirements for this equipment. Include the target market, initial and annual quantities, required changes and acceptance criteria.
Customization feasibility, permitted branding, development responsibilities, minimum quantity, cost and lead time are reviewed for the proposed supplier and configuration before a quotation is confirmed.
Frequently asked questions
Does a serial device server convert Modbus RTU to Modbus TCP?
Not automatically. It may transport serial bytes without translating the application protocol. If translation is required, specify an appropriate protocol gateway and roles. Describe what the host software expects so transparent transport is not mistaken for an implemented protocol-conversion function.
Which serial settings belong in the inquiry?
Identify electrical standard, connector pinout, wiring, baud rate, data bits, parity, stop bits and flow control. Include any relevant control-signal behavior. A connector type or device name alone does not establish that the supplied server and cable match the existing serial equipment.
Will virtual COM software work on every computer?
Driver and operating-system compatibility must be checked for the selected server and host environment. Provide the application and system versions and test the intended mode. A virtual port that installs successfully does not by itself establish that the legacy application communicates and handles interruptions correctly.
Can network delays affect a serial application?
Yes, timing and recovery can differ from a direct local connection. State application timeouts and message behavior and test real transactions, startup and reconnection. Generic data transmission or throughput results do not establish that every timing-sensitive legacy workflow will operate as intended.
What should device-server acceptance prove?
Use the actual serial device, cables, host software and selected mode. Verify representative transactions and agreed restart or interruption behavior. Keep settings and versions with the test record. A network ping or byte counter demonstrates connectivity but not the complete application’s required operation.
Can a serial connection package be customized for an OEM?
Labels, connectors, preconfiguration and panel mounting can be reviewed. Electrical or firmware changes need validation and support commitments. Supply pinouts and application details and retain a reproducible host setup so OEM/ODM integration remains traceable rather than dependent on undocumented commissioning adjustments.
Reference information
- NPort 6100/6200 Series - Terminal Servers | Moxa
- Serial Device Servers | Moxa
Reference data and images explain equipment configurations. IndustryApex engineers confirm the offered model, specification and commercial scope in your project quotation.