Create one small sequence, validate it, run it, and only then adapt it to a complete rig.

Create and run a sequence

1. Open Rules and Sequences and choose Sequences.
2. Choose New sequence, enter a name, and select Create sequence.
3. Open Code view and replace the starter document with the example below.
4. Replace the camera serials with serials from your rig.
5. Choose Validate, then Save.
6. Choose Run and watch the run log.
7. Confirm the expected files before binding the sequence to the main trigger.

{
  "id": "first-sequence",
  "name": "Warmup then two cameras",
  "description": "A small test sequence.",
  "version": 1,
  "groups": [
    {
      "id": "test-cameras",
      "serials": ["CAM_001", "CAM_002"]
    }
  ],
  "steps": [
    {
      "type": "trigger",
      "params": {
        "target": { "groupId": "test-cameras" },
        "phase": "warmup"
      },
      "duration": 1000
    },
    {
      "type": "trigger",
      "params": { "target": { "groupId": "test-cameras" } },
      "duration": 0
    }
  ]
}

The warmup step runs first and pauses for one second. The capture step then fires both cameras. duration: 0 prevents an extra pause after the capture.

Bind the main trigger

Under Trigger binding, select the radio button beside the sequence. The normal trigger button will then run this sequence. Select None (normal capture) to restore the regular capture behavior.

Binding is optional. A sequence can always be run directly, and a rule can start it after a matching Camera Server event.

Stop safely

Choose Abort while a sequence is running. Abort stops future steps and waits are; it does not undo a command that has already reached a camera, light, GPIO node, or transfer service.

JSONC editing

Sequence source is JSONC. // comments and trailing commas are allowed. The document still needs valid JSON structure and must pass server validation before it can run.