On the other hand, Imager side, I am very interested in your approach of "Ain INDIGO Imager" As I also want to use an X3 or X4 barlow, I am wondering about piloting for collimation with an EAF ASI. ![]() Normally with the goto function I don't need to deal with goto control at first. The expected hardware is a Raspberry 4 8GB with 64 bit OS. I have a plan to purchase an ORION SkyQuest XX14g GoTo Dobsonian or ORION SkyQuest XX16g GoTo Dobsonian in order to do EVAA with real-time view in a screen. That’s improved night vision, that’s awesome! I bought an Evscope and am impressed with the results obtained despite living in the south of Paris with high light pollution…. I am interested in amplified image processing and software rotation for altz mount Which one do you want to see in Ain version 0.2 - telescope control or sequence imaging? Please share below! Scheduling and plate solving will come a bit later □ So next two major updates planned for the next releases (0.2 and 0.3) are mount support and sequence imaging, in other words, executing several batches automatically in a predefined sequence, some call it plan or observing block. This is more than enough for basic imaging and I am well aware that this is not enough for advanced imaging. INDIGO logs can also be saved for debugging purposes or for a session log (using info log level).įocusing, Batch Imaging, Guiding and Dithering are all in place in this release. Guide session logs are saved in CSV format, so that every chart plotting software can be used to analyze the guiding performance. The folder changes at noon to have all the data from the night in one place. All images and logs are saved in /ain_data/YYYY-MM-DD/ now. It comes with many internal improvements and fulfills the requests of the people who devoted time to test and give feedback. This will make Ain better!įinally the first stable release of Ain imager for Linux and Windows is here: Special thanks to Stoyan Glushkov, who spent several nights testing the guiding, focusing, and the imaging, bombarding me with ideas and glitches he have found in the process. Thanks to everybody who tested the previous release and shared their thought and ideas. Only by switching from "raw" to "Fine Jpeg" preview, the traffic is reduced 10x times, and by using "Coarse Jpeg" and 10 radii selection the required bandwidth drops to less than 0.1 Mbit/s. So 2 new features are added to reduce this bandwidth requirement to more than 100 times - "sub frame guiding" and "use Jpeg to monitor guiding". With 1s exposure 16 bit image 1600x1200 you will need roughly 15Mbit/s to monitor the process in real time, which is too much just for monitoring. Also we have made it easier on the network while guiding. Your focusing can be way faster as it can focus on a sub frame around the selected star, avoiding full frame download which can take 10-15s with some cameras. ![]() Now you can select image type without the need to go to the control panel. It comes with several bugfixes along with several new features. Hope this points you in the right direction.Ain 0.1 second preview for Linux and Windows is available for download and test here: Routing and Remote Access (RRAS) on the new server and you can route traffic from external to the internal virtual switch Does the server use an internal or private virtual switch? You will need to install a server on the Hyper-V host using 2 network interfaces (1 connected to an external virtual switch, 1 connected to the same virtual switch as the virtual server).Is the server connected through an external virtual switch? If so, you should be able to connect to the server using "normal" network connectivity.Is your server a VM on an Hyper-V server? And where does the Hyper-V host reside? How is the connectivity between your home network and the Hyper-V host I don't know if this is an Hyper-V question, since there's not a lot of information in your question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |