It broke, but mostly because I'd been messing with enough stuff that wasn't in master. Then the stupid spaces/tabs thing. (Which is now all spaces, but Gah that was annoying!)
As azwing is having fun with his internet (/s) I just bumped the OnStep version and submitted version 1.7, with the following changes, but likely some I may have forgotten, or missed going through commits.
- Added support for Reporting Guide rate (to PHD2 among others)
- Updated Error codes to match up with Android/SHC (Unknown reserved for unknown, so Unspecified = Unknown on other platforms)
- Added descriptions to SlewRate to match, slider kept which matches OnStep values
- Support for up to 9 stars for alignment
- Changed align so the last step isn't the (Optional) Write to EEPROM
- Added support for polar adjustments, without having to redo the entire model. (:MP# command)
- Support for Full Compensation/Refraction only, and 1/2 Axis tracking
I don't have the :Gu# settings done yet, or a few other things in progress, but I figured the above would be welcome by people. And gaffes about merging an old variable name aside, I think things have been fairly well tested.
Do you mean the text of the instructions change, or there is a functionality change somewhere? If the latter, please elaborate more.
If you have a polar alignment that has significant errors (say > 3'), and you do the RefinePA (:MP), then you are better off re-doing the polar alignment since your gotos will off if you don't.
So now we have a Single and Dual button next to each of Full and Refr?
One more thing: the units for the polar error in the Align tab are wrong. They are ' but should be ". I am sure I reported this to Alain way back when, and it was fixed. Perhaps overwritten by some other change.
Write align got set to Write Align to NVRAM/Flash (Actually should be EEPROM/Flash, but whatever, storage that doesn't go away with power!)
No, I did it a little differently, along with status, which shows Single Axis, 2-axis or N/A (If off)
See probably the first screenshot, Alain corrected this a while back. I don't think it got pushed up to the main one though. It's there now.
No problem, Open source is awesome.
Now if I can just find what the hell is with that bug in the alignment routine. (I've somewhat narrowed it down bringing out things like wireshark, but whatever the issue is, it seems to defy my finding it. Though I've narrowed it down some as to what gets called, but that shouldn't as far as I can tell. Somehow kstars thinks that the EqNP.s is busy when as per wireshark it's not, so it goes into the case of IPS_BUSY (== Slewing) when it's actually another status, but I don't see HOW. At least I know it's not the OnStep INDI driver side (or the INDI side, or the OnStep side... I think anyway ). )
Also: If anything breaks that was working before, PLEASE LET ME KNOW. There were a bunch of stupid spacing things that git decided a whole function constituted a change, some of which had actual changes in them, and I think I decoupled the spacing changes from actual changes, but... I'm only human, and a little bit more persistent than git.
For me, any of the automated methods work in a very short amount of time. (When playing with it, I've tried to find an option that would take a while, but everything from grid to named stars seems to populate pretty much instantly for me. The only thing I have to sometimes check for is where I have trees. In which case, I can just generate say 8 when I want 6, and kill those too far NW, or use a higher altitude.
In any case, I did some local testing and 17/25 hit it. However, I did test a timer, and that worked great to mask whatever is causing the issue, and while reporting that, had an idea which should mask it fairly easily. (Provided Settle Time > polling time) Still haven't found the cause, but maybe a bandage will get to kstars relatively soon?
I believe since it's in INDI master, it should be in Jasem's PPA.
Yep. I added a .katesettings (I think that's the name) with the tab settings. Actually that might be worth pushing up to INDI master. (Doesn't solve it for all editors, but... (Hrm, a standard for that that all editors look at would be great.))
I have an install of INDI 1.8.0 built from source on a Raspberry Pi. I have OnStep installed onto an STM32 Blue Pill based PCB. I connect the RPi to the STM32 via WiFi link, which works fine.
Loading Kstars and opening Ekos I can connect, over wifi, to indiserver using the Ethernet method.
However, after the initial connect there is no further data exchange, no control works and I can't slew the scope at all. I have posted to the OnStep group (onstep.groups.io/g/main/topic/32712176#12458) and others have similar results. I can get the scope to run fine by connecting the STM32 pcb to the RPi via USB.
Is there something I am missing in the configuration, or does it simply not work yet?
Version 3.x of OnStep (which is 'master' in Github), has a new way for configuration which is much easier than before. Instead of one Config file for each board, there is a unified Config.h file.
It also has support for a persistent command channel on port 9998, which can make OnStep work over WiFi. Previously, port 9999 does not work because it times out after 2 seconds and closes the connection. The new port needs to be tested.
Another change is in how the focuser works, with new commands. Details in