Date   

WEMOS Module

Robert Benward
 

After setting the serial port to default 57600 ( a suggestion in the wiki) in both the ESP32 and the WEMOS, I finally got it working, to a point.  I turn on the controller, the blue light goes steady, the SHC is working, The RTC seems to be working,  I just can't access the web page.   All three of my devices, phone, ipad, laptop, can log onto the Onstep wifi (very strong signal), but none of them can bring up the web page, 192.168.0.1 or 192.168.0.1:9999.  The phone eventually dumps the Onstep and goes back to the house Wifi.  Bluetooth and the app is fine on my phone, but my ipad does not see the Onstep in bluetooth. 

I am using the SWS software Howard pointed to, default serial baud rate is 57600 on both the ESP32 and the WEMOS.  Any suggestions?

Bob


Re: Occasional error in guide speed - massive overcorrections

GuitsBoy
 

Just to update this, in case anyone else runs into the issue:

I found at least one cause of this pulse guide rate discrepancy. Seems if I issue any manual guide commands directly through APT, it will set OnStep pulse guide rate to whatever APT is configured for "m" or "s".  PHD wont realize this has changed and will attempt to guide expecting the normal slower rate.  To fix the issue on the fly, I have used the app to manually guide at the normal 0.5x rate, after which PHD2 guides correctly again. Additionally, you can manually guide through PHD2, however you need to change the guide rate and then change it back to the desired rate.   If you don't change the rate away and back, PHD2 will assume its already guiding at .5x and wont issue the command to set the guide rate.  At least that's the best I can figure.

So to sum up, its not an issue with OnStep, but a conflict between two different programs setting the guide rate and not knowing the other has changed it.

On 5/20/2021 8:11 AM, GuitsBoy via groups.io wrote:
Hi All -

Ive searched on this topic a few times in the past, but not really getting any hits.  Please excuse me if this has already been covered, and I simply missed it.

I'm experiencing a strange issue on very rare occasions, and I cannot seem to find a pattern that causes this to happen.  I'll be all set up, and happily image my first target for the night using APT, PHD2 and Device Hub with the ASCOM driver. I'll finish my first run of subs, do a goto to the next target, and star guiding.  As soon as PHD2 issues the first small correction, the mount makes a MASSIVE correction, as if its guiding at full slew speed.   Ive attempted manually guiding at .5x, Ive attempted disconnecting the mount and issuing the :R1# command through Arduino Serial Monitor.  Ive disconnected and reconnected each program.  Nothing seems to help until I reboot the laptop, and power cycle the mount, starting from the home position.    This is really no big deal to do on occasion, since my telescope is just a few feet from my back door.  But how do people with remote observatories handle this?   BTW, I've experienced this same behavior with multiple onstep mounts, and different laptops, so I don't believe its isolated to my specific build, unless something was copied between the two.

Has anyone else experienced this?  Is there a common cause?  Any suggestions on how I can help narrow down the suspected software glitch?

Thanks,
-Tony






Re: SHC

John Petterson
 

On Tue, May 25, 2021 at 03:55 PM, Robert Benward wrote:
When entering local time, what ever number you put in, is modified when you say "yes" to the DST.  If you put in 1400hrs, and then say "yes" to DST, the number recorded would be 1300hrs.  So you need to add 1hr to local, then say yes to DST and the time will be correct. But don't do it twice (see below)!  A little confusing if you don't know what is going on.

Bob,

This is expected operation.  The OnStep does not deal with DST. So if the time you are entering is DST, it changes it to standard time before setting its clock.

John


Re: SHC

Robert Benward
 

That is my other problem I'll be talking about in another topic, getting my WEMOS to work.  I get the wifi signal but cannot retrieve a web page at either 192.168.0.1 or 192.168.0.1:9999.  So right now I can't confirm the time that way.  Funny, I removed the WEMOS to program it, but powered up Onstep anyway.  The time was remembered...I put the WEMOS back in, and time was lost at first, but after hitting "set date/time" on my phone via app and bluetooth, the time came back.  maybe I am not waiting long enough?

I am now seeing your comment about the com ports.  Yes, it was strange, but with it working now, I will leave sleeping dogs lie.


Re: Smart Hand Controller on perfboard

Burton
 

Cool! thanks for the link.


Re: Smart Hand Controller on perfboard

Khalid Baheyeldin
 

One of OnStep's users did what you are asking for.

Here is the project

https://www.thingiverse.com/thing:4694885


Re: Smart Hand Controller on perfboard

Dave Schwartz
 

There is a design of case that does not require a board at all, it's all done with point-to-point wiring. Should be able to find it with a bit of searching.


On May 25, 2021 6:30:57 p.m. EDT, Burton <burton.rasmussen000@...> wrote:
Hi, I was curious if anyone had made the Smart Hand Controller without going and ordering the custom made pcb? I'm pretty sure I have all the components, but I really don't feel like spending the money to order the PCB and have 4 extras that wouldn't get used.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Smart Hand Controller on perfboard

Burton
 

Hi, I was curious if anyone had made the Smart Hand Controller without going and ordering the custom made pcb? I'm pretty sure I have all the components, but I really don't feel like spending the money to order the PCB and have 4 extras that wouldn't get used.


Re: SHC

Dave Schwartz
 

The date/time set through the SHC is definitely set in the RTC. I just tested it using my STM32 BP controller which has an RTC. I set the date/time using the new SHC to a few days in the future and many hours different and as I entered each, those values showed up on a web server status page being shown on a tablet connected through the WiFi. I then turned off the power and restarted and the values were retained after having been powered off for about 10 minutes.


On May 25, 2021 6:11:20 p.m. EDT, "Robert Benward via groups.io" <rbenward@...> wrote:
Yes, 3.2V in circuit.  "+" side up.

Bob

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Re: Wemos SWS

robert utecht
 

Thank you Khalid I see.

Robert

On Tue, May 25, 2021 at 6:24 PM Khalid Baheyeldin <kbahey@...> wrote:
On Tue, May 25, 2021 at 06:19 PM, robert utecht wrote:
just one more question please in the library tab I need to download a catalog I looked on Wiki but can't find one.
You don't need to mess with the Library tab at all.
It just allows people who want to, to upload their own very limited set of objects.
The limit is basically available flash memory space on the microcontroller.
For example, on my 256K RobotDyn, I only have room left for 231 objects.

Also, there is no user interface from SWS that allows you to navigate that library
or slew to objects from it.

You need another 'client' of OnStep to do that, and they all have their own catalogs.
Examples are the Android app, Stellarium Mobile Plus, and Sky Safari.


Re: Wemos SWS

Khalid Baheyeldin
 

On Tue, May 25, 2021 at 06:19 PM, robert utecht wrote:
just one more question please in the library tab I need to download a catalog I looked on Wiki but can't find one.
You don't need to mess with the Library tab at all.
It just allows people who want to, to upload their own very limited set of objects.
The limit is basically available flash memory space on the microcontroller.
For example, on my 256K RobotDyn, I only have room left for 231 objects.

Also, there is no user interface from SWS that allows you to navigate that library
or slew to objects from it.

You need another 'client' of OnStep to do that, and they all have their own catalogs.
Examples are the Android app, Stellarium Mobile Plus, and Sky Safari.


Re: Wemos SWS

robert utecht
 

Thank you for all your help got SWS working I like the interface,  just one more question please in the library tab I need to download a catalog I looked on Wiki but can't find one. Thanks again. 

Robert 

On Tue, May 25, 2021, 5:04 PM Ken Hunter <kb7hunter@...> wrote:
Is the NEW SHC  that you mention a hardware or software change?


Re: SHC

Robert Benward
 

Yes, 3.2V in circuit.  "+" side up.

Bob


Re: SHC

Dave Schwartz
 

The RTC doesn't have a battery out of the box... did you install a good one (+ side up)?


On May 25, 2021 5:32:22 p.m. EDT, "Robert Benward via groups.io" <rbenward@...> wrote:
Dave,
I figured the SHC doesn't have a clock, but when I enter the time into the SHC, doesn't that pass it on to the RTC to update it?  What's the battery for then? The RTC doesn't come ready to go out of the box does it?

Bob

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Re: SHC

Robert Benward
 

I am sorry, I misunderstood you.  Please add my comments to the issues pile.

Any insight on the clock issue?

Bob


Re: SHC

Dave Schwartz
 

The thing about the SHC not connecting if the WiFi module was in but not connecting is certainly strange but not likely to be the fault of the SHC as the SHC and Wifi are supposed to be two independent devices on two separate ports so the interaction can only be at the controller level. I've never heard of this before but don't deny it could be some sort of bug that's been there for a long time. However, since it goes away once you get the WiFi connection working (and it works forevermore) it seems like it would be a low priority to fix and probably wouldn't ever need to be addressed except in OnStepX.


On May 25, 2021 4:55:22 p.m. EDT, "Robert Benward via groups.io" <rbenward@...> wrote:
I finally got the SHC loaded.  Here are a few of the things I found.  If the WEMOS wifi is not connecting, it inhibits the SHC to controller communications.  I would plug in the WEMOS (before I got this to connect), and the SHC would fail the comm link.  When I pulled the WEMOS out, it worked fine.  When I finally got the WEMOS working (the new SWS code & baud rate change), the SHC connected fine.

Working the SHC:
  • The scroll rates when entering numbers are pretty fast.  The rates also change rather quickly.  It's easy to overshoot your mark and difficult to get within a minute of desired time.  Setting of coordinates (in goto) has the same issue.
  • When entering local time, what ever number you put in, is modified when you say "yes" to the DST.  If you put in 1400hrs, and then say "yes" to DST, the number recorded would be 1300hrs.  So you need to add 1hr to local, then say yes to DST and the time will be correct. But don't do it twice (see below)!  A little confusing if you don't know what is going on.
  • When repeating the process, the previous time entry is correct (that is after the DST modifies it, e.g. enter 9hrs, hit DST, 8hrs is recorded), but DST returns to the default value of "no". Change it to "yes", and now your recorded time goes to 7hrs. You think you are correcting the DST setting, but it actually subtracts 1hr each pass through.
  • When trying to slew below the horizon, it just stops and no warning is given.  When looking at RA & DEC, you end up scratching your head.
  • When I power off and back on, the SHC does not remember the time.
  • Selecting sites.  I can pick a site, but not clear how to program it or change the name

Note that I have hard coded the WEMOS and the controller to 57600 baud (per a comment in the wiki).  It did not seem to be able get beyond the handshaking mode.  I will cover this in another topic on my WEMOS issues, but I note it here in case there is an interaction.

Bob

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Re: SHC

Dave Schwartz
 

By saying 'no issues' I meant that there were no discernable differences between the way the new and old code performed, not that there might not be room for improvement in the way they did things in common.

For example, the difficulty of entering large numbers such as hours:minutes:seconds as one number by scrolling up and down could eventually be addressed by doing each element separately... entering the triple starts by scrolling just the hours portion, accepting that goes to scrolling the minutes then accepting that goes to scrolling the seconds. With this, the scroll rate while in the individual elements could be much lower and therefore have less problem with overshooting.


On May 25, 2021 4:55:22 p.m. EDT, "Robert Benward via groups.io" <rbenward@...> wrote:
I finally got the SHC loaded.  Here are a few of the things I found.  If the WEMOS wifi is not connecting, it inhibits the SHC to controller communications.  I would plug in the WEMOS (before I got this to connect), and the SHC would fail the comm link.  When I pulled the WEMOS out, it worked fine.  When I finally got the WEMOS working (the new SWS code & baud rate change), the SHC connected fine.

Working the SHC:
  • The scroll rates when entering numbers are pretty fast.  The rates also change rather quickly.  It's easy to overshoot your mark and difficult to get within a minute of desired time.  Setting of coordinates (in goto) has the same issue.
  • When entering local time, what ever number you put in, is modified when you say "yes" to the DST.  If you put in 1400hrs, and then say "yes" to DST, the number recorded would be 1300hrs.  So you need to add 1hr to local, then say yes to DST and the time will be correct. But don't do it twice (see below)!  A little confusing if you don't know what is going on.
  • When repeating the process, the previous time entry is correct (that is after the DST modifies it, e.g. enter 9hrs, hit DST, 8hrs is recorded), but DST returns to the default value of "no". Change it to "yes", and now your recorded time goes to 7hrs. You think you are correcting the DST setting, but it actually subtracts 1hr each pass through.
  • When trying to slew below the horizon, it just stops and no warning is given.  When looking at RA & DEC, you end up scratching your head.
  • When I power off and back on, the SHC does not remember the time.
  • Selecting sites.  I can pick a site, but not clear how to program it or change the name

Note that I have hard coded the WEMOS and the controller to 57600 baud (per a comment in the wiki).  It did not seem to be able get beyond the handshaking mode.  I will cover this in another topic on my WEMOS issues, but I note it here in case there is an interaction.

Bob

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Re: SHC

Robert Benward
 

Dave,
I figured the SHC doesn't have a clock, but when I enter the time into the SHC, doesn't that pass it on to the RTC to update it?  What's the battery for then? The RTC doesn't come ready to go out of the box does it?

Bob


Re: FYSETC S6: Error compiling for board 3D printer boards

Khalid Baheyeldin
 

This is your problem:
In file included from C:\Users\gerbyrne\Documents\Arduino\OnStep\OnStep.ino:108: C:\Users\gerbyrne\AppData\Local\Temp\arduino_build_471100\sketch\src/lib/TLS.h:12:10: fatal error: TinyGPS++.h: No such file or directory    12 | #include <TinyGPS++.h>          // http://arduiniana.org/libraries/tinygpsplus/       |          ^~~~~~~~~~~~~ compilation terminated.
The TinyGPS++ library is missing.

And the comment tells you where to get it from.

To make it easier, download this .zip file

https://github.com/mikalhart/TinyGPSPlus/archive/refs/tags/v1.0.2b.zip

You need to extract it in the same directory where you digitalWriteFast.


Re: SHC

Dave Schwartz
 

The SHC has no clock. The only date and time it can show to you is what it retrieves from the controller. If there is an RTC in the controller it should be pretty accurate from the start but if it comes from a GPS fix I really don't know what its relationship to the real time would be if you get the SHC to access it before the fix occurs.


On May 25, 2021 4:57:44 p.m. EDT, "Robert Benward via groups.io" <rbenward@...> wrote:
P.S., I am using the MaxESP with the RTC.  I assume the RTC has something to do with the SHC or Onstep controller remembering the time.
Bob

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

4821 - 4840 of 38760