Allsky.log Error Message - ERROR: Field 'ZWO ASI224MC' is outside of the image

[peng155]

Hi Folks,

I just got the Allsky program setup and running on a Raspberry Pi 4B, I'm still going through the online manuals and help guides to tweak my particular setup..

I'm using a Pi 4B, 4GB RMA, 64GB SD card with a ZWO 224MC.. everything is being run on my local home network

I'm getting the following error message in allsky.log file:
ERROR: Field 'ZWO ASI224MC' is outside of the image,
The error doesn't appear to be affecting the actual operation of the Allsky program, and I "THINK" it has more to do with the information 'ZWO ASI224MC' being displayed in some field output somewhere..

I've gone through the config.sh and configuration.json files via the WebUI Editor, but I can't for the life of me find where this field is, or where the output is being called at... I'm probably totally wrong.. but if someone can provide me with a clue as to where to look.. I would appreciate it. Like I said the error doesn't appear to be affecting how the program is working, but I'd like to correct any error messages that is being logged in the allsky log...

I did a search on the is "outside of the image" portion of the error message, but did come up with anything

Thanks

[peng155]

Just a bit more info.. I had another look at the Allsky.log file, and it looks like the error message is logged during the 30 sec delay between images

[troublestarter]

• Maybe you should post your full allsky.log (please attach it to the post)
• Can you also share your parameters ?

[peng155]

Attached is the allsky log file from overnight once I tweaked all of my night settings and restarted the program, and just let it program run last night..
As for my parameters.. which ones should i post??

Thanks for the help

allsky.log

[EricClaeys]

The default overlay includes the camera type and model in the lower left corner. However, when we put it there we failed to take into account the different resolution sizes of ZWO cameras, so on some cameras it's off the bottom and you get the message you see.

You can fix it by manually changing the field's "y" value to a smaller number. The overlay file is in ~/allsky/config/overlay/config. I forget the file name but it should have "ZWO" in the name.

[peng155]

Excellent!! Thank you very much

FYI,
I was able to use the Overlay Editor in the WebUI to make the adjustments once @EricClaeys posted his reply about what field the Error was being generated by.... Once again Thank you

[peng155]

I wanted to update my post with additional info on how I corrected the "ERROR: Field 'ZWO ASI224MC' is outside of the image" I was getting in the allsky.log file....

In my particular instance, I had to modify the ~/allsky/config/overlay/config/overlay.json file... The particular section I needed to modify was:
"label": "${CAMERA_TYPE} ${CAMERA_MODEL}",
"x": 163,
"y": 143,
"id": "oe-field-4",
"fontsize": 16,
"strokewidth": 0,
"sample": "ZWO ASI174MC",
"tlx": 14,
"tly": 135
Within this section I had to change both the "tlx" and "tiy" values to some value smaller than what they were (I think they were 198, 1040 ??)

Once the values were made smaller, I could then see them in the Overlay Editor, and use the editor to make changes to the x, y and font values.

[EricClaeys]

@peng155, thanks for the info.
This will be easier in the next version of Allsky. The Overlay Editor will indicate when a field is outside the image and let you fix the field or delete it.
It works well - I had to use it on one of my fields.

[peng155]

@EricClaeys
Sure no problem, I'm finding that as I make changes in one place, I may break something somewhere else, and i sort of like being able to figure out what broke and how to fix it , if I can... As I figure this stuff out, I'll update my post as I can with anything useful.

On another note regarding the OverLay Editor.... I'm finding that as I make X and Y position changes, and save them.. Go either to the Live view or the local allsky view to see how I like my changes...

If I don't like where I placed a field either in the X or Y location (say for instance "Gain"), and go back to the Overlay Editor, I've found that my X and Y positions have changed.... Not a lot, may 5px one way or another... Is this because I may be placing the
field in between an X and/or Y grid value?

Thanks

[EricClaeys]

@peng155, it could be that. I use a 5x5 grid in the Overlay Editor and align everything on that grid, and don't have an issue with objects moving on their own.
If you enlarge or shrink the field, e.g., by adding text, the field will move so I always double click on it and adjust the X and Y settings.

[Alex-developer]

@EricClaeys Sure no problem, I'm finding that as I make changes in one place, I may break something somewhere else, and i sort of like being able to figure out what broke and how to fix it , if I can... As I figure this stuff out, I'll update my post as I can with anything useful.

On another note regarding the OverLay Editor.... I'm finding that as I make X and Y position changes, and save them.. Go either to the Live view or the local allsky view to see how I like my changes...

If I don't like where I placed a field either in the X or Y location (say for instance "Gain"), and go back to the Overlay Editor, I've found that my X and Y positions have changed.... Not a lot, may 5px one way or another... Is this because I may be placing the field in between an X and/or Y grid value?

Thanks

Are you using the fields 'properties window' to change the x and y values? If so then there may be a bug there where its not recalculating the tlx and tly values. If this is the case let me know and I will add it to the bug list

Cheers

Alex

[peng155]

@Alex-developer

I think the answer to your question is Yes, I make adjustments to the X, Y placement in the overlay position fields. I've attached a screen shot of the pop-up windows I make the adjustments in.

[Alex-developer]

That's the window I was talking about. I'll try and reproduce it and then log a ticket to fix it

Cheers

Alex

[peng155]

@Alex-developer

FYI....
I don't think the problem I ran into is a bug... per Eric, I went back to the Ovelrlay Editor, and had a look at what the Grid setting was. I was still at the install default of 20x20.. I changed it to 5x5 and I haven't seen the problem re-appear

[Alex-developer]

The step size in the properties window should track the grid size, that the bug I was referring to.

I'll add a ticket to look at it after the next release

[EricClaeys]

@peng155, if you think this Discussion is resolved would you please close it?
Thanks - Eric