I already switched the country code to US, no luck. From what I'm reading, it's an opperating system issue - latest version no Raspian supports it. I thinking we may have to wait until a new release of Ubuntu Mate, and hope it's been addressed.
Thanks for your reply Jasem!
I'm running the Beta version of SM on a new RPi 4B, 4GB. So far it's working really well, connects to all my equipment perfectly and has been very stable. I testing the networking, trying to find the best/fastest connection possible. Obviously, the less extra gear I need and the fewer the cables, the better. I discovered that SM is only connecting with WIFI using wireless N at between 58 to 72Mbps. I have a wireless AC adapter on my laptop, and the RPi supports wireless AC, but refuses to connect using that protocol, only the slower N.
Is there a way to force SM to use 802.11ac for the fastest wireless networking?
FWIW, here are the three networking methods I've experimented with, all seem to work reliably while testing in my office:
1) Gigabit ethernet from SM to router, gigabit ethernet from router to laptop. 21MB images from my Canon T3i download in about 5 seconds.
2) Gigabit ehternet from SM to router, wireless AC from router to laptop (getting 433Mbps between router and laptop, downloading 21MB images takes about the same 5 seconds, maybe a fraction of a second slower.
3) Hotspot mode connecting completely wireless from SM to laptop, wireless N only (can't get SM to use 5Ghz AC) getting 58 to 72 Mbps, 21 MB images take about 10-11 seconds to download.
Stability has been the largest problem I've encountered with the Rpi3. Conneting two Rpi's distributed over ethernet using a dedicated router solved my stability problems. The Rpi's ran INDI, the laptop Kstars/Ekos, communicating to the SMs via WIFI. I agree, the RPi 4 should be able to do it all - but can it? I only control a mount, Canon DSLR and QHY guide cam.
Since ethernet proved for me to be far-and-away the most reliable, what do you think about connecting the SM over the gigabit ethernet, have it run everything, and control it via a laptop or tablet over WIFI using VNV, OR also connect the laptop using gigabit ethernet, run Kstars/Ekos on the laptop and enjoy blazing fast image downloads?
So many way this can be done... all part of the fun. I enjoy having all these possibilities to play with!
I just installed Stellarmate OS Beta on a new Raspberry Pi 4B, 4GB version - holy cow is this thing FAST - it's wonderful!!! Knowing there are multiple ways to connect to the SM, I wondering, in the ideal scenario, what's the best way to connect to SM and control my rig - since the RPi 4 is MUCH more powerful than the RPi 3B+ ?
1) Use SM in hotspot mode and have the SM run everything: INDI, Kstars/Ekos and connect to it for control using VNC from a laptop via WIFI.
2) Plug the SM into a router over gigabit ethernet, SM runs INDI, then run Kstars/Ekos on a laptop over WIFI - which is how I had been connecting since it proved to be the most stable.
3) Use a WIFI router, SM running everything, then using a laptop over WIFI, log into SM VNC from a web browser and control it that way? (This was the least stable method I found with the RPi 3B+.)
4) Use a WIFI router, SM running INDI only, then run Kstars/Ekos and connect using a laptop - everything over the WIFI.
Thoughts? Suggestions? Has anybody tested this yet?
I got it working. I can see "stellarmte" on my windows network and transfer files from the "pictures" directory on the stellamate RPi to my laptop PC, but not from my desktop - it does not see stellamate at all. Both are Win10 boxes. Weird.
How do you move images saved on my Stellarmate Rpi to my Windows 10 PC?
The images are located in home/stellarmate/pictures/lights
Linux noob so please forgive my ignorance.
In order to better learn Ekos, I've started using the Simulator. I'm running a CCD Sim, Telescope Sim and Guide sim - chosen in order to model the three pieces of equipment I actually own. The Camera module seems to work well, as does the Focus Module (without an auto-focuser, as I do not own an auto-focuser, but the Focus Module is still just as useful focusing manually). The Align module captures an image but the offline solving (I have the ANSVR catalog downloaded and installed and the server running) does not seem to work - it is pointed at 127.0.0.1:8080. In the Guide Module, autoguiding calibration is rejected with the report: "Star Drift is too short" which does not entirely surprise me since the guide image is the same every time and the stars of course never move, but then that begs the question: why have a Guide Simulator then? In short, only the Camera and Focus modules seem to work in Simulator mode. Is this normal, or am I doing something wrong/missing a piece to the puzzle?
I think I solved my problem and may have discovered a bug in the process: I had been using a one second mirror lock to prevent vibratrion with my Canon T3i/600D DSLR. If I set the mirror lock to 0, then the camera seems to consistently shoot the correct long exposure to whatever time I have the exposure set to. I do not believe this is how the system should work however, and appears to be a bug. Mirror lock is used to prevent vibration, which is why I'd prefer to use it.
I'm shooting with a Canon T3i. Camera is set to "M". In the INDI Control Panel, I have Force BULB set to ON. My configuration is saved and comes up the same every time I run Ekos. However, I'm finding that the Force Bulb is not being consistently applied. When it doesn't work, the camera shoots frames at an estimated .1 second exposure. I have to exit Kstars, re-launch and try it again. Then, sometimes that relaunch fixes it (with ZERO changes done be me), other times the camera still shoots at .1 second exposure. Any suggestions/help would be appreciated in permanently fixing this glitch (bug?). Rebooting the software until it works correctly is not a solution in my book.
SOLVED: Just as the others had said, I found that by changing the file permissions of: ~/.local/share/kstars/userdb.sqlite on each of my Rasberry PIs (I run two distributed) I am now able to save my hardware configurations. Here is the command syntax that was successful:
Open a MATE Terminal and type:
sudo chmod 644 ~/.local/share/kstars/userdb.sqlite (it will them ask you for the Stellarmate password, key it in and press enter. That's it, you're done!
To verify the permissions are set correctly, type in the following command in MATE Terminal:
ls -l ~/.local/share/kstars/userdb.sqlite
and just as wvreeven wrote, you should get:
-rw-r--r-- 1 ... etc..
This permission setting allows you to save your configurations once you change the settings in the INDI Control Panel Tab for your camera - AND ALSO - click on the SAVE button on the OPTIONS sub-tab/CONFIGURATION - if you don't click to save your config, nothing will be saved!!
I hope this info is helpful to others who my have run into this problem.
giorgio_ne wrote: Fantastic news!
I wasn't expecting a Pi 4 until next year. This new version will give performance to an already solid INDI/Ekos implementation on ARM and an even more enjoyable IoT solution for Astrophotography. I expect INDI/EKOS eventually to support planetary and solar imaging at some point.
Other interesting projects might now become a reality like for instance automated meteorite detection/mapping from an all sky camera... The sky is the limit!
You'd be far better served using a metal detector to find meteorites than a telescope with Stellarmate. Meteors are inbound and have not YET, but are about to hit Earth. Meteorites are the remnants of a meteor AFTER it hits Earth. Perhaps you meant asteroids - rocks in an orbit within our solar system?
Very, VERY interested in learning if and how well Stellarmate OS and Kstars/Ekos runs with the new PI 4. This is exactly the upgrade I've been waiting for - REALLY hope SM OS plays well with it. Also would be HUGE if we could now run Ekos smoothly on the PI instead of remotely - man would that be great!
...Eagerly awaiting news and reviews!