I use that driver modified to suit my home modified ZWO manual filter wheel, I use a small 4 wire stepper & a DRV 8825 stepper driver board with a Hall Effect Switch that I had originally developed for an ASCOM setup. I just reprogrammed the Arduino to use the sketch modified to suit my home tweaked filter wheel based on the XAGYL protocol works faultlessly, with the indi XAGYL driver, just make sure the capacitor modification to the reset pin on the Arduino is fitted and you’ll have no issues.
I would use the home WiFi initially, the hotspot on the Pi4 can be a bit weak at times.
To get it all working and ensure good connectivity in the first instance use a network cable if you have one direct to the modem router, then switch to the home WiFi once you have it working as it should. Take it a step at a time and you shouldn’t have any great issues
From my experiments with the hotspot on the Pi4 it appears to work best when there’s no other WiFi signals about for example in the middle of a field.
Install Real VNC Viewer on the Windows machine, connect the Pi to your home network and run everything on the Pi4 it is more than capable. You can also put Real VNC Viewer on your phone or tablet & monitor the progress there if you like.
I personally found that the guiding performance wasn’t as good when using it as a server client set up due to lag over the network, unless I ran PHD2 directly on the Pi via the ST4 cable. But that’s a bit of extra work to start PHD2 before you connect the server, again this can be done over VNC if needed.
I found I don’t need a static IP on the network just use the address shown in the Stellarmate tutorial video Stellarmate.local I think from memory.
At least doing it this way you’ll get results.
Try it first with the simulators, then connect the other equipment 1 item at a time and make sure it works before saving the configuration, then shutting down and restarting the Pi before connecting the next item. Doing things this way helps isolate problems with an individual piece of kit.
I can understand your frustration, I used Ascom and when I first started with Indi & KStars I struggled, especially with the Linux side of things getting all the USB ports set so they didn’t fight over their port numbers at every startup, but I like the all in one place set up so I stuck with it. Now my Pi4 mounts on the scope outside and I sit in the warm house and monitor the progress over VNC.
Stick with it it does work.
I’m sure that Stellarmate will do it’s thing when you get it sorted, this forum & Google will get it working that’s how I achieved it.
Try this, It works well, read the instructions carefully and give it a go
It's what I and a lot of other people on this forum use with a raspberry Pi 3B+ or Pi4. It takes a while for the initial set up but works fine over VNC or via Indi web manager.
Get a 32Gb class 10 SD card flash on the operating system (use Raspbian if you are using a Pi4 or Ubuntu Mate for a Pi3B+) connect the internet, monitor, mouse & keyboard to the Pi then follow the instructions and run the correct script from terminal.
Works every time for me.
Ray, have you tried the MyFocuserPro2 driver it uses Arduino, has backlash compensation a recent Indi driver was written by Alan. I’ve tried it on an MyFocuserPro2 I built a while back for use on ASCOM I just updated the firmware to version v291 and it works I believe there may be a version v292 by now there’s a long thread on here about it
Success I’ve just ran the script on a fresh install of Raspbian Buster and it’s all working fine, all cameras, mounts, focuses, filter wheels are there & no crashing on starting Ekos.
Well done, many thanks
Re-ran the script and all the cameras display in the drop down menu and can be selected, but trying to start Ekos results in a crash and Indiserver is left still running in the background. Restarting KStars allows you to set up Ekos again, but when trying to start Ekos there is a warning about Indiserver running and it asks if you wish to close, as soon as you try to close the Indiserver it crashes KStars again.
see below the error message from the cmake command
CMake Error at CMakeLists.txt:364 (add_subdirectory):
add_subdirectory given source "asi-common" which is not an existing
CMake Error at cmake_modules/FindASI.cmake:68 (message):
ASI not found. Please install libasi www.indilib.org
Call Stack (most recent call first):
-- Configuring incomplete, errors occurred!
See also "/home/pi/AstroRoot/indi-build/3rdparty-Drivers/CMakeFiles/CMakeOutput.log".
See also "/home/pi/AstroRoot/indi-build/3rdparty-Drivers/CMakeFiles/CMakeError.log".
I've just looked in the indi-build / 3rdparty-drivers and there's no manifest.txt screen dump attached