Troubleshooting

Another operation of the same module was still running. A second call is not queued; it returns at once and does nothing.

The module’s image stream is searching a frame. The stream and find-object never run at the same time on one module.

If another operation was still running: wait for the running execute to return, then call the method again. The lock is per module, so other modules are not held up.

If the stream of the module runs:

If system/remove-module answers busy: stop the stream of the module first. Removing a module stops its stream.

A required input is empty. input/object-id of find-object is required.

The image address points at this application itself.

input/object-id of system/create-object or input/object-dir of system/set-object-dir is an absolute path, or a path that climbs out of the configuration directory with ...

If a required input is empty: set it. For find-object, set input/object-id to an entry of system/objects.

If the image address points at this application: set input/input-image-address to the image node of the camera application, for example hdvisionsystems/lumiscan-cam-driver/camera1/output/image.

If a path is absolute or leaves the configuration directory: give it relative to the configuration directory, for example production-parts.

The camera application is not running, or it runs on another device.

The camera application has not captured an image yet.

The address in input/input-image-address is wrong.

The image node at the address is missing, empty or inconsistent.

The image uses an unsupported pixel format. Supported are Mono8, Mono12, RGB8, RGB12, BGR8, BGR12, BayerGR8, BayerGR12, BayerRG8 and BayerRG12.

If the camera application is not running: start it on the same device and capture an image.

If no image has been captured yet: capture an image in the camera application.

If the address is wrong: correct input/input-image-address.

If the pixel format is not supported: use one of the supported pixel formats, see Requirements.

The object’s picture is missing or unreadable: input/object-id names no entry of system/objects.

The object directory is missing or unreadable.

The picture is in another directory than the one in use.

If the object id is not listed: correct input/object-id, or teach the object with system/create-object. A file you put into the directory by other means is listed only after a refresh, see Problem: An uploaded .png does not appear on system/objects.

If the directory is not the one you expect: switch with system/set-object-dir, see Object Storage.

The region reaches past an edge of the image. The whole crop must lie inside the image; it is refused, not trimmed.

For system/create-object, input/crop/width or input/crop/height is 0. Both must be greater than 0.

If the region reaches past an edge: correct input/crop/startX, startY, width or height, so that the region fits the image size given in the message.

If width or height is 0 (create-object): set both to the size of the region, greater than 0.

The object is binned too far. Its picture then no longer has the edges the detector keys on, and the detector refuses it, for example a 128x128 object at bin-size 8 (reduced to 16x16). Small objects reach this limit sooner than large ones.

The picture was cropped along the part’s silhouette when the object was taught. A picture must yield a minimum number of strong gradient points, and a crop that stops at the silhouette hides the outline from the detector.

If the object is binned too far: lower input/preprocess/bin-size again. Raise it one step at a time and stop when the scores start dropping towards the threshold.

If the picture was cropped at the silhouette: teach the object again with system/create-object, with about 5 pixels of background around the part. See Creating an Object.

A file could not be written - usually a permission problem or a full disk.

If it is a permission problem: make the configuration directory writable for the application.

If the disk is full: free disk space on the device.

input/crop excludes the part.

The scores of the genuine parts are below input/confidence-threshold (default 0.6). A threshold at or above 0.9 usually rejects everything.

The part arrives in an orientation that no object was taught for. The detector does not rotate a picture.

The part sits closer to or further from the camera than in the picture it was taught from.

If the crop excludes the part: widen the region, or set all four input/crop/ values to 0.

If the scores are just below the threshold: set input/confidence-threshold a little below the worst score a genuine part produces. If the scores hover near the threshold or the images are noisy, set input/preprocess/blur-sigma-x to 1.0 (blur is off by default) and measure again.

If the part is missed at particular orientations: teach another object at the orientation being missed, for example screw-m6-tilted, and search for it in its own run. No setting fixes this.

If the part is missed at another working distance: teach an object at that distance.

If the part was not in the image: the result is correct; nothing needs to be changed.

input/nms-min-dist is 0 (the default), which keeps every match.

input/nms-min-dist is smaller than the distance between the matches of one part.

Set input/nms-min-dist to roughly half the size of the part in pixels, for example 40. Where several matches fall within that distance, only the highest scoring one is kept.

The next run has started. Every run clears its own outputs as soon as it begins, before anything that can fail. A run that fails for any reason leaves them empty.

A call refused with -1 (busy) clears nothing, so this is not the cause when the second call was refused.

If the next run started too early: wait for execute to return, read the outputs, and only then trigger the next run.

If the latest run failed: follow the entry for its status code.

The list was not refreshed. system/objects is refreshed only at startup, when system/set-object-dir switches directory and when system/create-object saves a template. Files added by other means - an upload or an SSH session on ctrlX OS, a file copied in by hand on a PC - are picked up at the next of these.

The file name does not end in a lower case .png. .PNG files are skipped.

The file is in a subdirectory. Only files at the top of the object directory are listed.

The file is in another directory than the one system/object-dir names.

If the file name or the place is wrong: use a lower case .png file name at the top of the object directory.

Then: run system/set-object-dir or restart the application. Expected: system/objects lists the object.

Only the inputs were written. Writing control/subscribe/input/enable alone starts nothing; control/subscribe/execute applies the inputs.

control/subscribe/execute was refused (Rejected, ctrlX: DL_INVALID_VALUE): stream mode without an address, or a queue size outside 1 to 64.

The settings file <module-id>.json could not be written, for example because it is not valid JSON (CreationFailed, ctrlX: DL_CREATION_FAILED). Nothing changed.

The stream of the Cam Driver does not run, so no frames arrive.

The source cannot be subscribed to. The module tries it again every 5 seconds while the stream runs, and logs the first failure.

Frames cannot be searched, for the reasons find-object gives in its status-text.

If only the inputs were written: set control/subscribe/input/enable to true and write to control/subscribe/execute. Wait until control/subscribe/output/stream/active is true.

If the call was refused (Rejected, DL_INVALID_VALUE): write the camera’s stream folder to control/subscribe/input/address, set control/subscribe/input/queue-size to a value from 1 to 64, and write to control/subscribe/execute again.

If the settings file could not be written (CreationFailed, DL_CREATION_FAILED): make <module-id>.json in the configuration directory valid JSON again, without comments, then write to control/subscribe/execute again.

If the stream of the Cam Driver does not run: start it. It is not kept after a restart: call its control/publish/execute with enable = true after every start, and connect the camera first. See A stream delivers nothing.

If the source cannot be subscribed to: check that control/subscribe/input/address is the camera’s stream folder and that the Cam Driver runs on the same device.

If frames fail: correct the input that last-failure names, as for a single find-object call.

The module list was not saved. Settings and new modules take effect immediately but are not saved until you ask; the module list and each module’s settings are saved separately.

The module’s settings were not saved.

A save failed: system/save-module-inputs or system/save-current-modules did not report status 1.

<module-id>.json contains comments. The stream reads such a file, but the module’s inputs are then not restored at start; the log reports the file as unreadable.

A setting whose node no longer exists after a software update is skipped, with a log entry.

If the settings or the module list were not saved:

If the module file contains comments: remove them from <module-id>.json. Changes made to the file by hand take effect at the next start.

If a setting was skipped after an update: set the input again and save the module’s settings.

The licence is missing. The reason is written to the system log.

The application needs more licences than are installed. One licence covers ten modules, see Problem: Status code -11 (licence unavailable).

If the licence is missing: install a valid licence on the device and start the application again. Expected: it keeps running, and its nodes are on the Data Layer.

No licence on the device covers the module. One licence covers ten modules; the eleventh module acquires a second licence of the same key.

If more modules exist than the licences cover: remove the modules you do not need with system/remove-module and save the module list with system/save-current-modules, or obtain another licence.