Live loom dashboard
Every loom at a glance: running or stopped, online or silent, today's output and the beam on it with how far along it is.
Sensor logging for weaving mills and plants
Every loom. Every beam. Every pick, logged.
Logger turns the sensors on your machines into live production — output per loom per day, warping beams tracked from warping to rollout, and one app for your whole team on Android and the web.
- Readings in seconds
- Days that start with your shift
- Android & web
79,604Picks today
4 / 4Looms running
3 + 2Beams on looms + ready
L-01runningWB-105
L-02runningWB-102
L-03offlineWB-103
1 sensorper loom — nothing else to wire
Per daycut at your shift start, not midnight
Per beamfrom rollout to the next beam
Every companyon one server, kept apart
Features
Everything between the sensor and the production report
Built for the people who run the floor: the numbers that matter today, and the history behind them.
Daily production per loom
Output per loom per day for any range, with loom and day totals. Copy it out as CSV in one tap.
Warping beam batches
Beam number, quality, ends and length for every beam you warp — ready, on a loom, or done.
Rollouts that hand over
Roll a beam onto a loom at a date and time. The next rollout ends it automatically, or finish it by hand.
Beam, day by day
What each beam produced on every production day it ran, down to the raw readings behind any day.
Counters done right
Your sensor reports a running counter. Logger works out the advance of every reading, and handles restarts and bad readings.
Your team, your roles
Managers add looms, beams and rollouts; viewers watch. Every company only ever sees its own mill.
Many companies, one admin
Run several mills on one server. Switch between them in the app, set each one's profile and shift start.
How it works
From a counter on a machine to a number you can act on
-
1
The sensor posts
Each loom's sensor sends its readings over the internet — a running counter and a status like running or stop. A retry never double-counts.
-
2
Logger works it out
Every reading becomes production: per loom, per production day, and per beam on the loom at that moment.
-
3
Your team sees it
Open the app on a phone, a tablet by the loom, or a browser in the office. The dashboard keeps itself up to date.
The loom workflow
Warp it, roll it out, watch it run
The way a weaving shed already works, without the register.
- Warp a beam — record the batch: beam number, quality, ends and length.
- Roll it onto a loom — pick the loom and the time. Whatever was on it hands over.
- Watch it run — its output grows reading by reading, with progress against the beam length.
- Next beam takes over — the moment the next rollout starts, the old beam is done and totalled.
WB-101on L-01 · done
98,102 picks of 90,000
| Production day | Produced | Readings |
|---|---|---|
| 06 Sep | 10,651 | 91 |
| 07 Sep | 33,117 | 288 |
| 08 Sep | 32,283 | 288 |
| 09 Sep | 22,051 | 197 |
Illustration
One app, everywhere
Android and the web, from the same sign-in
- Dashboard, looms, beams, rollouts, reports and sensors
- A desk layout with a sidebar on tablets and computers, tabs on phones
- Sign in with your email; managers edit, viewers watch
- The admin manages companies and users from the same app
For the people wiring it up
A plain HTTP API at both ends
Devices post JSON — one reading or a whole cycle — with the sensor ID and the time. Other systems pull readings out through a sync API that remembers where each one left off.
POST https://logger.jet66.cloud/v1
Content-Type: application/json
{
"readings": [
{ "sensor_id": "10001", "reading1": 452,
"reading2": 188233, "status": "running",
"ts": "2026-09-11 10:15:00" }
]
}See today's production
Sign in with the email your admin set up for you.