appyaardvark

It has been quite a while since I've posted here, posted anywhere, with an image, after a few years away, I present my first of a number of projects I have on the go. Veil Nebula, (Cygnus) wide field Equipment used: Camera : ZWO ASI183MC Pro Filter: Antlia ALP-T 5nm highspeed Lens: Samyang 135mm f/2 lens @f/2.8 Mount: Software Bisque Paramount MX+ Shot over the following nights: 2023-06-24 60 x 120s 2023-06-25 60 x 120s 2023-07-05 96 x 120s 2023-07-06 90 x 120s 2023-07-07 94 x 120s Total integration time: 13 hrs 20 mins Processing: WBPP DynamicCrop ABE Split RGB Channels StarXterminator EZ Suite soft stretch PixelMath curves NoiseXterminator BlurXterminator https://flic.kr/p/2pCDUcp

Well let me be the first to reply, with a possible solution... Once you've chosen ASCOM in the Choose Camera list Under Settings, don't choose the first option as I did...go for another and lo and behold, once you select connect and take your first photo... Happy now, I can go to bed and leave T point doing its thing. Hurrah! 🙂 Clear skies!

Well hello. it's been a while. I've recently decided to make my Paramount MX+ semi permanent; dug the hole, concrete etc, ran a T point with my Redcat and ASI183, no issues there, took some test shots of the Sun using the ED80 and ASI 174, no issues there.... Whilst my QSI 683 is sunning itself in Portugal and hopefully being repaired, I decided to dig out my Atik 314L+. I've not used it for a while, but was eventually satisfied it still worked, it connects and takes images in N.I.N.A, so problem. However, when I try to use it with TheSkyX Pro, whilst it connects and I can set the cooling etc, when I attempt to take an image, I get It never downloads and completes the process. Abort is the only option. I presume this is a Software Bisque issue and there's nothing wrong with the camera, as it works in N.I.N.A? Anyone have any thoughts? What I'm trying to attempt, is having several configurations of [scope + camera + mini pc], that I can take off the mount and replace with another [scope + camera + mini pc], for whatever target I choose. The Atik is a camera option that I hoped would still work. Each configuration will have its own T point calibration, hence the need to have the Atik playing nice in TheSkyX Pro.

Apparently so 🙂 Makes me a little wary about keeping the OS up to date though. However, when I updated this time, to test, no apps were affected. Thanks for your input

I tried with another SD card and both local and remote work as expected. Local: Remote: I reflashed the original card, set it all up again....both local and remote work as expected. Bit of a mystery this one. Tried on 2 different RPis, same issue, same success. The only difference was the SD card that had not previously been updated worked first time. Both cards were flashed on the same day, but one had an update applied to it a week or so ago (broke), the other didn't. The only visual difference was the Ekos GUI, so perhaps when I applied the update, Ekos was updated to a version that wasn't quite right? I don't know.

It's not running, stopped, auto start off, auto connect off. Clearing the fields won't change anything 🙂 I'm onto something though, just testing something else to see if it's the reason why......

Having connected to the Pi with a keyboard and mouse, with a monitor, I configure the Pi to use my Wifi. Restart the Pi, open my browser and type astroberry.local in the address bar, which takes me to Astroberrry Server Version 2.0.5 This is where Device Manager (a.k.a Indi Web Manager). It has not been started and auto Start and Auto Connect have been disabled: Click Connect, which allows me to remote onto the Pi with the VNC service Open Kstars Click on the dome icon Create a new profile called Test, local, disable autoconnect and only CCD is configured Hit save. Connect ASI 183 to the top USB3 port on the Pi. The camera has 12V power, just in case it's an issue Once connected, Start Ekos Output from lsusb -v shows ASI 183MM Pro is connected OACapture agrees:

I have used all sorts of combinations of drivers ZWO camera, ZWO camera 1,2 and 3. None are recognised as cameras by Ekos. lsusb shows that devices are detected, but the codes for the cameras are not recognised by Ekos, but they are for the EAF and EFW

It's the Indy Web Manager

I honestly have no idea 😆 I followed a YT tutorial by AstroExploring He suggests it needs to be remote because it's connecting to a remote INDI server that is already running.... Selecting local causes driver crashes:

This is all running on the Pi. I am connecting to it via VNC, with my PC

If I unplug the 183, so that just the 290 mini is plugged in, nothing connects (except the simulator). As I understand it, the power is for cooling only, but it's powered nevertheless. I've tried using ZWO camera driver for both devices, different combinations of ZWO camera and ZWO camera 1,2 & 3., all with the same outcome. When I use lsusb in the terminal console, I get the following With nothing connected: 290 mini connected to bottom USB2 port: When I reconnect the 183 on its own to the top USB3 port: 183 still connected, plus EAF connected to top USB2 port of the 183: 183 still connected, plus EAF connected to top USB2 port of the 183 and EFW connected to bottom USB2 port of 183: Finally (sorry about all this), with the 290 mini reconnected to the bottom USB2 port of the Astroberry: So.... 183e = 183 1f10 = EAF 1f01 = EFW 290f = 290 min I presume Cypress is the in built USB2 hub on the 183 How to make Ekos understand what these devices are and use them?

Hi Apologies if this has been covered elsewhere, but I was about to throw in the towel yesterday, having spent 2 hours trying to connect everything and searching for answers online, but thought I'd give RPi another chance. Alas, no change to the situation, even after I've given it over 24 hours to change its mind. Scenario: WO Redcat + ZWO ASI 183 MM Pro connected to USB3 port of RPi ASI290 Mini connected to USB2 port ZWO EAF & ASI EFW connected to USB 2 ports of ASI 183. Simulated Telescope mount Astroberry Server release 2.0.4, updated via apt-get to version 2.05 I've set up a profile in Device Manager [see image 1] Open Kstars Create a profile and save [see image 2] Click on start EAF & EFW have both been detected, along with the simulator, but no detection of either ZWO camera, despite the EAF and EFW being connected to the USB port of the ASI 183 camera.... [see image 3] I've tried with just the ASI 183 - no detection (multiple attempts, different ports) Obviously I'm doing something wrong Anybody any idea what that is? After this I connected everything to the ASIAir Plus and all connections made, no tinkering required. I know some would say just use the ASIAir, but I would like the option to choose between the two. The Astroberry should work, shouldn't it? RPi is model 4 B with 4GB of RAM, powered with an official RPi power supply (5V, 3A) connected to the mains indoors. I had previously attempted this with the Pegasus Power Box Advanced, but switched to mains supply just in case power was an issue. This is my first foray into INDI/Kstar/Ekos etc in the past having used an RPD session to connect to a laptop/ITX PC local to the mount. Any help would be appreciated. Cheers, Paul