You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Correct. THis is also what they state on the website. And this is why I don't understand why the provide the single DLL files  |
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Correct. THis is also what they state on the website. And this is why I don't understand why the provide the single DLL files
Thank you very much.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Let me know how it goes and if any success with proper results  |
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
sebaromano
Let me know how it goes and if any success with proper results  Very good results with the ASCOM driver, but not as good as yours. But it is alsmost in spec, so I am happy for now. The hassle with all the dlls was mind bending, so I will keep that as it is.  Regards
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
that looks quite good ;) Next test is under the stars |
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Hey Tobiasz,
Did you try to try open the camera with NINA and without issues? I use Voyager and everything seems to be working fine with Touptek ASCOM driver (which is the only driver I can use with Voyager). But then by curiousity I tried the camera with NINA and strange thing is that NINA cannot find the camera, not even iby opening the Touptek ASCOM (the camera doesn't show up in the listed optins) . I didn't have this issue with the 585C version.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Hey Tobiasz,
Did you try to try open the camera with NINA and without issues? I use Voyager and everything seems to be working fine with Touptek ASCOM driver (which is the only driver I can use with Voyager). But then by curiousity I tried the camera with NINA and strange thing is that NINA cannot find the camera, not even iby opening the Touptek ASCOM (the camera doesn't show up in the listed optins) . I didn't have this issue with the 585C version. After your suggestion with the Touptek ASCOM Setup, I got rid of everything and only reinstalled the ASCOM Setup. I tested both Sharpcap and Nina and there were no issues. You made sure NINA has the same .dll as Sharpcap? One of those many dll's I tested was faulty and my camera was not recognized in Sharpcap. When I uninstalled the Touptek Setup the dll files were still there in Nina and Sharpcap. I had to delete them manually. Edit: Just tested the connection in NINA right now and it works without problems.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Tobiasz:
Hey Tobiasz,
Did you try to try open the camera with NINA and without issues? I use Voyager and everything seems to be working fine with Touptek ASCOM driver (which is the only driver I can use with Voyager). But then by curiousity I tried the camera with NINA and strange thing is that NINA cannot find the camera, not even iby opening the Touptek ASCOM (the camera doesn't show up in the listed optins) . I didn't have this issue with the 585C version.
After your suggestion with the Touptek ASCOM Setup, I got rid of everything and only reinstalled the ASCOM Setup. I tested both Sharpcap and Nina and there were no issues.
You made sure NINA has the same .dll as Sharpcap? One of those many dll's I tested was faulty and my camera was not recognized in Sharpcap. When I uninstalled the Touptek Setup the dll files were still there in Nina and Sharpcap. I had to delete them manually.
Edit: Just tested the connection in NINA right now and it works without problems. *thanks TObiasz for the quick answer . Probably the DLL under NINA got corrupted. I will play with it agan tomorrow and try to reinstall the ASCOM. Probably it will fix it. I am not overly concerned.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Quick update: remember I said that I wiped the computer and reinstalled everything. Well, I remember now that I installed NINA after installing the Touptek ASCOM. So NINA didn't catch the DLL files. I re-installed the Touptek ASCOM and now NINA finds the ATR585M camera. So that was totaly my fault and nothing to do with NINA nor the camera….but it proved the importance of installing properly (and ONLY) the Touptek ASCOM |
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Quick update: remember I said that I wiped the computer and reinstalled everything. Well, I remember now that I installed NINA after installing the Touptek ASCOM. So NINA didn't catch the DLL files. I re-installed the Touptek ASCOM and now NINA finds the ATR585M camera.
So that was totaly my fault and nothing to do with NINA nor the camera....but it proved the importance of installing properly (and ONLY) the Touptek ASCOM *What are your sharpcap results now? Great that it works now!
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
I will not run another sensor analisys since i simply re-installed the same ASCOM driver that I have originally downloaded so I am not exepcting any changes on the camera performance
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
EDIT: I ran it again (damn) and values are back to the lower side. Don't ask me why as I am still scratching my head) and I am not going to figure this out by messing up with DLL files. I feel going through the exact same saga I ran with the 585C and at the end I settled by accepting the latest results that were comaparable to the 16 bit IMX571 sensor (this forum has the record of thse comments if you browes a few pages back ) . So the party is not completly ruined but still left me with a bitter taste from Touptek that advise something different from reality. BTW: did you get a reply from Touptek when you contacted about below performance?  |
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
EDIT: I ran it again (damn) and values are back to the lower side. Don't ask me why as I am still scratching my head) and I am not going to figure this out by messing up with DLL files. I feel going through the exact same saga I ran with the 585C and at the end I settled by accepting the latest results that were comaparable to the 16 bit IMX571 sensor (this forum has the record of thse comments if you browes a few pages back ) .
So the party is not completly ruined but still left me with a bitter taste from Touptek that advise something different from reality.
BTW: did you get a reply from Touptek when you contacted about below performance?
* I feel your pain, but those results look like you connected the camera as "ATR585M" and not "Ascom Touptek Camera", correct? Because when I run the test as "ATR585M" my results are 99% the same as yours. But the better results I get (~0,7e RN) are with the "Ascom Touptek Camera". I got only the answer from Touptek that they will contact the engineering departement, nothing more until now.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Tobiasz:
EDIT: I ran it again (damn) and values are back to the lower side. Don't ask me why as I am still scratching my head) and I am not going to figure this out by messing up with DLL files. I feel going through the exact same saga I ran with the 585C and at the end I settled by accepting the latest results that were comaparable to the 16 bit IMX571 sensor (this forum has the record of thse comments if you browes a few pages back ) .
So the party is not completly ruined but still left me with a bitter taste from Touptek that advise something different from reality.
BTW: did you get a reply from Touptek when you contacted about below performance?
*
I feel your pain, but those results look like you connected the camera as "ATR585M" and not "Ascom Touptek Camera", correct? Because when I run the test as "ATR585M" my results are 99% the same as yours. But the better results I get (~0,7e RN) are with the "Ascom Touptek Camera".
I got only the answer from Touptek that they will contact the engineering departement, nothing more until now. That is the unexplainable thing: camera was connected as Ascom Touptek Camera. The ONLY thing i did was reinstalling the Touptek ASCOM driver (the exact same one I still had saved in my download folder and that I installed just a couple days before).
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
I'm one of ToupTek-Astro technical staff. I alreday understand your doubts. I think our test eviroment and parameter might be different form yours. We cooled 585 mono to -10℃, testing in Sharpcap with ASCOM driver. And also the firmware version might be different. When we were writing ATR585M manuel, the firmware version was still 4.37, while the relesed version is 4.47. If you are interested, you may reverse the firmware version to 4.37 and do the test again. Here's the related file you may need:
<google-drive-link> Touptek answered me. It seems the results from the manual were done with the ASCOM driver and FW version 4.37. Newer cameras are provided with V4.47. They provided me both firmwares but I will not reverse my FW version for 0,1e read noise decrease. I am happy with this result and only use the camera via the ASCOM driver from now on. I wrote a response asking them why they provide two different drivers with different results for the same camera and if they recommend using the ASCOM driver for the atr585m over the native driver. Regards
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Thanks Tobiasz for sharing Touptek response. Would you share those 2 FW if you don't mind? Because in the ZIP file they usually include also the tool to upload the FW which has a functionality to check what FW the camera has. Also have you tried to run again the sensor analisys for results consistency ? I am thinking probably to give it another run just for the pleasure of torturing my self a bit more  …because I am still puzzled by the fact that got different results by reinstalling the same Ascom driver. I wonder if there is some sort of "randomness" behavior either from the camera or from Sharpcap ability to read results from this HDR feature. And if there is some sort of "randomness" I wonder what happens with NINA? Can we assume NINA is using actually the values we see in Sharpcap??? …..I need to change hobby  ….but I also like problem solving so I guess I am in the right territory  BR//Seba
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
and as promised, I just ran again the sensor analysis under ASCOM driver HDR mode. And voila'. I will not run it again and take these as last official ones. Perhaps someone will be able to figure this out.  |
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Thanks Tobiasz for sharing Touptek response. Would you share those 2 FW if you don't mind? Because in the ZIP file they usually include also the tool to upload the FW which has a functionality to check what FW the camera has.
Also have you tried to run again the sensor analisys for results consistency ? I am thinking probably to give it another run just for the pleasure of torturing my self a bit more  ...because I am still puzzled by the fact that got different results by reinstalling the same Ascom driver. I wonder if there is some sort of "randomness" behavior either from the camera or from Sharpcap ability to read results from this HDR feature. And if there is some sort of "randomness" I wonder what happens with NINA? Can we assume NINA is using actually the values we see in Sharpcap???
.....I need to change hobby  ....but I also like problem solving so I guess I am in the right territory 
BR//Seba * I think my results should be consistent now, because I changed nothing anymore after that. I think the DLLs Nina and Sharpcap use are the native driver. I checked both and both are the same version. The Ascom Driver is located in the Ascom folder on my C:\ drive, where also the Touptek Ascom dll is. I think this is the real "Ascom Touptek camera" driver. I think there is no randomness of the drivers, just the Ascom Setup which may not fully delete the old files before reinstallation. As I said before I had to delete the dll files manually before the Touptek driver setup because the versions didn't change after that. If you want, I can test my camera later again.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
and as promised, I just ran again the sensor analysis under ASCOM driver HDR mode. And voila'.
I will not run it again and take these as last official ones. Perhaps someone will be able to figure this out.
* Lookin' good. Now you just need to get those results consistently after several tests and then you can be 100% sure and finally sleep in peace 😀 I will do some tests this evening, let's see. It is cloudy so no lost time either.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
before re-running it I did re-install the ASCOM. "maybe" the previous installaiton something happened to the DLL files and now once reinstalled it did fix it Who knows!
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
before re-running it I did re-install the ASCOM. "maybe" the previous installaiton something happened to the DLL files and now once reinstalled it did fix it
Who knows! * I dont know, but I experienced the same issue here now. Started up the mini pc and get to the tests and im back again at 1e read noise. Did the test 3 times. Now reinstalled ascom and for whatever reason I am down to almost 0,6e RN. Its my best result so far. Man this is getting annoying to be honest. Tests are running and after a Reboot I will repeat them to see if something changed.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Tobiasz:
before re-running it I did re-install the ASCOM. "maybe" the previous installaiton something happened to the DLL files and now once reinstalled it did fix it
Who knows!
*
I dont know, but I experienced the same issue here now. Started up the mini pc and get to the tests and im back again at 1e read noise. Did the test 3 times.
Now reinstalled ascom and for whatever reason I am down to almost 0,6e RN. Its my best result so far. Man this is getting annoying to be honest.
Tests are running and after a Reboot I will repeat them to see if something changed. I am luaghing now, (sorry). Well, atleast this confirms that I am not crazy. I think Sharpcap needs to work something specific for this HDR FW. This is why I was making that comment about wondering what values NINA reads in reality In any cae and if of any consolation, the values we get in the worse case scenario are still better than what I see with the IMX571 sensor.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Tobiasz:
before re-running it I did re-install the ASCOM. "maybe" the previous installaiton something happened to the DLL files and now once reinstalled it did fix it
Who knows!
*
I dont know, but I experienced the same issue here now. Started up the mini pc and get to the tests and im back again at 1e read noise. Did the test 3 times.
Now reinstalled ascom and for whatever reason I am down to almost 0,6e RN. Its my best result so far. Man this is getting annoying to be honest.
Tests are running and after a Reboot I will repeat them to see if something changed.
I am luaghing now, (sorry). Well, atleast this confirms that I am not crazy. I think Sharpcap needs to work something specific for this HDR FW. This is why I was making that comment about wondering what values NINA reads in reality
In any cae and if of any consolation, the values we get in the worse case scenario are still better than what I see with the IMX571 sensor.
Did the Reboot and after that the test 3 times. 0,6e at best. Looks consistent now, lets hope it stays like that. I will still clarify it with Touptek.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
New update from Touptek engineering regarding different results between the drivers and what driver to use: We still recommend to use the local driver. The differences between
testing with "native driver" and "ASCOM driver" might came from the
way how sharpcap invokes the drivers. I don't think there are acutual
difference of sensor perfomance. We keep using ASCOM driver for sensor
analysis just because we did the test with ASCOM driver in the very
beginning, and we would like to maintain the consistency of testing. Local driver = "ATR585M" and not the ASCOM driver I guess? Hot take from Touptek: Sharpcap invokes vendor drivers differently, which results in worse results? I question myself: Can this happen with NINA, too? I asked them back, if they can verify that both drivers achieve the same sensor performance via internal testing and not relying on third party tools like sharpcap. A company like this should have their own big and expensive testing environment, I hope :-D Regards
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
At the moment I can't test the HDR mode in sharp cap because I too have the weird bug, which messes up the measurements. I accidently updated sharpcap and a rollback to an older version does not help either.
