To run two Stellarmates at remote site, Werper's approach of setting up a router and running them both on single wifi network sounds good (but its yet another piece of equipment to manage).
Did it work?
Is this still the best solution?
Issue resolved. Just needed to set DST to 'no' on mount. Thank Jasem for this simple fix. It resolved meridian flip offset too. No sure, but I guess even though "KStar Updates All Devices" was set, the mount setting was active and maybe effectively double counted the DST offset.
I'm running Kstars/Ekos on Mac, using StellarMate and Ioptron CEM60. I have issue that, after initial power up of all hardware and software, the very first GoTo is off by 1hour(angular), meaning I try to go to some location, then plate solve and always astrometry needs to correct mount RA by about 1 hour. After that correction, its ok for remainder of session, but I want to fix this initial problem. What am I doing wrong??
KStars Geography set up is correct (use 'San Jose' built-in location), DST is US is correct(now), the LT and UT time is correct on KStar left corner display, and INDI config get for "KStar Updates All Devices". I get impression something wrong with way DST is handled, but I can't pin it down. I have played with mount hand controller setting of time/UT/DST, but it doesn't seem to help(I think), and I assume with "KStar Updates All Devices" setting, it doesn't matter. Maybe the updating doesn't execute properly?
(Also, not sure this is important, but seems KStar and Ioptron use opposite convention for displaying UT Offset. While Jasem informs me Sktar UT offset setting is independent of DST (so should be -8 for San Jose,CA/Pacific Standard Time, regardless of DST or not), but Ioptron tells me on their controller, one inputs DST first, then HC displays UT offset relative to actual current local time, so it shows UT offset of -7 (during DST).)
Does anyone know the HASH# for stellarmate OS file "StellarMateOS_1.4.3_rpi3.img.xz" . ?
I can't find it on the SM site.
What is the correct way to tell Ekos the telescope is at its home position, when Ekos/KStar incorrectly thinks scope is not at its home position? Somehow Ekos got confused, and I wasn't clear how to reset it. Rebooting everything didn't help. Upon reboot, and reset of scope to home position manually, Kstars thinks the scope was somewhere far from Polaris. I tried PURGING DATA for park position on SiteManagement tab of the MOUNT in INDI Control Panel, but message said there was nothing to purge. The only thing I could do was have Ekos issue a "Park" command, let scope slew to the position Ekos thought was home, then after the slewing stopped, reset the scope so it in fact was at the home position (scope is iOptronCEM60, so this just involves disengaging clutches and swinging scope to true home position). But this is tedious and unreasonable. What's the correct way to do this?
The Ekos MOunt Module 'SYNC' command I assume does n't help here, as I assume it tells the mount where Ekos thinks the scope is pointing, but scope is not pointing there.
When I connect ethernet cable, there is no indication that its connected to SM. Capture file transfers are just as slow, like if still on wifi. Info button on Web Manager does not ever show an additional ethernet IP (like you show on web site). Here is what I get - there is nothing below 'wlan' listing:
terminal command 'arp -a' comes back with a reasonable IP address(and even the label 'stellarmate....') as follows:
stellarmategag3.local (169.254.7.73) at b8:27:eb:3d:db:8 on en7 [ethernet]
But if then I ping that IP, I get timeouts, as follows.
MyLaptop:~ xxxxxxxx$ ping 169.254.7.73
PING 169.254.7.73 (169.254.7.73): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Also, trying to use Web Manager with 'http://169.254.7.73:8624/' cannot connect.
I got it. Hotspot is back.
I don't exactly understand it, but here is what happened. I took down house wifi. THEN the SM hotspot appeared in wifi pulldown menu available networks. It needed a password (perhaps as I hadn't logged in since I did factory reset on SM network ), I gave PW, and now hotspot is fine. And now when I go back to house wifi, the Stellarmate hotspot still appears as available wifi network. Its odd, because before I had to log into stellarmate hotspot to do initial setup(after factory reset)? Also, before this fix, I would do a explicit search for wifi network by it's name 'stellarmate', and it was nowhere to be found. ?? Anyway, its ok now.
...My next issue is to to get ethernet working.
I lost StellarMate hot spot, ie it doesn't appear as selectable wifi network. I can connect to SM and operate in house wifi mode fine. I can VNC and and use web manager, but cannot operate in hotspot mode.
Pinging 10.250.250.1 comes back with destination not reachable.
I tried some SSH commands Jasem listed:
- comes back with time out.
- succeeds in getting access, but I assume this is thru house wifi network?
Help. At a minimum, in the field, I need to have hotspot mode working.
I didn't intentionally change these setting, but are they correct?
Apart from using the scheduler, is there a way to have Ekos do an alignment, say every 60minutes, during a capture sequence?
I see the option to refocus every xx minutes. How about realign/plate solve every xx minutes??
I had offline aligning working fine before last week's updates. Now its not working. Basically it bombs immediately after getting first image. Prob some simple config detail is incorrect. ?? Index files are there from my prior Kstars, FOV is correct, and otherwise I'm using the default settings. Online aligning works fine. Other detail is that I did factory reset on Stellarmate Saturday night (a few nights ago), and reran SM updater. I have Kstars 3.1.1 now (but 3.1.0 had same issue). When loading new version of Kstars, are there some pointers that need to be changed?
The message window messages are pasted below.
(Sorry, I tried to get log file too, with astrometry debug enabled, but time stamps on log file don't make sense to me, doesn't seem to be opening a fresh log file - I'll omit it now. It you really need it, let me know. I'll try again.)
2019-03-12T22:19:52 Solver failed. Try again.
2019-03-12T22:19:51 Reading input file 1 of 1: "/private/var/folders/_8/gnwd575x7c96v7ms30ckkzqh0000gn/T/fitszxCmqH.fits"...
2019-03-12T22:19:51 /Applications/kstars 3.app/Contents/MacOS/astrometry/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -L 26.505 -H 38.85 -u aw -3 89.0424 -4 7.40641 -5 30 --config /Applications/kstars 3.app/Contents/MacOS/astrometry/bin/astrometry.cfg -W /private/var/folders/_8/gnwd575x7c96v7ms30ckkzqh0000gn/T/solution.wcs /private/var/folders/_8/gnwd575x7c96v7ms30ckkzqh0000gn/T/fitszxCmqH.fits
2019-03-12T22:19:51 Starting solver...
2019-03-12T22:19:51 export PYTHONPATH=/Applications/kstars 3.app/Contents/MacOS/python/bin/site-packages
2019-03-12T22:19:51 export PATH=/Applications/kstars 3.app/Contents/MacOS/netpbm/bin:/Applications/kstars 3.app/Contents/MacOS/python/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
2019-03-12T22:19:51 Solver iteration #1
2019-03-12T22:19:51 Image received.
2019-03-12T22:19:41 Capturing image...
Yeh - it seems to be working !! Great - thanks. For unrelated reasons, I had to do a factory reset on SM last night. So I ran the updater last night after the reset, and now focuser seems to be working. At least Min=0 and Max=60, and I can move focuser inward and outward. Great !!
Still there is some points of confusion, ie why Celestron Utility claims my Min~2000 and Max ~ 37000, and how they relates to SM values of 0 and 60000. Maybe Celestron original values are in some raw units, and the 0-60000 units SM reports are renormalized units ? Later I can test if stellarmate can really reach beyond 37000.
Other item I couldn't figure - how do you copy and paste to MATE terminal (from Mac)? I tried various command/control/shift C/V combos, and none worked. Do you run SSH?
Chris - what recommended way to copy and paste from mac to SM Mate terminal ( in order to do the build)? (I'm using VNC thru browser.)
Thanks. Ok, just so I understand the process, to install from source, is the following correct?
From the 'MATE Terminal' in Stellarmate, I need to run this:
sudo apt-get install libnova-dev libcfitsio-dev libusb-1.0-0-dev zlib1g-dev libgsl-dev build-essential cmake git libjpeg-dev libcurl4-gnutls-dev libtiff-dev libfftw3-dev
git clone github.com/indilib/indi.git
mkdir -p build/libindi
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ../../libindi
sudo make install
Is that correct?
Or some how I can get only the focus drivers from indi/libindi/drivers/focuser/ . ?
Thanks. The 2nd version I sent yesterday was directly after calibration, and yes it was completed; after running calibration, utility flashed 'Calibration Completed'.
You say I should 'rebuild (driver) from sources'? Newbie issue: Is it obvious how to do this, or will I need some instructions? (sorry, not in front of hardware now, will need to try it later to night.)
You say "...new version of the sources released that will check the limits and only update them if ...": is this all the new source does thats new? Anyway, I can try.
Fyi, the stellarmateOS was updated just 2-3nights ago by running 'software updater' on Stellarmate 'desktop' (ie as seen in VNC).