Device profiles
Each plotter needs a profile: name, pen count, page limits, origin, scale, connection type, and known-good settings.
Sender software
The software path from HPGL to real plotter.
The public site should not send directly to hardware. Approved jobs should move through local sender software that knows the plotter profile, serial settings, pen behavior, speed, flow control, and production log requirements.
Serial / interface control
Sender must handle ports, baud rate, flow control such as XON/XOFF where needed, pacing, pause/resume, and recovery.
Preflight checks
Before sending: path count, page bounds, pen numbers, estimated plot time, and whether the HPGL uses unsupported commands.
Production log
Every job should record file hash, plotter, date, settings, result, failures, photos/proofs, and reviewer notes.
Sender agents
- SenderSoftwareLead — owns the local sending app plan.
- DeviceProfileAgent — maintains per-plotter settings.
- HPGLPreflightAgent — checks file safety before plotting.
- QueueToPlotAgent — moves approved production jobs into sender-ready format.
- PlotProofAgent — records output proof and completion notes.