Does a Meeting Room Booking Panel Need PoE and RS485?

A meeting room booking panel needs power and a data path from the wall. PoE carries both over one cable, while RS485 reaches the room's HVAC and lighting.

Most room booking projects are specified backwards. The software is chosen first, the panel is chosen second, and the wall is looked at last — usually a week before installation, when someone notices there is no power outlet outside the door and the nearest network point is six metres away in the ceiling. At that point the project either gains a surface-mounted conduit run or loses a week.

The electrical decision is worth taking early because it constrains everything else: where the panel sits, how deep the back box has to be, whether the room can still be controlled when the network is down, and how the panel behaves after a power cut. This guide works through the two interfaces that matter — PoE for the panel itself and RS485 for the room behind it — using the BVS-QR101 V3.0 10.1-inch Android PoE touch panel as the reference point. It is a metal-housed wall panel with a 10.1-inch 1280 × 800 display, an RK3566 processor running Android 11, LAN, RS485, OTG and USB Type-C, and power taken from the PoE link.

1. What the Panel Actually Does All Day

A booking panel is not a computer in the usual sense. For most of its life it displays one screen: the room name, whether the room is free, what is booked next, and a button to claim the room or release it. The processor is idle, the network traffic is a few kilobytes per minute, and the display is on for perhaps twelve hours a day. What the panel really needs is not performance but the ability to be boring for five years.

That changes the specification in three ways:

• ◆ Reliability beats speed. An eight-core processor will not make a booking screen load faster. A stable Android build with a kiosk mode and a watchdog will.
• ◆ The installation is the project. Chasing cable through a finished corridor costs more than the panel. The hardware choice should minimise that work, not add to it.
• ◆ Nobody will service it. A panel outside a meeting room is touched by hundreds of people and owned by nobody in IT. Anything that requires a login to recover has to be designed out in advance.

2. Why PoE Changes the Installation

Power over Ethernet delivers DC power and a data link on the same twisted pair, which for a wall panel means one cable instead of two. The practical value is not the cable saving. It is that the panel can be mounted on any wall within reach of a switch port, without an electrician, without a socket at skirting level, and without a visible adapter.

There are four consequences worth planning for:

• ◆ The switch becomes the power supply. Put the switch on a UPS and every panel in the building rides through a short outage. That is a low-cost way to keep every panel on the floor running through a short outage.
• ◆ The 100-metre channel still applies. PoE does not extend Ethernet reach. If the nearest switch is further than the cable run allows, the answer is an intermediate switch or a fibre uplink, not a longer cable.
• ◆ Power budget is shared. Every port on a PoE switch draws from one supply. A 24-port switch with a 370 W budget will not run 24 panels at 25 W each, and the arithmetic has to be done before the switch is bought.
• ◆ Cable quality decides whether it works at all. Cheap copper-clad aluminium cable has higher resistance, drops more voltage over the run and is the most common reason a panel reboots when the corridor lights switch on.

3. Where RS485 Earns Its Place

A booking panel that only talks to a cloud calendar is a display. A panel that also controls the room is a control point, and that is where a serial bus still has a role. RS485 survives in commercial buildings because it is cheap, tolerant of long runs, and supported by almost every fan coil controller, lighting relay and blind actuator installed in the last twenty years.

The typical wiring inside one meeting room looks like this:

RS485 is a two-wire differential bus, normally run as a daisy chain from device to device with termination at the far end and a shared reference. Three details account for most of the faults on site. The first is topology: a star wired from one junction will work on a bench and fail in a riser. The second is addressing: every device on a Modbus segment needs a unique address, and duplicate addresses are usually set by whoever installed the controllers. The third is grounding, because a bus that references earth at both ends will carry current it was never meant to carry.

The alternative is to put a gateway in the ceiling and keep the panel purely IP. That is the cleaner design in a new building with a modern building management system, and it is the right answer when the panel is supplied by a third party who will not touch a serial bus. RS485 earns its place in three situations: a retrofit where the room already has a bus and no gateway, a site with no BMS at all and no intention of adding one, and a room where control has to keep working when the network is down.

4. Sizing the PoE Budget

Two standards cover almost every wall panel. 802.3af guarantees about 12.9 W at the device; 802.3at guarantees about 25.5 W. The panel draws well inside the first figure, which means a standard access switch will run it — but the switch still has to have the budget across all ports.

One habit saves a great deal of trouble later: label the port, not just the cable. When a panel goes dark two years after handover, the person sent to fix it needs to know which switch and which port, and a label at both ends turns a two-hour search into a two-minute check.

5. Mounting Height, Back Box and Cable Route

The panel is read standing up, often while walking past, so height matters more than it does for a desk terminal. A centre height of roughly 140 to 150 cm above finished floor puts the screen at eye level for most adults without forcing anyone to stoop. Where the building has a mix of seated and standing users, the lower end of that range is easier for wheelchair users.

• ◆ Mount outside the door, on the handle side. A panel on the hinge side is hidden by the open door at exactly the moment someone is looking for the room.
• ◆ Allow a recess deep enough for the connector. A standard 86 mm box is often too shallow once a shielded RJ45 with a strain relief boot is plugged in. A 45 mm deep box, or a panel with a recessed rear compartment, avoids a panel that sits proud of the wall.
• ◆ Leave a service loop. Twenty centimetres of slack inside the wall lets the panel be removed and reconnected without cutting and re-terminating.
• ◆ Keep it out of direct sun and away from diffusers. A panel in a glazed corridor can run noticeably warmer than the room, and a panel under a ceiling diffuser collects dust along the upper edge.
• ◆ Match the mounting pattern to the wall. Drywall needs a proper anchor or a stud; a metal stud wall needs a backing plate; a glass partition needs a bracket designed for glass rather than adhesive.

6. What to Specify on the Panel Itself

The reference unit in this guide is deliberately modest, because a booking panel does not need more. The table below is the configuration that matches the job:

Two of those rows are worth arguing about. The first is housing material: a metal front takes knocks in a public corridor and does not flex when someone presses the screen, which matters on a panel that is pressed hundreds of times a day. The second is the interface terminal. If the room has no serial devices at all, a purely IP panel is simpler and cheaper; if it does, buying the serial option at the start costs far less than adding a gateway later.

7. Failure Modes Worth Designing Out

Four faults account for most of the calls a facilities team receives about booking panels, and each has a fix that belongs in the configuration rather than the maintenance contract.

• ◆ Blank or rebooting screen. Nearly all of them come down to power: a switch port near its budget limit, a long run on thin cable, or a PoE injector shared with something else. Check the port's power draw before replacing the panel.
• ◆ Booking app frozen on screen. Kiosk mode plus a watchdog that restarts the app when it stops responding. Set it up before deployment; it cannot be configured remotely after the panel is sealed to the wall.
• ◆ Times that drift. A panel that is four minutes behind the calendar will show a room as free while someone is walking into it. Point the panel at an NTP server and confirm the time zone is set in the image, not by hand.
• ◆ Ghost touches and a dirty screen. A capacitive panel needs a clean, dry surface and a stable ground reference. Glass cleaner applied directly to the panel, or a metal frame bonded to nothing, produces exactly the phantom presses that get reported as a hardware fault.

8. The Short Version

Specify the wall before the panel. PoE gives one cable for power and data, puts the panel on the same protected supply as the switch and removes the adapter from the corridor — but it does not extend the 100-metre channel, and it draws on a shared switch budget. Add RS485 when the room already has a serial bus and you want the panel to control HVAC, lighting or blinds without a separate gateway; leave it out when the building has a modern IP-based management system. Mount the panel outside the door on the handle side at about 140 to 150 cm, give the connector a deep enough box, and configure a watchdog and NTP before the panel goes on the wall. Do those five things and the panel becomes the part of the project nobody has to think about again.

Our PoE tablet and meeting room display collection covers the wall panels used outside booking rooms, and the VESA-mount Android panel range is the alternative when the wall cannot take a flush box. If you are also fitting out the room itself, the BVS-QR101 V3.0 page lists the interface options in full. Tell us how many rooms you have, what controls them today and what cable already reaches the wall, and we will tell you which configuration fits.