Glimera Fleet — how-to for the Route manager (the operator's master login)
You run a route of stores: you place the kits Glimera ships you, name the machines, watch the money, collect, and manage your own people. Your login is the master of your operator. You see only your own stores, kits, machines and users. The other guide: Store login & area manager. A G-Stick is the Glimera device that plugs into a machine's SAS port (called a board in older notes).
Two looks, chosen at sign-in and switchable from the sidebar: Simple (Dashboard, Locations, Live, Inventory, Revenue, Revenue by Date, 0 Revenue, Exceptions, Collections, Kits, Settings, Help) and Complex (adds Machines & G-Sticks, 17 Reports, Users). Same data, same buttons. You and your area managers land on Revenue. Help in the menu opens this guide; your store logins' guide is a tab away.
0. Signing in: your password, and the optional six-digit code
Two-factor sign-in is optional for every login — Glimera, route managers, area managers and store logins alike. It is off unless the person turns it on for themselves (Change password → Two-factor sign-in) or their route manager (or Glimera) requires it for them (Users → Edit → Require two-factor sign-in). With it on, each sign-in asks for a six-digit code from an authenticator app (Google Authenticator or Microsoft Authenticator, free) after the password. The first time, the portal shows a QR code: install the app, tap +, scan, type the six digits. The code changes every 30 seconds; if one is refused, wait for the next (the phone's clock must be automatic). For a login that uses it, until the code is in the cloud shows that session nothing — a stolen password alone opens an empty portal. Once someone has set the app up, they are asked every time until they turn it off under Change password.
Lost or replaced phone. Users → Edit → Reset two-factor (or the store page → Store logins → Reset two-factor). Their next sign-in shows the QR code again. For your own login, ask Glimera.
1. Your people
Users (Complex) or Settings → Users (Simple) → + Add user. Two presets:
- New login — full name, a user name (e.g.
sam.store— it is how they sign in), a password, the role, and optionally an email (only where a password-reset link goes; no email → they add theirs at their first sign-in) and a phone. Logins made before user names keep signing in with their email; give one a user name under Edit and it signs in with that instead. - Someone who already has a login — a person who already signs in for another route manager (a store owner with shops under two route managers, a partner who runs two routes). Type their exact user name or email, pick the role and the stores here. They keep their password and choose your company from the Working for menu in the sidebar. Their role and stores here are yours to change; their name, sign-in, password and two-factor are theirs (ask Glimera). Remove from this company takes them out of yours only.
The roles:
| Role | Sees | Can |
|---|---|---|
| Master (you, or a partner) | everything of the operator | everything below, plus stores, users, settings, share % |
| Area manager | the stores you tick | name machines, set SAS settings, Read now, Kill / Live, record collections, acknowledge alerts, store logins — but not move G-Sticks: putting a G-Stick on a machine, taking it off, swapping, replacing, a machine from inventory onto a G-Stick and removing a machine from the store are yours only |
| Store login (the owner) | the locations you give it — one owner, several shops, one login | Revenue, Revenue by Date, 0 Revenue, Exceptions, My locations, Help for those locations, read-only; changes only its own password; never sees setup codes or WiFi passwords |
Untick Active to stop someone signing in without deleting anything. Share the login by hand; there is no invitation email. Store logins also live on the location page → Edit → Store logins: reset a password, add an existing owner to this location (one of yours, or a login from another route manager by its exact user name or email), or create a new login (user name + password). Your area managers can do the same for the stores they look after: the store page → Store logins — create, add existing, reset a password, remove. A login can also be made while creating the location: tick Create a login for the store owner on the new-location form and give it a login name and a starting password. At their first sign-in the owner adds their name and email and can choose their own password. A new location needs no time zone (New York), kit WiFi or notes — the kit you pick brings its WiFi (a store with no kit gets its own, GLM-<code>), and its G-Sticks are tied to the store the moment it is placed.
2. Settings (once)
Settings: default revenue share % for new stores, default revenue basis (Cash: cash in − cash out − handpays unless told otherwise), after how many minutes a silent G-Stick counts as offline (10 by default), how long raw meter readings are kept (daily totals, collections and history are kept for ever).
3. Assign a kit to a location, then machines to its G-Sticks
Glimera assigns you a kit: one router plus its G-Sticks, each G-Stick labelled with its slot (B001, B002, …). You cannot create kits; Kits lists yours with their location, address, online/offline and a button: Assign on a kit with no location, Unassign on a placed one.
- Kits → Assign. A searchable list: + Add a new location first, then your locations without a kit, then the ones that already have one (this kit becomes their second kit; the store keeps its router). Only an active location can take a kit. Pick one and confirm — Kit K200 is being assigned to ….
- G-Sticks → machines. The G-Sticks land at the location as G-Sticks (named by kit and slot, e.g. K200 B003) with no machine on them yet — they are never renamed "Machine 1, 2, 3" for you. A G-Stick becomes a machine only when you put one on it, from either direction:
- On the location page, press Place from inventory: pick a machine from your inventory (§3a) and, optionally, the G-Stick it sits on. Leave the G-Stick blank to just bring the machine to the store and pick a G-Stick later (Assign G-Stick on its row).
- Or on a G-Stick's row (badge G-Stick · no machine) press Assign machine and pick the machine. On the kit page the same Assign machine button works one G-Stick at a time: the Machine box searches your inventory by name or number — pick one, or + Add a new machine… right there. A new machine needs only its name (from the machine-model list, or a new name you add), the SAS Host port (Host 1 unless you press Change) and a SAS address that numbers itself from 1 at the location (Change to override — it must match what the cabinet's own menu says). The location is the kit's and cannot be changed. The machine leaves the inventory for this location and takes that G-Stick; its name and number follow. You can leave G-Sticks without a machine and come back later from the kit page. Done finishes.
- Swap machine puts a different inventory machine on a G-Stick (the old one goes back to inventory). Remove machine sends the machine back to inventory and leaves the G-Stick at the location. Inventory then shows the store it came from under Last location.
- Unassign takes the kit off the location — only once no G-Stick carries a machine ("please remove the machines first"). The G-Sticks go back into the kit, still paired.
3a. Machine inventory
Inventory is every machine you own that is not on a G-Stick. A machine taken off a store (Remove machine, Remove from store) comes back here, and Last location shows the store it was last at and since when (click it to open the store); its page says In inventory · last at …. A machine that was never at a store shows —. Add Machine: pick the machine model from the list (87 names; type a new one and press Add "…" as a new model if yours is missing) — the name fills in from the model, and the model sets the SAS settings the cabinet needs. Each machine gets a number (M1001, M1002, …). Click a machine to edit its name or model, or delete it. Copy settings from at the top of Add Machine takes every setting from a machine you already have (or a game): model, host port, address, cable, timing — give the new one its name and change only what differs. The SAS settings are all on the form as buttons: Host 1–4 and the port label, address, Straight / Null-modem, the handshake bridges, the byte gap (3000 for a Banilla), the poll CRC and the denomination.
Machine polling: Live reads every report interval (30 s); Live, instant also listens to the machine and reads the moment money moves (bills and cash-outs show within seconds; use it where you want the Live view to feel live); hourly / every 12 h / every 24 h keep the line quiet between reads, for cabinets that mind.
On site: plug the router into the store's internet, power it, mount each G-Stick on its cabinet (DB9 to the cabinet's SAS port, USB power). The G-Sticks join the store's WiFi by themselves and the store locks to that router on the first report. Locations → Edit changes anything about a location — address, share, polling, time zone, notes, the store logins and their passwords — and Active on/off (an inactive location keeps its history and takes no kit). The WiFi name and password are Glimera's: they come with the kit, and only Glimera changes them (you see the WiFi name, never the password). A location's own number (L1001…) is shown there; the code you type is optional.
4. Name the machines and set them up
On the store page press Edit on each row:
- Name it after the cabinet ("JVL by the door").
- Model / preset — pick the make. This is not cosmetic: the preset fills the SAS timing the cabinet needs (a Banilla Fusion needs a 3000 µs byte gap and answers nothing without it), the port, the cable and the bridges.
- SAS address and SAS host port as the cabinet's own menu says (Banilla: COM2, address 1; COM1 only echoes). Asset number, denomination if not 1 ¢.
The G-Stick applies the settings on its next report. Read the row's status:
| Status | Meaning | Do |
|---|---|---|
| no G-Stick yet | the machine record has no G-Stick | Assign G-Stick — pick the G-Stick that is plugged into it (see below) |
| not paired | the G-Stick is on the row but lost its pairing | a kit G-Stick pairs again by itself; if it stays like this, call Glimera |
| setting up · finding the machine | the G-Stick is trying every SAS address for the cabinet (a newer G-Stick does this by itself) | nothing — give it a minute; it sets the address, the timing and the game on its own, and the machine page's Found by the G-Stick card shows what it found |
| no answer at any address | the G-Stick tried every address twice and heard nothing | not a setting: the cable, the port on the cabinet, a null-modem, or the operator door |
| online · no meters yet | the G-Stick reports, the cabinet has never answered | Edit: model preset, host port, address; then the cable / bridges (wiring card) |
| online / idle / in play | reading | nothing |
| wrong router | the G-Stick is on a WiFi that is neither its kit's nor the store's (the row and the alert name both) | put the store's router back on its WiFi name (Store WiFi & G-Sticks tab) — Glimera has the password; a replaced router with the same WiFi name needs nothing; otherwise call Glimera |
| offline N min | no report for longer than the offline setting | router power / internet; the G-Stick rejoins on its own |
G-Sticks come from Glimera, set up and ready. You never set a G-Stick up yourself — there is no Set up G-Stick for a route manager. A G-Stick Glimera sends joins the store's WiFi by itself and shows up at the store; plug it into the machine, then on the machine's row press Assign G-Stick and pick it. The list holds every G-Stick you can use:
- Free G-Sticks — in the kit, in inventory, or at this store with no machine on it (G-Stick · no machine). A G-Stick that has already started reading the machine it is plugged into is listed too (reading a machine that has no name yet); what it read so far stays under the G-Stick's own name until the next collection.
- On another machine here — a G-Stick you unplugged from one machine and plugged into this one. Picking it shows Move G-Stick here: the other machine keeps its name, its history and what it made this period, and waits for a G-Stick in turn. No collection needed first.
If the list is empty, the dialog says so: every G-Stick of yours is on a machine. Ask Glimera for a G-Stick, or take one off a machine that no longer needs it with Remove G-Stick.
A G-Stick Glimera set up again (it came back from the bench, or was reinstalled) arrives as a G-Stick with no machine on it, even if it used to serve one: the machine it served keeps everything and waits (its Activity says set up again from scratch). Put the G-Stick on the machine it is plugged into with Assign G-Stick.
Read now on any row asks the G-Stick to read the cabinet right away and shows what happens.
5. Day to day
- Live — one store, every machine as a card, money in and out as it happens, weak-signal and reboot warnings. Click a card to enlarge it.
- Revenue — every store since its last collection: cash in, cash out, net, your share. Revenue by Date for a range; 0 Revenue lists machines with no cash in for 48 hours (with why: offline, never read); the store and machine names are links.
- Exceptions — every machine that is not delivering numbers right now, grouped by store with the reason and what to do: no G-Stick yet, not paired, wrong router, offline N h, online · no meters yet. Empty means every machine at every store is reporting and reading. (Complex: a Reports tab.)
- What happened to a machine — offline, wrong router, meters reset, rebooted on its own, pairing refused — is on its machine page (Activity / Recent Activity); a store's on its store page (Complex: Activity & alerts, where you acknowledge what you have seen). The Dashboard counts the open ones.
- Reports (Complex): locations, by day of month, comparison of two periods, machine history, missing data, inactive locations and machines, zero revenue, data dump, due now, collections — every table exports to Excel.
- Credits on machine with a "≈" — that machine has no credits meter, so the credits are worked out from its meters. If they do not match the machine's screen, press Correct next to them on the machine's page and type what the screen shows (for example 0.75). Revenue does not change. A full cash-out sets them to $0 by itself.
5a. Turning machines off and back on
You can take any of your machines out of play from the portal, and bring it back, without going to the store.
- One machine: open the machine's page, press Kill, and confirm. Players see a lockout on the floor. Live on the same page brings it back.
- A whole store: on the store page, Turn machines off next to Mark collected. Restart machines brings them back.
Nothing is lost: the G-Stick keeps reporting and no meters are cleared. The Machine lock banner on the machine's page shows who turned it off and whether the G-Stick confirmed it.
A machine Glimera turned off stays off. Glimera can also turn machines off (for example when a subscription is unpaid). Such a machine shows Off by Glimera instead of Live, and Restart machines leaves it off and tells you so. Only Glimera can turn it back on: call Glimera.
Your area managers can do the same on the stores they hold. Store logins cannot.
6. Collections
On the store page → Mark collected. The portal snapshots every machine's period, records who collected and when, and starts a new period from zero. Enter the amount actually collected if it differs from your share: the difference is the balance that carries to the next pickup (a pickup with no amount counts as collected in full). Collections lists every pickup per store; open one to correct an amount.
Collection sheet
Right after Mark collected the portal opens the collection sheet — "Game Meters at Period Close" for the store: every machine's start and end meters, what went in and out, its net and hold %, the totals, your share, the balance carried in (Adj.), what is due, what you collected and the balance carried forward, and the machines' start of the new period.
- Download PDF saves it (
Collection L001 2026-10-21.pdf); Print prints it. - Share (on a phone) sends the PDF itself — WhatsApp, text or email.
- Send to store: Text the store / Email the store open a message with the totals to the store's phone or its store logins' emails — attach the downloaded PDF.
- Every pickup keeps its sheet: Sheet next to it in Collections, Reports → Collections and the store's collections opens it again, exactly as it was (resend it any time). Correcting what was collected on that pickup shows on its sheet.
A machine with uncollected play cannot be removed or have its G-Stick taken off — collect first. Money never disappears with a machine.
7. Changes on the floor
Only you move G-Sticks. Everything in this table that puts a G-Stick on a machine, takes it off or moves it — and removing a machine from a store — is the route manager's alone: your area managers, your store logins and Glimera do not get these buttons, and the cloud refuses them too.
| You want to | Where | What happens |
|---|---|---|
| A G-Stick set up with a machine code should count on the kit | kit page → Add a G-Stick already at the store | it keeps its machine, name and pairing; it now counts on the kit row and behaves like a kit G-Stick. A slot must be free |
| Put a free G-Stick on a machine, no cable | store row → Assign G-Stick (or kit page → Assign to machine) | the G-Stick keeps its pairing and reports as that machine within a minute; the same operator only |
| A G-Stick was moved by hand to another machine at the store | that machine's row → Assign G-Stick → the G-Stick under On another machine here → Move G-Stick here | the G-Stick reports as this machine within a minute; the machine it left keeps its history and money and waits for a G-Stick |
| Take a G-Stick off, keep it for later | store row / machine page → Remove G-Stick | back to the kit or inventory, still paired; the machine keeps its history and waits for a G-Stick |
| The G-Stick died | machine page → Replace G-Stick (or Remove G-Stick to keep it), and call Glimera for a new G-Stick | the broken G-Stick stops reporting; the machine keeps everything and waits; a spare or the new G-Stick goes on with Assign G-Stick |
| Two G-Sticks on the wrong cabinets | machine page → Swap G-Sticks | nothing resets, each G-Stick is told which cabinet it reads |
| A new cabinet under the same G-Stick | machine page → Replace machine | the old machine keeps its history and revenue so far; the new one starts at zero |
| A machine leaves the store | kit page / G-Stick row → Remove machine | the machine goes back to inventory, where Last location shows this store; the G-Stick stays at the location for the next machine (refused with uncollected play — collect first) |
| Another machine under the same G-Stick | kit page → Swap machine | the G-Stick takes the inventory machine you pick; the old one goes back to inventory |
| A G-Stick was lost or stolen | machine → Edit → Unassign & revoke | it can never report again |
| The WiFi password changes | call Glimera — only Glimera changes a kit's or a store's WiFi | Glimera saves it on the kit; G-Sticks receive the new password first and switch when the router changes; then the router is changed |
| The router is replaced (same WiFi name and password) | nothing — the G-Sticks join it | G-Sticks are judged by the WiFi name, not the router; Router replaced… only clears the recorded address |
| A kit moves to another location | remove its machines, Kits → Unassign, then Assign | the G-Sticks stay paired |
8. Taking a store apart
Bottom up, always: Mark collected → Remove machine on each G-Stick → Kits → Unassign → Delete location. Each dialog lists what is still in the way, each item a link. Edit location → Active off keeps a closed store's history without deleting anything.
9. Quick fixes
- A user cannot get past the six-digit code (lost phone): Users → Edit → Reset two-factor. They scan a new QR code at the next sign-in.
- **A machine's Activity says Firmware update:** Glimera sent your G-Sticks a new build over the air. Each G-Stick restarts into it within a minute or two and reads its machine again; the machines keep running and nothing is lost. Nothing to do on your side — a G-Stick that could not take it says why on the same line, and Glimera sees it too.
| Symptom | Fix |
|---|---|
| A bill takes 30 s to show | the store's Machine polling must be Live, instant |
| Live says "checking every 5 s" | the page polls until the first pushed report arrives; Refresh fetches now |
| "reading… N s" for more than 30 s, then "no answer" | the note says which: the G-Stick is offline, or the machine is not answering on SAS |
| "weak WiFi signal" | below −78 dBm: router closer or higher, 20 MHz channel width, a clean channel, antenna out of the metal |
| "rebooted on its own" | watchdog = it hung (SAS cable / signal); brownout = power dipped (adapter, cable); could not reach the cloud for 10 minutes = the router's internet |
| Assign G-Stick shows nothing to pick | every G-Stick of yours is on a machine — the dialog says so. Ask Glimera for a G-Stick, or Remove G-Stick on a machine that no longer needs one |
| An alert says a machine is reading a different cabinet now | its G-Stick was moved to another cabinet. Open the machine the G-Stick is plugged into → Assign G-Stick → Move G-Stick here, so the money is counted on the right machine. If the cabinet's game board was replaced instead, nothing to do |
| A yellow or red Subscription due / past due banner on every page | your Glimera subscription is paid through the date it names; from the day it names the portal closes for you and all your logins. Call Glimera and settle it — the banner goes the moment the date is extended |
| Subscription past due is all the portal shows | the subscription ran more than 7 days past its date. Your machines kept reporting and nothing is lost; once Glimera extends the date everything is back exactly as it was |