I am a bit frustrated at the moment. I thought I read where KStars 3.5.2 was part of Astroberry, so I expected it to be there with the latest Astroberry install I did. It was not. Thinking maybe I needed to update/upgrade, I the the sudo app update and that went fine. I then did sudo app upgrade, and that pretty much wiped my sdcard back to 4 green blinks and almost nothing on the sdcard. Having to start all over again. 

For now, I'll look on the bright side and say I needed the experience anyway. ;)

Read More...

I had the tv power up ready to go. The Pi blinked momentarily like it was going to do something, then I kept getting 4 blinks on the green LED.

Fortunately, it was not a big deal to install the latest version.

Read More...

I connected to a keyboard and monitor, but it was just a black screen.

I have since installed Astroberry 2.0.3 and it came up fine. Seems a few configuration bugs have been worked out, too, as I didn't have to jump through hoops to get my gps (UART) working, and configuring connection to my wifi was much simpler than previously. 

So, it *seems* like I am in pretty good shape for Kstars 3.5.3 when it comes out. Actually glad this crash happened now rather than later. ;)

Read More...

I did use two commands and it got a lot further/did much more, but it still failed (too many errors).

Unfortunately, it appears my Pi has locked up.

Hard reboot (power cycle) but it doesn't come up. I get a solid red LED, and the green LED flashes 4 times.

I think my installation is fubar. Argh...

Read More...

Thanks for the reply, but it turns out there was no root password. Sudo passwd root took care of it.

Read More...

I'm in a bit of a pickle. 

I just read on CN that Kstars 3.5.3 has "real time" vectoring for polar alignment - very exciting. So, I fired up my Astroberry Pi4 and attempted to sudo apt-get update && apt-get upgrade. Unfortunately, I can't seem to remember the root password! 

Forget for a moment I read moments ago here that 3.5.3 has not yet been released for Astroberry, am I SOL on the password? Do I have to do a complete reinstall? I'm currently connected via VNC, if that matters.

Thanks.
 

Read More...

A small update.

Success! Turned out didn't need to add the "missing" file(s). She needed the proper FOV set. We couldn't figure out why the numbers we put in got overwritten, but once we figured that out (solver options), solving was very quick.

Read More...

Hi Jon,

The down sampling is set to '2', but I see 'Auto' is also checked.

I *think* I may have found a misconfiguration - the field size solves to 2.78573 x 1.86033 degrees. However, Ekos is set for 51.08' x 40.86'. This should be 161.14' x 111.62 (multiplying degrees by 60 to get arcminutes), yes? Does that seem likely?

My setup (Nikon D5100 and f/6 80mm scope) uses CCD FOV of 168.71' x 111.74'.

Thanks!

Read More...

So, I found an old .cr2 file taken with her 80mm refractor and, after converting it to .jpg, ran the command line. This was the output:

Reading input file 1 of 1: "/home/astroberry/Light/solve_test.jpg"...
Extracting sources...
Downsampling by 2...
simplexy: found 1257 sources.
Solving...
Reading file "/home/astroberry/Light/solve_test.axy"...
Field 1 did not solve (index index-4219.fits, field objects 1-10).
Field 1 did not solve (index index-4218.fits, field objects 1-10).
Field 1 did not solve (index index-4217.fits, field objects 1-10).
Field 1 did not solve (index index-4216.fits, field objects 1-10).
Field 1 did not solve (index index-4215.fits, field objects 1-10).
Field 1 did not solve (index index-4214.fits, field objects 1-10).
Field 1 did not solve (index index-4213.fits, field objects 1-10).
Field 1 did not solve (index index-4212.fits, field objects 1-10).
Field 1 did not solve (index index-4211.fits, field objects 1-10).
Field 1 did not solve (index index-4210.fits, field objects 1-10).
Field 1 did not solve (index index-4209.fits, field objects 1-10).
Field 1 did not solve (index index-4208.fits, field objects 1-10).
Field 1 did not solve (index index-4207-11.fits, field objects 1-10).
Field 1 did not solve (index index-4207-10.fits, field objects 1-10).
Field 1 did not solve (index index-4207-09.fits, field objects 1-10).
Field 1 did not solve (index index-4207-08.fits, field objects 1-10).
Field 1 did not solve (index index-4207-07.fits, field objects 1-10).
Field 1 did not solve (index index-4207-06.fits, field objects 1-10).
Field 1 did not solve (index index-4207-05.fits, field objects 1-10).
Field 1 did not solve (index index-4207-04.fits, field objects 1-10).
Field 1 did not solve (index index-4207-03.fits, field objects 1-10).
Field 1 did not solve (index index-4207-02.fits, field objects 1-10).
Field 1 did not solve (index index-4207-01.fits, field objects 1-10).
Field 1 did not solve (index index-4207-00.fits, field objects 1-10).
Field 1 did not solve (index index-4206-11.fits, field objects 1-10).
Field 1 did not solve (index index-4206-10.fits, field objects 1-10).
Field 1 did not solve (index index-4206-09.fits, field objects 1-10).
Field 1 did not solve (index index-4206-08.fits, field objects 1-10).
Field 1 did not solve (index index-4206-07.fits, field objects 1-10).
Field 1 did not solve (index index-4206-06.fits, field objects 1-10).
Field 1 did not solve (index index-4206-05.fits, field objects 1-10).
Field 1 did not solve (index index-4206-04.fits, field objects 1-10).
Field 1 did not solve (index index-4206-03.fits, field objects 1-10).
Field 1 did not solve (index index-4206-02.fits, field objects 1-10).
Field 1 did not solve (index index-4206-01.fits, field objects 1-10).
Field 1 did not solve (index index-4206-00.fits, field objects 1-10).
Field 1 did not solve (index index-4219.fits, field objects 11-20).
Field 1 did not solve (index index-4218.fits, field objects 11-20).
Field 1 did not solve (index index-4217.fits, field objects 11-20).
Field 1 did not solve (index index-4216.fits, field objects 11-20).
Field 1 did not solve (index index-4215.fits, field objects 11-20).
Field 1 did not solve (index index-4214.fits, field objects 11-20).
Field 1 did not solve (index index-4213.fits, field objects 11-20).
Field 1 did not solve (index index-4212.fits, field objects 11-20).
log-odds ratio 157.581 (2.73177e+68), 20 match, 0 conflict, 50 distractors, 24 index.
RA,Dec = (148.897,69.0896), pixel scale 4.44828 arcsec/pix.
Hit/miss: Hit/miss: +-++++-++++-+---++-+----++-+-+


+
+
+(best)
Field 1: solved with index index-4211.fits.
Field 1 solved: writing to file /home/astroberry/Light/solve_test.solved to indicate this.
Field: /home/astroberry/Light/solve_test.jpg
Field center: (RA,Dec) = (148.894787, 69.088732) deg.
Field center: (RA H:M:S, Dec D:M:S) = (09:55:34.749, +69:05:19.436).
Field size: 2.78573 x 1.86033 degrees
Field rotation angle: up is 89.2952 degrees E of N
Field parity: neg
Creating new FITS file "/home/astroberry/Light/solve_test.new"...
Creating index object overlay plot...
Creating annotation plot...

I thought maybe the solving problem happened when she was using her other scope, a Mak127, but I just ran a pic from that one and it also solved (with index-4209.fits), so maybe the issue has nothing to do with index files and something else is going on.

Suggestions?

Read More...