Leo, when using MaximDL for camera control and an image is downloaded from MaximDL to Voyager, does that image contain a Airmass value in the FITS header? The reason I ask is I used the 2.1.7s version of Voyager last night with the update airmass property in camera setup unchecked. On each image recorded to disk I do not see an airmass value in the FITS header. But if I use MaximDL standalone and take an image, the disk image does contain a airmass value. To fix this I checked the update airmass property in camera setup and the airmass value is restored.
If you use maxim fior camera control voyager doesn’t manage fit save … maxim save with header.
Does Voyager add data to the FITS header?
Yes for sure , but not airmass if you remove flag. Your solution is outside voyager
If the image from MaximDL had an airmass value in the FITS header, does Voyager remove it or not include it in the image written to disk by MaximDL?
Craig voyager doesn’t remove anything. Shot from maxim is not equal to shot from voyager using maxim… Save button in Maxim probably do different things than save command with external COM interface.
Please let me know if Maxim have a command to retrieve AirMass value … i can force inside FIT, or you must use Voyager calculation (in this case please provide an algorithm that have a number of dot compatible with your appliance).
All the best
Leo, can you tell me what the difference is between the two images? Does MaximDL only pass the image bits and Voyager has to create the FITS header?
Craig i can only save the image and before if i want i can add some header … i cant remove , i can add or change value !!
I think the best solution is to ask directly to Maxim developers when they add the airmass entry or if there’s a flag to check to add it or a method to read it.
All the best
What interface does Voyager use to access MaximDL? ActiveX, COM, ASCOM, etc? I’ll need to know this when asking the MaximDL guys what is contained in the image when passed to an external application and what properties might be available.
maxim have only one interface to interact.
All the best
I think I found the answer. When I link Voyager to MaximDL then MaximDL does not know the state of the telescope and hence it cannot put many fields such as RA and DEC and Airmass into the header. I am assuming then that Voyager is doing this. One way to fix it is to have MaximDL also link to the telescope as another ASCOM client.
I check again the code and is all ok. I think problem is what you wrote. Can you test it? Solution for me is to find a more digit algorithms
Confirmed. If MaximDL is not connected to the mount then airmass is not put in the FITS header. If NOT manage Airmass is checked in Voyager camera setup then all new images will not contain the airmass in the FITS header.
In MaximDL, connect to mount and NOT manage Airmass is checked in Voyager camera setup then all new images do contain the airmass value calculated by MaximDL.
So as part of my startup procedure I go to the MaximDL window (after Voyager has started it) and connect to the mount. I now get airmass in the FITS header and it is high precision value.
Ok thanks , I’ll check if I can connect the mount with voyager at startup in maxim (I’ll add a check)