G-code Monitor

The simplest and most widely-compatible trigger mode. SnapAzule watches the G-code stream coming from the printer's SD card and fires a keystroke whenever it sees a line containing your configured pattern.

When to use it

• You already insert a specific command (M600, M117 SNAP, a custom marker) at points where you want a photo.
• Your slicer lets you inject arbitrary G-code at layer change, pause, or end-of-print.
• You want to trigger on an event that has no geometric signature — end of print, filament change, etc.

How it matches

• The pattern is a plain substring match against each line of the stream.
• Matching is case-sensitive. M600 matches M600, M600 ; filament change, and G1 X0 ; M600 — but not m600.
• An empty pattern disables G-code matching entirely.

Trigger Delay

Most printers read G-code hundreds of lines ahead of what's actually printing. If you trigger on the first match, your camera may fire up to a few seconds before the physical event happens.

Trigger Delay (in seconds) tells SnapAzule to wait after the match before firing the keystroke. Start with 1–5 seconds and adjust based on your printer's read-ahead.

A value of 0 fires immediately.

Example patterns

Limitations

• This mode reads from the SD card slot on the SnapAzule, not the printer's own SD. You have to either:
  • put the G-code file on the SnapAzule's SD card and have the printer read it from there, or
  • use Prusa Link mode instead, which reads from the printer over the network.