Menu Board Media Players That Stay Online: Installation in Richmond, TX 77407

A menu board player is a network device before it is a video box

Day to day, a menu player behaves less like a video source and more like an unattended computer that must reach the internet, keep correct time and restart cleanly after every outage.

Whether it is a separate box or a system-on-chip inside a commercial display, each player leans on the network for five things:

1. A stable address. Ideally a DHCP reservation, so the player keeps the same IP address after a power failure and management tools can still find it.
2. Name resolution. Working DNS, so the player can locate its content platform.
3. Outbound access. Most signage platforms connect out over HTTPS, and some need additional ports that are listed in the platform’s documentation.
4. Correct time. Every schedule depends on the player’s clock, and the clock depends on reaching a time server.
5. Bandwidth at update time. A refreshed menu package with video can reach hundreds of megabytes per player, and several players downloading at once can swamp a small business connection in the middle of service.

When one of these is missing, the display works perfectly while the menu on it quietly goes stale. That is why diagnosing a menu board almost always starts in the network closet rather than at the screen.

What we confirm on the network before a player is mounted

None of this needs exotic gear: a business firewall and a VLAN-capable managed switch cover most single-location restaurants.

Keep the menu boards off the payment network

Restaurants that accept cards fall under the Payment Card Industry Data Security Standard (PCI DSS). One of its central ideas is segmentation: systems that never touch cardholder data should be separated from those that do, which keeps the scope of compliance small. A menu player plugged into the same flat network as the POS terminals has no reason to be there, and it runs software that updates itself from the internet.

We usually find one of three arrangements in Richmond restaurants:

• The POS vendor manages the router. Common with franchise concepts and many independent POS providers. The vendor may already have a designated non-POS port or VLAN, so we ask for it instead of grabbing any open port.
• The owner manages a business router. We set up a separate VLAN or a physically separate network for signage, with rules that allow internet access but block the POS subnet.
• Only the provider’s gateway. Some new tenants open with nothing but the internet provider’s box. That can carry a pilot, but we recommend a proper business firewall or a VLAN-capable switch before more devices pile onto it.

We never reconfigure a POS vendor’s equipment without them on the call; they know which ports their terminals depend on.

Opening in a new 77407 shopping center: timing is the hard part

Many restaurant openings in 77407 happen in newly built pad sites and inline suites around Aliana, Grand Mission and the Grand Parkway corridor. New construction is easier to cable than an old building, yet it brings scheduling problems of its own.

• The internet circuit arrives late. In a brand-new center, the provider’s installation can trail the tenant’s opening date. We can preload content over a temporary cellular link so the boards are right on day one, then move them to the permanent circuit.
• The closet is at the back. Inline suites typically put the telecom demarcation point and the office at the rear, while the menu wall faces the front counter. Those runs can easily reach 80 feet or more, well within Ethernet’s 100-meter (328-foot) limit but far beyond sensible HDMI.
• The ceiling closes before the screens arrive. If cable is not in before the drop ceiling or drywall goes up, installing it later gets slower and messier. We coordinate low-voltage rough-in with the general contractor, even when the players show up weeks afterward.
• Landlord rules. Newer centers often publish tenant construction rules covering roof penetrations, noisy work hours and access to shared telecom rooms, and we document any cable that leaves the suite.

Clocks, dayparts and the breakfast menu that won’t leave

The complaint we trace to setup more than any other is a schedule firing at the wrong moment. The causes are usually mundane:

• Time zone left at the default. Players shipped from a warehouse may be set to UTC or Pacific time. Richmond runs on Central time, and the player, the CMS schedule and any display-level on/off timers all have to agree.
• Time sync blocked. Some firewalls block NTP by default. The player’s clock then drifts by seconds, then minutes, until dayparts visibly slide.
• A fixed offset instead of a named zone. A player set to UTC minus six rather than to Central time is an hour off for the half of the year when daylight saving applies.
• Two schedules in conflict. Displays carry their own power timers. If the display is told to shut off at 10 p.m. while the CMS expects to show late-night items until midnight, the display wins.

During commissioning we compare each player’s reported time against a reference, confirm the zone by name, and walk the manager through every scheduled transition.

When the internet goes down: cached content and self-recovery

A properly configured player keeps playing from local storage through an outage, but not every setup behaves that way, so we test it.

• Web-page menus. Some systems simply open a web page in a browser on the player. If the connection fails and nothing is cached, customers see a browser error. During commissioning we unplug the network and watch what your platform actually does.
• POS-linked items. When prices or sold-out flags come live from the POS or a cloud feed, decide in advance what the board shows if that feed fails: the last known values or a static fallback menu.
• Storage limits. Players with little storage may purge old content before the new package finishes downloading. Video-heavy menus need a player sized for them.
• Recovery after power loss. We set players and displays to power back on by themselves and resume playback without anyone reaching for a remote, then prove it by pulling power to the whole wall.

How an EVOTECH installation unfolds in a Richmond restaurant

1. Planning call. Confirm the signage platform, player models, screen count, and who manages the router and the POS network.
2. Site survey. Walk the suite, measure from the closet to each display, check the ceiling, confirm a receptacle at each display location and photograph the existing network gear.
3. Network design. Assign the signage segment, reserve addresses, pull the required outbound ports from the platform documentation and agree with the POS vendor on where signage connects.
4. Cabling. Run and terminate Cat6 to each player position, test every run and label both ends with the screen it feeds.
5. Mounting and control. Mount players with ventilation clearance, add surge protection and wire up serial or IP display control where the platform can use it.
6. Enrollment. Register each player to your account, name it by position, such as Counter Left or Drive-Thru Order, and confirm it pulls the right content.
7. Schedule and failure tests. Verify time and dayparts, then disconnect the network and the power to confirm unattended recovery.
8. Handover. A one-page record listing player names, reserved addresses, switch ports, cable labels and platform support contacts.

Doing it yourself, calling a pro, and what changes the quote

When plugging it in yourself is fine

One or two screens with built-in players, an Ethernet jack already behind each one, and a platform that activates with a simple code: many owners handle that themselves. Read the platform’s network requirements page and confirm the time zone before you walk away.

When a low-voltage contractor earns the call

New cable, a POS network you do not control, a multi-screen wall, a drive-thru board, an opening date that cannot slip, or a brand that requires documented commissioning are all sound reasons to have it installed.

What changes the quote

• The number of screens and players
• Cable runs, their length, and whether the ceiling is still open
• Network equipment needed, such as a managed switch, firewall or VLAN configuration
• Coordination with the POS vendor, the brand and the general contractor
• A temporary cellular connection for an opening ahead of the internet circuit
• After-hours or overnight scheduling

Setup errors we are called in to correct

• Players parked on the guest Wi-Fi alongside customers’ phones
• No address reservations, so display control breaks after every outage
• The CMS account opened under a former employee’s or installer’s email
• Content downloads scheduled for the lunch rush
• No record of which player drives which screen

Related services

Frequently asked questions