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

Hello,

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?

Just pushed a pull request up, and updated to version 1.8. No new features, but it does fix a delay issue for fork mounts.

It also changed the mount type to be an enum, because that seemed a bit more readable, and has a few incomplete things for looking at the PEC recorded values.

As I look at the PEC values, it strikes me, that everything using a ms value derived from an ancient interface is silly, as opposed to sending it in arc-seconds, or fractions thereof.

It is a known issue, and has to do with the timeout.
For an unrelated, but similar API, I had to issue a connect before sending every command.

James Lancaster is working on it, and his latest status update is here

onstep.groups.io/g/main/message/12653

The master branch of OnStep (version 3.0h) now has support for communicating with it over WiFi.

If your controller has a WiFi module, you need to re-flash that module with the WiFi-Bluetooth addon from the above version.

The difference is that you use port 9998, but keep using 9999 for the Android App as usual.
For INDI, you can change that under the Connect tab.

This was tested with Stellarium Mobile Plus and found to be working.

More detail here .

James / Alain,

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

Since I haven't updated in a bit. I fixed a bug yesterday not allowing to set the slew rate, should be in the next release.

Port 9998 has worked for quite a while.

As far as the focuser, I haven't implmented it yet. I did get into the habit of using 1 micron = 1 step in Config.h. I'd like to not break it for anyone potentially using it, but I need to refresh myself on the focuser. I'll probably let it toggle.

Couple of things on my todo list (numbered for convenience, not priority):

1. Changing the MaxRate replacement (degrees per sec)
Question on this: Would people prefer a settable 50-200%, as Degrees per sec, or the 50,75, 100, 150, 200%?
2. Intervolometer support
(Might be a priority, simply because I have some D5100s, and if I could trigger them as well as the main one in Ekos, that'd be handy until the Ekos/Kstars Imaging train gets done.)
3. Focuser Changes
4. Dew heater
5. Weather support. (Read BME280/etc)
6. Tangent arm support (Plate solve then adjust?)
7. Check backlash values (Changed to allowed to 3600)
8. DC Focuser support (Not sure if that works already or not?) Might need someone who has one to help with this.
9. TMC_SPI reporting support. (I got one for testing, and finally went to put it in on this cloudy night. I unfortunately missed the: You have to have both axis be SPI if one is, so this will be working at some point, but when is a big question. Oops.)
10. Equivalent of MoveAxis support to allow for following satellites. (Kstars issue more likely than OnStep directly, as the custom rates are added in, but Kstars doesn't have a way to send the rates/information, AFAIK)

Anything anyone else wants?

Would love the weather support

Thanks in any case!

Joachim

I've entered this thread to report a problem with the Slew rate... and I see that is fixed right now (but not available yet for macOS users) . Any way, very happy to see that the driver is not dead

I've another question. I'm still building my OnStep system (soldering, waiting for some components to arrive, etc). Mean while I've built a prototype with a Mega board and one small 28BYJ-48 motor to see movement. Gotos speeds are reasonable, change slew rata didn't work, and I don't know if this is related, changing the speed at witch the polar assistant rotates the mount neither work. If you go to the polar assistant and star it, the 30deg slew is performed at very low speed, aside of the one that you have chosen in the combo.

Regards

Added to the latest master. It's read only though, and I need to look into the dew heaters, and for the BMP280 I have, add support for changing the values (and useful for a heater for anyone who doesn't have a weather sensor, or maybe I can pull that from others.)

Please let me know if anything is broken. (I don't think so, but well it can happen.)

rbarberac: That should be fixed with OnStep unless I misread conversations?

Yes it's fixed on OnStep 4.X versions

Awesome, I will check it out.

And what you say about also making it possible to set the Onstep weather data from INDI or some other connected device makes perfect sense to me!