Problem connecting to QSI camera via ASCOM

[SimonWalsh1000]

Hi Michel - I am running MW4 v0.150.29

I can't connect to my QSI camera. I had previous be using an ASI 1600mm without problems but now, when I try to change the camera setting via camara>set>ASCOM device set up>QSI CCD Camera the field will not update to the QSI camera. It remains on ascom-ASICamera2.Camera. Do you have any suggestions please? Best, Simon

[mworion]

Hi Simon, I will try this during the weekend. As I own a QSI as well, but never used it from ASCOM, I'll give it a try. Did you try QSI with ASCOM or the native driver ? Michel

[SimonWalsh1000]

Hi Michel,

I tried to connect via the native driver.

ie selected ASCOM, then selected QSI CCD Camera from the drop down. But could not get it to connect.

Simon

[mworion]

Simon,

I think I found the issue. v 0.151.1 should do the trick. I used the actual QSI driver from their webpage 1.0.0.4 which was uploaded recently.

Michel

[SimonWalsh1000]

Unfortunately there are issues with the new QSI driver and other programmes like Voyager and SGP. Does this version of MW work with the older driver?

Best, Simon

On 7 Aug 2020, at 17:34, Michael notifications@github.com wrote:

 Simon,

I think I found the issue. v 0.151.1 should do the trick. I used the actual QSI driver from their webpage 1.0.0.4 which was uploaded recently.

Michel

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[mworion]

Basically it should be no problem, but I only took the recent driver for testing. Michel

Am 07.08.2020 um 18:49 schrieb SimonWalsh1000 notifications@github.com:

Unfortunately there are issues with the new QSI driver and other programmes like Voyager and SGP. Does this version of MW work with the older driver?

Best, Simon

On 7 Aug 2020, at 17:34, Michael notifications@github.com wrote:

 Simon,

I think I found the issue. v 0.151.1 should do the trick. I used the actual QSI driver from their webpage 1.0.0.4 which was uploaded recently.

Michel

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mworion/MountWizzard4/issues/61#issuecomment-670609523, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSTMFCDCKN7DR4WCMO3TD3R7QWA7ANCNFSM4PXMGHEQ.

[SimonWalsh1000]

Michel thanks very much for this and all your work; I will give it a go tonight!

Best, Simon

On 7 Aug 2020, at 18:23, Michael notifications@github.com wrote:

 Basically it should be no problem, but I only took the recent driver for testing. Michel

Am 07.08.2020 um 18:49 schrieb SimonWalsh1000 notifications@github.com:

Unfortunately there are issues with the new QSI driver and other programmes like Voyager and SGP. Does this version of MW work with the older driver?

Best, Simon

On 7 Aug 2020, at 17:34, Michael notifications@github.com wrote:

 Simon,

I think I found the issue. v 0.151.1 should do the trick. I used the actual QSI driver from their webpage 1.0.0.4 which was uploaded recently.

Michel

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mworion/MountWizzard4/issues/61#issuecomment-670609523, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSTMFCDCKN7DR4WCMO3TD3R7QWA7ANCNFSM4PXMGHEQ.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[SimonWalsh1000]

Hi Michel,

Unfortunately, I couldn't get it to connect to the camera either with the new or legacy drivers. I find that the new drivers don't work for me in Voyager or SGP and I have discussed this at length with QSI (although the legacy drivers work fine). There are also some posts on CNs about it.

Not sure what the next step is - is there a way to debug this?

Best, Simon

On Fri, 7 Aug 2020 at 18:31, Simon Walsh slfwalsh@gmail.com wrote:

Michel thanks very much for this and all your work; I will give it a go tonight!

Best, Simon

On 7 Aug 2020, at 18:23, Michael notifications@github.com wrote:



Basically it should be no problem, but I only took the recent driver for testing. Michel

Am 07.08.2020 um 18:49 schrieb SimonWalsh1000 <notifications@github.com :

Unfortunately there are issues with the new QSI driver and other programmes like Voyager and SGP. Does this version of MW work with the older driver?

Best, Simon

On 7 Aug 2020, at 17:34, Michael notifications@github.com wrote:

 Simon,

I think I found the issue. v 0.151.1 should do the trick. I used the actual QSI driver from their webpage 1.0.0.4 which was uploaded recently.

Michel

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/mworion/MountWizzard4/issues/61#issuecomment-670609523>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABSTMFCDCKN7DR4WCMO3TD3R7QWA7ANCNFSM4PXMGHEQ .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mworion/MountWizzard4/issues/61#issuecomment-670624043, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACNL4HVO4XZ4NHN2AKGQ4ELR7Q2CHANCNFSM4PXMGHEQ .

--

SLFWalsh MD MRCP FFRRCSI Consultant Radiologist, NIHR Clinician Scientist, National Heart and Lung Institute, Imperial College, London

Imaging Chair, European Respiratory Society Associate Editor, European Respiratory Journal http://erj.ersjournals.com

[mworion]

Simon,

If you could post the Logfile that could help. Unfortunately I already put mit rig into the garden so I can‘t check QSI with ASCOM connection when using an older driver and debug it. Could be done probably tomorrow if the log does not tell anything.

Michel

[SimonWalsh1000]

No worries!

Will do tomorrow.

Many thanks again.

Clear skies for tonight.

Best, Simon

On 7 Aug 2020, at 20:22, Michael notifications@github.com wrote:

 Simon,

If you could post the Logfile that could help. Unfortunately I already put mit rig into the garden so I can‘t check QSI with ASCOM connection when using an older driver and debug it. Could be done probably tomorrow if the log does not tell anything.

Michel

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[mworion]

Simon, Any news about the QSI driver ? Michel

[SimonWalsh1000]

Hi Michel,

Sorry for the late response; I still can’t get my camera to connect using the legacy driver which is the only one that works for me otherwise. Incidentally, there are quite a few people having problems with the newest QSI driver and unfortunately ATIK (who now own QSI) seem indifferent to their customers.

It’s cloudy now but tomorrow I’ll create a log in MW4 so you can see what the issue is.

Thanks again for your interest.

Best, Simon

[SimonWalsh1000]

Hi Michel,

Sorry for the late response.

I have a new computer and downloaded MW4 onto it. I managed to connect my QSI camera and then proceeded to connect my other ASCOM devices (focuser, FW, mount and MGPBox). This all worked fine...once. And then when I closed the application and reopened it, I couldn't get anything to connect. I have attached my log (it's the full log, but all you need to look at are the entries after about 10:15 (am).

One thing I am unsure of. There is a section that says "connect" and "disconnect" as well as a tick box for "automatic connection" via ASCOM. Should this be used?

Lastly - and this is a different issue; regarding the platesolver. I am using ASTAP. When I set this up, the path to ASTAP works but the I cannot seem to get the path to the index files to work. I placed the Astrometry.net index files in a folder called "Astrometry" in my main MW4 folder (and also tried placing them in the ASTAP folder without luck.

Let me know what you think...and many thanks.

Simon mw4-2020-08-23.log

[mworion]

Hi Simon,

as I‘m on holiday till 30/08 I probably not able to help you with the log analyses. Regarding ASCOM there was a wish of Rüdiger and other ASCOM users to be able to check autoconnect (then MW4 tries to connect ASCOM device 5 times during startup) in addition you could uncheck this and connect you ASCOM devices manually (pressing the connect button).

Regarding ASTAP: It brings it‘s own index files with it. So please have a look to Han‘s page and download the G17 (i think so it is called) database as well in the default folder.

Michel

Am 23.08.2020 um 12:55 schrieb SimonWalsh1000 notifications@github.com:

 Hi Michel,

Sorry for the late response.

I have a new computer and downloaded MW4 onto it. I managed to connect my QSI camera and then proceeded to connect my other ASCOM devices (focuser, FW, mount and MGPBox). This all worked fine...once. And then when I closed the application and reopened it, I couldn't get anything to connect. I have attached my log (it's the full log, but all you need to look at are the entries after about 10:15 (am).

One thing I am unsure of. There is a section that says "connect" and "disconnect" as well as a tick box for "automatic connection" via ASCOM. Should this be used?

Lastly - and this is a different issue; regarding the platesolver. I am using ASTAP. When I set this up, the path to ASTAP works but the I cannot seem to get the path to the index files to work. I placed the Astrometry.net index files in a folder called "Astrometry" in my main MW4 folder (and also tried placing them in the ASTAP folder without luck.

Let me know what you think...and many thanks.

Simon mw4-2020-08-23.log

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[SimonWalsh1000]

Hi Michel,

Many thanks for your email. No problem. I seem to have it working now. For some reason, my devices fail to automatically connect but if I go through the - set up>properties and just press OK for each device, they connect.

One feature that would be really useful for me would be the ability to park the mount after running a full model. Occasionally I don't have time to sit by the mount but once I ran a model and went to bed; in the morning I had a pier collision because it was tracking the final point. If you could set the mount to park after solving the final point, that would be great.

Best, Simon

On Sun, 23 Aug 2020 at 15:18, Michael notifications@github.com wrote:

Hi Simon,

as I‘m on holiday till 30/08 I probably not able to help you with the log analyses. Regarding ASCOM there was a wish of Rüdiger and other ASCOM users to be able to check autoconnect (then MW4 tries to connect ASCOM device 5 times during startup) in addition you could uncheck this and connect you ASCOM devices manually (pressing the connect button).

Regarding ASTAP: It brings it‘s own index files with it. So please have a look to Han‘s page and download the G17 (i think so it is called) database as well in the default folder.

Michel

Am 23.08.2020 um 12:55 schrieb SimonWalsh1000 <notifications@github.com :

 Hi Michel,

Sorry for the late response.

I have a new computer and downloaded MW4 onto it. I managed to connect my QSI camera and then proceeded to connect my other ASCOM devices (focuser, FW, mount and MGPBox). This all worked fine...once. And then when I closed the application and reopened it, I couldn't get anything to connect. I have attached my log (it's the full log, but all you need to look at are the entries after about 10:15 (am).

One thing I am unsure of. There is a section that says "connect" and "disconnect" as well as a tick box for "automatic connection" via ASCOM. Should this be used?

Lastly - and this is a different issue; regarding the platesolver. I am using ASTAP. When I set this up, the path to ASTAP works but the I cannot seem to get the path to the index files to work. I placed the Astrometry.net index files in a folder called "Astrometry" in my main MW4 folder (and also tried placing them in the ASTAP folder without luck.

Let me know what you think...and many thanks.

Simon mw4-2020-08-23.log

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mworion/MountWizzard4/issues/61#issuecomment-678780000, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACNL4HQOT2MCPVJC5VJJLV3SCEQLHANCNFSM4PXMGHEQ .

--

SLFWalsh MD MRCP FFRRCSI Consultant Radiologist, NIHR Clinician Scientist, National Heart and Lung Institute, Imperial College, London

Imaging Chair, European Respiratory Society Associate Editor, European Respiratory Journal http://erj.ersjournals.com

[SimonWalsh1000]

Just to add one thing Michel.

The imaging section in settings lists the camera parameters which seem to be pulled from the camera driver. But my QSI does not have this listed in the driver; is there a way to manually populate these fields?

Best, Simon

On Sun, 23 Aug 2020 at 17:32, Simon Walsh slfwalsh@gmail.com wrote:

Hi Michel,

Many thanks for your email. No problem. I seem to have it working now. For some reason, my devices fail to automatically connect but if I go through the - set up>properties and just press OK for each device, they connect.

One feature that would be really useful for me would be the ability to park the mount after running a full model. Occasionally I don't have time to sit by the mount but once I ran a model and went to bed; in the morning I had a pier collision because it was tracking the final point. If you could set the mount to park after solving the final point, that would be great.

Best, Simon

On Sun, 23 Aug 2020 at 15:18, Michael notifications@github.com wrote:

Hi Simon,

as I‘m on holiday till 30/08 I probably not able to help you with the log analyses. Regarding ASCOM there was a wish of Rüdiger and other ASCOM users to be able to check autoconnect (then MW4 tries to connect ASCOM device 5 times during startup) in addition you could uncheck this and connect you ASCOM devices manually (pressing the connect button).

Regarding ASTAP: It brings it‘s own index files with it. So please have a look to Han‘s page and download the G17 (i think so it is called) database as well in the default folder.

Michel

Am 23.08.2020 um 12:55 schrieb SimonWalsh1000 <notifications@github.com :

 Hi Michel,

Sorry for the late response.

I have a new computer and downloaded MW4 onto it. I managed to connect my QSI camera and then proceeded to connect my other ASCOM devices (focuser, FW, mount and MGPBox). This all worked fine...once. And then when I closed the application and reopened it, I couldn't get anything to connect. I have attached my log (it's the full log, but all you need to look at are the entries after about 10:15 (am).

One thing I am unsure of. There is a section that says "connect" and "disconnect" as well as a tick box for "automatic connection" via ASCOM. Should this be used?

Lastly - and this is a different issue; regarding the platesolver. I am using ASTAP. When I set this up, the path to ASTAP works but the I cannot seem to get the path to the index files to work. I placed the Astrometry.net index files in a folder called "Astrometry" in my main MW4 folder (and also tried placing them in the ASTAP folder without luck.

Let me know what you think...and many thanks.

Simon mw4-2020-08-23.log

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mworion/MountWizzard4/issues/61#issuecomment-678780000, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACNL4HQOT2MCPVJC5VJJLV3SCEQLHANCNFSM4PXMGHEQ .

--

SLFWalsh MD MRCP FFRRCSI Consultant Radiologist, NIHR Clinician Scientist, National Heart and Lung Institute, Imperial College, London

Imaging Chair, European Respiratory Society Associate Editor, European Respiratory Journal http://erj.ersjournals.com

--

SLFWalsh MD MRCP FFRRCSI Consultant Radiologist, NIHR Clinician Scientist, National Heart and Lung Institute, Imperial College, London

Imaging Chair, European Respiratory Society Associate Editor, European Respiratory Journal http://erj.ersjournals.com

[mworion]

Simon, park after model I add in one of the next releases. I checked QSI quickly and I got the values, but I might have a second driver running. Still have to clarify this Michel

[mworion]

Simon,

I checked my QSI690 in detail. All parameters from camera (cooling status and temp, pixel size, resolution, download) are loaded from driver. I tested the 1.0.0.3 and the new 1.0.0.4. Both work. Still what I found that the connection to the camera through ASCOM is sometime not reliable.

If you still have the problem, please post the log and some screenshots of the Ascom configuration for QSI

Michel

[mworion]

Simon, closing it as there are no new reports. Data comes with my QSI690. Hopefully it's fixed now. Michel