Quantcast
Channel: Recent Topics - INDI Forum
Viewing all 15748 articles
Browse latest View live
↧

Boxdoerfer Dynostar Mount Control - by: RvB

January 8, 2020, 8:29 am
$
0
0
Hi@All!

Is anybody using one of Sigurd Boxdoerfers Mount Control ?

If yes, what driver do you use ? In the Moment I use the LX200 Basic, with basic functions.

CS
Reiner
↧
Search

Celstron cpc1100 remote control - by: bmorrelltx

January 8, 2020, 1:16 pm
$
0
0
I am looking to set up a cpc11 for remote operation. Currently the hand controler needs to have the enter button pushed to intialze the scope. Has anyone figured out how to remotely run the cpc1100?.... Bruce
↧
↧

Guide camera not taking exposures on RPI4 - by: RugbyRene

January 8, 2020, 2:57 pm
$
0
0
Hi all,

Apologies if this has been raised before. I recently bought a RPI4 and loaded up the latest RPI4 compatible version of Ekos. I connected everything up and took it for a spin. Everything was working fine, until I tried to capture an image with my guide camera (ASI120MM Mini). I changed USB ports, cables etc. I then swapped back to the RPI3 and it worked fine, so there appears to be a problem with this camera on RPI4.

Rene
↧

Focus Per Filter - by: Megiddo

December 21, 2019, 4:26 pm
$
0
0
I see there is something that might be doing this in the Filter Setting button.
But what I would like is a way to set a value per filter and have the focuser move to that location.
or
Have the focuser module focus after a filter change. Problem with this choice is the auto focus doesn't work for me (it creates donuts from tight stars then fails).

I''d prefer a hard setting that I find with my Bahtinov mask. Example:
LP 49909
Red 49879
Green 49864
blue 49849
HA 49909

When the filter changes, move the focus to these values.
↧

What is the point of Device manager in Kstars - by: stash

January 21, 2019, 8:00 am
$
0
0
so tools---devices---device manager gives you client or local set up of devices.

What is the point and how is it used in conjunction with Ekos Profiles if at all ?

Does it allow you start devices before.instead of choosing a Ekos profile and if so will it appear on the profile as being used ??

thanks!
↧
↧

Is there an indi compatible focuser featuring encoder / absolute position - by: dolguldur

January 9, 2020, 3:56 am
$
0
0
Dear all,

I am playing with the indi focuser simulator, which is absolutely awesome because the camera simulator also simulates the defocus/blurring accordingly :)
At some point, I'd like to implement the solution that runs with the simulator in real life. Unfortunately, I realized that, on the contrary of the simulator, getting /setting absolute position on off-the-shelf focuser is usually impossible due to the absence of encoder on commercial solution.
Even a low resolution encoder would be fine, or even a homing sensor with the hability to set home position (much like on the common 3d printers) would be nice to control a remote telescope, but it looks like there is no such solution currently available.

Please tell me if there are solutions available to get to know the absolute position of the focuser

Thank you in advance for your help.
↧

Canon DSLR 5X and 10X question - by: khobar

January 9, 2020, 7:16 am
$
0
0
Hello!

Last night, I was testing things with our Canon 450d/XSi and Ekos on Astroberry using the moon and "Live View", and at 1x it worked fine. I shot a movie, brought it into Autostakert! etc. Worked fine though the moon was small, as expected.

I tried the 5x zoom mode, but the sliders didn't appear to do what I needed. It's like my view window was too small, and while I saw a glow of the moon off to the right of the window, I could never bring it into view.

The whole point is to get planetary capture going similar to BackyardEOS.

Thanks very much!
↧

Problems with ZWO EFW - by: tango13

January 9, 2020, 8:26 am
$
0
0
Hi all,
recently I started having problems with my 5-position ZWO EFW.
Everything used to work fine until the last time I went under the stars. On that occasion, the following morning I found out with surprise that, after a certain moment in the photo session, the EFW had stopped working silently.
The capture software (CCDciel) sent the commands to the wheel and showed as if the filter had changed, but actually it had not, so I ended up the whole photo session with all frames (more than 1000) only in the red channel :(
The problem is that it happens silently, the efw indi driver hangs and no error messages come from it, it just hangs and I have to kill it manually because also indiserver seems to lose control over it.
Has it happened to someone else? Is there a way I can send more information to investigate this issue deeper?
Thank you.
↧
Search

Snooping issues, paches to 1.8.3 - by: stefanz

January 9, 2020, 10:37 am
$
0
0
Hi,

for me, a few things in the indi package does not work as desired (I already reported some of the issues in the past) and I therefore use a patched version. I attached these patches for the latest version. Maybe some one wants to apply them to the main repository.

Changes are:
  • Camera drivers now support snooping from J2000 coordinates. In practice telescopes are usually synced to J2000 coordinates (I cant imagine a situation where mount is synced to EOD coordinates). My software therefore correctly uses the 'EQUATORIAL_COORD' property. The patch now also snoops this coordinates and prefers them if both kinds are delivered. (If libindi converts EOD to J2000, the difference seem to be quite large, a few arcmin. I'm not sure whether this is correct.)
  • The EOD -> J2000 conversion now moved to 'addFITSKeywords()' and thus updated per image if the loop capture function is used (enabled to, I make heavy use of it)
  • Names of the driver I use are now script compatible and unique if possible (I use indi_getprop and indi_setprop for device control)

Regards Stefan
↧
↧

Using Astap solver - by: CapnRon

January 9, 2020, 11:14 am
$
0
0
I am running on a Rpi 4. I have Astroberry working and connected to my equipment. thank you for this development. I downloaded Astap solver (/opt/Astrometry) and a bunch of index files. I have not set everything up , so I cannot try a solve from inside Kstars, but I can run the ASTAP program free standing. However, I do have a fits star image and I am trying to use the local Astrometry.net. I do not know what to put in that field for the path to astrometry.net. I have no such file, I have an executable astap and I have index files, but it does not accept either of those locations.

Can someone help me configure ASTAP for stand alone use?

thanks,
Ron
↧

iEXOS100 Mount Tested With PMC8 Driver - by: mikefulb

January 29, 2019, 2:54 pm
$
0
0
I was able to test the PMC8 mount driver last night with an Explore Scientific iEXOS100 mount with the changes made recently by Thomas Olson to support the multiple mounts sold by Explore Scientific and it worked great. I tested slewing, plate solving and syncing and pulse guiding from PHD2. I left it guiding for a couple of hours and then told it to park and everything worked as expected. That said I would still consider the driver in development so I would not use the mount unattended in case you need to intervene if there is a hiccup.
↧

Multiple Zwo Cameras - by: hy

January 9, 2020, 8:19 pm
$
0
0
I'm trying to configure Ekos with a ZWO 1600 for imaging, and a ZWO 290 for guiding.
I don't see how to do that. In the configuration setup, I selected ZWO CCD for both Guider and CCD in the Profile editor.
I connect both cameras, start up Indi, but we only get one camera tab in the indi window, and don't think we have the guider connected.

Is this possible? How should we proceed?
Thanks,
Hy
↧

Nikon D3200 broken - by: indigreg

January 10, 2020, 12:03 pm
$
0
0
Hi folks,

I've been using INDI to control, such as it is possible, my Nikon D3200 DSLR from a Raspberry Pi 3B running Stretch. In support of some additional equipment and automation, I've moved to a Raspberry Pi 4B and Buster, via the nicely packaged Astroberry Server 2.0.0 distribution. With the new software, I am no longer able to access the camera. INDI says it's connected, sort of, but I'm not able to actually do anything with it (e.g. take a picture). By "sort of" I notice that CCDciel shows the camera as "yellow" not green, suggesting that something about the communication isn't completing. I also notice that the camera's image parameters (max x, y) in the indi settings page aren't populated, so I'm thinking this is a matter for the indi_nikon_ccd code, not that of CCDciel.

Looking at the INDI settings for the camera, the "Options" tab has changed significantly, so it's clear that some work has been done on the implementation.

As a cross-check on the overall communication with the camera on the new system, I find that Entangle talks to it just fine, as does gphoto2.

The working version of INDI Server on the 3B is 1.7.4. The not working version is 1.8.2. I don't know what the individual indi_nikon_ccd versions are, but presume they are related to the server.

Any ideas for a fix or workaround?

Thanks!
↧
↧

Astromechanics Canon Lens Focuser - Aperture Setting? - by: rdricks

January 10, 2020, 1:46 pm
$
0
0
I recently acquired the Astromechanics lens focuser for Canon lenses. I'm using an ASI1600mm with filter wheel connected to the focuser then lens. Via Ekos, it detects the focuser and functions. I am able to use the autofocus routine successfully. I am unclear on the aperture setting though. When I go in the the control panel, in the Main Control tab, the aperture is set at 10. Allowed values, as I understand it, are 0-22. If I try to change the value (enter a new value in the right box, then press Set the message returned is "SetApperture(X)" where X is the value I entered. However, the actual value remains at 10. Any thoughts/suggestions?
↧

Raspberry Pi 4 solved my ASI120MM split-frame nightmare - by: rserpell

January 10, 2020, 1:59 pm
$
0
0
Hi everyone,
I though it would be good to share a recent positive experience regarding the random split frame problem that plagues the old USB2 version of the ASI120MM camera. In case it helps someone else.

I was a about to angrily throw away this camera and buy the newer "mini" version, but decided to give it a chance first with the new raspberry 4 (I was set for the raspberry upgrade from 3 model B anyway). I'm happy to tell that the camera works flawlessly now. I had to update the camera firmware to "compatible" though, as after the raspberry upgrade it would not show a single image with the original one.

I have the camera connected to one of the USB2 ports on the raspberry 4. On the other USB2 port I have a FTDI for EQMOD and on one of the USB3 ports I have an ASI1600MM Pro. The pi is loaded with astroberry 2.0 server. I have updated all dists yesterday (INDI included). So far, dry runs only (too many clouds). I will report back when I have a chance to test the whole system under the stars.

For a bit of context/history: On notebooks running Windows, my camera had displayed the split frame problem since I bought it (in 2016, I think). Nevertheless, it had worked without issues with my raspberry pi 3 model B using iastrohub (raspbian jessie, linguider and a now outdated version of libasicamera). I used it for guiding via the camera's ST4 output and an FTDI was used to trigger a mirrorless camera. All of that was with the original camera firmware. Last year I decided to ditch iastrohub and try astroberry to benefit from updated INDI, kstars and Ekos. I was shocked to discover that using the same hardware as before the camera was now displaying the split frame problem (!!??). Searched every forum, tried most suggestions (different drivers, plugging it alone, binning 2x2), nothing. Useless for guiding.

I am aware that ZWO has officially recognized that this particular camera had hardware issues and thus would not be able to solve them via a firmware or driver update. Still, I find it a bit disturbing that the same hardware combination would work with a particular set of software and not with another. Sometimes one is lucky enough to find a working match. But then every future software update is a scary though.

Best,
Ricardo
↧
Search

Monitoring Astroberry Server at the scope - by: CapnRon

January 10, 2020, 5:44 pm
$
0
0
I have my equipment set up and working with the Astroberry Server (running on an Rpi 4 at the scope), now I am waiting for clear skies. My question has to do with monitoring activity at the telescope; principally focus and polar alignment , while the equipment is controlled from a remote computer. I have my equipment setup on home made scope caddy, I role it out of the garage down into the yard ; it is tethered to the house router via a long ethernet cable. I have a laptop, in the garage, running a Chrome connection to the server over the ethernet network. When I get to where I have to focus the scope (manual focus control) I need a monitor at the scope to see what is happening. My thought is that I can run a VNC connection to the WiFi server using an Ipad and the screen of the Ipad will mimic what ever is going on a the laptop in the garage. I can see that now just sitting in my study, but I am never sure of stuff until I see it happen under the real conditions. I will also need to monitor the adjustments I make during polar alignment, but again there should be nothing I need to actively do with Kstars , all the adjustment is at the scope. I just want to be able to monitor the results of that adjustment, just as in focus.

Does anyone see a problem with this approach?
↧

StellarMate App Development - by: knro

January 10, 2020, 10:18 pm
$
0
0
I want to involve the StellarMate users community to see how we can improve and develop the App in the future. Please note that the resources are quite limited. We just have a single developer working on the App. App developers especially those with experience necessary to work in IoT devices tend to be expensive, so we need to strike a balance. At any rate, let me start to say that MOST of the issues within the App are usually some issues in the Stellarmate OS itself. This could be:

1. KStars is not started (for whatever reason, crash..etc)
2. EkosLive service is not running (again for whatever reason).

So when the app tries to authenticate (via EkosLive service), it can fail and loops back again. We are working on improving this in the upcoming SM OS Beta v1.4.7. What would be the priorities for App now? Here are some ideas:

1. Implement offline viewer (so you see captured images in StellarMate)
2. Implement INDI Control Panel (so you get access to ALL the properties).
3. Implement Sky Map (This is actually pretty hard to do). The App is written in React-Native and there is nothing there that can be used for Sky Map unless you do it from scratch, which could takes months and cost a lot.
4. Change UI design (This needs to be specific with mock-ups)
5. ???

I'm also working on SM OS v1.4.7 Beta. The issue with ZWO cameras USB3 WiFi disconnection is resolved. It has been also optimized further to reduce memory and CPU usage. We will need testers for the new Beta coming up.
↧
↧

Stop trying to use Astroberry kstars and ekos - I'm tired - by: josemsubcn

January 11, 2020, 3:28 am
$
0
0
Dear all,

I bought stellarmate OS and with my RPI4 I try to use the systems, but with a lot of problems, and the system was very slow. Then, I tried to use astroberry server 2.0.0 and works a lot better tahn stellarmate. I spend a lot of time to configure all, some times didn't work some Pegasus PPB driver, some times another driver, some time when I reboot the system, astroberry don't find some equipment... 3 or 4 weeks later finally with the last updates all the equipment's worked fine. Pegasus Driver, Sony Camera, EAF focusser, guide camera, etc. Today I planned to go ouside for the first session, before I need to change the wifi access to HOTSpot, because outside I dont have internet connection and I don't have a router for this. And this was the last problem, I try t disconnect the wifi router in my home, them reboot astroberry, then I can see the astroberry hot spot in my wifi connections, tried to connect to the hot spot, write the password (astroberry) and my laptop say "I can't connect to this network"). (I remember that in the fist version from astroberry server 2.0.0 the HOTSpot wors well). I tested all the posibilities, for example to be sure about the password, and it is impossible.

My decision now is that I need to buy a MINI PC, and install Windows 10 Pro and use comercial software. Reallly I'm very tired about to use Linux software and hardware, It is never possible to know if all the things will work or not. And I can't spend more time for all the systems works well and with reliably. The only problem for me is taht I use a Sony A7RIII, there are not ascom windows driver for this cam, and probably I need to buy another cam. INDI drivers have driver for this cam and works very well...

Thanks for the hard work to the people that develop this OS, if all works well it's a good system, with a lot of posibilities, but the problem finally is the same, Linux and free software in front of Windows.

Regards,
↧

AZ synscan : mount doesn't track - by: jrannou

January 11, 2020, 3:39 am
$
0
0
Hi all,



I have problems using a synscan with an AZ GoTo mount.

Using Kstars/Ekos, when I the system ask to track a specific RA/DEC coordinates point, the 'main control' tab of the 'INDI control panel' indicates (most of the time) :

On Set : track
Tracking : Off

and the mount doesn't move instead of tracking.
Actually, sometimes 'Tracking' is On, sometimes is 'Off'. I didn't find any rational behind this strange behavior.

When 'Tracking' is Off, the Ekos tab indicates 'Mount Status : Idle'


I have the same weird behavior using skychart (carte du ciel).

Has it happened to someone else? Is there a way I can send more information to investigate this issue deeper?
Thank you.



ps :


synscan version : 4.39.1
indilib version : 1.8.3
OS : debian 9
↧

Nikon flats Ekos exposure time problem? - by: khobar

October 20, 2019, 11:06 am
$
0
0
I must be overlooking something - I'm using a Nikon D5300 in bulb mode - works great for long-exposure. However, trying to capture flats it seems I cannot really control the exposure time. For example, I just tried to shoot 1/10sec and it shot 1/4sec. 1/20sec also yielded 1/4sec. I cranked it all the way to the fastest setting in Ekos and it yielded a 11.1sec exposure.

The "status" message area says the following:
2019-10-20T14:29:10: [INFO] Starting 0.00025 seconds exposure.
2019-10-20T14:29:10: [ERROR] Failed to expose.

The tail of the log says:
[2019-10-20T07:28:27.483 MST INFO ][ org.kde.kstars.ekos.capture] - "Capturing 0.000-second image..."
[2019-10-20T07:28:27.534 MST INFO ][ org.kde.kstars.indi] - Nikon DSLR DSC D5300 : "[INFO] Starting 0.00025 seconds exposure. "
[2019-10-20T07:28:38.596 MST INFO ][ org.kde.kstars.indi] - Nikon DSLR DSC D5300 : "[ERROR] Failed to expose. "
[2019-10-20T07:28:38.596 MST INFO ][ org.kde.kstars.ekos.capture] - "Capture failed. Check INDI Control Panel for details."
[2019-10-20T07:28:38.601 MST INFO ][ org.kde.kstars.ekos.capture] - "Restarting capture attempt #1"
[2019-10-20T07:28:38.605 MST INFO ][ org.kde.kstars.ekos.capture] - "Capturing 0.000-second image..."
[2019-10-20T07:28:38.657 MST INFO ][ org.kde.kstars.indi] - Nikon DSLR DSC D5300 : "[INFO] Starting 0.00025 seconds exposure. "
[2019-10-20T07:28:41.406 MST INFO ][ org.kde.kstars.indi] - "NEF" file saved to "/home/stellarmate/Pictures/Flat/Flat_019.nef"
[2019-10-20T07:28:41.410 MST INFO ][ org.kde.kstars.ekos.capture] - "Received image 1 out of 1."
[2019-10-20T07:28:58.908 MST INFO ][ org.kde.kstars.ekos.capture] - "Job requires 0.000-second images, has 0/1 frames captured and will be processed."
[2019-10-20T07:28:58.912 MST INFO ][ org.kde.kstars.ekos.capture] - "Capturing 0.000-second image..."
[2019-10-20T07:28:58.972 MST INFO ][ org.kde.kstars.indi] - Nikon DSLR DSC D5300 : "[INFO] Starting 0.00025 seconds exposure. "
[2019-10-20T07:29:10.087 MST INFO ][ org.kde.kstars.indi] - Nikon DSLR DSC D5300 : "[ERROR] Failed to expose. "
[2019-10-20T07:29:10.089 MST INFO ][ org.kde.kstars.ekos.capture] - "Capture failed. Check INDI Control Panel for details."
[2019-10-20T07:29:10.094 MST INFO ][ org.kde.kstars.ekos.capture] - "Restarting capture attempt #1"
[2019-10-20T07:29:10.100 MST INFO ][ org.kde.kstars.ekos.capture] - "Capturing 0.000-second image..."
[2019-10-20T07:29:10.195 MST INFO ][ org.kde.kstars.indi] - Nikon DSLR DSC D5300 : "[INFO] Starting 0.00025 seconds exposure. "
[2019-10-20T07:29:12.923 MST INFO ][ org.kde.kstars.indi] - "NEF" file saved to "/home/stellarmate/Pictures/Flat/Flat_020.nef"
[2019-10-20T07:29:12.927 MST INFO ][ org.kde.kstars.ekos.capture] - "Received image 1 out of 1."

What am I missing?

Thanks.
↧
Viewing all 15748 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>