Integrations
It runs on the hardware you already have.
What SynSpect works with, how it connects to your scanner and your line, and what it takes to go live.
Fig 2.0 / Mounted scanner over a fillet weld
- 01Software only
- 02No GPU, no cloud
- 03OPC-UA / EtherNet/IP / Modbus/TCP
Compatibility
What SynSpect works with.
- Sensors
- Laser-line profilers and 3D scanners
- Mounting
- Robotic arm, gantry, conveyor, or handheld
- Joints
- Fillet and T-joint welds today
- Codes
- CSA W59, AWS D1.1, ISO 5817
- Compute
- A standard industrial PC, CPU only
- Connection
- None needed to inspect: on-premises and offline
We are working to expand SynSpect to all weld types.
No scanner or profiler yet? Get in touch and we will help you work out whether SynSpect is the right fit. Talk to us
Mounting
Mounted or handheld.
Fig 2.1
Mounted
On a robotic arm, gantry, or conveyor. The PLC triggers the scan and SynSpect returns the verdict.
Fig 2.2
Handheld
The same measurements with a handheld scanner, for parts that cannot come to a cell.
Two ways in
SDK integration or custom integration.
3.1
Inside your scanner's software
Where the scanner maker offers an SDK, SynSpect runs inside the maker's own software. Operators keep working in the tool they already know, and nothing new sits between them and the scan.
3.2
Custom integration
For other setups, we build a custom integration around your scanner, your cell, and your line, and agree its scope with you before the work starts.
What we ask about when we scope it
- Your scanner or profiler, and how it is mounted
- What starts a scan, and what identifies the part
- The codes and weld recipes you inspect to
- Where verdicts and records need to go
On the line
The PLC handshake.
Your PLC stays in charge of the cell. SynSpect takes a part ID and a trigger, and gives back a verdict.
01
PLC
Sends the part ID and triggers the scan
02
Scanner
Captures the weld surface
03
SynSpect
Measures, checks, and returns the verdict
04
Quality system
Receives the inspection record
- From the PLC
- Part ID, which selects the weld recipe and code limits
- From the PLC
- Scan trigger, when the part is in position
- To the PLC
- Pass, check, or fail for the part
- To your systems
- The inspection record, with per-cross‑section evidence
Line interfaces
- OPC-UA (recommended)
- EtherNet/IP
- Modbus/TCP
- Digital I/O
Rollout
From install to live in four steps.
- 1
Install SynSpect
On a standard industrial PC, connected to your scanner or profiler.
- 2
Train on about 10 samples
From your line, on your scanner, to fit the models to your weld.
- 3
Check
We run SynSpect against your own gauges, so you can compare the results.
- 4
Live
You decide when it goes live on the line.
Deployment
On-premises and offline.
No cloud is required to inspect, and no GPU. Scan data and inspection records stay on your network.
- Processor
- Industrial multi-core CPU
- Memory
- 16 to 32 GB RAM
- Storage
- SSD
- GPU
- Not required
- Network
- Not required to inspect
Records
Records go where your quality data lives.
Every part gets an immutable inspection record with per-cross‑section evidence. It is exported in the format your systems need.
- MES
- Verdict and record against the part
- Quality system
- The record your inspector reviews and signs off
- Historian
- Readings and verdicts beside your process data
- Custom formats
- Agreed with you during integration
- API
- Available on request
Start with one part on your line.
We run SynSpect against your own gauges, and you decide when it goes live.