BricsCAD -PLOT Command: Automate Plotting with Scripts and Routines
BricsCAD -PLOT exposes plotting through command-line prompts, making it suitable for scripts and routines. Automation should begin only after the manual Page Setup is already correct.
Beginner takeaway: Automate a proven plot recipe; do not use -PLOT to hide uncertain paper, scale or plot-style decisions.
What you need to understand first
Command-line plotting is useful because a script can answer deterministic prompts, but it is fragile when device names, media names or drawing standards vary unexpectedly.
- Bricsys documents -PLOT as the command-line plotting command intended for scripts and routines.
- The interactive PLOT/PRINT dialog remains better for establishing and testing a configuration.
- Named Page Setups reduce the number of settings an automation routine must reinvent.
Related guides: CAD Plot Automation Guide, AutoLISP Plotting Automation for Beginners: Start Here, and Build a Safe AutoLISP Loop for Batch Plotting Layouts.
Step-by-step workflow
Step 1 — Prove manual plot
Where: PLOT/PAGESETUP
Do this: Make one Layout produce a correct PDF or hardcopy.
Check: Automation has a known-good target.
Step 2 — Run -PLOT manually
Where: Command line
Do this: Step through prompts and record the exact choices needed.
Check: You understand the prompt sequence.
Step 3 — Use stable names
Where: Page Setup/device/media
Do this: Prefer controlled configuration names over ad-hoc values.
Check: Script inputs are predictable.
Step 4 — Automate one sheet
Where: SCR/LISP or routine environment
Do this: Run a single Layout first and capture errors.
Check: One automated output matches manual output.
Step 5 — Expand cautiously
Where: Batch scope
Do this: Add loops/logging only after the single-sheet path is stable.
Check: Failures can be traced to a specific sheet.
What usually goes wrong
| What you see | Likely layer | First check |
|---|---|---|
| Prompt sequence changes | Version/context difference | Re-test interactively. |
| Device/media name missing | Environment mismatch | Validate before execution. |
| Batch outputs wrong scale | Bad Page Setup assumption | Fix source standard. |
| Script stops on one sheet | Unhandled exception/config difference | Log and isolate sheet. |
Practical example
Instead of scripting twenty prompt answers for every Layout, create a validated named Page Setup and make the routine select that standard whenever possible. The script then controls the batch, while the Page Setup remains the source of plotting truth.
What not to do
- Do not begin automation with a 100-sheet production set.
- Do not hard-code local printer names without validation.
- Do not let a script overwrite output files silently unless that behavior is explicitly intended.
Good office standard
Separate standards from automation: Page Setup defines correct output; -PLOT/routine controls execution, naming and logging.
Quick verification before you move on
- Use one representative drawing or sheet, not a production batch.
- Verify page size, orientation and a known dimension.
- Compare Preview/PDF with the physical output when a printer is involved.
- Save the setting or set only after the result is repeatable.
Official references
Frequently asked questions
Why use -PLOT instead of PLOT?
-PLOT uses command-line prompts and is specifically intended for scripts and routines.
Should I script paper sizes directly?
Only if those names are controlled and validated; named Page Setups are often safer.
What should an automation log?
At minimum drawing, Layout, chosen setup/device, output file and success/failure.
Explore more in BricsCAD Printing & Plotting Guide.