Replies: 2 comments 1 reply
-
|
Hi @schrej-zz, I convert it to a discussion, because it's not a bug. It just states that alignment step was aborted (marker matching was not successful to find a proper match to due various reasons) and actual cycle was automatically discarded to avoid misreadings based on a not properly aligned image. No impact to further processing as long it's not discarding every cycle.
As stated in the error message it indicates most likely an not optimal alignment marker selection / positioning. To optimize, try to use another marker area. If you provide a screenshot of your image I can give you potential further advise. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
Description
Hi,
I get errors in the logs regarding alignment:
[0d00h00m09s] 2025-10-11T11:01:45 <ERR> [IMG_TPLMATCH] Angle dev: -1.9, dX1: 20, dY1: 20, dX2: -17, dY2: 13 [0d00h00m09s] 2025-10-11T11:01:45 <ERR> [ALIGN] Alignment by algorithm failed. Verify image rotation and alignment marker [0d00h00m10s] 2025-10-11T11:01:46 <ERR> [FLOWCTRL] Process error in state: "Image Alignment" [0d00h00m10s] 2025-10-11T11:01:46 <ERR> [MAINCTRL] Image evaluation: Process error occuredReference image looks fine though.
Logs
Firmware Version
17.3.0
Beta Was this translation helpful? Give feedback.
All reactions