Bently Nevada 3500/91 EGD Gateway: Mark VIe Interface, Slots and Limits

Industrial control cabinet with PLC modules, HMI panel and field wiring

TL;DR: The Bently Nevada 3500/91 is the EGD (Ethernet Global Data) communication gateway for a 3500 rack. It publishes rack, module and channel values, status, measured values and configured setpoints to an EGD network, and it accepts only a small set of group commands back. It needs a 3500/22M TDI, occupies one full-height front slot plus one full-height rear slot, and only one EGD gateway is allowed per rack. It has no relay outputs, no redundant configuration and no nanosecond timestamp capability. Machine protection trips stay in the rack’s relay modules, and anti-surge control stays in the Mark VIe controller.

The 3500/91 is often described as a high-speed bridge that “publishes vibration data to the UDH bus at nanosecond accuracy and improves trip response”. None of those three claims survives a reading of the datasheet. What the module actually does is narrower, more useful and easier to specify: it turns a 3500 rack into a standard EGD producer on an Ethernet network, so a GE Mark VIe controller, HMI or historian can consume monitored values without a protocol converter. This article works through the datasheet, the rack requirements and the data path, and marks the points where common descriptions go wrong.

What does the Bently Nevada 3500/91 EGD gateway actually do?

The 3500/91 is the EGD communication gateway for a Bently Nevada 3500 rack. It publishes rack, module and channel values, status, measured data and configured setpoints as EGD producer exchanges over UDP/IP, and it accepts only group reset, trip-multiply and alarm-inhibit commands back from the network. It carries no trip contacts and performs no protection logic itself.

  • Protocol: EGD version 2.01 over Ethernet UDP/IP, on IEEE 802.3 10BASE-T/100BASE-TX or 100BASE-FX (datasheet 165361 Rev. J).
  • Interface to the rack: a 3500/22M TDI (Transient Data Interface) is required for the gateway to communicate with monitor modules.
  • Power: 7.4 W typical; main module 0.79 kg, I/O module 0.39 kg; operating range −30 °C to +65 °C at 95% non-condensing humidity.

The important architectural point is that the 3500/91 does not talk to monitor modules directly. The 3500/22M Transient Data Interface (TDI) is the rack’s data interface; the gateway is a network node attached to it. A rack without a TDI cannot use the 3500/91 at all, which is why retrofit quotes that list only the gateway are incomplete.

The values it publishes come from the monitor modules in the rack. Radial vibration and axial position usually originate in the 3500/42M Proximitor/Seismic Monitor, while the 3500/25 Enhanced Keyphasor module supplies the once-per-turn reference needed for phase and order analysis. Local indication is handled by the 3500/94M display module, not by the gateway.

Data direction Content Exchange type
Rack to network Rack, module, channel and data-value status Producer
Rack to network Data values (float) Producer
Rack to network Setpoints (float) Producer
Network to rack Group reset Consumer
Network to rack Group trip multiply Consumer
Network to rack Group alarm inhibit Consumer
Network to rack Group special alarm inhibit Consumer

Is the 3500/91 an EGD producer or a consumer?

The 3500/91 is a producer first and a consumer second. Its EGD configuration publishes rack, module, channel and status data plus float values and setpoints; the only consumed exchanges are group reset, group trip multiply, group alarm inhibit and group special alarm inhibit. It never writes alarm setpoints or control outputs to monitor modules.

That asymmetry matters in a specification review. A Mark VIe controller can read vibration levels, alarm states and setpoints from the rack, and an operator can issue group-level reset or inhibit commands across the EGD network. What the gateway cannot do is push a new alarm setpoint, a trip limit or a control output into a monitor module. Setpoint changes remain a configuration-software function performed through the TDI.

The datasheet is explicit about consumed-exchange support: it requires version 2.21 or later of 4-channel firmware. In other words, the reverse path is not just a gateway setting; the monitor modules in the rack must support it.

Where does the 3500/91 connect inside a GE Mark VIe unit?

In a GE Mark VIe unit the 3500/91 sits on the supervisory Ethernet side, not on the IONet I/O network. It publishes EGD exchanges onto an Ethernet network that the Mark VIe controller or HMI can consume; the UDH is the Unit Data Highway that carries that traffic, while EGD is the protocol, not a separate bus.

This is the correction that matters most. The Unit Data Highway (UDH) in Mark VIe is an Ethernet LAN that links controllers, HMI servers, historians and engineering stations; GE’s system guide describes EGD as the messaging protocol used for live data fan-out on that network. The 3500/91 therefore connects at the supervisory network level, next to the controller and HMI, not at the I/O level where Mark VIe I/O packs live on IONet.

The practical consequence: the 3500/91 is not a Mark VIe I/O module and cannot replace one. For a Mark VIe controller to use the data, its configuration must include a consumer exchange for the 3500 producer exchange, and the network must be designed so that the EGD traffic reaches that controller. That is an engineering task, not an automatic discovery process.

Speed and keyphasor inputs often reach the rack through the 3500/50M tachometer module, which is why a gateway retrofit should be planned together with the monitor modules that feed it rather than as a standalone network upgrade.

How many slots does a 3500/91 occupy, and how many fit in a rack?

The 3500/91 uses one full-height front slot for the gateway and one full-height rear slot for its Ethernet I/O module. A rack accepts only one EGD gateway, so a plant with four 3500 racks needs four 3500/91 modules and four 3500/22M TDI interfaces, not one shared gateway.

The datasheet states “only 1 EGD per rack is allowed” and gives the rack-space requirement as one full-height front slot plus one full-height rear slot. The rear module is not optional: it carries the physical Ethernet connection, so the front and rear modules must be ordered as a matched pair.

Specification 3500/91 value
Function EGD communication gateway for a 3500 rack
Protocol EGD version 2.01 over Ethernet UDP/IP
Ethernet physical layer 10BASE-T/100BASE-TX (RJ-45) or 100BASE-FX (MT-RJ)
Gateways per rack 1 maximum
Rack space 1 full-height front slot + 1 full-height rear slot
Rack interface required 3500/22M TDI, firmware 1.20 or later
Configuration software 3500 Rack Configuration Software 3.70 or later
Power consumption 7.4 W typical
Operating temperature −30 °C to +65 °C
Humidity 95%, non-condensing
Relay outputs None
Redundant gateway option None — one module, one Ethernet port

Baker Hughes does not publish a fixed maximum point count for the 3500/91 in datasheet 165361. The number of published values follows from the monitor modules and channels configured in the rack and from the EGD exchange configuration, so a point count should be confirmed in the rack configuration rather than assumed from a catalogue figure.

Does the 3500/91 offer redundant gateways or dual network ports?

There is no redundant 3500/91 configuration and no second Ethernet port. The module is single, a rack can hold only one EGD gateway, and the front-panel connection is a single RJ-45 or MT-RJ socket. Mark VIe’s dual-UDH fault tolerance ends at the switch, so the gateway remains a single point of failure for its rack’s EGD data.

This is a real availability difference between the 3500 monitoring path and the Mark VIe control path. A Mark VIe unit can be built with dual UDH networks and redundant controllers, but a single-port 3500/91 cannot be dual-homed across both networks. If the EGD data is used for operator advisory or condition trending, that is usually acceptable; if a specification assumes gateway redundancy because the controller is redundant, the assumption is wrong.

  • One gateway per rack, one port per gateway.
  • No published redundant-pair configuration in datasheet 165361.
  • Recommended mitigation: a spare 161204-01 main module and the matching 161216 I/O module on site, plus a documented IP and exchange plan for fast replacement.

Which EGD version, firmware and network topology are required?

The gateway implements EGD version 2.01 over Ethernet UDP/IP, with a 10BASE-T/100BASE-TX RJ-45 I/O module or a 100BASE-FX MT-RJ module. It needs a managed switch and a planned VLAN or subnet because EGD exchanges are cyclic multicast or broadcast traffic, and it requires 3500 Rack Configuration Software 3.70 or later.

EGD is a producer/consumer protocol: the producer sends an exchange at a configured period, and each consumer expects updates within a timeout. That is a different traffic model from Modbus polling. A shared office network with unknown multicast behaviour is the wrong place for it; the gateway belongs on a segmented control network with a managed switch, documented VLANs and a consumer list that matches the actual controller and HMI configuration.

For the rack to support consumed group commands, the datasheet also requires 4-channel firmware 2.21 or later. For the gateway to work at all, the TDI needs firmware 1.20 or later and the rack configuration software needs to be version 3.70 or later.

Does the gateway improve trip or anti-surge response?

No. A 3500 rack trip is voted and wired through monitor alarms and relay modules such as the 3500/32M or 3500/33; the gateway has no relay outputs and is not in that circuit. Anti-surge control runs in the Mark VIe controller on its own process I/O, while the 3500/91 supplies vibration and machine-state data for monitoring.

Function Signal path 3500/91 involved?
Machine protection trip Monitor alarm → backplane → relay module → hardwired trip circuit No
Vibration and condition data to Mark VIe Monitor → TDI → 3500/91 → EGD → controller/HMI Yes
Alarm setpoint change Rack Configuration Software → TDI → monitor No
Group reset, trip multiply, alarm inhibit EGD consumer exchange → 3500/91 → rack Yes, limited commands only
Anti-surge control Mark VIe process I/O and control algorithms No

The trip path in a 3500 rack is deliberately independent of the communication gateway. Monitor modules raise alarms on the backplane, and dry contacts come from relay modules such as the 3500/33 16-channel relay module; overspeed protection has its own module, the 3500/53 electronic overspeed module. None of those functions passes through the 3500/91.

Anti-surge control is a compressor control function executed in the Mark VIe controller using its own process inputs and algorithms. The 3500/91 can make vibration and machine-state data visible to that controller, and an engineer can use it for trending, advisory logic or diagnostics. It is not part of the anti-surge control loop, and describing it as improving anti-surge response confuses monitoring data with closed-loop control.

Can the 3500/91 deliver nanosecond timestamp synchronisation?

No. EGD is a cyclic producer/consumer protocol whose timing comes from the configured producer period and the consumer’s update timeout, not from a nanosecond clock. The 3500/91 datasheet specifies no nanosecond timestamp, IEEE 1588 or PTP capability, so the gateway should not be sold or specified as a nanosecond-synchronised data source.

The datasheet describes EGD exchanges and Ethernet UDP/IP framing; it does not publish a timestamp resolution, a clock-synchronisation method or a PTP profile. The honest specification is “cyclic EGD data with a configured producer period”, and any latency or synchronisation figure should come from a site-specific network measurement, not from a marketing description.

If a project genuinely needs tightly aligned time stamps across controllers, that requirement belongs to the plant’s time-distribution architecture, not to this gateway. EGD data is well suited to monitoring, trending, operator displays and historian collection; it should not be treated as a nanosecond time reference.

How does the 3500/91 compare with the 3500/92 Modbus gateway?

The 3500/91 speaks EGD; the 3500/92 speaks Modbus RTU, Modbus/TCP and the proprietary Bently Nevada protocol. Choose the 3500/91 when the consumer is a GE controller or another EGD device, and the 3500/92 when the plant DCS, PLC or SCADA expects Modbus polling. They are different gateways, not two versions of one product.

3500/91 EGD gateway 3500/92 communication gateway
Primary protocol EGD version 2.01 over UDP/IP Modbus RTU, Modbus/TCP, proprietary Bently Nevada protocol
Data model Cyclic producer/consumer exchanges Client/server polling
Typical consumer GE Mark VIe controller, EGD-compatible controllers and HMIs Plant DCS, PLC, SCADA and data-acquisition systems
Best fit Native EGD integration with GE control systems Modbus integration with third-party control systems

Both gateways expose rack-monitored values and status, but they solve different integration problems. A site that already runs EGD on its control network should not add a Modbus gateway and a protocol converter; a site whose DCS only polls Modbus should not expect the 3500/91 to answer that poll. Confirm the current ordering variant and rack interface requirements with Baker Hughes before specifying either module.

Which part numbers belong on the spares list?

Order the gateway as 3500/91-AA-BB-CC: AA is 01 for the EGD main module, BB is 01 for the copper 10BASE-T/100BASE-TX I/O module or 02 for 100BASE-FX fibre, and CC is the agency approval. The spare main module is 161204-01 and the spare I/O modules are 161216-01 and 161216-02.

Item Part number Notes
EGD main module 161204-01 3500/91 gateway main board
Ethernet I/O, copper 161216-01 10BASE-T/100BASE-TX, RJ-45
Ethernet I/O, fibre 161216-02 100BASE-FX, MT-RJ
User guide 161232 3500/91 User Guide
Rack interface 3500/22M TDI Required in the same rack

The I/O module is a separate line item and must match the installed cabling. A copper gateway ordered against a fibre installation will fit the rear slot but will not connect. The Bently Nevada spare parts buying guide explains how the ordering suffix maps to what ships, and the complete 3500 system guide covers rack layout and interface modules.

What do the most common 3500/91 claims get wrong?

  • “Nanosecond timestamp synchronisation” — not supported by the datasheet. EGD is cyclic; timing comes from the producer period and consumer timeout.
  • “Publishes to the UDH industrial control bus” — the UDH is a Mark VIe Ethernet network, not a protocol. The 3500/91 publishes EGD, and that EGD traffic can travel on the UDH.
  • “Improves combined anti-surge and trip response” — trips go through relay modules, not the gateway; anti-surge runs in the Mark VIe controller, not in the 3500 rack.
  • “Redundant gateway pair” — only one EGD gateway is allowed per rack, and the module has a single Ethernet port.
  • “One gateway covers the plant” — one gateway per rack, each with its own TDI.
  • “Modbus and EGD in one module” — EGD is the 3500/91’s protocol; Modbus is the 3500/92’s role.

For the wider rack context, the 3500 machinery protection system overview covers power supplies, interfaces and rack layout, while the 3500 module deep dives cover individual monitor modules in the same format. When a rack is being replaced rather than extended, the Orbit 60 conneX DCS interface is the migration path to compare.

Frequently asked questions

What is the Bently Nevada 3500/91 EGD gateway used for?

It connects a 3500 machinery protection rack to an Ethernet network that uses Ethernet Global Data. The gateway publishes rack, module and channel values, status, measured values and setpoints as EGD producer exchanges, so a GE Mark VIe controller, HMI or historian can consume them without a protocol converter. It also accepts a limited set of group commands from the network. It is a communication module, not a protection or control module.

Is the 3500/91 a producer or a consumer on EGD?

It is primarily a producer. The datasheet lists producer exchanges for rack, module, channel and data-value status, float data values and float setpoints. Its consumer exchanges are limited to group reset, group trip multiply, group alarm inhibit and group special alarm inhibit. It does not write setpoints, trip limits or control outputs into monitor modules; those changes remain a rack configuration function.

Can the 3500/91 write setpoints or trip limits into the rack?

No. Setpoints are published as read-only data, and the consumed exchanges carry group commands only. Changing an alarm setpoint or a trip limit is done through the 3500 Rack Configuration Software via the TDI. This distinction matters during a retrofit: the gateway can make existing settings visible to a Mark VIe HMI, but it does not become a configuration or control path into the protection system.

Does the 3500/91 connect to the Mark VIe IONet?

No. It connects at the supervisory Ethernet level, where the Mark VIe controller, HMI servers and historians communicate. IONet is the controller-to-I/O-pack network. The 3500/91 is not an I/O pack and cannot replace one. Its EGD exchanges can travel on the Unit Data Highway because the UDH is an Ethernet LAN that carries EGD, but the gateway itself is a peer device on that network, not part of the I/O layer.

How many 3500/91 modules can one 3500 rack hold?

One. The datasheet states that only one EGD gateway is allowed per rack. A plant with multiple 3500 racks therefore needs one 3500/91 and one 3500/22M TDI per rack, plus one rear Ethernet I/O module for each gateway. The gateway occupies one full-height front slot and one full-height rear slot, and the rear I/O module must match the front module and the installed cabling. Plan the spare, IP address and EGD exchange list separately for every rack in the unit.

Is the 3500/91 redundant?

No. There is no redundant gateway pair and no second Ethernet port. The module has a single RJ-45 or MT-RJ connection, and only one EGD gateway is permitted per rack. A Mark VIe unit may have dual UDH networks and redundant controllers, but a single-port gateway cannot be dual-homed across both networks. Treat the gateway as a single point of failure and keep a spare main module and matching I/O module.

Does the 3500/91 have relay contacts for a trip circuit?

No. The module has front-panel OK and TX/RX LEDs and an Ethernet connection, but no relay outputs. Machine protection trips are voted and wired through monitor alarms and relay modules such as the 3500/32M, 3500/33 or 3500/34. Overspeed protection uses the 3500/53 module. The gateway can report alarm status, but it cannot trip a machine and is not part of the trip circuit.

Does the 3500/91 support nanosecond timestamps?

No. The datasheet does not specify nanosecond timestamp resolution, IEEE 1588 or PTP. EGD is a cyclic producer/consumer protocol: the producer sends at a configured period, and consumers time out if updates stop. That is adequate for monitoring, trending and historian collection. If a project needs tightly aligned time stamps, that requirement belongs to the plant time-distribution architecture, not to this gateway.

What software and firmware are required for the 3500/91?

The rack needs a 3500/22M TDI with firmware 1.20 or later, and the configuration tool must be 3500 Rack Configuration Software 3.70 or later. If consumed group commands are used, 4-channel firmware 2.21 or later is also required. These are minimum versions from datasheet 165361 Rev. J; confirm the current release with Baker Hughes before ordering, because the values in older copies of the datasheet can differ.

Should I choose the 3500/91 or the 3500/92?

Choose the 3500/91 when the consumer speaks EGD, typically a GE Mark VIe controller or another EGD-compatible device. Choose the 3500/92 when the plant DCS, PLC or SCADA expects Modbus RTU, Modbus/TCP or the proprietary Bently Nevada protocol. The two modules solve different integration problems, and adding a protocol converter to force one into the other’s role usually costs more than specifying the correct gateway.

Where do these 3500/91 specifications come from?

Leave a comment

Your email address will not be published. Required fields are marked *

Need a part? Ask us.

We reply within one business day.