SharpCap Forums

I am using a ZWO ASI294MM Pro with SharpCap version 4.1.12529.0. The astro computer is an PrimaLuceLab Eagle4Pro running Microsoft Windows 11 pro. I am capturing spectra from an LHiresIII spectroscope destined to end up being published to the AAVSO Avspec spectra database. My version of SharpCap writes the serial number of my camera to the CAMID field.

OBSLONG = -121.46041666666667 /
CAMID = '39228C0525090900
PIERSIDE = 'WEST'

Unfortunately it does leave out the second hash mark so the Avspec entry form software, crashes when I try and submit an individual spectra record. If I add the second hash mark, it submits quietly without protesting. A good friend of mine, who is teaching me how to process the spectra, also uses SharpCap to capture his raw spectra sub frames. His version does not even write a CAMID field to the fits header so they process without a hitch.

Is it possible to stop the field CAMID from being written to or to make it complete writing the contents with the second hash mark?

Hi,

Ok, thanks for the report. I think what is happening is that the camera does not have a custom name set up, so the data for that is all zero value bytes. SharpCap was incorrectly including those zero value bytes as part of the CAMID field. The terminating quote character is being written after them, but a lot of code treats a zero byte as 'end of string', so when the FITS file is being read back, the data is cut short and appears without the closing ' character.

Anyway, it's something I can fix for the next SharpCap update on Monday.

cheers,

Robin