Rows 14 and 15, and the first table of row 16, were scanned by the client with two scans missing and nothing in the sheet to say where. Every serial after a missed scan sits one place too far west in the register. We do not rescan the rows; we find the two places.
On the row
- Walk the row once, in the direction the stop says. At each table the app asks for one scan, normally the top module at the end you reach first.
- Each scan is looked up. The app tells you how many missed scans lie west of that module: none, one or two.
- When that number goes up between two tables, the missed scan is in the table you just passed. The app then halves that table: scan where it says. In five or six scans you will be at the missed module itself. Its serial is not in the register, and that scan is the one we came for.
- It then asks for the modules next door, to prove which one was missed, and asks you to recount and rescan the missed module and its neighbours. A module counted one out gives an answer that looks right but isn't; counting again from the table end is what catches it.
- Once both are found the row says Solved. Keep doing the one-per-table check scans to the end of the row: they prove nothing else is out of place, and you are walking that way anyway.
Counting
The app always counts from the nearer end of the table and says which end. TOP is the upper module of the pair, BOTTOM the lower. The drawings show the table as you see it from behind: east on your left, west on your right.
When things go wrong
- Unreadable label: press Unreadable. The app offers the module next to it.
- Scanned the wrong module: press Undo last, then scan the right one. Or tap the module you actually scanned on the drawing first.
- "Scan straight through": the numbers don't add up in that stretch (an extra or wrong scan in the client sheet). Scan each module in turn until it settles.
- Odd read (wrong length): scan again. The same code twice is recorded as read.
- "Doesn't fit the scans either side": nothing was recorded. The app names the module the reading belongs to, which usually shows you are one out. Count again and scan. If you are sure, scanning the same module again records it.
- Label unreadable next to a missed module: the app asks you to type the number printed on the label. If there is no number either, press Unreadable again; only that module stays flagged.
- A serial already scanned at another module this visit is refused, with the module it was scanned at.
Records
Every scan is kept on this device with time, initials and GPS. Export the CSV at the end of each stop and at the end of the day. Undo marks a scan as undone; it stays in the export.