×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Re:Re:Looking for all MAC users of Kstars / Ekos

  • Posts: 2877
  • Thank you received: 812
Ok now I understand what you mean about the picture now that you said "white picture". I think the issue you are referring to has to do with the image stretch and display of images in the fitsviewer. I suspect this does not have anything to do with your camera or the connection to kstars actually. It has everything to do with the stretch that is being applied and the either the brightness or signal to noise ratio of the items in your image if I understand your issue correctly. I have observed similar behavior in a couple of different circumstances myself recently.

One situation in which I have seen it was when some of my images were too short and had too little signal to noise ratio. They stopped showing a noise pattern and went all white. I'm planning to look into the cause of this. In the past, when this has happened, it just showed a dimmer noise pattern, but something seems to have changed in that regard. But a longer exposure time fixed the problem and showed a noise pattern again.

The other times I have seen it go all white was when the exposure time was too long. For instance when using a ZWO camera and taking pictures or viewing in live video during the daytime or in a room in your house with the lights on, you have to make the exposure time for images or frames in a video EXTREMELY short because the ZWO cameras are so sensitive. The last time I put it on live video in a room, I had to basically cover up the camera with my coat before I could see any details in the screen that were not over saturated. I would like to see if we can change the live video controls to allow exposure times shorter than 1 ms, because that is just too long with a ZWO camera for some targets like the moon and bright planets.
5 years 2 months ago #34831

Please Log in or Create an account to join the conversation.

  • Posts: 321
  • Thank you received: 19
Yes you are right. When the exposure is too long, this is clear. But i had this sometimes with gain 1 and 0.01sec.

I can confirm that i also think it has only to do with stretching, say, only the Interpretation of the pictures is „wrong“ but the pictures themselves are ok.

Another thing i would find nice, would be a gain setting in the capture tab. Or is there one, i just cant see?

Have to go now and shorten my Moravian OAG with the angle-grinder :)

Cheers, Niki


Gesendet von iPhone mit Tapatalk
Skywatcher EQ6-R | Lacerta 10" Carbon-Newton | Lacerta MFoc Motorfocus | Moravian G2 8300 Color | Canon EOS 5DMarkIIIa | Lodestar X2 guiding cam | KSTARS 3.4.3. on my outdoor-Laptop with KDE-Neon/Plasma | KSTARS 3.4.3. on Remote-IMac with Catalina | KSTARS 3.4.3 on Remote-Macbook Air with Catalina
5 years 2 months ago #34836

Please Log in or Create an account to join the conversation.

  • Posts: 527
  • Thank you received: 139
I was able to run 3.1 with no issues other than the attached config issue which popped up right when I launched EKOS. All hardware loaded, but it's been cloudy so didn't get to test beyond that.

Last edit: 5 years 2 months ago by Andrew Burwell.
5 years 2 months ago #34885
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 31
  • Thank you received: 5
Yes please, GAIN setting in Capture module, great idea!
The following user(s) said Thank You: Craig
5 years 2 months ago #34886

Please Log in or Create an account to join the conversation.

  • Posts: 2877
  • Thank you received: 812
So that box that popped up is not an issue, it is the new feature that I added so that you can update the config file inside the app bundle to match the location of your computers index files. I added it to fix the issue that was reported the last time I posted the dmg of the path to the index files in the config file being incorrect.
5 years 2 months ago #34898

Please Log in or Create an account to join the conversation.

  • Posts: 1000
  • Thank you received: 155
Just a short chime, to say that I too use a new Macbook (Air) now to to connect to my astrorig. I was just connecting via VNC to the Linux box that was running INDI/Kstars, but lately its just been too buggy to be reliable.

So now I use the Mac to run the OSX version of KStars and connect to the same Linuxbox (NanoPC T4) and that works great! It's fast, and I solved the issue of download times by installing a 500GB Solid State Drive card onto the NanoPC and have EKOS save files to it instantly. Then I connect to the NanoPC via SMB and share that SSD on my Mac. I can then download files at a later time easily.

I connect the Macbook to the NanoPC via a local wifi network.

The NanoPC rides shotgun on my mount and all my equipment is plugged into the NanoPC which has both USB2 and USB ports. One 12V powercable leads to a saddle on the mount which uses a RigRunner powerstrip #405 to distribute power to the cameras, focuser, NanoPC, and dew heater.

The NanoPC (running INDI) connects to the iOptron CEM25P via iOptron's StarFi wi adapter. It's flawless.

PS: I too would love to see the GAIN and OFFSET settings right on the Capture screen, so they can be incorporated easily in an imaging session.

So when I go out in the field, here's what happens:

1. I setup the mount and attach the entire astrorig to it. I store my complete imaging rig all assembled in a Pelican case. I just take it out of the case, and attach it to the mount. No assembly required. This includes my WO STar71, ASI1600MM Pro, OAG with Lodestar X2, Filter wheel, dew heater with temp probe, NanoPC T4 (Lubuntu), and powerstrip.



2. I turn on the mount and wait for it to aquire it's GPS settings. While it is doing that, I adjust the balance of the imaging setup.

3. I turn on the NanoPC T4 and 6 seconds later it has connected to the Starfi (iOptron CEM25P) and is broadcasting it's own network.

4. I Open my MacBook, connect to the Nano's network, and start KSTARS/EKOS.

5. Ready to roll! I do a polar alignment, and start my imaging session.

That whole setup from car to imaging takes about 30 minutes.



Peter
Last edit: 5 years 2 months ago by Peter Kennett.
5 years 2 months ago #34903
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 131
  • Thank you received: 11
Hey quick question if that’s OK, how are connecting to the mounts wifi and concurrently presenting a different SSID back to your Mac?

Also what case are you using on the nano and also was OS image is this little guy based on?

Thanks in advance.
5 years 2 months ago #35003

Please Log in or Create an account to join the conversation.

  • Posts: 131
  • Thank you received: 11
Agree 100%, it’d be great to set the gain in the capture screen. I can see the ISO setting but it’s greyed out for my ZWO camera.
5 years 2 months ago #35004

Please Log in or Create an account to join the conversation.

  • Posts: 1000
  • Thank you received: 155
My NANO PC sets up a wifi network upon booting. It's crazy, as it has this network up and running in 6 seconds from power on.
The Starfi has a mode that connects to the NanoPC's wifi network.
(I will verify all the settings when I get home)

My Mac also connects to the same NanoPC wifi network to gain access to INDI, and the shared drive folder (SSD).

I am running Lubuntu.
The case is the clear plastic one (top and bottom only).
I tried the steel fully encased one, but it seemed to run very hot that way.
The following user(s) said Thank You: Craig
Last edit: 5 years 2 months ago by Peter Kennett.
5 years 2 months ago #35010

Please Log in or Create an account to join the conversation.

  • Posts: 42
  • Thank you received: 1

Hi Rob

I'm trying to connect my hardware to Kstars on mac: iOptron CEM60, ZWO 071, Microtouch focuser and Orion SSAG.

Of those pieces, only the ZWO camera gets to connect. Being the SSAG mainly a QHY camera, is it supported now under mac? (your post is of a few months ago)

I'm getting also this message when trying to connect the mount: 2019-06-08T22:58:37: [ERROR] Failed to connect to port (/dev/cu.usbserial). Error: Port failure Error: No such file or directory. Check if device is connected to this port.

And this for the focuser: 2019-06-08T22:58:37: [ERROR] Failed to connect to port (/dev/cu.usbserial). Error: Port failure Error: No such file or directory. Check if device is connected to this port.

Nevertheless, those devices are shown on the "System information" display (from the apple menu on the top bar, so the MacOS is able to see them.

Is it needed to install an app similar to Indi server on windows?

Thank you very much,

Alfredo
4 years 10 months ago #40005

Please Log in or Create an account to join the conversation.

  • Posts: 2877
  • Thank you received: 812
No, the latest INDI server is included with KStars. I can probably look into the star shoot auto guider this summer if I can get access to one. I think some people were connecting to that with the qhy driver, but it wasn’t perfectly reliable . For the microtouch focuser, are you using the focus boss? I have used that with my Mac. It did work but required some configuration. I don’t know about an ioptron Mount . I haven’t tried that
4 years 10 months ago #40020

Please Log in or Create an account to join the conversation.

  • Posts: 42
  • Thank you received: 1
I chose the corresponding drivers on the equipment profile, when configuring Ekos, including the QHY driver for the SAAG.

When doing the same under Linux, all of the devices worked perfectly.

Will it be some port configuration? If so, how can be done?

Thanks,

Alfredo
4 years 10 months ago #40027

Please Log in or Create an account to join the conversation.

Time to create page: 0.672 seconds