Automated PLT to .hs Converter Development
Budget: $250 – $750 USD
Project Brief (Freelancer.com)
Project Title: Build an automated PLT (Left/Right) → Han’s Laser .hs Converter (Windows)
Client: Betterway Systems (BWS) — Korea
Posting Date: 20 Oct 2025 (KST)
Project Type: One-time build with optional maintenance
Experience Level: Expert (HPGL/CAM/CNC, file-format writer & reverse engineering)
0) TL;DR
Input is already two PLT files per job (left.plt, right.plt) generated by us.
Your task is to convert PLT (L/R) → .hs (L/R) and fully automate what we currently do inside the machine software:
auto-detect the centers of two registration crosses, create mark1/mark2 point entities on dedicated layers,
translate the Right design by −263.5 mm in X (HPGL baseline 40 units/mm ⇒ −10,540 units),
and save native Han’s Laser .hs files that load and cut without manual edits.
Timeline: 2 weeks (14 days) fast track, with a D+2 format-access gate (official SDK/spec or lawful interoperability reverse-engineering).
1) Company & Background
Betterway Systems (BWS) runs high-volume custom printing and laser cutting lines. We already generate Left/Right PLT (HPGL) files. Today, operators still need to add marks, offset the Right design, and export .hs inside the Han’s Laser software. This manual step is the bottleneck and a source of errors. We need a fully automated converter from PLT(L/R) to .hs(L/R).
2) Objective
Given left.plt and right.plt, automatically produce two .hs files (Left/Right) that open and cut in the Han’s Laser software with zero manual edits.
3) Scope of Work (V1 — 2-Week Fast Track)
Ingestion: Watch-folder + CLI (Windows). Input per job: left.plt, right.plt.
HPGL parser & unit guardrails: Validate or configure 40 units/mm (1016 dpi); prevent double conversions.
Cross detection: Auto-detect two registration crosses in each PLT and compute their intersection centers (robust against noise/±5° rotation).
Marks: In the output .hs, create mark1 and mark2 point entities on dedicated layers at those centers.
Right-side offset: Apply X = −263.5 mm translation to the Right design (configurable), with precise unit conversion (−10,540 units at 40 units/mm).
.hs writer: Generate native Han’s Laser .hs files for Left/Right with the required layers/attributes so the machine software can load & cut without manual edits.
Preview & logging: Produce PNG thumbnails and JSON logs per job (mark coordinates, unit conversions, offsets, warnings/errors).
Deferred (Phase 2, optional after 2 weeks): Minimal GUI, advanced geometry healing beyond essentials, broader PLT dialect compatibility matrix, multi-threaded batch orchestrator, RBAC.
4) Inputs We Provide
For each job: left.plt and right.plt (already split by our existing process)
2–3 reference .hs files exported from the machine software
Device notes: Han’s Laser model/software version, work area, origin/units, current calibration values
Registration cross specs: line length/thickness, layer/color, edge cases
5) Deliverables
Windows build: Installer or portable package (watch-service + CLI)
Source code in a Git repository + build scripts + sample configs
.hs writer implementation with format notes/spec (if reverse-engineered)
Documentation: Architecture, data flow, CLI usage, operations manual, troubleshooting
Automated tests: Unit/integration/E2E + verification report (precision & compatibility)
Demo assets: Short screencast; throughput & accuracy report
6) Technical Expectations (Preferred Stack)
Language/runtime: C#/.NET or Python (C++ module if needed for performance)
HPGL handling: robust PLT (HPGL) parser/writer know-how
Geometry: clipping/offset/healing as needed to ensure stable export
Rendering: Cairo/Skia for preview images
Packaging: Windows Service + CLI (minimal GUI may be Phase 2)
Licensing: Avoid GPLv3-viral dependencies for distribution
7) Acceptance Criteria (UAT / Quality)
Precision: mark placement error ≤ ±0.02 mm; offset/coordinate error ≤ ±0.05 mm
Performance: P95 ≤ 10 s/job (A3-scale complexity, ≤100k primitives) on a standard Windows workstation
Compatibility: .hs opens and runs in Han’s Laser software with zero manual edits (Left & Right, ≥3 jobs each)
Robustness: Batch of 50 jobs (100 PLTs) ⇒ initial failure ≤ 0.5%; after auto-retry ≤ 0.2%
Logging: Each job logs mark coordinates, unit conversions, offset applied, and any error reasons
8) Legal & IP
.hs is a vendor format. Plan A: use official spec/SDK if available.
Plan B: lawful reverse engineering for interoperability (jurisdiction-compliant).
All source code and deliverables are work-for-hire assigned to BWS. Third-party licenses must be listed with versions.
NDA required prior to receiving proprietary samples.
Project Title: Build an automated PLT (Left/Right) → Han’s Laser .hs Converter (Windows)
Client: Betterway Systems (BWS) — Korea
Posting Date: 20 Oct 2025 (KST)
Project Type: One-time build with optional maintenance
Experience Level: Expert (HPGL/CAM/CNC, file-format writer & reverse engineering)
0) TL;DR
Input is already two PLT files per job (left.plt, right.plt) generated by us.
Your task is to convert PLT (L/R) → .hs (L/R) and fully automate what we currently do inside the machine software:
auto-detect the centers of two registration crosses, create mark1/mark2 point entities on dedicated layers,
translate the Right design by −263.5 mm in X (HPGL baseline 40 units/mm ⇒ −10,540 units),
and save native Han’s Laser .hs files that load and cut without manual edits.
Timeline: 2 weeks (14 days) fast track, with a D+2 format-access gate (official SDK/spec or lawful interoperability reverse-engineering).
1) Company & Background
Betterway Systems (BWS) runs high-volume custom printing and laser cutting lines. We already generate Left/Right PLT (HPGL) files. Today, operators still need to add marks, offset the Right design, and export .hs inside the Han’s Laser software. This manual step is the bottleneck and a source of errors. We need a fully automated converter from PLT(L/R) to .hs(L/R).
2) Objective
Given left.plt and right.plt, automatically produce two .hs files (Left/Right) that open and cut in the Han’s Laser software with zero manual edits.
3) Scope of Work (V1 — 2-Week Fast Track)
Ingestion: Watch-folder + CLI (Windows). Input per job: left.plt, right.plt.
HPGL parser & unit guardrails: Validate or configure 40 units/mm (1016 dpi); prevent double conversions.
Cross detection: Auto-detect two registration crosses in each PLT and compute their intersection centers (robust against noise/±5° rotation).
Marks: In the output .hs, create mark1 and mark2 point entities on dedicated layers at those centers.
Right-side offset: Apply X = −263.5 mm translation to the Right design (configurable), with precise unit conversion (−10,540 units at 40 units/mm).
.hs writer: Generate native Han’s Laser .hs files for Left/Right with the required layers/attributes so the machine software can load & cut without manual edits.
Preview & logging: Produce PNG thumbnails and JSON logs per job (mark coordinates, unit conversions, offsets, warnings/errors).
Deferred (Phase 2, optional after 2 weeks): Minimal GUI, advanced geometry healing beyond essentials, broader PLT dialect compatibility matrix, multi-threaded batch orchestrator, RBAC.
4) Inputs We Provide
For each job: left.plt and right.plt (already split by our existing process)
2–3 reference .hs files exported from the machine software
Device notes: Han’s Laser model/software version, work area, origin/units, current calibration values
Registration cross specs: line length/thickness, layer/color, edge cases
5) Deliverables
Windows build: Installer or portable package (watch-service + CLI)
Source code in a Git repository + build scripts + sample configs
.hs writer implementation with format notes/spec (if reverse-engineered)
Documentation: Architecture, data flow, CLI usage, operations manual, troubleshooting
Automated tests: Unit/integration/E2E + verification report (precision & compatibility)
Demo assets: Short screencast; throughput & accuracy report
6) Technical Expectations (Preferred Stack)
Language/runtime: C#/.NET or Python (C++ module if needed for performance)
HPGL handling: robust PLT (HPGL) parser/writer know-how
Geometry: clipping/offset/healing as needed to ensure stable export
Rendering: Cairo/Skia for preview images
Packaging: Windows Service + CLI (minimal GUI may be Phase 2)
Licensing: Avoid GPLv3-viral dependencies for distribution
7) Acceptance Criteria (UAT / Quality)
Precision: mark placement error ≤ ±0.02 mm; offset/coordinate error ≤ ±0.05 mm
Performance: P95 ≤ 10 s/job (A3-scale complexity, ≤100k primitives) on a standard Windows workstation
Compatibility: .hs opens and runs in Han’s Laser software with zero manual edits (Left & Right, ≥3 jobs each)
Robustness: Batch of 50 jobs (100 PLTs) ⇒ initial failure ≤ 0.5%; after auto-retry ≤ 0.2%
Logging: Each job logs mark coordinates, unit conversions, offset applied, and any error reasons
8) Legal & IP
.hs is a vendor format. Plan A: use official spec/SDK if available.
Plan B: lawful reverse engineering for interoperability (jurisdiction-compliant).
All source code and deliverables are work-for-hire assigned to BWS. Third-party licenses must be listed with versions.
NDA required prior to receiving proprietary samples.