Axel replied to the topic 'StellarmateX on ThinClients' in the forum. 2 months ago

# Dell Wysee 5070

The 5070 is a pretty good StellarmateX device. It it more modern than the M93p ThinkCentre



- NVME support (I use a 1 TB Western Digital Red)
- PC 2400T RAM (speedy) up to 32GB
- one USB-C at the front
- general more USB-ports

There is a Pentium and a Celeron version.

The only thing: I had to manually reset the BIOS pass, which is sonde with a jumper on the motherboard. Then I could alter BIOS settings. Read here: www.parkytowers.me.uk/thin/wyse/5070/firmware.shtml
Installation of StellarmatX went flawlessly. Nothing more to say.

You will find easily manuals (e.g. here: thinclientspecialist.de/media/pdf/30/23/...eet1Wf2AJzkcYg2o.pdf)

Cheers, Axel

Read More...

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

[b]
to
<strong>
and also and [code] which is very problematic on editing the code again. I hope, this can be fixed ...

Having faith :-)

Read More...

Axel replied to the topic 'Automated Flat Panel Control' in the forum. 4 months ago

<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":
</blockquote>

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

Then I can install the driver there with <sudo make install>.

Problem no 1 solved :-)

Conclusion: one more sentence like "You need to install the dependencies to compile INDI like described in <link as described in Readme> and compile it (!) with <make install>. This puts the necessary Indi driver libindidriver.so into the appropriate library directory of you linux environment so you are able to compile the Indi driver Indi_arduino_cap".

Read More...

Axel replied to the topic 'Automated Flat Panel Control' in the forum. 4 months ago

Hi there,

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:

  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: "
    CMake Error at cmake_modules/FindINDIDriver.cmake:43 (message):
      INDI-DRIVERS not found!
    Call Stack (most recent call first):
      CMakeLists.txt:17 (FIND_PACKAGE)
  2. PyFirmata, and it's dependencies...To install PyFirmata see this page on pypi.org
    There are two ways of installing PyFirmata: I used pip. Is this enough?
  3. How do I install PyFirmata on the Arduino. The homepage github.com/firmata/arduino says "There are two main models of usage of Firmata. In one model, the author of the Arduino sketch uses the various methods provided by the Firmata library to selectively send and receive data between the Arduino device and the software running on the host computer"
    Which method to use in this context?
Why do I have to make a "$ sudo make install" for this. Does this compile the Indi driver?[/]
  • Wiring: there is utterly no wirering design. I am a little bit los, on how to wire the Servo to the Arduino.
  • Same is for USB2Relay


  • Thanks for any contribution to my questions. I know, they are a little dumb. Unfortunately, programmers tend to be very short in context explanations, which is not very helpful in this case.

    3D Print is not the problem, but get the essentials up and running. I also do not have any problems on getting things compiled on Linux. But I do not understand how to use the dependencies in this context.

    Cheers, Axel

    Read More...

    Axel replied to the topic 'FireCapture on SM OS' in the forum. 4 months ago


    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

    So my stellarmate is 64bit (and all software components, inkluding java too.

    FC actually on ARM is 32bit only !!! So any software, that FC uses, like JAVA, has to be 32bit. Therefor the "lot of code" which installs the 32bit version of Java inside a 64bit system.

    That's for clarification..
    Cheers, Axel

    Read More...

    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
    - went to my home directory, and created a folder "Stellarmate". Symlink the "SM-Home Pictures and Video" directory there.
    - Tipp/Idea: create the Pictures and Video folder within my Nexcloud (or you can use whatever Cloud you are using). Then symlinked with in the /home/stellarmate directory to this cloud folders. Then everything is automatically synched to the cloud (if you have enough space, like a big "Pcloud" device (400 € live time for 2TB), this is the way to go.

    Read More...

    Take 03

    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 ...

    Cheers, Axel

    Read More...

    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:



    Read More...

    StellarmateX - error on file format settings



    Hi there,

    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
    the following directories to the new device (yes, made a backup of the old dir :-)
    • .indi
    • .ZWO
    • .local/share/kstars
    • .config/kstars*

    Then I rebooted the device. Everything came up like expected. I could use my settings, had my profiles there and so on. So far so good.

    Then I started a local KStars session on my PC (not the StellarmateX!).
    1. I configured a named profile with EKOS with the same settings like in SmateX
    2. I configured the profile in the INDi profile manger and deselected "Auto connect"
    3. I also configured KStars to not connect on startup

    What happens: immediately after opening the connection, within the Indi settings for my camera the Upload section switches from "Local" to "Client" and switches my "Dir" to the Windows-Path of my local PC.



    I'll investigate and try with upload setting "(upload to) Both". We will see ... this worked in the past on the Pi.

    Cheers, Axel

    Read More...

    Axel replied to the topic 'Kstars 3.4.6 autofocus issue' in the forum. 4 months ago


    Take a look into your Filter settings. I encountered yesterday evening, the same problem. The "last AF Solution" had been used from filter settings.



    Probably this helps.
    Cheers, Axel

    Read More...