The share stays in the box
The RT-6100 talks to nexMEM over a direct RJ45 link. Its XML share does not need to be exposed on the client's IT network.
AvailableSwiss made
nexMEM
RT-6100 to RT-5100 RS-232 without SMBv1 on the client network
nexMEM targets a precise need: keep the bidirectional serial flow expected by software configured like an RT-5100 while connecting an RT-6100 through a direct RJ45 link. The EHR stays on RS-232. The RT-6100 exchanges its XML files with nexMEM. The practice or hospital IT network does not have to carry that share.
RT-6100RT-5100RS-232Direct RJ45Share kept off client network
Built for one precise NIDEK connection
Patient softwareRT-5100 serialnexMEMRT-6100IT
Three views
One need, three diagrams.
The initial constraint, the nexMEM flow, and the difference in scope with a broader box.
An RT-6100 seen as an RT-5100 by software
"The EHR stays on serial. The RT-6100 share stays inside the box."
nexMEM exposes an RS-232 interface to the PC that is compatible with the RT-5100 flow. The box then talks directly to the RT-6100 through its RJ45 port and handles the instrument XML files. The flow stays bidirectional without exposing that share to the client's IT network.
RS-232 serialRJ45 / network link
Why nexMEM?
Keep the right flow, isolate the right share.
nexMEM is not meant to become a universal gateway. It handles this RT-6100 case cleanly.
Works with the existing software
The PC software stays configured like an RT-5100 when it knows how to communicate over serial.
Bidirectional
Exchanges flow both ways between the software, nexMEM, and the RT-6100.
Clear scope
nexMEM targets this precise NIDEK connection instead of a broader instrument architecture.
Specifications
nexBox hardware, specialized for its flow.
Same compact enclosure. Dedicated nexMEM configuration for the RT-6100 link to RT-5100 compatible software.
- Connectivity
- Ethernet RJ-45 10/100/1000 · USB-A host · USB-C · RS-232 DB9 male
- Software side
- RS-232 with compatible RT-5100 protocol
- Instrument side
- Direct RJ45 / LAN link to NIDEK RT-6100
- Flow
- Bidirectional PC ↔ nexMEM ↔ RT-6100 communication
- Format
- 40 × 57.6 × 62.25 mm (H × W × D)
- Weight
- ~100 g
- Power
- 5 V DC via USB-C · certified 5 V / 3 A power supply recommended (not included)
- Network
- No network configuration required on the acquisition PC
- Conditions
- +10 to +35 °C · storage −10 to +55 °C · humidity 30–90 % without condensation
- Protection
- Class III · IPX0 (indoor use)
- Compliance
- CE · FCC · not considered a medical device
- Origin
- Designed and made in Switzerland 🇨🇭
Typical use cases
When nexMEM is the right box.
- Practice or clinic replacing an RT-5100 with an RT-6100
- EHR or patient software with RT-5100 compatible serial mode
- IT team that refuses SMBv1 on the client IT network
- Technician who wants a direct link between PC, nexMEM, and RT-6100
Transparency
What nexMEM requires.
The software must support RT-5100 over serial. Without that EHR or patient software mode, nexMEM does not replace software integration.
Cabling, serial settings, and RT-6100 configuration must be validated before deployment.
nexMEM targets this direct link. To route multiple instruments or multiple systems, nexBox or nexRef may fit better.
Not a measuring medical device. nexMEM transports and converts an interoperability flow. It does not produce the clinical measurement.
Is the RT-6100 blocked by network constraints?
Share the patient software, its RT-5100 mode, and the current setup. We will quickly validate whether nexMEM can isolate this connection from the client IT network.