No exposures occur during NINA control of camera in Image tab and when Saving and Quiting MW4 it disconnects the camera also in NINA abruptly

[abdiastroboy]

MW4 now connects to NINA controlled camera however is unable to expose any images as says the following

[2023-01-16 07:35:49.355][W][ ninaClass.py][ 108] Request NINA response invalid: [400]

Also when Saving and quiting MW4 it disconnects the camera in NINA itself everytime

Posted on the NINA discord

20230116-182929-3.0.0.1011.9968.log

Above is NINA log

mw4-2023-01-16.log

Above is MW4 log

[abdiastroboy]

[2023-01-16 07:37:25.417][T][ ninaClass.py][ 93] GET NINA: [http://127.0.0.1:59590/disconnectdevice/Camera?format=json]

[2023-01-16 07:37:27.977][T][ ninaClass.py][ 111] Request NINA response: [{'Message': None, 'Success': True}] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [Driver - Device disconnected - camera] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [Driver - Server disconnected - camera] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [NINA - Device remove - N.I.N.A. controlled] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [Driver - NINA disabled - camera]

I suspect this is the issue, is this the behaviour you wanted when saving and quiting because it forces the cooled camera to close abruptly

[mworion]

…good to hear that things could be changed. As I remember (but I’m at work and could not check), the connection handling to NINA server (connect and disconnect) did not impact the connection status of the camera on NINA side. MW4 does not send the command of connecting or disconnecting the camera on NINA’s side (which definitly could be done). So the exspectation should be that NINA keeps it state to the camera, regardless of the Server state as it was in the past.Am 16.01.2023 um 09:41 schrieb abdiastroboy @.***>: [2023-01-16 07:37:25.417][T][ ninaClass.py][ 93] GET NINA: [http://127.0.0.1:59590/disconnectdevice/Camera?format=json] [2023-01-16 07:37:27.977][T][ ninaClass.py][ 111] Request NINA response: [{'Message': None, 'Success': True}] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [Driver - Device disconnected - camera] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [Driver - Server disconnected - camera] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [NINA - Device remove - N.I.N.A. controlled] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [Driver - NINA disabled - camera] I suspect this is the issue, is this the behaviour you wanted when saving and quiting because it forces the cooled camera to close abruptly

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

[abdiastroboy]

Not sure, but it definitely disconnects everytime even with stable version of nina. basically after the model is built there is no need to close the camera connection via the server. maybe i try again this wayOn 16 Jan 2023, at 19:58, Michael @.> wrote: …good to hear that things could be changed. As I remember (but I’m at work and could not check), the connection handling to NINA server (connect and disconnect) did not impact the connection status of the camera on NINA side. MW4 does not send the command of connecting or disconnecting the camera on NINA’s side (which definitly could be done). So the exspectation should be that NINA keeps it state to the camera, regardless of the Server state as it was in the past.Am 16.01.2023 um 09:41 schrieb abdiastroboy @.>: [2023-01-16 07:37:25.417][T][ ninaClass.py][ 93] GET NINA: [http://127.0.0.1:59590/disconnectdevice/Camera?format=json] [2023-01-16 07:37:27.977][T][ ninaClass.py][ 111] Request NINA response: [{'Message': None, 'Success': True}] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [Driver - Device disconnected - camera] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [Driver - Server disconnected - camera] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [NINA - Device remove - N.I.N.A. controlled] [2023-01-16 07:37:27.977][U][ mainApp.py][ 365] Message window: [Driver - NINA disabled - camera] I suspect this is the issue, is this the behaviour you wanted when saving and quiting because it forces the cooled camera to close abruptly

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[mworion]

Hi, checked the log. NINA now does connect (as the return values for connecting are now fitting the existing interface), but all other commands still have issues being compatible to the existing implementation. MW4 still sends the same commands for exposure, but the NINA server responds with error 400 without sending something back. I See no entry for the refused HTTP Post in NINA log set to debug level.

PS: MW4 does not disconnect when leaving. Attached the actual beta9 with latest version 2. 1 NINA

https://www.dropbox.com/s/0p168fpr9nnxvbk/Bildschirmaufnahme%202023-01-17%20um%2018.44.43.mov?dl=0

Michel

[abdiastroboy]

So the behaviour Im seeing with the camera disconnecting in Nina, is that a NINA problem. ?On 18 Jan 2023, at 05:24, Michael @.***> wrote: Hi, checked the log. NINA now does connect (as the return values for connecting are now fitting the existing interface), but all other commands still have issues being compatible to the existing implementation. MW4 still sends the same commands for exposure, but the NINA server responds with error 400 without sending something back. I See no entry for the refused HTTP Post in NINA log set to debug level. PS: MW4 does not disconnect when leaving. Attached the actual beta9 with latest version 2. 1 NINA https://www.dropbox.com/s/0p168fpr9nnxvbk/Bildschirmaufnahme%202023-01-17%20um%2018.44.43.mov?dl=0 Michel

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[mworion]

Anything new with your contact to NINA. I checkt the actual nightly (16), but the Error 400 is still there. Michel

[abdiastroboy]

HiUnfortunately no change that i have seen i have not even checked tbh hard to converse via discord.On 25 Feb 2023, at 05:20, Michael @.***> wrote: Anything new with your contact to NINA. I checkt the actual nightly (16), but the Error 400 is still there. Michel

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.