From f8959efb5acdfaa337d3e259e109d6fd7fbd9d59 Mon Sep 17 00:00:00 2001
From: Mark Nolan
+ It now lives at
+ shimmerresearch.github.io/shimmer-capture-web, built from
+ ShimmerResearch/shimmer-capture-web.
+ You should be redirected automatically. If not:
+ Go to Shimmer Capture
-
-
- ` | Put the sensor's clock this many seconds short of the point where the 24-bit stream counter rolls over, so a short stream crosses a wrap. It moves the clock, not the counter, because on a Shimmer3R the two are the same number. |
-| `&debug=1` | Log every command and reply to the browser console. |
-
-While the mock is connected, `mockTransport.writes` in the console is every
-command the page has sent, and `mockTransport.emitDisconnect()` simulates a
-dropped link. `mockTransport.factoryTest` reports how many self-tests have run,
-whether one is still printing and exactly what text it printed;
-`mockTransport.rtc` exposes the sensor's own running clock. The panels
-themselves are `factoryTestPanel` and `rtcDriftPanel`, beside `sdBrowser`,
-`brandEditor` and `calibrationEditor`.
-
-It is opt-in from the URL only, and deliberately so: a page that reached for
-the mock on its own would quietly show fake data to somebody debugging real
-hardware.
-
-## Status
-
-This is an early example. It has been exercised end to end against the mock
-link; the paths that only a real sensor can prove — that a configuration write
-is accepted and applied, that a calibration dump round-trips, that a long
-recording holds up at high rates, that the self-test report arrives whole over
-a real link, that the red LED really lights — want confirming on hardware
-before anyone relies on them for real work. Check a recording before it
-matters.
-
-The calibrated values are the newest part and the least proven. Worth checking
-against Consensys reading the same sensor, in this order:
-
-- **Pressure and temperature.** The whole conversion is host-side and none of it
- has met a real BMP390 or BMP581. A Shimmer3 with a BMP280 is worth its own
- look: its 20-bit registers are reassembled from a 16-bit temperature and a
- 24-bit pressure, and getting that wrong is not subtle.
-- **GSR in µS and kΩ**, and the battery in mV — both against Consensys, and the
- battery against a meter.
-- **ExG in mV** with the test-signal preset, whose amplitude is known.
-- **The time axis.** That a Shimmer3R's packet timestamp really is the low bits
- of its real-world clock is read out of the firmware, not measured; if it is
- wrong the axis will be out by a whole multiple of 512 seconds, which is
- obvious the moment you compare it with the Device panel's clock.
-- **The sensor rules**, by writing an image that breaks one and reading it back:
- the device should correct exactly what the banner predicted.
+A change to `common/` no longer reaches anything in this repository, and a
+change here no longer reaches Shimmer Capture.
diff --git a/ShimmerCapture/index.html b/ShimmerCapture/index.html
index 4515075..3a8d5ce 100644
--- a/ShimmerCapture/index.html
+++ b/ShimmerCapture/index.html
@@ -1,5612 +1,128 @@
-
-
-
-
+
+ Shimmer Capture
- Shimmer Capture has moved
+ .bin. The firmware seeds the record with the factory
- names at first boot and treats it as the only source of truth
- afterwards, so what is shown above is what the sensor really
- announces. Every link reaches the record — BLE, Classic Bluetooth
- and the USB-C/dock connection alike.
-