my FITS files generated by EKOS (with Toupcam driver) do not have the OBJECT keyword set to the Target name. It's always UNKNOWN although the target is known and appended as Prefix to the filename. I searched around but could not find the option to make this work or maybe it is a bug?

Markus

Read More...

the DBUS problem reappeared after a reboot and this time I found the solution without another reboot. The environment variable XDG_RUNTIME_DIR has to be set to /run/user/$UID.

Markus

Read More...

upgraded to the nightly build ppa yesterday evening and got almost no time out errors anymore (one error, disappeared on the second try).

Markus

Read More...

thank you very much for enabling this feature request. Looking forward to test it with the upcoming May release.

Markus

Read More...

Thanks a lot, Vielen Dank, let's hope for a quick release with the May edition.

Markus

Read More...

unfortunately, I made the experience that the Indi driver for touptek cameras works very unreliable and I'm very frustrated now, because I have tried all kinds of problem solving attempts with no success but would really like to use Indi and EKOS for my setup. Really, I like EJOS a lot and would like to cobtinue using it.

Why do I think it is a problem of the driver?
1) it works reliably with Windows 10 and the exact same hardware (Lenovo Thinkpad, dual-boot), same cables, USB hub, other gear...
2) my two QHYCCD cameras (QHY 5II-L, QHY 168C) work fine with the same cables, USB hub, EKOS version
3) same problems with either Intel notebook or RPI4 (astroberry 2.04, 4GB RAM)

What is the problem exactly?
Usually after power on, boot , Indiserver start and connect it does work. I can take a picture with the touptek camera (usually 2x binned), plate-solve, take a picture again etc. Then I start guiding using the QHY camera and try to focus the main camera. This usually involves a changed exposure time, gain, binning and subframing. On the first attempt this usually works, sometimes the first failures (exposure timeout, rexposure attempt #2, final timeout) start to appear. Then I take the first test picture with the final imaging parameters but a short exposure time of a few seconds. In maybe 20% of the evenings this does work, but almost never as it should. The exposure starts counting down and just before download finishs a long break occurs. In lucky evenings the FITS viewer will appear and everything is fine if nothing major changes, I can do my exposure series. Unfortunately most of the time nothing will happen. The download will never start or if started will stop a few hundreths of a second before finishing. After waiting for some time, I can stop and redo the exposure. Usually with the same result. Sometimes reloading the driver, reconnecting using the Indi panel or changing some parameters will help after many, many tries but most of the time only a reboot will reliably make it wokr again for some time. Even if it works, any change like going back to focusing or plate solve will trigger the problem again.

What can I do to help solving the problem?
I have tried all kinds of permutations of hardware (new cable, hub, RPI4) and software (local Linux, remote Linux, remote Windows client) March version, January version. The error message about the exposure timeout does not help. I was unable to activate the debug mode, maybe that could help.

Any further recommendations?

Markus

Read More...

Hi Aaron,

you can convert the raw files to the DNG format and correct the whitebalance using PiDNG (github.com/schoolpost/PiDNG) Maybe the easiest solution.
Here you can find the necessary CCM matrix for conversion: git.linuxtv.org/libcamera.git/tree/src/i...ypi/data/imx477.json if you want to program it into your code.

Markus

Read More...

Rob, maybe it is helpful to know that rtsp is just a protocol to transmit technical parameters like resolution or used codec. The data itself is transmitted via the rtp protocol. I just downloaded the current release 5.01 build for Windows x64 (gyan.dev) and used ffplay to play various rtsp URLs (Reolink, unknown chinese OEM vendor, v4l2rtspserver, vlc acting as server). Worked perfectly. Unfortunately there is a great variety of possible URLs. Every security cam vendor has a diiferent opinion. Thats the reason I asked for a generic input string. There is little to be gained by wrapping this up in a menu. I do not know how this translates into an API call inside your indi webcam driver, but I hope for working solution. Thank you very much already.

Markus

Read More...

you talk about rstp but it is rtsp. I'm 100% sure that rtsp is supported by default in the Debian/Ubuntu distributions and the Windows x64 binaries distribution of ffmpeg. You can check it with the ffplay <URL> command to receive a stream.

Markus

Read More...

Hi Aaron,

it worked! I changed the setup.sh for port 444 (http) and the script completed its work and apache2 started. I could access the web page and do the configuration. For the first time I changed the image path and initially forgot to rerun the script. After doing that all was fine. THANK YOU!!!

Markus

PS: the disablement of other web servers (nginx, lighttpd) should be optional, I had to manually reenable/restart them...

Read More...

although u defined the remote indi server/port, how do I define/select/configure the right camera?

Markus

Read More...