GPS information with 4.1.11013.0-64bit
-
- Posts: 417
- Joined: Sun Oct 13, 2019 10:52 am
- Location: Germany
GPS information with 4.1.11013.0-64bit
Hello Robin,
Do you change something how the GPS information's are saved and showed in the version 4.1.11013 ?
I did an occultation this evening (from (200013) 2007 LC29) in preparation to the occultation of tomorrow evening with the asteroid Limpopo (1490).
I remark 2 changes :
- the GPS information are now not complete
- the upper part of the image is no more several lines, but only a few pixels on the first line on the left
Can you confirm that all the important information are still saved in the SER (ADV or FITS) files (means directly on the images) ?
If not the case, then I will reinstall an older version.
Regards,
Jean-Francois
Do you change something how the GPS information's are saved and showed in the version 4.1.11013 ?
I did an occultation this evening (from (200013) 2007 LC29) in preparation to the occultation of tomorrow evening with the asteroid Limpopo (1490).
I remark 2 changes :
- the GPS information are now not complete
- the upper part of the image is no more several lines, but only a few pixels on the first line on the left
Can you confirm that all the important information are still saved in the SER (ADV or FITS) files (means directly on the images) ?
If not the case, then I will reinstall an older version.
Regards,
Jean-Francois
Re: GPS information with 4.1.11013.0-64bit
Hi,
So far I did not find the time for testing the new SC 4.1 (mainly regarding stellar occultations recording with the QHY174GPS).
A short test confirmes Jean-Francois' report, see the pictures below (W10-64, SC pro, QHY174GPS with firmware upgrade):
Cheers
Christian
So far I did not find the time for testing the new SC 4.1 (mainly regarding stellar occultations recording with the QHY174GPS).
A short test confirmes Jean-Francois' report, see the pictures below (W10-64, SC pro, QHY174GPS with firmware upgrade):
Cheers
Christian
- admin
- Site Admin
- Posts: 13520
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: GPS information with 4.1.11013.0-64bit
Hi folks,
let me check this - I haven't really changed the relevant code significantly between 4.0 and 4.1, but there have been SDK updates from QHY and I am suspicious that the fact that the amount of digital noise at the top of the image has changed might mean that the SDK change has done this
cheers,
Robin
let me check this - I haven't really changed the relevant code significantly between 4.0 and 4.1, but there have been SDK updates from QHY and I am suspicious that the fact that the amount of digital noise at the top of the image has changed might mean that the SDK change has done this
cheers,
Robin
- admin
- Site Admin
- Posts: 13520
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: GPS information with 4.1.11013.0-64bit
Hi,
yes, it looks like the latest QHY SDK update that I included stops the extra data from coming through to SharpCap. I have just seen that there is another new SDK version from 2 days ago, so I will test that later and see how it does.
cheers,
Robin
yes, it looks like the latest QHY SDK update that I included stops the extra data from coming through to SharpCap. I have just seen that there is another new SDK version from 2 days ago, so I will test that later and see how it does.
cheers,
Robin
- admin
- Site Admin
- Posts: 13520
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: GPS information with 4.1.11013.0-64bit
Hi folks,
the latest 23.09.06 SDK on the QHY website also has this issue
I have reported the issue to QHY and will be putting SharpCap back to the 23.05.09 SDK in next week's update, since that one works correctly.
cheers,
Robin
the latest 23.09.06 SDK on the QHY website also has this issue
I have reported the issue to QHY and will be putting SharpCap back to the 23.05.09 SDK in next week's update, since that one works correctly.
cheers,
Robin
-
- Posts: 417
- Joined: Sun Oct 13, 2019 10:52 am
- Location: Germany
Re: GPS information with 4.1.11013.0-64bit
Hello Christian and Robin,
Thanks for checking.
Some pixels are changed at the begin of the first line. I guess that it is the time and position information.
If the additional information is today missing, that is not a problem. It is more a problem if the GPS time is not inserted in the images.
Note that I synchronise my computer with the GPS from the camera ... so the time difference would be minimised.
Yesterday evening, I did an observation of the (200013) 2007 LC29 asteroid and I did a quick analysis with Tangra.
Tangra did the analysis without error message. But may be it takes automatically the time of the SER images and not from the info from the image itself. I do not know how to check the origin of the time.
For the event of this evening, I will reinstall an older version of 4.1.
Christian, my script works only with the 4.1 while several changes (ASCOM and IronPython).
Regards,
Jean-Francois
Thanks for checking.
Some pixels are changed at the begin of the first line. I guess that it is the time and position information.
If the additional information is today missing, that is not a problem. It is more a problem if the GPS time is not inserted in the images.
Note that I synchronise my computer with the GPS from the camera ... so the time difference would be minimised.
Yesterday evening, I did an observation of the (200013) 2007 LC29 asteroid and I did a quick analysis with Tangra.
Tangra did the analysis without error message. But may be it takes automatically the time of the SER images and not from the info from the image itself. I do not know how to check the origin of the time.
For the event of this evening, I will reinstall an older version of 4.1.
Christian, my script works only with the 4.1 while several changes (ASCOM and IronPython).
Regards,
Jean-Francois
Re: GPS information with 4.1.11013.0-64bit
Thank you, Robin, for your quick reply (and to Jean-Francois for finding this problem).
Christian
Christian
Re: GPS information with 4.1.11013.0-64bit
TBH, I thought that truncating the data payload in the top of the image file had been done on purpose to stop it interfering with the processing of auto gain settings which finally works properly (and makes finessing of the settings so much easier).
I have been doing my own testing, including a +ve occultation and was a little concerned that the time was out. Fortunately, I have been keeping the QHY GPS logs also and can confirm that the time on my SER file matches the time recorded in CameraSettings.txt and the GPS time recorded in the log file. Phew!
NOTE: I have added the header line and spaced the text in the GPS log file to line up for clarity.
I have been doing my own testing, including a +ve occultation and was a little concerned that the time was out. Fortunately, I have been keeping the QHY GPS logs also and can confirm that the time on my SER file matches the time recorded in CameraSettings.txt and the GPS time recorded in the log file. Phew!
NOTE: I have added the header line and spaced the text in the GPS log file to line up for clarity.
- Attachments
-
- Confirmed timestamp.png (197.44 KiB) Viewed 5191 times
Jonathan Bradshaw
Quaerens veritatem de umbrae
Quaerens veritatem de umbrae
-
- Posts: 417
- Joined: Sun Oct 13, 2019 10:52 am
- Location: Germany
Re: GPS information with 4.1.11013.0-64bit
Hello Robin,
Do you change something ?
The GPS extra data are now back in the 4.1.11049 version.
Regards,
Jean-Francois
Do you change something ?
The GPS extra data are now back in the 4.1.11049 version.
Regards,
Jean-Francois
- admin
- Site Admin
- Posts: 13520
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: GPS information with 4.1.11013.0-64bit
Hi,
yes, I went back to an older QHY SDK which didn't have the issue.
I have reported the problem to QHY, and they acknowledged it a couple of weeks back, but no new update that I have seen yet.
cheers,
Robin
yes, I went back to an older QHY SDK which didn't have the issue.
I have reported the problem to QHY, and they acknowledged it a couple of weeks back, but no new update that I have seen yet.
cheers,
Robin