Hi Robert I hope this finds you well.
i have been testing the MyfocuserPro2 with NINA and ran into an issue I hope you may be able to help with.
the system works for a while then stops freezing NINA in the process. this is on windows using the Ascom driver 2.8.0. the log file in NINA shows this error:
2021-10-30T23:01:59.2816|ERROR|AscomDevice.cs|CheckDotNetExceptions ASCOM.myFocuser2ASCOM.Focuser Position Get System.Threading.AbandonedMutexException: The wait completed due to an abandoned mutex.
does this make any sense to you?
best regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
System.Threading.AbandonedMutexException: The wait completed due to an abandoned mutex.
This is a error output from NINA, about its handling of things. Does not refer to the driver. The mutex in on the NINA side.
So I really need to see what the driver was doing.
Please provide the tracing log from the driver. there is a trac on box for the ascom driver, when checked the driver logs everything.
Sorry but the NINA log is not much use.
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I don't think that is the ascom log file. I think it is a portion of a windows log file?
I see a whole lot of connects followed by disconnects,
The ASCOM log where-abouts, For Windows this will be in your Documents folder, in a sub folder called ASCOM and then by date Logs 2021-11-01. You will know it is for the myFocuserPro2 because it will be something like ASCOM.myFP2......txt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Dave.
For what it's worth, I've been using NINA since the very beginning of
Robert's project, and it works fine.
I use Wifi and serial and I have never had any problem.
The bluetooth usually gives many problems in the connection PCs, I would
try to change to serial or Wifi.
I want you to solve the problem
thanks for the info. annoyingly its been fine on the ekso/kstars setup no issues at all nut now windoz
not sure if I can change the uln2003 board to wifi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Dave
The logs show that there was an exception around
Nina
021-10-31T11:39:53.2945|ERROR||An exception GET of Focuser.TempComp:
myFP2
11:39:48.244 CS send: 24
11:39:53.278 CS Exception
yet there were a lot of :24# (get tenpcomp) prior to this.
That means the call was working priot to this with the driver returning the correct values.
And the exception around
Nina
021-10-31T11:42:40.5725|INFO|Retrying to GET Focuser.Position
myFP2
11:42:40.572 Position Check for time of last call
11:42:40.572 CS :00#
11:42:40.795 Position Raw returned value = 20000
Prior to the focuser.position call, there was this
2021-10-31T11:39:53.2945|ERROR|Serial port Exception|293
|An unexpected exception occurred during GET of Focuser.TempComp:
which sorta makes me think that the tempcomp call then causes a focuser position failure.
So we do know that the driver and controller and NINA were fine with the same calls prior.
I am thinking that the cause points to bluetooth connection.
Can you please try attached 280-1 ascom driver. I added a little extra logging plus some code tweaks around the actual tempcomp call itself. Ypu will need to install it, then enable Trace On in the ASCOM driver.
My thoughts are:
A lot of users/me use the driver with NINA, and I personally have not seen this before.
It points to either Bluetooth or tempcomp on. The fact that tempcomp worked fine most of the time prior to the exception points to something like a dropped connection.
(othewise it would happen on every call).
I would be interested to know what error is
Serial port Exception 293
in NINA.
just an update on what I have been testing, tried two seperate focusers (both ULN2003) reported same issue
also installed NINA onto another PC as I thought it maybe the bluetooth module and that also reported same issue.
I am sure its BT related and its dropping the connnection somewhere!
best regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For me this looks like you have som eserial port communication failures
which lead to the issues and to the abandoned mutexes inside the driver.
No I don't think so. Any mutexes inside the driver are totally invisible to
the client. So the abandoned mutex they are referring to is inside NINA, not
the ASCOM driver. The driver never shares or reports back about internal
things.
The puzzle is this. Clearly the tempcomp call is working (nearly all the
time). That is proven by the many times it works (in the logs) before this
error occurs.
I have not had time as yet to look at the second log files. I am NZ so there
is a time zone difference.
My secondary PC went bye bye saluting to Windows 10. I could no longer click
on start to get the menu and it was stuck in a loop, update, reboot, update,
reboot, update, reboot that after everything I just went stuff it and did a
clean install over it all.
Speaking of Win 11, I did that on 2 computers yesterday. On each I have a
large HDD attached via a USB 3 port. And Win 11 completely trashed the data
on those external disks. The first time I thought it was me perhaps, but the
2nd time on the other computer gave the same result, So spent some time on
the restores.
Bob is back
I have had a look at both logs.
I have a new version for you to try.
I did not find anything obvious in the driver. Will post it here soon.
In the last logs I saw the get that matched the get in NINA, but the focuser also sent the reply back to the driver, at least that is what the log indicates.
And another hour has lapsed since Bob is back.
I have here version 280-4 for you to try.
let me know how it goes. I did a quick run under NINA, but certainly did not test everything.
Try to uninsatll the older ascom driver first.
You will it is the right one when looking at the setupform - it should say 280-4 in the title bar
I wrote earlier
No I don't think so. Any mutexes inside the driver are totally invisible to
the client. So the abandoned mutex they are referring to is inside NINA, not
the ASCOM driver. The driver never shares or reports back about internal
things.
Generally that is so. The reason why NINA appeared to know that was it was in one of the error messages I sent back to the client - sometimes the fingers are fasterat typing than the brain is at remembering things.
Last edit: brownrb 2021-11-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Robert.
I installed 280-4 but it only shows as 280 in NINA and the config box see attached images but looks ok in control panel.
also I ran the ascom diagnostics and it had 1 error ! is this relevant?
14:36:19.551 Error Error List
14:36:19.551 Error GetCOMRegistration - *** ProgID ASCOM.myFocuserASCOM.Focuser not found
Ok so it appears that the uninstall routine fails to remove/overwrite the ASCOM.myFocuser2ASCOM.Focuser.dll from the C:\Program Files (x86)\Common Files\ASCOM\Focuser folder so after manually removing them I re-installed the newer version and it is now showing the correct version in the setup dialogue box!
this occures on 2 x pc's that I have the other version was 2.78 which was also not updated!
now running a test on the new version.
best regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert I hope this finds you well.
i have been testing the MyfocuserPro2 with NINA and ran into an issue I hope you may be able to help with.
the system works for a while then stops freezing NINA in the process. this is on windows using the Ascom driver 2.8.0. the log file in NINA shows this error:
2021-10-30T23:01:59.2816|ERROR|AscomDevice.cs|CheckDotNetExceptions ASCOM.myFocuser2ASCOM.Focuser Position Get System.Threading.AbandonedMutexException: The wait completed due to an abandoned mutex.
does this make any sense to you?
best regards
System.Threading.AbandonedMutexException: The wait completed due to an abandoned mutex.
This is a error output from NINA, about its handling of things. Does not refer to the driver. The mutex in on the NINA side.
So I really need to see what the driver was doing.
Please provide the tracing log from the driver. there is a trac on box for the ascom driver, when checked the driver logs everything.
Sorry but the NINA log is not much use.
Regards
Robert
Thanks Robert
can you tell me where the trace log is to be found?
I switched it on but cant find a log
found it :)
Hi
I don't think that is the ascom log file. I think it is a portion of a windows log file?
I see a whole lot of connects followed by disconnects,
The ASCOM log where-abouts, For Windows this will be in your Documents folder, in a sub folder called ASCOM and then by date Logs 2021-11-01. You will know it is for the myFocuserPro2 because it will be something like ASCOM.myFP2......txt
gotchya attached correct one
this is the nina log that was at the same time as the above log showing when it errored
not sure if it helps
Hi Dave.
For what it's worth, I've been using NINA since the very beginning of
Robert's project, and it works fine.
I use Wifi and serial and I have never had any problem.
The bluetooth usually gives many problems in the connection PCs, I would
try to change to serial or Wifi.
I want you to solve the problem
El dom, 31 oct 2021 a las 11:49, Dave Wilkes ( cedricthebrave@users.sourceforge.net) escribió:
thanks for the info. annoyingly its been fine on the ekso/kstars setup no issues at all nut now windoz
not sure if I can change the uln2003 board to wifi
are you using the nightly build?
Yes
El dom, 31 oct 2021 a las 15:11, Dave Wilkes ( cedricthebrave@users.sourceforge.net) escribió:
connected via bluetooth
Hi Dave
The logs show that there was an exception around
Nina
021-10-31T11:39:53.2945|ERROR||An exception GET of Focuser.TempComp:
myFP2
11:39:48.244 CS send: 24
11:39:53.278 CS Exception
yet there were a lot of :24# (get tenpcomp) prior to this.
That means the call was working priot to this with the driver returning the correct values.
And the exception around
Nina
021-10-31T11:42:40.5725|INFO|Retrying to GET Focuser.Position
myFP2
11:42:40.572 Position Check for time of last call
11:42:40.572 CS :00#
11:42:40.795 Position Raw returned value = 20000
Prior to the focuser.position call, there was this
2021-10-31T11:39:53.2945|ERROR|Serial port Exception|293
|An unexpected exception occurred during GET of Focuser.TempComp:
which sorta makes me think that the tempcomp call then causes a focuser position failure.
So we do know that the driver and controller and NINA were fine with the same calls prior.
I am thinking that the cause points to bluetooth connection.
Can you please try attached 280-1 ascom driver. I added a little extra logging plus some code tweaks around the actual tempcomp call itself. Ypu will need to install it, then enable Trace On in the ASCOM driver.
My thoughts are:
A lot of users/me use the driver with NINA, and I personally have not seen this before.
It points to either Bluetooth or tempcomp on. The fact that tempcomp worked fine most of the time prior to the exception points to something like a dropped connection.
(othewise it would happen on every call).
I would be interested to know what error is
Serial port Exception 293
in NINA.
Thanks Robert
I have removed the other version and installed this one and will report back as soon as I get another freeze
didnt take very long
attached both files again
NINA say
That is an error coming from the driver itself after calling the getter for Focuser.TempCom.
For me this looks like you have som serial port communication failures which lead to the issues and to the abandoned mutexes inside the driver.
just an update on what I have been testing, tried two seperate focusers (both ULN2003) reported same issue
also installed NINA onto another PC as I thought it maybe the bluetooth module and that also reported same issue.
I am sure its BT related and its dropping the connnection somewhere!
best regards
Morning Robert
I am not going to touch Win11 for a while yet. Beside it says non of my PC's
are compatible!
This is definitely BT related. I left the device connected via the direct
USB port and running on Nina through the night and no Mutex errors!
Best regards
From: brownrb brownrb@users.sourceforge.net
Sent: 01 November 2021 08:02
To: [arduinoascomfocuserpro2diy:discussion]
general@discussion.arduinoascomfocuserpro2diy.p.re.sourceforge.net
Subject: [arduinoascomfocuserpro2diy:discussion] MFP2 and NiNa
For me this looks like you have som eserial port communication failures
which lead to the issues and to the abandoned mutexes inside the driver.
No I don't think so. Any mutexes inside the driver are totally invisible to
the client. So the abandoned mutex they are referring to is inside NINA, not
the ASCOM driver. The driver never shares or reports back about internal
things.
The puzzle is this. Clearly the tempcomp call is working (nearly all the
time). That is proven by the many times it works (in the logs) before this
error occurs.
I have not had time as yet to look at the second log files. I am NZ so there
is a time zone difference.
My secondary PC went bye bye saluting to Windows 10. I could no longer click
on start to get the menu and it was stuck in a loop, update, reboot, update,
reboot, update, reboot that after everything I just went stuff it and did a
clean install over it all.
Speaking of Win 11, I did that on 2 computers yesterday. On each I have a
large HDD attached via a USB 3 port. And Win 11 completely trashed the data
on those external disks. The first time I thought it was me perhaps, but the
2nd time on the other computer gave the same result, So spent some time on
the restores.
MFP2 and NiNa
https://sourceforge.net/p/arduinoascomfocuserpro2diy/discussion/general/thr ead/6ecccac557/?limit=25#7bf7
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/arduinoascomfocuserpro2diy/discussion/general/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
Bob is back
I have had a look at both logs.
I have a new version for you to try.
I did not find anything obvious in the driver. Will post it here soon.
In the last logs I saw the get that matched the get in NINA, but the focuser also sent the reply back to the driver, at least that is what the log indicates.
And another hour has lapsed since Bob is back.
I have here version 280-4 for you to try.
let me know how it goes. I did a quick run under NINA, but certainly did not test everything.
Try to uninsatll the older ascom driver first.
You will it is the right one when looking at the setupform - it should say 280-4 in the title bar
uninsatll = uninstall
I wrote earlier
No I don't think so. Any mutexes inside the driver are totally invisible to
the client. So the abandoned mutex they are referring to is inside NINA, not
the ASCOM driver. The driver never shares or reports back about internal
things.
Generally that is so. The reason why NINA appeared to know that was it was in one of the error messages I sent back to the client - sometimes the fingers are fasterat typing than the brain is at remembering things.
Last edit: brownrb 2021-11-01
Cants see the 280-4 anywhere other than in control panel!
From: brownrb brownrb@users.sourceforge.net
Sent: 01 November 2021 11:34
To: [arduinoascomfocuserpro2diy:discussion]
general@discussion.arduinoascomfocuserpro2diy.p.re.sourceforge.net
Subject: [arduinoascomfocuserpro2diy:discussion] MFP2 and NiNa
uninsatll = uninstall
MFP2 and NiNa
https://sourceforge.net/p/arduinoascomfocuserpro2diy/discussion/general/thr ead/6ecccac557/?limit=25#4f8b
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/arduinoascomfocuserpro2diy/discussion/general/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
Robert.
I installed 280-4 but it only shows as 280 in NINA and the config box see attached images but looks ok in control panel.
also I ran the ascom diagnostics and it had 1 error ! is this relevant?
14:36:19.551 Error Error List
14:36:19.551 Error GetCOMRegistration - *** ProgID ASCOM.myFocuserASCOM.Focuser not found
Ok so it appears that the uninstall routine fails to remove/overwrite the ASCOM.myFocuser2ASCOM.Focuser.dll from the C:\Program Files (x86)\Common Files\ASCOM\Focuser folder so after manually removing them I re-installed the newer version and it is now showing the correct version in the setup dialogue box!
this occures on 2 x pc's that I have the other version was 2.78 which was also not updated!
now running a test on the new version.
best regards
see attached image this time :)
think you have cracked it :)
no more mutex issues