Hi, Jasem

Thank you really for the fast response.

Today I could do some testing and tried to set the SD card to "Delete".
Having the Raspberry Pi running, I powered up the camera with an SD card mounted into the camera. Connected to RPI with USB, via powered hub.
I started the INDI server (web interface) and started kstars.
In kstars I called EKOS and started the profile. All devices connected correctly.

I performed several previews with the Sony alfa 6300. All worked correctly, without any old image being displayed and downloaded.
So far so good!

Let me see if the error has been solved this way. Tonight no clear skies. We'll see next week, but the weather forecast for Andorra is not quite in favor of deep sky imaging.

Anyhow, thanks for the hint, I'll keep you up to date.

All the best,
Alexander

Read More...

Good afternoon everbody.

Since half a year I use INDI server at a Raspberry Pi (RPI )with Raspbian "Stretch". As camera I use a Sony Alfa 6300, connected to the RPI via USB. This combination is controlled with kstars and EKOS at a Mac. Images are taken at the EKOS panel.

Lately, I have trouble to get the latest image from the camera. The camera connects correctly and answers to the commands. Exposure time, ISO setting and other parameters are set the right way. Neverheless, using "Preview", the downloaded (and displayed) image is not the latest one. It seems that an image gets "stuck" in a kind of cache and this one is downloaded every time, despite the camera, which changes correctly the exposure time and executes it, followed by a download of the old, stuck image.

Repeatedly disconnecting and connecting the camera, combined with closing and restarting kstars fixes the problem finally, but it can happen that this takes abouthalf an hour, which is valuable clear sky time.

I tried to operate the camera without SD card to discard the possibility of having a stuck image stored in this card, but without success. Thee problem persists. Also, I played with the Sony DSLR driver configuration in the INDI control panel, but without success.

I also tried to change the automount policy in Raspbian, editing the file pcmanfm/LXDE-pi/pcmanfm.conf to set the automount and startuo moubnt parameters at zero, but without succes.

Some details about my equipment:
- Raspberry Pi B3 with Raspbian "Stretch", latest updates applied. Connected to LAN with ethernet cable (cat 6)
- INDIlib 1.7.4
- Gphoto2 versions: , gphoto2: version 2.5.11, libgphoto2: 2.5.12, libgphoto2_port: 0.12.0
- INDI server web manager to stop/start the service and to configure profiles
- Camera: Sony Alfa 6300, connected to RPI with USB cable. Tried with and without powered HUB. USB mode set to "Remote" (no "Mass storage")
- kstars version 3.2.1, build 2019-04-24T18:40:46Z at MacBook pro with OS/X "Mojave", version 10.14.5, connected to LAN via 5 GHz WiFi

Other equipment at the RPI, connected to EKOS, like EQMOD mount, Baader Steeldrive focuser and LodeStar SX CCD for guiding are always working correctly. These devices are connected the same way via USB and managed in kstars at the Mac and EKOS.

My Questions:
- Has anybody had the same or similar behavior with Sony DSLRs (or even other marks) ?
- Should I change the gpoto2 settings in file ~/.gphoto/settings to change line "libgphoto=cached-images=2" to "libgphoto=cached-images=0" ?
- Is there another solution for this problem, e.g. by changing a configuration?

Maybe you need more details to investigate this problem. For the moment I would be pleased to receive some hints. The Sony Alfa 6300 is a perfect camera for deeep sky photography in the primery focus of a 200 mm F4 Newton. I enclose the photo of NGC5353 with supernova 2019ein to show what is possible.

Thank you very much for any help!
Clear skies and greeting from the Principality of Andorra.
Alexander



Read More...

Alexander Beening shared a photo. 2 years ago

Pleides. Newton 200mm - F/4. Camera: Sony ILCE-6300, 1600 ISO, 25 images of 30 seconds, stacked with Nebulosity-4. Sky conditions: Slightly hazy, Moon disturbed somewhat.
Alexander Beening replied to the topic 'INDI server on Raspberry Pi 3 works correctly' in the forum. 3 years ago

Good afternoon

Just to report in this forum that this weekend I could install the INDIserver on the Raspberry PI 3 without any problem. Here is the setup I currently could validate:

  • Raspbian "Jessie", latest release from Raspberry Pi site. I started "from zero" with the minimum image
  • SD card 8 GB (will expand to 32 GB later
  • tightvnc server, latest version
  • packages "lightdm" and "lxde" to add Xserver capabilities
  • INDIServer 1.2.0 from this site, installed as documented
  • lin-guider, installed as documented for the LodeStar X2

At this moment I cannot give all the install details, but if somebody is interested, please let me know.

I use the following devices:
  • ATIK 383 L+ BW CCD (INDI)
  • EQMod for NEQ6 Pro, cable version (INDI)
  • LodeStar X2 guider (INDI or lin-guider, both works)

My observations are that the RPI 3 is faster, both in processing as in communication with WiFi. Download time for a 2x2 binned image from the ATIK 383 L+ is about 40% shorter that for the RPI2 with WiFi USB dongle.

Attention: The RPI3 really uses more than 2 amperes of current, so an ordinary 5V power supply sometimes is not sufficient: you will see the red LED on the board blinking if the power is insufficient.
Furthermore I could even activate the Bluetooth option. Not necessary to install any package, the device is already active at bootup.

One other hint: Attention with the WiFi: By default power saving is active, so after a couple of minutes the connection (ex: ssh or vnc) will be lost. Power saving can be switched off, just like the RPI2 with an USB dongle.

Finally I recommend this new RPI3 for astro work. It is worth it.

I hope that these comments are helpful for you. Please contact me, maybe I can be helpful

All the best and clear skies from Andorra

Alexander

Read More...