Recommended
equipment.

Connect each table camera to a managed PoE switch on a network that both the assigned RF table and security recorder can reach. Give it a stable IP address and a dedicated streaming account.

1. Enable a continuous H.264 RTSP stream. Start with a fixed resolution and 25/30 fps where supported, a 1–2 second keyframe interval, and approximately 8–16 Mbps. Adjust after checking the actual image quality.
2. In RF, open Command Center → Hands → your table → Table controls → Recording. Configure the camera source as RTSP, enable it, and assign the intended vision camera the wide role.
3. Calibrate the fixed view with real cards, chips and venue lighting. Check all seats, moving hands and chip stacks, plus recovery after a camera or network restart.
4. Record a hand, render a clip, play it back and verify its storage delivery. Turn on Upload raw footage with the master if you also want RF to archive the source recordings remotely.

Axis, after creating an RF stream profile:rtsp://CAMERA_IP:554/axis-media/media.amp?streamprofile=RF

RF needs a readable view of the table, not just general room coverage. Security NVR recording and RF clip storage are separate. Keep the view fixed, test simultaneous NVR and RF connections, and retain RFID inputs for concealed cards.

Axis stream documentation ↗

1. Use the recommended ASUS NUC 15 Pro configuration with RF OS Display. Connect each player to its TV using HDMI and wired Ethernet. Select the RF HDMI input on the TV.
2. Install RF OS Display and connect to your venue’s RF OS server. Register and name every screen by its physical location. For browser pairing, enter its six-digit connection code in the venue’s Displays controls.
3. Choose each screen’s table status, tournament clock, seating, floor plan or other available RF view in operator-web.
4. Configure automatic startup and AC power recovery, disable sleep and screensavers, and check that the screen retains its identity after reboot.

One player per TV enables independent content. An HDMI splitter mirrors the same output. Switching between RF and sports/cable also needs TV input control or a separate AV control system.

Install the printer’s Windows driver and configure the Epson roll-paper profile to 80 × 200 mm, 100% scale, no browser headers or footers, and the appropriate cutter setting. The documented Epson profile has a 72 mm printable width.

Use USB HID keyboard mode on scanners, enable QR decoding, select a US keyboard layout and add an Enter suffix. Test a phone-screen QR code and an actual printed ticket in RF’s scanning field.

RF OS Client’s current silent-print workflow follows the OS default printer. Keep the Epson as the desk default; use deliberate printer selection or a separate issuance station/profile for Magicard jobs. Test duplex orientation and printed-code readability.

Keep thermal paper, spare cables, scanner stands, the correct Magicard ribbons, CR80 blank cards and cleaning kits in stock. Add a webcam and even lighting for player photos.

1. Complete merchant onboarding with RF. Confirm the account, supported checkout workflow and country before ordering hardware.
2. Choose an S710 for each handheld payment point or a T600 for each fixed counter. Order through Stripe for your RF-connected merchant account, adding the hub, dock or case needed for that reader.
3. Connect the reader to Wi-Fi or use a Stripe Reader Hub for wired Ethernet. Keep the reader powered for software updates.
4. Have RF register and pair the reader to the correct venue checkout, then verify the checkout workflow before opening.

Stripe device details ↗