Real, virtual and simulated devices
Real hardware isn't in the loop yet, so two stand-ins exist. They solve different problems.
| Real device | Virtual device | Fleet simulator | |
|---|---|---|---|
| What it is | The NS-C1 hardware | An Android app that acts as one device | A program that generates a whole fleet |
| Talks to AWS | Yes, over LTE-M | Yes, exactly like a real device | No, it writes a dataset |
| Location | Its own GNSS or cell tower | The phone’s GPS | Scripted owners and routines |
| ID | 8BFBC681DFDFACE7 |
VIRTUAL-<12 hex> |
emul-001 … |
| Used for | The product | Demos, and walking a flow end to end on dev | Scoring models, replaying the pipeline |
| State | Waiting for hardware | Working | Working |
The virtual device
The app shows a 3D model of the NS-C1 with its real LEDs and sounds. You can draw, plug it in, swap pods, lose signal or carry it around, and it sends the matching messages to AWS in the firmware’s format. It obeys lock commands through its shadow, and shows a “Scan to unlock” QR code while it’s locked.
Because it uses the same topics, rules and policy as a real device, everything after IoT Core is tested for real: ingest, models, the trust ladder and the admin.
The fleet simulator
It plans owners with homes and routines in Montréal, gives each a scenario (normal life, a weekend trip, a vacation, a handoff to a new owner, lingering near a school), and simulates 30 days of messages. It follows the firmware spec’s timing and accuracy. The same seed always gives the same fleet.
Because it knows which devices really changed hands, it can tell us how often a model is right. See Models.