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...

Hopefully will get the chance to check this tonight. Will post an update!

Read More...

Wife's Astroberry Pi is missing some of the index files I have on my Pi. For example index-4201* (8.8GB). I copied mine to her Pi, but I'm wondering if this works or what because when I check that in astrometry, it tries to start a download.

The files are in /home/astroberry/.local/share/kstars/astrometry. Can I install/register?

Read More...

Paul Nixon replied to the topic 'HIDDEV0 HID relay for D5100?' in the forum. 1 month ago

Hi Jasem,

Thanks for the reply. I wasn't sure what the status of support for these relays was. If I understand you correctly, these boards should work with NINA or Backyard Nikon? I can test that. ;)

I do have another relay board that's a bit different - it plugs into the USB port of a PC/Pi, etc. I tested it in Windows, and it gets assigned COM13, so it is the right type in that sense. I was able to trigger it with the KMTronic utility using different string (FF A0 01 01 A2 turn the relay on and FF A0 01 00 A1 to turn it off). Is there a way for the end-user to use that info to support this particular relay in Ekos?

Low priority, I know. Just am curious.

Thanks!

Read More...

Paul Nixon created a new topic ' HIDDEV0 for D5100?' in the forum. 1 month ago

I have a D5100 that I use with the KMTronic relay, and it works just fine on Astroberry or Windows.

Today, I was going through some drawers and found a couple of relay boards I'd bought early on that, at the time, I could not get to work. I think I was using Windows at the time.

Anyway, I thought I'd plug one into the Pi and see if I could maybe get the relay to fire. Not so far. But I've a couple of questions.

1) the relay board showed up as hiddev0 under /dev/usb. But when I attempt to plug in /dev/usb/hiddev0 as the "port", Ekos accepts it but tries to connect to serial port /dev/hiddev0 and fails.
2) Quick and dirty like, I created a link, but it still doesn't trigger the relay. I get his:

2020-12-03T22:57:18: [ERROR] Failed to expose.
2020-12-03T22:56:44: [WARNING] Closing Nikon remote serial shutter failed.
2020-12-03T22:56:43: [WARNING] Opening Nikon remote serial shutter failed.
2020-12-03T22:56:43: [INFO] Starting 1 seconds exposure.

I noticed when I plugged it into Windows 10, the OS saw something out there but could not load a driver. Windows 7 loaded some HID driver, but that was the extent of it - no Comm port. My NUC is Windows 10 so I think if there's any hope, it's with the Pi.

I tried it using gphoto and nikon. I do NOT actually have the other side of the relay connected to the camera (have not made that part of cable yet) - I just want to test the relay communication.

My question really is - am I doing something wrong, or does this sort of relay board still not work?

Read More...

Night before last, I was not guiding. I was just testing the meridian flip. I set up for 60s exposures of NGC246. At the appropriate time, the scope flipped and plate solved to put NGC246 back dead center. I did not expect to get any usable images what with the full moon, but to my surprise, there was the Skull!

Last night, I decided to try for 120s. I got PHD up and running, and when it came time for the flip, I got all the appropriate messages, and after the flip, Ekos plate solved and put NGC246 dead center of the image view. But PHD went off to la la land and image capture quickly aborted. RA (if RA is blue and DEC is red - I think that's the way it is) went off-screen down. I tried to simply restart guiding from that point, but RA kept going to la la land. I ended up recalibrating.

I don't seem to have much trouble with flipping, only with picking up guiding after the flip. Someone mentioned clearing alignment data and purging the data from Ekos - is there a very specific order?

Read More...

Paul Nixon replied to the topic 'ASTAP help please' in the forum. 7 months ago

Hi Han,

I know the image is easily solvable - the problem is that for some reason, ASTAP thought the target was centered. It started off centered by ASTAP just fine, but over time, the target drifted down. It was when I attempted to recenter the target that something went amiss, and what you see is the result.

Is there any reason for portrait mode? Not that I'm aware of. It's something that just seems to happen and I really have no idea why. I've gone back through several directories of images and sometimes they are all portrait, or all landscape, and sometimes they start off landscape and turn to portrait.

I just took a dark with "Capture and Solve". I hope it contains what you need: drive.google.com/file/d/13oM2uJ4b0j8x-tD...m0R/view?usp=sharing

It's cloudy here tonight so no imaging. :(

Thanks!

Read More...