Second By Second

A focused view for incident-level forensics. It shows the same raw stream as Messages but is optimized for very short, high-resolution windows to inspect second-by-second behavior.

This page lists only what’s different from the Messages module. For the full workflow (filters, views, grid & chart tools) see Messages.

Permissions

• Users must have view access to the selected unit(s).
• If units are shared via Shared Groups, users with View Only / Inherit can read messages for those units.
• Admins can query a single unit only, even when accessing shared accounts.

Scope & Limits

• Data availability: Users can select any date range using the From and To fields, but the interval must not exceed 7 days
• Best practice window: keep queries small (e.g., 1–6 hours) to make per-second charts readable and exports manageable.
• Everything else (filters, views, export): behaves like Messages.

Tracing Second by Second

Follow the same order as Messages → Tracing Messages (Unit → Source → Time → Execute). Only the parts below differ:

1. Select Time
• Data availability: Users can select any date range using the From and To fields, but the interval must not exceed 7 days
• Prefer short windows (minutes → a few hours) for incident analysis.
2. Execute
• Run the query. If you over-scoped, use Cancel and reduce the window (identical to Messages).
3. Review & Explore
• Summary shows the same KPIs as Messages.
• Use Table for exact timestamps; use Graph to visualize second-by-second spikes/drops.
• Export please be mindful exports can be much larger due to 1-second cadence.

Table View

• Columns & grid tools: identical to Messages (sorting, filtering, column menu, day folding, block, pagination, export).

• What changes in practice: expect many more rows for the same duration than in Messages; filter early (by unit/time) to stay responsive.

Graph View

• Resolution: emphasizes per-second points (if the device transmits at 1 Hz).
• Working style: add fewer series (e.g., 1–2) and zoom incrementally to keep the chart legible.
• Same tools as Messages: parameter picker, legend toggles, zoom/pan, tooltip, and (if enabled) “go to row.” afaqy on Notion

When to use

• Fuel theft suspicion (minute scale): Plot Fuel Level with Speed to confirm drops while stationary.
• Harsh event spike: Plot Speed / RPM around the event time to see the exact second of the peak.
• Cold-chain breach: Plot Temperature with Door to correlate openings with temperature climbs.
• GPS jitter inside yards: Inspect Speed + Satellites/Accuracy to separate noise from true motion.

Troubleshooting

• No results: From/To added is outside the last 7 days, or the unit didn’t transmit in that slice.
• Slow or heavy charts: Narrow the time window; avoid plotting more than a couple of series at once.
• Large exports: Trim the window or export by segments (e.g., 30–60 minutes each).

API Documentation

Units