Alignment Markers correctly set, Digit ROI correctly set, but boxes don't fit on Overview Screen

[contentpirate]

The Problem

Hi folks,

following case:

• Alignment markers are set correctly under Settings -> Alignment -> Alignment Markers:

• Digit ROIs are set correctly under Settings -> ROI -> Digit ROI

• Image in Overview is not looking aligned:

Version

v15.3.0

Logfile

[0d19h06m15s] 2023-12-09T09:32:36	<ERR>	[POSTPROC] main: Raw: 41111.14N, Value: , Status: Rate too high - Read: 41111.143 - Pre: 16059.603 - Rate: 25051.540
[0d19h46m15s] 2023-12-09T10:12:36	<ERR>	[POSTPROC] main: Raw: 16060.043, Value: , Status: Neg. Rate - Read:  - Raw: 16060.043 - Pre: 16060.046 
[0d19h52m30s] 2023-12-09T10:18:52	<ERR>	[OTA FILE] File sending failed!
[0d21h31m15s] 2023-12-09T11:57:36	<ERR>	[POSTPROC] main: Raw: 41111.114, Value: , Status: Rate too high - Read: 41111.114 - Pre: 16061.085 - Rate: 25050.029
[0d21h51m15s] 2023-12-09T12:17:36	<ERR>	[POSTPROC] main: Raw: 41111.372, Value: , Status: Rate too high - Read: 41111.372 - Pre: 16061.252 - Rate: 25050.120
[0d22h06m15s] 2023-12-09T12:32:36	<ERR>	[POSTPROC] main: Raw: 41111.112, Value: , Status: Rate too high - Read: 41111.112 - Pre: 16061.436 - Rate: 25049.676
[0d23h21m15s] 2023-12-09T13:47:36	<ERR>	[POSTPROC] main: Raw: 41114.213, Value: , Status: Rate too high - Read: 41114.213 - Pre: 16062.251 - Rate: 25051.962
[0d23h31m15s] 2023-12-09T13:57:36	<ERR>	[POSTPROC] main: Raw: 16062.431, Value: , Status: Neg. Rate - Read:  - Raw: 16062.431 - Pre: 16062.555 
[0d23h36m14s] 2023-12-09T14:02:36	<ERR>	[POSTPROC] main: Raw: 16062.515, Value: , Status: Neg. Rate - Read:  - Raw: 16062.515 - Pre: 16062.555 
[0d23h41m15s] 2023-12-09T14:07:36	<ERR>	[POSTPROC] main: Raw: 16062.530, Value: , Status: Neg. Rate - Read:  - Raw: 16062.530 - Pre: 16062.555 
[1d00h06m14s] 2023-12-09T14:32:35	<ERR>	[POSTPROC] main: Raw: 41113.712, Value: , Status: Rate too high - Read: 41113.712 - Pre: 16062.666 - Rate: 25051.046
[1d00h26m14s] 2023-12-09T14:52:35	<ERR>	[POSTPROC] main: Raw: 41113.111, Value: , Status: Rate too high - Read: 41113.111 - Pre: 16062.759 - Rate: 25050.352
[1d00h31m15s] 2023-12-09T14:57:35	<ERR>	[POSTPROC] main: Raw: N1114.116, Value: , Status: Neg. Rate - Read:  - Raw: N1114.116 - Pre: 16062.759 
[1d00h56m14s] 2023-12-09T15:22:35	<ERR>	[POSTPROC] main: Raw: 16063.052, Value: , Status: Neg. Rate - Read:  - Raw: 16063.052 - Pre: 16063.654 
[1d01h01m14s] 2023-12-09T15:27:35	<ERR>	[POSTPROC] main: Raw: 16063.093, Value: , Status: Neg. Rate - Read:  - Raw: 16063.093 - Pre: 16063.654 
[1d01h06m14s] 2023-12-09T15:32:35	<ERR>	[POSTPROC] main: Raw: 3111N.N1N, Value: , Status: Rate too high - Read: 31113.614 - Pre: 16063.654 - Rate: 15049.960
[1d01h06m31s] 2023-12-09T15:32:52	<ERR>	[OTA FILE] File sending failed!
[1d01h11m14s] 2023-12-09T15:37:35	<ERR>	[POSTPROC] main: Raw: 16063.203, Value: , Status: Neg. Rate - Read:  - Raw: 16063.203 - Pre: 16063.654 
[1d01h16m14s] 2023-12-09T15:42:35	<ERR>	[POSTPROC] main: Raw: 16063.204, Value: , Status: Neg. Rate - Read:  - Raw: 16063.204 - Pre: 16063.654 
[1d01h21m14s] 2023-12-09T15:47:35	<ERR>	[POSTPROC] main: Raw: 41114.247, Value: , Status: Rate too high - Read: 41114.247 - Pre: 16063.654 - Rate: 25050.593
[1d01h26m14s] 2023-12-09T15:52:35	<ERR>	[POSTPROC] main: Raw: 16063.266, Value: , Status: Neg. Rate - Read:  - Raw: 16063.266 - Pre: 16063.654 
[1d01h31m14s] 2023-12-09T15:57:35	<ERR>	[POSTPROC] main: Raw: 16063.353, Value: , Status: Neg. Rate - Read:  - Raw: 16063.353 - Pre: 16063.654 
[1d01h36m15s] 2023-12-09T16:02:36	<ERR>	[POSTPROC] main: Raw: 16063.369, Value: , Status: Neg. Rate - Read:  - Raw: 16063.369 - Pre: 16063.654 
[1d01h41m14s] 2023-12-09T16:07:35	<ERR>	[POSTPROC] main: Raw: 16063.437, Value: , Status: Neg. Rate - Read:  - Raw: 16063.437 - Pre: 16063.654 
[1d01h46m14s] 2023-12-09T16:12:35	<ERR>	[POSTPROC] main: Raw: 16063.439, Value: , Status: Neg. Rate - Read:  - Raw: 16063.439 - Pre: 16063.654 
[1d01h51m14s] 2023-12-09T16:17:35	<ERR>	[POSTPROC] main: Raw: 16063.488, Value: , Status: Neg. Rate - Read:  - Raw: 16063.488 - Pre: 16063.654

Expected Behavior

No response

Screenshots

No response

Additional Context

No response

[contentpirate]

Also mis-aligned under "Data -> Recognition":

[caco3]

the contrast is not very good
and one ref mark should be somewhere on the top. you could use stickers for this to make it more accurate.

[contentpirate]

Okay but why is the difference between the view on setting the alignment marker to the actual placing of the box of the alignment marker in the Data -> Recognition view so different? The same for the Digit ROI?

[contentpirate]

Setting the Alignment markers to a position somewhere to the top wasn't possible after mutiple tries, as after clicking "Update Marker" after changing the Marker position didn't actually save the new marker size and position.

As the position of the markers in the Settings -> ROI -> Digital ROI view didn't match the position of the markers in the Data -> Recognition view, I chose the workaround to simply blindfoldedly adjust the Digital ROI position and then control if the boxes fit the numbers in the Recognition view.
This method is stupid, but it works and the numbers are now recognized (more) correctly.

[contentpirate]

Mis-aligned number recognition squares in the settings:

...and the correctly-aligned recognition squares in the Data -> recognition view with somewhat correctly recognized numbers:

[Slider0007]

Whenever you're alignment marker are not recognized properly the orientation seems not like defined in ROI digit/analog screen and the ROIs get cut out wrong. The overview / recognition page shows wrong alignment by misaligned ROI boxes as well

Two possiblities:

1. Either you have to ensure that alignment marker have proper contour, contrast and positoned as far as possbile (like already described by @caco3)
   OR
2. It's possible to switch off algorithm based alignment by an expert parameter in configuration screen. Just switch this parameter to "off". Then only initial rotation which is defined in reference image screen is getting applied. No Alignment marker are necessary anymore. (Small but possibly negligible drawback: Small variances of missalignment are not getting corrected, only static orientation tasks are performed)

[Marvel912]

same issue here. setting the points of interest, all looks good, but on Overview screen view, a bit off :-( taken the numbers incorrect too. i just did first time installation, with using ver. 15.3.0

updated 5min later: looks like after 2nd measurement, camera is getting clother with point of interest. not perfect, but closely.. numbers looks ok now. will keep an eye on it..

[caco3]

make the m3 ref mark smaller.
where is the 2nd mark?
dig ROIs must be maller