Skip to content

Vision: troubleshooting ​

Last updated

License feature: Machine Vision

Camera and connection ​

SymptomCauseFix
Device will not connect: "Vision cannot run: …"The appliance's image-processing component is missingReinstall or update the appliance software, then restart the drivers from the Appliance page
"No image from Camera 1 (Camera returned HTTP 404)"Wrong path for this camera's firmwareOpen the URL in a browser; set the correct one in URL (optional)
"… Camera returned HTTP 401"The camera needs a loginSet Camera username and Camera password when adding the device; the Vision page has no login fields — see Cameras
"No camera IP configured." / "No snapshot URL configured." / "No stream URL configured."The address or URL field is emptyFill it in and Save
"No test image uploaded."Uploaded test image chosen with no fileUpload an image under Test image
"Could not read the test image at …"The file was deleted, or the configuration came from a selective export rather than a full backupUpload the image again
"Could not open camera source 0"No USB camera at that number, or another program has itTry Camera number 1; unplug and replug; check nothing else uses the camera
"The camera did not return a frame. It may have disconnected."USB camera unplugged or stream endedCheck the cable or stream; the next grab reconnects
Timeout after about 5 sCamera unreachable or very slowCheck network and IP; a camera on another subnet needs routing
The picture never changes although the part doesThe camera serves a cached imagePut {cb} in the Snapshot URL, e.g. http://cam/snap.jpg?t={cb}
Preview shows "Preview failed." or a 502 errorThe device is not connected, or the drivers service is downCheck the device's status on the Devices page; connect it

Results ​

SymptomCauseFix
Count is one or two highNoise, highlights or the tray edge countedDraw a tighter region; raise Min radius/Min area; raise Cleanup (Blobs); raise Sensitivity (Circles)
Count is lowParts missedLower Sensitivity; widen the radius or area window; check Invert (Blobs)
One part counted twice (Circles)Min distance too smallRaise it towards the part diameter
Verdict reads Nothing checked / pass uncertainNo tool is judged, or judged tools have no target/limitsTick Include this tool in the verdict and set Expected count or a limit
Presence reads high on an empty fixtureAutomatic threshold on a flat region, or threshold on the wrong sideSet Threshold between the empty and good readings; check Invert
Color match reads 0% on the right partSaturation or brightness floors too high, or wrong hueUse the color in view; lower Ignore below this saturation
"Nothing taught yet. Draw a box round the feature and press Teach."Pattern tool not taught (its own tags read bad; if it is judged, pass reads false)Teach it, or remove the tool, and Save
Pattern score low on a good partLighting or camera changed since teaching; part rotatedTeach again; or allow Search angles
Following tools fail with "… did not find the part."The locator's score is below its At leastCheck the locator; lower its limit carefully, or teach again
Caliper reads too wideThe region crosses another edge beyond the partNarrow the region; set Which edges
Gauge limits suddenly wrong after setting a scaleLimits were set in pixelsRe-enter the limits in mm
Text reads ? for some charactersCharacter not taught, or below Confidence neededTeach that character from another label; check the print quality
"Found 6 characters in the box but was told it says…"Characters touching or splitAdjust Gap between characters and Threshold; draw the box tightly
Barcode not readCode too small or low contrastUpscale 2; better lighting; draw a region round the code

Tags and saving ​

SymptomCauseFix
New tool's tags do not existNot saved yetPress Save; the tags are created on save
Changes on the page have no effect on the lineNot saved, or the device was disconnected when saved (it picks up settings when it next connects)Save with the device connected, or reconnect it
One tool's tags are badThat tool errored (not taught, no image from its camera, a locator it follows did not find the part)Read error (or the tool's red message on the Vision page) and fix that
Every tag on the device is badThe whole inspection failedRead error and fix that
Tool results uncertain after a recipe ranA changeover invalidates results until the next inspectionExpected — trigger an inspection
Writing trigger from the tag browser fails with "Write access is not enabled for this device…"Allow Tag Writes is offTurn it on in the device's settings
"Trigger missed: the previous inspection sequence was still running."Triggers faster than the sequence completesShorten Wait steps, raise the source's debounce, or slow the trigger
"tool '…' is not in the running program '…'. Change over first, then set it."A setting written for another productWrite program first, then the setting
Save fails: "Tool "…" is a circles tool in "…" and a barcodes tool in "…"…"Same tool key, different types in two programsGive one of them a different Tag prefix
Statistics counts reset unexpectedlySave, changeover, Reset counts or restartUse the window figures from the historian for shift yield

Performance on a Pi ​

  • Watch last_run_ms (and the ms figure beside the verdict). Big frames cost most: a 5 MP JPEG takes far longer to decode and search than a 1 MP one. Set the camera to the lowest resolution that resolves the feature.
  • Regions make every tool faster, especially Pattern match.
  • Search angles multiplies pattern time by the number of angles.
  • In Continuously mode a device inspects on every poll; with a 1000 ms polling rate and a 700 ms inspection there is little spare. Use a trigger or a slower poll.
  • Keep every inspection writes a JPEG per inspection to the SD card or eMMC; use it for fault-finding only.

See also ​

Scada.Ink Help Center