That's fine, I wonder why I had set it to Mount once, probably a misclick while trying to adjust something else.
Thank-you for helping.
Read More...
Well, then I feel lost.
I just have one imager and the mount. No extra device dedicated to guiding.
So, shouldn't I set guiding to none ?
Also, as I don't use extra guiding device, the train is the same in all tabs.
I'll check as soon as I can take photos again, but I think I had to do this way, otherwise it did not work at the time I set it up.
Then, I don't modify anything that works, until I face situations where it fails.
Read More...
I modified the train so the guide device is set to "--".
It was previously set to "Mount".
Thanks to both.
Read More...
Honnestly, I don't know for sure. What is certain, is that the mount did hang during capture, two times : the night before and the night when I took the screenshot.
Both times I was not able to understand the reason. I first thought of problem with meridian flip, but none of the targets would have needed this.
I'm facing some issues which I'm unable to determine whether it is because of my misunderstanding or they are real.
I tried to reproduce one that happened twice, last night and three nights ago, but unfortunately, there, in my living room, all worked correctly.
I'll open a ticket when it happens next time.
When I go on the field, I hope all will go smoothly. But next time I'll capture the session and activate all logs.
Read More...
Last time I was toally unable to use goto and other functions from the tablet app, and had to use vnc instead.
Whether or not it was because of previous rPI updater update is the question.
Read More...
Hello Fred,
So, the way it was in my case was a non-sense, and the cause of drift in tracking, am I right ?
Read More...
Hello,
When building optical trains, I can chose between none, the camera and the mount, which seems normal since there is no extra device declared for this purpose.
However, I am still wondering what the best choice would be.
What would happen upon setting each of the proposed choices ?
Rgrds,
J.-Luc
Read More...
Hello,
Clouds, clouds, clouds, clouds and wind and rain... no astro since monday.
So, trying to understand how to set up video mode so as to get smooth frames with ASI183 on RPi 5.
The sensor is 5496x3672, which needs almost 2 seconds to transfer to the PCIe SSD. It has always been, and I think it will always be.
This means that fast exposure subjects are not a good idea : almost 120 seconds for 60 pictures at 0.1 second, 3600 frames of the moon that ought to last 6 minutes actually take around two hours.
Okay, there is a video mode in the capture tab, but at 0.1 second exposure, I get a framerate of ca. 4 images per second. A little bit better, but still not satisfying.
I then tried to figure out the way to lower the resolution, for instance decreasiing to 1280x720 at which, according to the manufacturer's data, the 183 is capable of 103 fps.
But nowhere in the menus of the SM APP on the tablet I could find how to achieve this.
I finally thought this could be done from the streaming tab of the Indi dashboard, but alas! even with so lower resolution of 1280x720, when i start capturing the framerate remains at 4 FPS
Long preamble to explain my problem, so now : how can I get a real video mode, that would allow to capture at least 20 fps ? What and where in the SM APP do I need to set ?
Rgrds,
Read More...
Hello,
RPi5 + ASI183MC + SA GTI + SM APP android.
The mount is the access point which both the PI and the tablet connect to.
On startup, I get the warning : "serial port read failed for 200ms (1 retries), verify mount link".
I don't know why this happens, since the mount is connected via wan.
Depending on the answear, I might go further with another question or a bug report.
Rgrds,
Read More...
Hello Hy,
I don't think the doc being faulty. Rather the CKI (Chair-keyboard interface = the user).
I did read (the french translation) many times and read the part about that, but I did not understand it until I read your reply in this post.
I know how difficult and time consuming is making a doc. Especially when the product evolves regularly.
In this case, there are two problems : mastering the hardware / software and the language frontier.
For translations, the translaters must master the hardware / software, the languages subtilities, and be precise enough for the beginners to understand but not too much for not boring neither them nor the experienced users.
Demanding this from volunteers would be quite unfair.
I intend to compare both the english and french docs, and try to find whether this was because of the docs themselves or (more probably) because of me.
It took me only 20 minutes yesterday to achieve polar alignment, modelise the mount bring M51 very near or the cetnre of the field and start aquiring with a very accurate tracking.
Before that, I would have spent (less than 2 minutes for visual polar align and) up to 2 hours to bring the target in the field.
Read More...
Yessss ! I finally could success in polar align, whereas that systematically failed before, whatever the method and settings I chose.
Never would have thought to uncheck those.
It is written in the manual, however I did not understand it since it is mentioned that that can happen because of poor alignment of the telescope. Which was not the case for me.
Read More...