# Dell Wysee 5070
The 5070 is a pretty good StellarmateX device. It it more modern than the M93p ThinkCentre
Sorry, but still working. I thougth, this was my fault editing or a problem with the browser. Also it is very annoying, that the editor changes
<blockquote>="Axel post=93342 userid=4376"] 1. INDILib, and it's dependencies ... To build libindi from source see instructions on indilib.org"
What does that mean? Do I have to recompile the hole INDI (with make install) or just need to install the dependencies in Linux (which did lead to the error on compiling "indi_arduino_cap":
Yes I have to
Then I got
-- Found INDI-DRIVERS: /usr/lib/x86_64-linux-gnu/libindidriver.so -- Configuring done -- Generating done -- Build files have been written to: /myProjectpath/build/indi_arduino_cap
I like to reopen this because I like to implement this with "Indi Arduino Cap" (github.com/magnue/indi_arduino_cap ). Did anybody have success in compiling get this running with an Arduino (not with Raspberry PI!)? This is from the same author like "Servoblaster". Unfortunately the instrucions on the Github page how to compile things are very, let's say rudimentary.
Therefore some dump questions on the instructions there.
The Readme says, I have to install dependencies:
CMake Error at cmake_modules/FindINDIDriver.cmake:43 (message): INDI-DRIVERS not found! Call Stack (most recent call first): CMakeLists.txt:17 (FIND_PACKAGE)
Please be careful posting such a solution The given architecture is MANDATORY for the porblem! you cannot simply combine 32 and 64bit programms.
You get the info this way:
stellarmate@stellarmate:~ $ uname -m aarch64
Tested on Linux Client (Kstars on Linux PC):
Works a little more convenient. No problem with the format, but with directory. Also here the "local" directory anf format setting applies like set for the Stellarmate device which assumes there is a directory /home/stellarmate (which I don't dare to change, to mix things up):
- had to create the directory /home/stellarmate/Pictures and /home/stellarmate/Videos
- set access rights, so the PC client user can read the directory
chown -R myuser:myuser /home/stellarmate
I deattached the WIndows KStars sessionf from StellarmateX (deconnect). I then stopped the active EKOS profile and restarted. And voilá: the settings are back and working.
Conclusion / question:
I am sure, Jasem did the correct job, because this behavior seems to be intended. Choose to work with the client Program: upload to client. Or choose to work with Stellarmate via VNC plus Smate app only (!): upload to the Smate device. I know, there is EKOS-Live for a partly solution without using VNC, but:
1. Should it not be possible to distinguish the path of the local and the remote device.
2. KStars and EKOS is a platform independent Client/Server program, so it should be possible to connect a Client and choose to save to the StellarmateX device to avoid traffic. This is not possible in the moment (did not test on Linux).
Most likely, I do not see the point in the Stellarmate universe and are wrong
I give myself a coffee pause. Probably I'll find a solution ...
I altered the "Upload" settings to "Both". In Indi, in EKOS. On the Client (KStars on PC) and in StellarmateX (VNC).
This lead to strange Upload behaviour on the StellarnateX device:
StellarmateX - error on file format settings
yesterday, I installed my first StellarmateX on a Lenovo M99p ThinkCentre Thin Client .
What I did: I also have a Pi. I liked to preserve my settings and like always I started the system, stopped KStars on the new StellarmateX installation. Then I copied with
rsync -av --delete local_dir remotepc:remote_dir