Oh.. Found solution -
It involves switching from GDM3 authorization to LightDM but works...
Now I am to install kstars/ekos
Got the Miniforum Mini PC. Installed Ubuntu 18.04, configured network, etc.
Now I am stuck with VNC autostart.
X11vnc works fine when started manually but wouldn't autostart (I followed your link for instructions).
I am getting "xauth: unable to generate an authority file name" when I run [systemctl status x11vnc].
There are thread about this on inet but I was unable to fix.
wvreeven wrote: For a VNC server I used to use vino, which is the Gnome standard VNC server but it is quite hard to properly configure in Ubuntu Mate. So I switched to x11vnc which works very well for me. I used this tutorial for how to set it up:
except for Step 5 (Setup AutoStart on Boot) which I replaced with the instructions given by the user "Casey" in the third comment dated January 8, 2019 at 1:55 am.
For a VNC client on both my MacBook and iPad I use RealVNC which connects to x11vnc perfectly OK.
Really? I am going to receive a Z83-F Minisforum tomorrow. Bought it on an impulse.. Soon after realized that it wouldn't boot without a monitor. There are also reports about wifi issues...
Should I keep it?
I am debating between this one and odroid-n2 and RockPro64.
Which one to go with? Odroid-n2 is the newest one... Is it better?
wvreeven wrote: By the way, with the latest BIOS the Z83-F doesn’t boot without an HDMI device connected. A simple cable will not do the trick so I bought a few cheap HDMI to VGA converters and that works. I filed a request for reversal of this change in the BIOS via the MinisForum support email address and they replied that their developers are looking into it.
A new BIOS was released two days ago which fixes the issue where the Z83-F wouldn't boot without an HDMI device connected
Look. It was failing with the simulators because the cameras were mis-assigned. Once the cameras assigned correctly - the procedure works. With the simulators.
The problem is - it doesn't work with the Windows client. Works with simulators but not with real setup. On Windows client.
Works fine on RPI/Ubuntu client.
And, no, you cannot test it indoors. You need to see/shoot Polaris.
NH - as I reported it works in simulation mode (after cameras are properly assigned) but doesn't with real cameras (at least I couldn't make it work)...
Also it works on RPI/Ubuntu client. The problem only exists for Windows client.
Sorry. It doesn't have anything to do with a web browser.
The client runs on Windows 7 64 bit. Server is on RPI which is wire-connected to my home network.
NH wrote: Do you use Microsoft Edge? I had connection issues and found out that INDI seems not to like Microsoft Edge. After changing the standard web browser, the connecting issues are solved. So if you use Microsoft Edge as standard web browser this could perhaps be the reason for your problems.
NH wrote: ...
I want further wanted to test the Polar Alignment with the simulators, but I cannot do that. I read somewhere that I have to install the GSC catalog (on StellarMate?). But how do I do that? If you can help my with this I can test this also.
Look here: www.indilib.org/forum/ekos/4569-download...mulator-on-os-x.html
Unfortunately, no... it didn't work with a real setup (not with simulators).
Two ZWO cameras.
Same symptom. "Refresh" in Polar Alignment wouldn't refresh.
Again - that's only for Windows client.
On RPI all works fine.
Really puzzled since nobody else is complaining.
knro wrote: The focus module has no scope selection... so I'm not exactly following here?
Jasem - please see attached
Wrong assignment in INDI control panel
Wrong assignment in INDI control panel
Refresh doesn't work
Once I change CCD in Focus Mode from Guide to CCD (or set options in INDI control panel to begin with),
Polar Alignment works.
Of course it was something simple (but it's kind of a bug).
Often, when INDI starts it assigns both Guide and CCD as Primary scopes.
I used to have all kinds of issues when this would happen.
So, I took a habit to check and correct for this on RPI but not so on the Windows client (since I rarely use it).
When this happens, the guide scope gets selected in the Focus Module by default and even though the Focus Module is not active this messes up the Refresh in the Polar Alignment.
If, in INDI control panel, I correctly assign guide to guide and CCD to primary then it doesn't matter what is selected in the Focus Module - Polar Alignment goes through.
I am glad I got it sorted out. Will test tomorrow for real (not with simulators).
Rob - you forgot the polar alignment... : ) (my setup is mobile, so I have to do this every time)
0. Level tripod, point scope to the North Pole as accurately as you can.
3. Go to Align module, Slew to a couple of stars in different parts of the sky and plate solve on them
3.1 Go to Align module, do Polar Alignment
3.2 Go to Align module and again slew to a couple of stars in different parts of the sky and plate solve on them
OK. Installed 1.4. Restored my KStars/Ekos configs.
All seems to be working except one thing that I noticed so far:
My mount shown as disconnected in Ekos.
Mount: SW AZ-Gti (EQMod).
Connection is over WiFi (AZ-GTi is in Station mode).
Looks like the mount cannot connect to SM's hotspot.
SM's hotspot is active and I can VNC to it.
Jasem - thanks!
Where the Tools place the backup?
knro wrote: Use StellarMate Tools application on the desktop to do backup/restore.
You can also save the directories you indicated above and restore them on the new machine. These are the most important ones.
Is there a way to transfer INDI/Ekos configs/settings from an older Stellarmate to a fresh install?