NxSphere® Plexer
SECS/GEM Multiplexer.
More Hosts. Same Production Interface.
Connect More Factory Systems to One Equipment Interface
NxSphere® Plexer shares one equipment connection across a production host and additional engineering, FDC, SPC and analytics hosts. Configure how equipment messages are distributed and how competing control requests are handled.
One equipment connection. Multiple host applications.
How the SECS/GEM Multiplexer Works
NxSphere® Plexer sits between your equipment and its hosts. The equipment uses one HSMS connection to Plexer; the production host and each additional host maintain independent HSMS sessions with Plexer.
PlexerRouting · Isolation · Arbitration
Existing interface preserved
Independent HSMS session
Additional host connections
Independent host sessions
Expand Access While Preserving Production Connectivity
Add engineering, fault detection and classification (FDC), statistical process control (SPC) and analytics hosts while preserving the existing production host interface.
Isolate slow or disconnected hosts
Each host has separate HSMS Select/Deselect state, System Bytes and T3/T5/T6/T7/T8 timers. A slow, disconnected or reconnecting host does not block or delay other hosts or the equipment.
Connection epochs prevent stale replies after reconnection.
Configurable message routing
Deliver Equipment Messages to the Right Hosts
Broadcast or targeted delivery
First-match-wins routing policies match all messages, collection event IDs (CEIDs), alarm IDs (ALIDs), or an exact SECS Stream/Function. Deliver equipment messages to all selected hosts or a specific target.
Replies return to the originating host
Host requests are forwarded using a collision-free equipment-side System Bytes namespace. Each equipment reply returns to exactly the host that originated the request.
Automatic trace ownership
S2F23 / S6F1 trace traffic is routed automatically to the host that defined the trace request ID (TRID), independently of general routing rules.
Real host replies
Plexer relays the first target host's real reply verbatim. If no host answers, it sends nothing and lets equipment T3 govern. No acknowledgement is fabricated.
Host control arbitration
Resolve Competing Host Requests
Configure control arbitration per Stream/Function to manage competing requests from multiple hosts.
DesignatedController
Use a designated-controller policy for selected control requests.
FirstRequestWins
Use a first-request-wins policy for selected control requests.
Confirm routing and control policies against your equipment interface and host workflows during integration.
Configuration and diagnostics
Change Policies Live. Inspect Every Traffic Leg.
One XML configuration
Declare equipment and host HSMS endpoints, routing rules and conflict policies in one XML file. No deployment-specific code changes are needed.
Live configuration reload
Swap routing rules and conflict policies without disconnecting any host.
Complete traffic logging
File logs capture requests, deliveries, replies, rejections, timeouts and abandonments. An aligned console view includes SML content, CEIDs, ALIDs and alarm text for troubleshooting.
Factory automation applications
Add the Host Access Your Factory Needs
Engineering alongside production
Connect a separate engineering host while keeping the existing production host interface.
FDC and SPC connectivity
Extend equipment access to FDC and SPC hosts using configured message routing and control policies.
Equipment data for analytics
Add analytics host connections through independent HSMS sessions.
Plan your deployment
Plexer is inserted into the communication path. Review equipment compatibility, host behaviour and deployment validation with our factory automation team.
Häufig gestellte Fragen
What is a SECS/GEM multiplexer?
A SECS/GEM multiplexer lets multiple host applications share one equipment connection. NxSphere® Plexer provides independent HSMS host sessions, configurable message routing and control arbitration.
Can a production host and FDC host connect to the same equipment?
Yes. NxSphere® Plexer supports the production host plus additional FDC, SPC, engineering and analytics host connections through one equipment HSMS connection. Routing and control policies are configured for your application.
Does adding another host change the production host interface?
Plexer is designed to preserve the existing production host interface while adding host connections. It sits between equipment and hosts, so installation and integration should be planned and validated with your production systems.
What happens when an additional host disconnects?
Host sessions are isolated. A slow, disconnected or reconnecting host does not block or delay other hosts or the equipment. Connection epochs prevent stale replies after reconnection.
How are conflicting host control requests handled?
DesignatedController or FirstRequestWins policies resolve competing requests. Policies are configurable per SECS Stream/Function.
Can routing rules change without disconnecting hosts?
Yes. Live configuration reload lets you swap routing rules and conflict policies without disconnecting hosts.
How are trace reports routed to the correct host?
S2F23 / S6F1 trace traffic automatically routes to the host that defined the TRID, independently of general routing rules.
Kontakt
WIR SIND FÜR SIE DA
Discuss Your NxSphere® Plexer Application
Tell us about your equipment, production host and additional engineering, FDC, SPC or analytics hosts. Our factory automation team can discuss routing, control policies and deployment requirements.