Troubleshooting

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

The module’s image stream is searching a frame. The stream and detect-area 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. system/analyse-scene has its own lock and does not block detection.

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/method is not FIXED. FIXED is the only method this version offers; anything else is refused.

input/preprocess/method is unknown. It accepts NONE, LOG, DOG and DOH.

A parameter is outside its range, for example input/method-specific/fixed/level outside 0-255, input/preprocess/dog/sigma-first equal to sigma-second, input/preprocess/doh/kernel-size other than 1, 3, 5 or 7, or system/analyse-scene/input/histogram-bins outside 2-256. Only the chosen preprocessing method’s parameters are validated.

The image address points at this application itself.

If a required input is empty: set it.

If input/method is not FIXED: set it to FIXED.

If input/preprocess/method is unknown: set it to NONE, LOG, DOG or DOH.

If a parameter is outside its range: correct it to a value inside the range given in the Data Layer Reference.

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.

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 region reaches past an edge of the image. A region reaching past an edge is refused rather than trimmed.

Correct input/crop/startX, startY, width or height, so that the region fits the image. A zero width or height reaches the right or bottom edge, so all zero searches the whole image.

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/detect-dark does not match which end the parts are. Set it to true when the parts are darker than the background.

The level input/method-specific/fixed/level is above every pixel in the part.

If input/detect-dark is wrong: set it to true when the parts are darker than the background.

If the level is above every pixel in the part: set input/method-specific/fixed/level to the level output/recommended-settings gives. Nothing is written for you.

If the histogram shows one hump: no level will work; fix the lighting, see Problem: The reading drifts with the lighting, or no level works.

The area is much larger than the part: the level is letting background in.

The area is consistently short: the level is trimming the part’s edge.

input/detect-dark does not match which end the part is.

The part has a hole, and input/fill-holes is off. A region is counted as the pixels that passed the threshold, so a hole is not counted unless fill-holes is set.

If the level is letting background in: check input/detect-dark, then commission the level again with system/analyse-scene, see Problem: Nothing is found, or the result is empty.

If the area is consistently short: lower input/method-specific/fixed/level, and try input/detect-dark if the part is the darker of the two.

If a part with a hole measures as a ring: turn on input/fill-holes to measure the shape its outline encloses. A washer then measures as a disc.

Sensor noise and dust cross the threshold. The application reports every region it separated; there is no area window.

At the level: raise input/method-specific/fixed/level until the noise stops crossing the threshold. This is the better fix, because those regions then cost nothing to find.

In your control program: ignore blobs[] entries whose area is below what a part can be. A quarter of the area of the smallest part you care about is a good starting point.

The part is being split by a shadow or a highlight.

Try preprocessing with input/preprocess/method (LOG, DOG or DOH), or input/detect-dark. All three filters normalise their output, so revisit the level after enabling one.

The picture is brittle: system/analyse-scene/output/area-sensitivity is above 0.05, so one grey level costs 5 % of the measured area, and a fixed level is not safe to commission. No value in detect-area/input/ repairs this; it is fixed at the camera.

Uneven lighting: the light varies more than about a third of the part-to-background gap.

The features are too fine: below about 8 px.

The edges are soft (defocus, motion blur, sensor noise at high gain), or the contrast is low.

If the lighting is uneven: fix the uneven lighting first. No single level fits the frame.

If the features are below about 8 px: put more pixels on the part: magnification, a closer working distance, or a higher resolution sensor.

If the edges are soft: refocus, shorten the exposure or steady the part, drop the gain and add light instead.

If the contrast is low: change the lighting: backlight, another angle, a diffuser or a polariser, another background.

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.

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

control/subscribe/execute was refused (DL_INVALID_VALUE, on a PC Rejected): 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 (DL_CREATION_FAILED, on a PC CreationFailed). 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 detect-area 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 (DL_INVALID_VALUE, Rejected): 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 (DL_CREATION_FAILED, CreationFailed): 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 detect-area call.

The module list was not saved. Settings and new modules are live at once but not permanent until saved; 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.

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.