Records the topics you configure
Point Tin Box at the DDS topics and log files that matter. It keeps the exact message bytes along with where they came from.
Tin Box
Record what happened.
Tin Box listens to the DDS topics and log files you choose and writes them into MCAP recordings on local storage. Each recording belongs to a named session, so you can find the run you care about later. Run it alongside your robot or on a recording computer on your network. Keep the data from a test run together, even when its topics come from different DDS domains.
Engineering preview for development and retrospective investigation, not clinical decisions or robot control.
What it does
Organizes runs into sessions
Start, list, inspect, and end sessions. The session identity travels inside each MCAP file and its manifest, so moved files still say where they belong.
Uploads when it can
Finished recordings wait on the device and upload when a connection is available. A recording is marked delivered only after the server accepts it.
From a test run to an investigation
Keep the run, not just the error log.
-
1. Choose what to record
Configure the domains, topics and logs you need. Start a session for the run you want to investigate.
-
2. Keep it on site
Store recordings locally in MCAP files. Cloud connectivity is not required to record.
-
3. Investigate with your team
Upload finished recordings to Tin Cloud to compare runs and inspect the signals behind a finding.
Recording visibility
Know what made it to storage.
Tin Box records only what you configure; it is not a capture-everything network tap. Each session keeps counters for samples that were accepted, stored, or rejected by the recorder. An interrupted recording can have an unknown tail; it is not reported as complete. When local storage runs low, new segments pause; pending uploads can continue.
Tin Box only listens. It sends no commands to your robot.
Local first
Recording works without the cloud. Connect Tin Cloud when you want to browse, compare, and investigate sessions.
Contact engineering@tinverse.com.