Glabella Thanks for your suggestion, we will take it into consideration.
Ability to change fit key word value for TELESCOP
7 days later
AstroImg@ZWO that would be much appreciated by many of us in my circle of users ..you folks at ZWO Seestar division rock!
3 months later
AstroImg@ZWO any update on this? Would anticipate this would be relatively easy since controlling the light pollution filter already gets posed in the fits header
4 days later
Sorry, Do not have this plan in recent version for now.
7 days later
How unfortunate. Does seem to be a relatively simple task that would allow for distinguishing images from various s50’s …low hanging fruit
Glabella
Sorry, We'll reconsider.
Support@Seestar Now two of the FITS fields are the same and redundant information.
INSTRUME= 'Seestar S50' / instrument name
TELESCOP= 'Seestar S50' / telescope used to acquire this image
One of those could be default to the WiFi ID of the scope. This is in the format "S50_xxxxxxxx" i dont know the FITS format to much but if the field is limited to 11 characters the WiFi could be truncated to "S50xxxxxxxx"
LA3QMA
What is the purpose of the requirement that you want to add an SN to the Seestar S50 in the header of the Fit file? Because we need to know what you want to use this to help do.
Support@Seestar see the wish/request from @Glabella. If you have more than one Seestar and/or are working with data from different users it could be useful to identify where the data is from.
Support@Seestar very happy to know this may be reconsidered. It really should be a no brainer. And with all due respect to another poster I truly believe it should be the serial number of the telescope that replaces the field value or a concatenation of something like “S50” and it’s serial number if not too long or just the serial number. Once again and as others have also indicated this allows for any of your users who read the fit headers of your images for any classification documentation to be able to automate and document automatically which scope the data comes from. Thank you for bringing the Seestar to market. IMO it’s a very useful product for beginners and experienced astronomers of any type
LA3QMA It's useful, but probably not very useful, but I'd also bring up the requirement to the team to discuss if it needs to be changed.
Glabella Thank you very much for your much support to Seestar and recognizing ZWO. For your needs and suggestions, we will take them into consideration.
2 months later
Support@Seestar it certainly doesn’t need to be changed and it would definitely be useful to keep track of which S50 took which image when one has more than 1 Seestar imaging the same object and external post processing will be occurring. This is something that is fundamental. Currently ZWO has 2 yes 2 fit header fields that are populated with the same value when it would make a lot of sense to have one of them changed to the serial number of the scope or user definable.
Glabella
I see your point, and I agree that having a way to distinguish which Seestar captured each image would be very useful, especially when processing data from multiple devices.
It makes sense to utilize one of the existing FITS header fields for this purpose—either by assigning it the scope’s serial number or making it user-definable. This would be a simple yet effective way to improve data organization for external post-processing.
Support@Seestar I was just going over some issues I have plate solving with Siril on a somewhat irregular basis so looking at coordinates in the sub’s fit headers and also noticed that since I upgraded back around January 16th the TELESCOP header tag is now populated with what seems to be the serial number or hopefully a device unique identifier. Mine says S50_31bf74e9. (identifier changed for privacy purposes). So I would say this is great and thank you very much. I realize ZWO may have reservations about adding this to the already lengthy file name since any users that would use this piece of data would always flex the file name upon transfer in orde to avert any file name collision. In any event adding this tag to the file name between the exposure time identifier and the filter type identifier would be yet another great addition. Thanks again.
Glabella
Our team seem to be thinking about that already.