Skip to content

Cafe · food service

Cafe Neulbyeot — a day run on three displays

A menu board above the counter, a pickup number board and a window screen facing the street. The three switch by daypart on their own, and sold-out, price, queue numbers and notices set from a phone show up on all three at once.

Example setup

This is a fictional cafe, not a real shop or customer installation. The name Cafe Neulbyeot was made up for this case.

3displays (1920×1080 landscape)

5dayparts — morning to closing

1phone console (manager, barista)

22tags (all memory tags, no device links)

The fictional site

Cafe Neulbyeot is set up as a small neighborhood cafe, open 07–22 on weekdays and 08–22 on weekends. Staff are a manager and one or two baristas, with no time to sit at an office PC to edit screens.

Two things are set up front. Schedule rules switch screens by daypart, and what changes day to day (sold-out items, prices, queue numbers, notices) is changed with one tap on the phone console.

The picture is the store view screen bundled with the sample. The three spots show the actual display pages scaled down, so you can see the whole store change on one screen even without displays.

Store view — illustrated cafe with the menu board, pickup board and window screen — The sample's store view (afternoon). The buttons on the right change sold-out, prices, queue numbers and notices. (Korean UI)

Layout

A display is any browser that opens the LinkVion screen address (a smart TV browser, a small PC, a kiosk). One gateway holds the schedule and values; displays and the phone join over the store network.

1
Menu boardAbove the counter · group 'Menu'Daypart feature and six item prices. Sold-out band on the item, last-order notice at closing.
2
Pickup boardWall next to pickup · group 'Pickup'Ready number in large type, the last three called numbers, and a daypart tip band.
3
Window screenFront window, facing the street · group 'Window'Daypart promotion for passers-by and today's coffee price. Outside hours, when the cafe opens next.
G
LinkVion gatewayBack shelf (a PC or LinkVion Box)Holds schedule rules, hours, tag values and the daypart script, and serves all three displays.
P
Phone consoleManager's or barista's phone browserSold-out, prices (number pad), next number, notices, fire test.

Floor plan of the virtual cafe (illustrative, not a wiring diagram).

Daypart schedule (weekdays; opens at 08 on weekends)

Time	1 Menu	2 Pickup	3 Window
07–11 Morning	Morning set (coffee + croissant) 6,900 won	Queue + morning set tip	Morning set for commuters
11–14 Lunch	Lunch set 9,500 won	Queue + lunch set	Lunch set
14–17 Afternoon	Happy hour americano 1,000 won	Queue + happy hour	Americano 1,000 won
17–21 Evening	Today's dessert	Queue + dessert	Strawberry latte promo
21–22 Closing	Last order 21:30 band	Queue	Closing soon
22–07 Closed	Off (outside hours)	Off (outside hours)	See you tomorrow · opening hours

When an item sells out the feature spot moves to the next candidate, e.g. evening strawberry latte → cheesecake → decaf.

The day

Recorded scenes

Each video shows the three displays on top, and the store view and phone console below. The panel at the bottom right follows what is happening (captions are in Korean).

Scene 1 · 07:00 → 22:00 · 32 s

The day — all three switch together with no one touching them

What was done: Only schedule rules are set: five dayparts per group (menu, pickup, window), plus operating hours for the menu and pickup groups.
Result: Before opening the menu and pickup boards are off and only the window shows a notice. At morning all three come on, then switch through lunch, afternoon (happy hour), evening and closing without reloading.

Scene 2 · Evening · 9 s

Sold out — one tap on the phone

What was done: Strawberry latte runs out. The manager taps Strawberry latte under sold-out on the phone console.
Result: A sold-out band covers the item on the menu board, and the menu feature, window promo and pickup tip move to cheesecake.

Scene 3 · Evening · 11 s

Price change — set it on the number pad

What was done: Bean prices went up, so the americano goes from 4,500 to 4,800 won. On the Prices tab, tap the americano field and enter 4800 on the number pad.
Result: The americano field on the menu board and the window's 'today's coffee' line change to 4,800 won. Set prices are fixed text and stay the same.

Scene 4 · Evening · 13 s

Queue numbers — every tap on Next

What was done: Each time a drink is ready the barista taps Next number on the console.
Result: The pickup board shows the ready number in large type and pushes the previous ones to 'recently called'.

Scene 5 · Evening · 11 s

Notice band — on all three

What was done: The card terminal is down. Pick the Card payments paused notice on the console, then No notice once it is fixed.
Result: The same band appears at the bottom of the menu, pickup and window screens, then goes away.

Scene 6 · Any time · 16 s

Fire test — the emergency screen takes over all three

What was done: Tap Fire alarm test on the console and confirm. In a real installation the fire panel signal drives the same tag.
Result: The emergency rule (tag condition) overrides the daypart schedule and all three show the evacuation notice; turning the test off restores them.

Scene 7 · 22:00 · 9 s

After hours — screens that go dark and one that stays

What was done: Operating hours are set only for the menu and pickup groups. The window has an after-hours rule instead.
Result: At 22:00 the menu and pickup boards go dark, and the window shows 'See you tomorrow' with the opening hours.

How this was recorded: the sample was opened on a LinkVion 0.1.0.20 gateway (Mac), and five browser windows on one PC (three displays, the store view, a phone-sized console) were recorded at once and combined. Daypart scenes moved the schedule times to one-minute steps and fast-forwarded the waits. Taps were made by the recording tool; the yellow dot marks each tap.

Features used

Names follow the LinkVion feature list. No new code was written for this case; everything is in the sample file (screens, tags, script, schedule).

Area	Feature	In this case
Signage	Display registration, status, commands	Approve the code shown on each display browser in display management and give it a name, location and group.
Signage	Group schedules — hours, weekdays	Five daypart rules per group, separate weekday and weekend morning rules, operating hours for menu and pickup.
Signage	Emergency screen — button, REST, tag condition	An emergency rule that switches the three groups to the evacuation notice when `cafe.fire = 1`.
SCADA runtime	Multi-monitor windows, phone screens, master background, menu frames	A 430×932 phone console, and the store view's three spots are frames showing the real display pages.
SCADA editor	Controls — button, toggle, slider, number entry, navigation, confirm before write	Sold-out toggles, the price number pad, the next-number button and the fire-test confirmation.
SCADA editor	Bindings — value, color, visibility, rotation, level, flow, color by threshold	Price text uses value bindings; sold-out bands, notice bands and substitutes use visibility bindings.
Tags	Virtual (memory) tags — values without devices, initial values	22 tags: six sold-out flags, six prices, four queue numbers, notice, fire, daypart and so on.
Scripts	JavaScript scripts — control logic inside the gateway	Every second it sets the store view daypart from the clock, and shifts the called numbers on Next.
SCADA editor	Korean and English — one screen in two languages	Korean/English buttons on the store view and phone console; displays follow their account language.

Try it yourself

Sample title: Cafe with three displays — menu, pickup, window (virtual store)

This case was built from one sample bundled with LinkVion. Open it to press the same buttons yourself.

In LinkVion go to Project → Samples, press Open on the 'Cafe with three displays' card, then Open this project.
Without displays, open the first page Store view of the SCADA screen cafe-signage and use the buttons on the right.
For real displays, open /scada/view on each display browser (log in first if auth is on), and approve its register code in display management with the group Menu, Pickup or Window.
The phone console is the SCADA screen cafe-console; open it in a phone browser.

Three displays plus the store view and console make five concurrent screens. The trial edition allows fewer, so some screens show a limit notice.

Limits

What this case does not show

Not a real shop or real displays; the three displays were browser windows on one PC.
Queue numbers are entered by hand on the console. No POS link was made; one would need the POS to write the tag over REST.
Only six single items have price tags; set prices (6,900, 9,500, happy hour 1,000) are screen text.
The window screen is landscape; there is no portrait standee screen in this sample.
Display power control was not used; outside hours is shown as a black screen only.
Video ads and play logs (CSV) are not part of this case.