Phoenix Contact wireless products serve different roles. RadioLine carries serial-based communication and can accept I/O modules, but it does not support Ethernet. Wireless MUX uses battery power for outdoor testing; normal installations power the modules from 24 VDC. A safety pushbutton signal can cross a Bluetooth link only as part of a complete safety communication architecture—not by connecting the contact directly to an ordinary radio.
RadioLine communication boundary
RadioLine supports communication based on RS serial interfaces and permits I/O module expansion. It does not transport Ethernet. Therefore, reject RadioLine when the application requires an Ethernet path; use it only where the serial or attached-I/O architecture satisfies the signal requirements.
| Product or technology | Supported role | Explicit constraint |
|---|---|---|
| RadioLine | RS-based communication with optional I/O modules | No Ethernet support |
| Wireless MUX | Wireless module evaluated outdoors with battery power | Battery supply is for field testing; normal supply is 24 VDC |
| EPA 2 | Example radio module for Bluetooth transport | Must sit within the described safety communication chain |
| SafetyBridge | Alternative wireless safety architecture | Moves the safety-control function to the output module |
Bluetooth safety-signal architecture
Do not wire an emergency-stop contact into a standard I/O point and assume that adding a radio makes the path suitable for a safety function. The evidence supports the following architecture:
- Connect the safety pushbutton to an input on a safety I/O module.
- Connect that I/O module to a communication module approved for PROFIsafe communication, using PROFINET as the stated example.
- Add a radio module such as EPA 2 to transport the communication over Bluetooth.
- Deliver the communication to the safety controller.
This sequence describes the required component roles, but the evidence does not provide approval identifiers, achieved safety level, range, latency, diagnostics, or fault-response timing. Confirm those items against the selected modules and the application safety requirements before commissioning.
SafetyBridge alternative
SafetyBridge provides a second wireless implementation path. In this architecture, the controller may be a standard controller rather than a safety controller, while the output module performs the safety installation's controller function. This changes where the safety function resides; it does not justify substituting standard I/O for the required safety components.
Power and design verification
Use 24 VDC for a normal Wireless MUX installation. Treat its battery supply only as a field-test arrangement; the evidence gives no battery capacity, runtime, environmental rating, or alarm-duration guarantee. Before deployment, verify that the selected architecture matches the required interface type, uses safety-rated I/O for the safety pushbutton, and has documented approval for every safety communication component and link.
FAQ
Does Phoenix Contact RadioLine support Ethernet?
No. RadioLine supports RS-based serial communication and optional I/O modules, but it does not support Ethernet.
Can an emergency-stop signal be transmitted over Bluetooth?
Yes, but not by attaching an ordinary radio directly to the contact. Route the signal through safety I/O, a communication module approved for PROFIsafe communication, a Bluetooth radio such as EPA 2, and a safety controller.
Can Wireless MUX run permanently from its test battery?
The evidence identifies battery power only for outdoor testing. Power the modules from 24 VDC in a normal installation unless product documentation for the selected hardware explicitly supports another arrangement.