To my best of knowledge that firmware is for ASI120MM/MC and not for the mini since there is no downloadable firmware for the mini. This essentially is the compatibility firmware that you probably already applied. I did the same thing once and never got my ASI120MC to work properly as well so I replaced it with an ASI120MC-S (USB3 version) and that works like a charm.
Read More...
That's a very creative solution. I now have a ZWO 5-position EAF as well and was thinking to replace it with an 8-position EAF so I can add OIII to the LRGBHa that I already have. Even when I add SII (no plans yet but you never know) one position remains so I could do the same as you and block it to be able to take darks and bias! So, thanks very much for this fantastic idea!!!
Wouter
Read More...
Good advise from phomer60. You can "abuse" the Object Name field for this. I suppose that this is for quick inspection of the files because the temperature info is added to the headers of the images (either FITS or CR2 in case of a Canon DSLR) so the info is available.
Wouter
Read More...
A few weeks ago I unticked Use Scale and ever since plate solving has been working very well. I had some plate solving issues where the wrong scale was used with a DSLR and that led to solving problems that could be solved with disabling Use Scale. I now have disabled this always, even with my ASI1600MM for which solving works fine when Use Scale is enabled as well.
HTH, Wouter
Read More...
Thanks for the logs. Unfortunately I won't be able to help you with that since I do not own a single Windows computer. I hope someone else on this forum can follow up on your issue.
Wouter
Read More...
My suspicion is that all traffic is routed via wlan0 because that one is enabled first and then wlan1. By then the default route has been set to use the wlan0 interface so deleting the default route and adding one for wlan1 should also solve the issue. It should also be possible to create a script that runs at some point and tries to detect if both wlan0 and wlan1 are up and have a valid ip address. If yes it could delete the default route and create it again for wlan1.
Another solution could be to try and see if the kernel modules for the two wlan devices can be given a priority so the current wlan1 kernel module gets loaded first so it will always get the default route. No idea if that really works because it probably also depends on how quickly your network assigns an ip address via dhcp.
And perhaps this can be configured via wpa-supplicant or so but I really wouldn’t know if that is possible at all.
Just a few thought that I hope may be useful to you.
Clear skies, Wouter
Read More...
Good to see that you managed to replace the mini with a working camera, Stefan.
Jo, I share your experience with the ASI120MC USB 2 and 3 versions and I wasn’t able to flash the USB 2 version either. I was of the impression that the mini should work but it looks I was wrong.
Wouter
Read More...
However, this thread reports issues aa well
indilib.org/forum/ccds-dslrs/5673-asi120...ini-not-working.html
and a suggestion is to use 8 bit mode and not 16 bit.
Read More...
Have a look at the Remember Job Progress option in the KStars configuration settings.
HTH, Wouter
Read More...
Sorry Jo, you are mistaken. The ASI120MM mini works fine under Linux. The ASI120MM (USB2) camera has a firmware issue and the ASI120MM-S (USB3) camera works fine as well. But the firmware issue does not affect the mini camera.
Wouter
Read More...
No clue as I don’t use Windows.
Can you reproduce this reliably? If yes, can you post the logs grabbed while reproducing this?
What happens if you don’t use the Windows machine as Ekos client and try via VNC?
Wouter
Read More...
You don't need to use the solver on stars only. You can also use it on M 31 and other deep sky objects and that will help the mount point very accurately to the object that you want to image.
HTH, Wouter
Read More...
There is a difference between the azimuth and right ascension coordinates. If the telescope is facing the celestial pole with the counter weights down then azimuth should be 0 and right ascension the value of the local sidereal time which is equal to the right ascension at the meridian. So depending on the local wall clock time at which you parked the mount, the value of 07h 14m 0s for right ascension could be correct. The marks on the telescope, by the way, show coordinates relative to that zero position (with the telescope pointing north and the counter weights down) and the fact that right ascension is measured in degrees is a bit confusing but that's how these setting circles are constructed.
HTH, Wouter
Read More...