Thanks for the offer of help if I get stuck.
I did indeed get stuck when doing the last part - making the rolloffino driver.
I will give it another try and post the errors. Not able to do it this morning.
It might well have to do with building on a system that does not have KStars installed. The last part is the install which includes making the driver available in the Ekos profile.
I went through the INSTALL directions on a somewhat clean machine, but it was a odroid rather than a Rpi. I did encounter a problem since last used.
At the start referring to the external indi howto web page. It is missing the clone of the 3rdparty drivers. So now
there should be a line "Section 4. Work down to and including the clone of the 3rdparty drivers. No need to do the build." After that it worked through okay.
If you got down to the `sudo make install` which is where you encountered the error. Then instead of that command try simply `make -j4` which will omit the actual install and leave the executable in the local directory.
Mach1, TS86SDQ, ASI071, ASI174, OAG, focusPro
Last edit: 1 year 3 months ago by wotalota. Reason: added info
I have started fresh.
I think I have done a bit better this time.
However I am getting a different error, that seems to be pointing to the CMakeLists.txt file.
I have attached the terminal details and the CMakeOutput.log files.
Edit: I have also added the CMakeLists.txt file
Krish,We might not have the directory files placed and the defaults set to the expected place.
Before running the cmake command. Check that the following things are true.
libindi-dev is in fact installed.
In the ~/Projects there are 2 directories that have been populated "indi" and "indi_3rdparty".
In ~Project/indi_3rdparty/indi-rolloffino/ are the files from wotalota github.
Your default directory is ~Project/indi_3rdparty/indi-rolloffino/build
I made some edits to the INSTALL file, not checked in yet, to try and be more explicit. Take a look and see if it helps.
I'm replacing the readme file with one with examples and more detail about the Arduino sketch. Will attach after getting through a first pass. Any suggestions to improve and additions that would help getting started are appreciated.
Hello Tom & Jasem
I have managed to get there. I can now see RollOffino in Ekos on Stellarmate on my RPi.
I found that a "build" directory was created in the "Projects" when building the Indi portion of the process. I had to use that "build" directory for the cmake of the Indi-rolloffino.
The command had to be: $ cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ~/Projects/indi-3rdparty/indi-rolloffino
Now to get the Arduino and Ekos to play. I think I have a connection but not quite the relay control and sensor inputs yet.
Thanks again for all the help you guys have provided.
That is the same directory that the ../ was supposed to point to. So your tree and default working directory is something different than expected. But make a note of how you got it working for the next time.
Look at the INDI window for the roof driver main tab. It will indicate if it is connected or not. The buttons and status lights will show what switches it has detected as closed. Using the park unpark buttons will try to activate relays.
What code are you running on the Arduino and what kind of roof control do you have or intend to get. Are you presently working using a bench breadboard kind of setup?
I do have a connection. I see it in Indi Control panel.
I am using the Arduino with a relay board and sensors connected testing on the bench.
One relay for open another for close and 2 sensors for open and close.
I am using the rolloffino.standard file for the Arduino. That seems the closes match for what I have for testing.
I did manage to see some action on the Arduino today. I set the sensors as expected and Indi sees it as well.
If I hit the open or closed buttons in Indi I see the corresponding relay come on but then the Indi driver Rolloffino crashes and a few seconds later Kstars crashes.
I have attached a zipped folder with log files.
You indicated that I should be able to use the same process from the HOWTO: Building latest libindi and Ekos on a macOS.
I tried that and get a message: "sudo: apt-get: command not found".
Do you perhaps know what I may be doing wrong.
On the MacOS. There is a good chance that the driver code will work on the Mac, but it will need to be built and installed according to Mac procedures. The present directions in the INSTALL file did not include any thought given to how that is done. For example the apt-get is a Ubuntu specific command. I did get a Mac but since you said it was the RPI4 you were going to use I have not done anything with it. If you intend to run a Mac in the observatory I can spend more time learning how to use it.
The files you posted appear to be the rolloff debug logs or fragments of, just showing the commands and results, most ending in timeouts. Was one of them in particular associated with the crash?
Do you have the KStars log associated with the crash? Did Kstars put up a message indicating the driver had crashed?
The only time I have had the driver crash was when the version of indi / Kstars it was built against was different from the one installed. Although that always happened when starting. If the version you built against in the ~/Projects tree was the one that was cloned into ~/Projects/indi then it would have been the nightly build.
The Kstars and indi versions running for the testing should be from a nightly or the current stable release since I have been using the driver on those and perhaps the previous release without a rebuild.
[ Edit ] Working with a breadboard you might be using the command buttons and receiving response with much different patterns and frequency than the normal open or close roof while waiting without requesting other actions going on. So if you encounter a particular button or sequence of steps that can cause the crash it will be helpful in looking for the weakness in the drivers handling of them that results in a crash.