TerryMcK

I just had a brainwave and did a google. I found a compiled version for Raspbian of libopencv_2.4.11.deb.zip from this website https://github.com/Nolaan/libopencv_24 I installed it into /usr/local/lib and bingo PoleMaster now works on Astroberry - problem solved

Yes it appears as Astroberry uses Raspbian so the software package from QHY CCD for Polemaster does indeed only seem to run on Ubuntu Mate - I omitted to read the first half of their instructions on their website which talked about burning an image of MATE. Oh well .... polar align using Winders and everything else automated using Ekos. The law of Sod - until some bright spark (not me!) ports it to Raspbian. Building an observatory and having the scope permanently aligned is a long way down the road so that isn't an option either.

One thing I have found is that there doesn't appear to be any way of setting mount limits in Ekos as you can in EQMOD ASCOM. So it is possible to clout the tripod or pier with the backend of the scope. I haven't done it yet but can see it is possible. Reading threads on the Indi forum it appears that it was thought about 5 years ago but doesn't look to have been implemented. Anybody come across this?

A right angle adaptor is good as it has a normal position and a magnified view too. It helps immensely to prevent you getting your knees dirty in the higher latitudes like anywhere in the UK. However the best thing if you use a laptop is something like a PoleMaster. I can get polar aligned and spot on within 2 minutes with mine. It even works just around dusk when you can't see Polaris withe your naked eyes due to the sky still being light. The PoleMaster has adaptors for all sorts of mounts. There is another one, which I haven't used, the Ioptron iPolar which also has adaptors for different mounts. You don't even need to see Polaris with that one as it does plate solving in the vicinity of Polaris. Again though there is a cost decision here and if you want to use a right angle scope then that it fairly cheap and you don't need a computer. If you are going down the astrophotography route then I assume you would have a computer in the field then the electronic polar alignment option is the way to go.

I have Astroberry server running ok on a Raspberry Pi4. I have tried to get the PoleMaster to run on this following the instructions from QHY https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=30&id=223 When I run up the PoleMaster from the CLI using sudo PoleMaster I get PoleMaster: error while loading shared libraries: libopencv_core.so.2.4: cannot open shared object file: No such file or directory Looking in /usr/bin/Polemaster the file is present. 1.2M -rw-r--r-- 1 pi pi 1.2M Dec 14 2018 libopencv_imgproc.so.2.4 Here are the results of a filtered ldconfig -v astroberry@astroberry:/usr/bin/PoleMaster $ sudo ldconfig -v | grep -i libopencv_core.so ldconfig: Can't stat /usr/local/lib/arm-linux-gnueabihf: No such file or directory ldconfig: Path `/lib/arm-linux-gnueabihf' given more than once ldconfig: Path `/usr/lib/arm-linux-gnueabihf' given more than once ldconfig: /lib/arm-linux-gnueabihf/ld-2.28.so is the dynamic linker, ignoring ldconfig: file /usr/lib/arm-linux-gnueabihf/libsbig.so.4 is truncated ldconfig: file /usr/lib/arm-linux-gnueabihf/libsbig.so is truncated ldconfig: Cannot stat /usr/lib/arm-linux-gnueabihf/libmca_common_ofi.so: No such file or directory ldconfig: file /usr/lib/arm-linux-gnueabihf/libsbig.so.4.9.9 is truncated To troubleshoot I have installed libopencv-dev but still get the same error. Anybody else seen this on the Pi 4? Maybe PoleMaster will not run on the Pi4?

You should get 2 minutes ish

I use the William Optics ZS73 on the HEQ5PRO. It is an excellent mount for this size of telescope and slightly wider apertures like 102s. You will see even more of an improvement by converting to belt drive - the Rowan belt mod that I have is excellent. The mount will be a great combo for your scope but get a field flattener, look at getting a guide scope for longer exposures and you will be well on the way to spending lots more cash down this rabbit hole called Astrophotography.

Not the postman but DHL brought my Lakeside Focuser. Now attached to the WO ZS73 and working fine. Whisper quiet, accurate and dead easy to use. Manual control is a breeze. Hooked up to a PC on ASCOM or Raspberry Pi using EKOS works great. Very impressed with the build quality and extremely easy to assemble. Now going to wait a couple of months until a clear spell occurs to try it out - maybe thats why astronomy gear warranties are 2 years ... kit rarely get used to wear out ! The box from FLO does say “May contain clouds” and thats what I expect to see for the next few weeks.

Yes I tried to get it going but it seemed a little flakey. I was following Polemaster instructions in their raspberry Pi manual. I ended up not being able to sudo because it stated that you had to sudo nano ~/.bashrc alias sudo='sudo env PATH=$PATH &>/dev/null' $ source ~/.bashrc // Make the changes take effect Entering that alias into .bashrc meant that anything I sudo'd just went to null. You couldn't even edit the .bashrc file as it just went to null. So I managed to copy in the backup of the .bashrc file I had made so I could sudo again! I'll have another go at it at the weekend but if you have any pointers that would help. Up to now everything has worked and I have the Windows Kstars app running on a winders PC indoors controlling the astroberry Kstars remotely.

I've been trying out sequencing using Ekos - during the day I must add. It is fantastic

I'm really impressed with the Astroberry server running Kstars with Ekos to control all the gear. Sequencing like Sequence Generator Pro Guiding using PHD2 Full control over the ZWO cameras I have - not limited to ZWO gear either unlike the ASIAir. Full control of the HEQ5Pro mount Parking at the end of your sequence Control from a browser/iPad or remote from a multiplatform KStars/Ekos client Oh and focusing provision - anxious to try that out with my new Lakeside Focusing system. Too many other features to mention. What excellent piece of software running in a little tiny box.

I have just had notification that my Lakeside motorized focuser kit is on its way and should be with me Friday - thanks FLO - also found that Ekos has a Lakeside driver built in for it in the Raspberry PI4 In anticipation my mount has a loose USB B cable (of the right length) ready and waiting to be hooked up.

Most people go for 1.1/4” filters in filter wheels. They are also a bit cheaper than the 2” versions especially for the very narrow bandwidth ones.

I just watched the video on Youtube. He actually believes passionately that he is right so I can't knock that. Me however .... I howled laughing 🤣

I've just done the same with mine but ran it by ssh'ing into the pi itself it returned a lot of drives but it is 128GB card astroberry@astroberry:~ $ sudo fdisk -l [sudo] password for astroberry: Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/mmcblk0: 119.3 GiB, 128043712512 bytes, 250085376 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xd9b3f436 Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 8192 532479 524288 256M c W95 FAT32 (LBA) /dev/mmcblk0p2 532480 250085375 249552896 119G 83 Linux Disk /dev/zram0: 64 MiB, 67108864 bytes, 16384 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 64 MiB, 67108864 bytes, 16384 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram2: 64 MiB, 67108864 bytes, 16384 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram3: 64 MiB, 67108864 bytes, 16384 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes astroberry@astroberry:~ $

Yes I agree with Carole. The W&W dew heaters are really good. I have a few of them. Mine do plug into a controller I got from FLO which is controlled by USB (not powered by USB) and is handy to remote control the current delivered to each strap. The controller is Lynx Astro 4 Port Dew Controller with DSLR Power Supply https://www.firstlightoptics.com/dew-prevention/lynx-astro-4-port-dew-controller-with-dslr-power-supply.html Although there are others without the dslr power output. Have a look and make your choice.

No I haven’t tried that.

The fish head looks like it is blowing a smoke ring. Fantastic framing Gina. Now looking forward to seeing your colour additions.

I’ve just ordered Lakeside Focuser Kit from FLO. My last outing Feb 6th and 7th imaging the fish head was slightly out of focus Astro Pixel Processor detected no stars. There were hundreds! But apparently its star detecting algorithm likes stars to be spot on. So I’ve put off motorising the focuser for far too long. Looking forward to a package that says “May contain clouds” and then wait a month until I can try it out in anger! It’s made in Britain and has great reviews and I also ordered the bracket kit for the WO ZS73. Deep Sky Stacker still worked OK on the data I collected so all is not quite lost.

I have exactly the same setup. Remove the focus ring and screw on the lens again. Then screw the lens in until around 4mm of thread is showing and you will be nearly there. Focus is only a hair around this area and you may find no more than half a turn or so gets you in focus. My scope is the 9x50 straight through finder scope which has a 180mm focal length. There is another finderscope by skywatcher which carries the diagonal and that is much shorter. That one will NOT work with the C adapter as the focal length is too short.

I've been playing around with the PI4, Astroberry, PHD2, KStars and of course Ekos for a couple of days. I found I had to have PHD2 loaded first but not connected to guidecam/mount. Then I fired up KStars and clicked onto Ekos I could start all the services ok - click connect and all devices were connected. Then I found that PHD2 had automatically connected to the guide camera and mount (which I had preconfigured). Iassume Ekos does this automatically. As we haven't had any cloudless nights in these here parts (looking forward to Tuesday night 04/02/2020 though) I've taken a few darks while the guider was looping (both ASI cameras BTW) and found downloads worked fine without interrupting the guider. I used to occasionally get camera disconnects on Windows for PHD2 with ZWO gear while imaging (download time outs). Then I found the solution was to use native driver for the guide camera and ASCOM for the capture software (APT on Windows). Not sure if INDI has the same problems but not come across anything - yet...

Yes EQMod cable used. The 5m one from FLO

I bought yet another Raspberry Pi4 the other day. It has a metal case that keeps it cool that I specced from Amazon - iUniker Raspberry Pi 4 Case, Raspberry Pi Case with Heatsink, CNC Metal Case with Heatsink Raspberry Pi Shell without Cooling Fan for Raspberry Pi 4B if you want to get one yourself. This comes with heat conducting tape that you apply to the CPU, RAM and USB chips. The case then has internal metal blocks which conduct the heat away. I have to say for £13 it is very good. Much better than the Pi4 fan which develops a noise in time. It is also relatively heavy duty case so should work ok strapped/velcroed to the scope. I also bought a 128GB microSD card. Following Ian's x6gas excellent guide on setting up the Astroberry server I had the scope connected and guiding in under 3 hours of receiving the new Pi4. I have then been playing around with the included free software. Ekos is excellent and connection to PHD2, My ZWO ASI183MC, HEQ5 was seamless. Then firing up KStars and getting it to slew and then update the Files setting in Ekos to whatever you are pointing at is fantastic. I've only been playing around with it indoors for now. Remote control via VNC or Web-browser is also great. I'm now looking forward to some clear nights to try it out in anger. BTW anybody know if PoleMaster will work with Astroberry? Otherwise I shall have to drag the winders laptop out to polar align (no static observatory here I'm afraid - I do it ala Trevor Jones at astrobackyard.com or Chuck at Chuck's Astophotography)

My Pi4 came at 12:45 - installed Astroberry and now have Kstars and PHD2 configured and guiding - barebones to running in less than 3 hours. Seems to work ok with my HEQ5, EQDIR cable and ZWO cameras.

Just got another Raspberry PI 4 with a metal case and 128GB flash for playing around with Astroberry. This is my third Pi and second Pi 4 having been a fan since they came out.