Skip to main content
All integrations
Vision + Inspection

Basler / pylon Vision + Ignite Lean

Available now

Basler industrial cameras + pylon SDK run many custom vision deployments. Stream results to builds.

REST API Webhooks

How the Connection Works

Basler / pylon Vision
REST APIWebhooks
Ignite Lean
Into Ignite Lean
  • Frame metadata + results
Back to Basler / pylon Vision
  • Capture triggers

How It Works

  1. 1Custom inspection apps publish results to Ignite Lean via REST.
  2. 2Results attach to builds and trigger NCs on fail.
  3. 3Capture triggers fire on operator events.

Recommended Workflows

How Basler / pylon Vision works best with Ignite Lean. These are recommended patterns: Ignite Lean fires the trigger, and how Basler / pylon Vision routes it (which work group, which device, which rule) is configured to your IT setup.

Inline inspection raises an NC instantly
Trigger A vision system flags a fail
  1. 1Basler / pylon Vision posts the fail result + defect image to Ignite Lean.
  2. 2Ignite Lean attaches it to the build and opens an NC.
  3. 3The line gates downstream steps until the NC clears.
Quality is enforced at the camera, not just after the fact.
Active recipe pushes to the camera
Trigger A build of a new product starts
  1. 1Ignite Lean pushes the active recipe / inspection model to Basler / pylon Vision.
  2. 2The camera switches to the right configuration automatically.
  3. 3Operators never select a recipe by hand.
No mis-set cameras, no false fails.

Connect Basler / pylon Vision today

This works now through our REST API, outbound webhooks, and Excel/CSV. Start with the API reference, or talk to us about a guided setup.

API ReferenceTalk to Us