OnStep group 1. I, Howard Dutton, established this group to share information about OnStep Telescope Controller and its use. These rules are here to keep things courteous and on-topic - and to keep scammers and spammers out... 2. Discussion of any topic not related to OnStep and its subsystems and/or use such as data/images generated with the help of OnStep, is prohibited. 3. Registering to use this group under a false name or for false pretenses is prohibited. Please include a first name when setting up your account, not just your email. It helps to identify who we are addressing and promotes a friendlier atmosphere. 4. Before asking a question, read the relevant *Wiki ( https://groups.io/g/onstep/wiki/home )* sections (aka read the manual.) 5. When asking a question, first provide background on the hardware and software including version info. and configuration/settings, be methodical. Describe what you are trying to do, the steps you took, what you expected, and what happened instead. 6. Excessively vague posts are more likely to go unanswered for fear of the time/effort required to obtain the above information and figure out the problem. 7. More experienced users are encouraged to help beginners. 8. When uploading images, please try to minimize their size as they end up in the e-mail boxes of many people. If you can, upload the images somewhere (e.g. imgur, Google Photos, Flickr) and post a link to it - especially for large images. 9. Try to avoid repeatedly editing messages, since each edit sends the new message to all members. * * 10. Moderators will not allow posts that are rude, uncivil, belittling, derogatory, or discourteous. Members who post such messages are subject to being banned from the group. 11. Advertisements for commercial products or services must first be approved by the group owner, these requests may be approved or denied for any reason the group owner sees fit. Members who choose to make mention of products or services when approval is denied are subject to being banned from the group. Note that this provision should not be taken as an endorsement of any product or service mentioned in this group. 12. The moderators reserve the right to edit, modify or delete any post they deem a violation of these rules. 13. If you have a question or complaint about a specific post, notify a moderator. 14. The group owner (Howard Dutton) may modify these terms of service without notice.

Just a reminder that OnStep sub groups exist relating to Developer Talk and the Observatory Control System (OCS.)

This is a notice to STM32 who are building new controllers, or users who upgrade their OnStep firmware. Several users reported an issue where the WeMos D1 mini WiFi would not connect to OnStep. The problem was traced to a recent (Dec 26, 2019) change ( https://github.com/rogerclarkmelbourne/Arduino_STM32/commit/0c580b988a21ce365c89b90a08cb1407b4dcdf57 ) to the Arduino_STM32 which changed the mapping of serial ports. The result is the problem reported. The solution is to upgrade to OnStep. Which versions depends on your use case: * If you are building a new controller, or upgrading from previous versions to the latest 3.x, then use the latest OnStep 3.x ( https://github.com/hjd1964/OnStep/archive/release-3.16.zip ) (which must be OnStep 3.15e or later) as well as the latest Arduino_STM32 master ( https://github.com/rogerclarkmelbourne/Arduino_STM32/archive/master.zip ). * If you are using an older version of OnStep and prefer to stay on it, then you need to upgrade to the latest OnStep 2.22q ( https://github.com/hjd1964/OnStep/archive/release-2.22.zip ) as well as the as the latest Arduino_STM32 master ( https://github.com/rogerclarkmelbourne/Arduino_STM32/archive/master.zip ) too. In either case, no Config.h parameters are needed. If you still have problems, post on the OnStep group for help.

The *master* branch has some low level changes to the motor timer code design. These changes bring more consistency across the various platforms supported and in some cases a very slight performance (timer accuracy) improvement under certain circumstances. This is critical code and while I (and Khalid in the case of STM32) did basic tests on all platforms, except the Teensy4.0, there is always the possibility something might not work correctly. So please test carefully and report any changes in behavior. For comparison tests or those who want a bit more stability I spun off a *beta* branch just before this change for your use until this new code is better proven.