I feel I'm kinda tossing "snippets" here there and everywhere. I figured I'd try ONE THREAD I can say in as I work out the issues. Not sure if should be her or Astroberry. This might also be more helpful as a resource for others in take this path as well.

At this point I'm trying to get all the drivers and equipment to comply. I have had the mount connected before, but now it won't connect. Seems there is no port for it and I'm wondering... how do we configure more ports?
I run APCC for the mach1 which adds several v-ports. Seems like by the time all is said and done - I have 8-10 ports in use. (com). on windows.

I've installed linux. (I don't know how it handles ports).

My mount is astro-p GTO 4 (I don't see such a driver?) what do others use with a GTO 3 or 4? There is a Astrophysics (generic) I've been trying but it can't seem to find a port.

AH - it just hit me. This may be... (when it worked before I had windows installed) and APCC would fire up. Now with linux APCC isn't coming up and that must be the problem.

With Ekos I was worried about the dome and slaving. But the latested connection now shows a slave tab. = )

Though when it connects I get a WARNING please STOP dome before issing any further motion commands warning (what does it mean and why?)


hmmm Will the AP mount work without ascom2 driver or APCC on linux?

GTO4 would work fine with Astrophysical Experimental Driver. I'll talk to Mike to see if he feels the driver should still be deemed as experimental or should be named to something else.

Regarding the message, what is it exactly? is it please "drop" dome? or perhaps park dome?

Please STOP dome (typo). I'll try experimental. No APCC is used then I take it.

I run my AP1100 GTOCP4 with the A-P experimental driver and have had no issues so far. I do not use APCC except when I connect to VPC or my Mini PC. 95% of the time I connect and use it with my MacBook pro and directly through EKOS/KStars.

ODDLY - the dome use to work fine with windows indi server I was running. Now in linux It looks okay but doesn't move at all.

important info: With windows I used poth and the PDmeloy nexdome driver which I tested for Pat during development. Works well for me with windows.
However I don't know how these indi drivers work and maybe it work with or is based on the old nexdome 1.1 driver?

And my mount issue. Everything else SEEMS to be okay (Oh except the cloud watcher) refuses to connect and no error logging at all
The dome problem above and the mount both worked with the Windows indi server I was running. ???

Mine works in 3.0.0 and 3.1.0 on my Mac. The author is on Linux and I am sure it is working for him. He are my connection settings:

MAJOR BREAK THROUGH!

Before I put more time into putting astroberry on the nuc. I thought lets try it on the PI. I put the PI in the dome and plugged in 3 necessary USB connections. After some very strange network mess ups - and then finding the PI picked another IP. (I have to set a static IP in my router). I had major advancements. And some impressive experience with the software.

So the mount. Once in the PI - with proper OS/INSTALLS it tried to connect the problem mount. It pissed and moaned a bit and we spewing nice text updates to me as it tried. It said trying other ports... and things were flipping and then - GREEN light - all is well. I haven't tried to move it yet. Was REALLY COLD OUT THERE (record temps coming to Michigan again). so I did some quick checks and came in to pop on remotely. Here's my triumps and problem updates.

It CRASHED (I found I needed to turn off the web manager/server thing).
fixed - turned it off and booted. ODDLY it never asked me before but it wanted me to power up each item? (first time?) last time they just popped up, but then then didn't all work.

Next I tried my foxlynx focuser. WORKS! nicely. more options than I'm use to.
Next after mount (green but not tested) and focus - camera. (1600mm seemed fine) still need to test lodestar now that I'm in the house. Looking promising.

HOWEVER - Nexdome - my biggest fear - connects and says it's moving the desired amount I specified but does no move or open. In fact I went to push the rotation buttons and they acted like the firmware was wrong. TO NEXDOME PEOPLE... help! what firmware are you running on rotator and shutter? I had problems with 1.0 and 1.1 and worked with Pat to upgrade it and (works on windows with his new driver). Though Tim Long is writing all new code for NexDome as I type this. Still it's winter and cloudy and I'd not mind testing a old 1.1 or (working firmware that you guys are using).

Anyway I'm back in the house 300 ft from the dome. Pi is out there (amazing little unit). Running the browser remote display and there is very LITTLE Lag. Amazing. HOWEVER - it's 2.0 USB and I have 3.0 cameras and one spits out 73MB subs. I think I'll need to put astroberry on the nuc to get 3.0 ports. But no worries - as it is looking as if this may all work out.

Oh CLOUDWATCHER has fits too - anyone using one with this software and INDI? I'll look into this stuff from in the house now. Now to go see if the mount works.

Did some testing. Mount seems to be working. EXCEPT - it shows my latitude being way off. I checked my info in the initial setup of Kstars and it is still correct. -85. It's showing me at like 274.
This is where the mount thinks it is. (using APCC I've never had any issue). gonna miss that. = (

DOME is out... pretty sure it's the new firmware with the current infi driver.

All in all - a good day and good tests - both cameras seemed to work. I could test better if the dome would work. I did CRASH to desktop a couple times. I'm thinking since I have to go to the NUC PC for USB 3.0 it will also be nice to have a lot of ram vs 1gb in the pi.

In the options for EKOS go to the INDI options and check the box that says "KStars updates all devices" and make sure to check the time and location boxes. After I did this it seemed to know exactly where I was. I also seem to remember MikeFulb (the author) telling me to subtract 360 from your actual latitude if you are inputting it manually.

Seems like those where the choices I selected... But I'll check again. I've installed it 4 times on various platforms so maybe I didn't on the version I tested.

Ron, you will not be able to install astroberry on your NUC. These are two different CPU architectures. Astroberry is designed for Raspberry Pi 3B and 3B+ only. If you want to go the NUC way (it is probably Intel x86 or x86_64) you need to install regular linux distro (e.g. Ubuntu, Kubuntu or Ubuntu Mate) from ISO file and follow this guide to install INDI/KStars.
I'm sure one day you will appreciate this weird terminal window and level of control it gives you. You need to get used to permission model though