I know the feeling.
I have the same version running on Raspberry PI/Astroberry. In my last session, I had it twice, each time involving the FITS viewer, once when clicking the histogram icon and once when just bringing it to the front.
I could not find any thing relevant in /var/log/messages or other log files in /var/log
I run on a PI with 8GB memory, so lack of memory shouldn't be the problem.
Next time I'll activate the debug logging, but looking at the weather report, that will not be for any time soon
Hello,I'm using Ekos on astroberry with a ZWO EAF focuser, I got for my birthday from my kids. I looked around a bit and these are the settings I've tried (found info on this forum):
this is in the meantime solved - as I was quite sure it wasn't a problem with ekos.
There were a couple of other problems:
- I suspect that there wasn't a bind with the gspd.socket; hence it worked by specifying on the command line /dev/ttyACM0, but not when without. Once started at boot via gpsd.service, it worked ok
- As I was testing this inside (though close to a window), I wasn't patience enough
Thanks for you reaction!
I configured a U-Blox7 USB gps on my astroberry. When I launch the command gpsmon /dev/ttyACM0 it shows the satellites, time and position correctly, at the top it shows astroberry:/dev/ttyACM0 57600.
When I don't specify the device it shows no satellite nor location information and at the top it displays: tcp://localhost:2947
In the ekos indi control panel at first I thought it showed the correct location, but that was not the case, it just showed what was in /etc/location.conf. Once I commented all lines in /etc/location.conf it did not show any location info any more.
I'm sure it's a configuration issue, but can anybody tell me what config setting could wrong?
Thanks and kind regards,
I recently have reinstalled all my gear and wanted to align the guider scope with the main scope using the attached cameras.
Here's my problem, and how I reproduced it (twice only, as I don't want to wreck my equipment)
I finally had the chance to check this out, and indeed setting bulb mode on the camera and "force bulb" now takes all exposures with the exposure time requested; but now I'm having issues when trying to take sub-second exposures (like for the flats), if I set the exposure to 0.04 then it takes 1 seconds exposures. I'm puzzled.
I'm a beginner and I'm using Ekos (KStars version is 3.4.3) on astroberry.
My camera is a Canon 500D.
I've setup a sequence of 20 captures of 1 minute each.
My problem is that every uneven capture is a capture of 1 second (I verified this with nomacs), though Ekos logs that it's capturing a 60 second image.
My darks, same problem.
My question, what am I doing wrong here, or what setting did I mess up?
All help appreciated!
I'm using ekos (KSTars is version 3.4.3) on astroberry.
My camera is a canon 500D.
It's the second time I'm using ekos to capture. First time I did not have any problem.
The second time, I've setup a capture of 20 exposures of 1 minute.
Every uneven capture is an exposure of 1 second (I checked that with nomacs), though ekos says it's capturing for 60 seconds. All even exposures are ok.
I don't have a clue what is going on.
What am I doing wrong?
Any help appreciated.