Date   
Classic byers mount on Astromart for a great price..

John Scherer
 

I'm not the current owner of this or in any way affiliated with him but, if anyone is looking for a great mount for conversion to Onstep, this Byers 812 mount would be a fantastic candidate.  I wish I had $1500!

Re: "Align" button greyed out

Howard Dutton
 
Edited

On Sat, Oct 5, 2019 at 02:22 PM, Drew 🔭📷🚴‍♂️ wrote:

Attached is a pic of the screen. The "Align", "RevNS" and RevEW" buttons have the grey lettering. It doesn't show well in the pictures. The button reverses work (some of the time) Also the North and West button can hang and keep the motor running until you push another button.
In the Connection activity where you enter the IP check the "error correction" box, see if that improves things. (assuming WiFi?)

Re: "Align" button greyed out

Khalid Baheyeldin
 

Yeah, a long press is not obvious, but it is safer on those pesky touch screens.

But greyed out has nothing to do with long or short press. When the slew ends (beeeep) all buttons that can be used are red.

Re: "Align" button greyed out

Drew 🔭📷🚴‍♂️
 

Thnx, I don't think I would have ever guessed the long press in this case.

Re: "Align" button greyed out

Drew 🔭📷🚴‍♂️
 

New info and possible workaround for now. For fun I went into the main "guide/focus" screen. The one where the buttons fill the screen. I unchecked the "Lock" checkbox and the align button turned red (the mini guide screen in the alignment menu is always red, locked or not). I clicked it and got a "alignment success" The button then turned to a "Sync" button.

Re: "Align" button greyed out

Khalid Baheyeldin
 

Here is what I did trying to reproduce this.

Flashed my STM32 with today's master (3.0f).
From Android, select Initialize, and 1 Star Align.
Selected Alioth in UMa.
After the slew completed, the Align was red (not grey).
I long pressed Align, and OK at the prompt, and got align successful.
Then selected Bright stars, then Alkaid (also in UMa), and after the slew completed, the Sync button was red.
Long pressed it, and it Synced.

The 3 dot menu has Lock checked. I never change this, since I did not need to reverse, ..etc.

I repeated the above with 3 Stars (Alioth, Alkaid, and Arcturus), and it all worked too.

Re: "Align" button greyed out

Drew 🔭📷🚴‍♂️
 

Pic didn't attach to last post, here it is.

Re: "Align" button greyed out

Drew 🔭📷🚴‍♂️
 

If you are referring to the "Locked" checkbox, I have tried it both ways. I thought it just locked the guide speed. Anyway I can guide the scope fine.

Attached is a pic of the screen. The "Align", "RevNS" and RevEW" buttons have the grey lettering. It doesn't show well in the pictures. The button reverses work (some of the time) Also the North and West button can hang and keep the motor running until you push another button.

Anyway pushing the Align button generates a click but nothing else. If I look at the initial data screen I still see "Last Align?" If I select another star it says "Align  in progress" This is why I believe the button is not imputing the align data.

Re: Can I use OnStep to control my telescope from a laptop with stellarium?

Howard Dutton
 

I fear changing the timeout to something longer will play havoc with the Android App, ASCOM, etc.  And I'm not about to go through re-working those.

Probably a better solution would be to add another command channel server on a different port (to the WiFi Addon) and use that for those applications that need it.

Re: Can I use OnStep to control my telescope from a laptop with stellarium?

Howard Dutton
 

On Sat, Oct 5, 2019 at 11:55 AM, Khalid Baheyeldin wrote:
On Mon, Sep 30, 2019 at 10:32 AM, Dave Schwartz wrote:

Note that it does not currently work over TCP/IP (WiFi) because Stellarium does not function with the short connection lifetime (after each interaction, OnStep closes the socket). Although Howard said that this was required for resource management on the ESP, Fabien thought this was a bizarre way to operate and had no plans to implement it.
If you look at this file, specifically line 388 and 394, you will find that the WiFi firmware explicitly closes the connection after 2 seconds.
Perhaps this can be changed somehow. One method would be timing out and closing the connection if no command received in, say, X seconds, otherwise keeping it open. X can be 10 seconds in the Config.h, and therefore can be tuned.

This will also solve the INDI problem of not working over TCP.

Not saying that Howard should do this immediately, but that someone tests it first, and prove it to work. After that Howard can merge it in the repo.

Yet it works and has always worked with Sky Safari?

It was originally done this way for the W5100 where hung connections would always lock up sockets over time, this was the one solution I found.  Probably a limitation of the Arduino libraries but I wasn't about to recreate those.  So short socket timeouts were the solution and the rest of the software stack ended up going that way.  Then when WiFi came along, ditto.

Re: Can I use OnStep to control my telescope from a laptop with stellarium?

Khalid Baheyeldin
 

On Mon, Sep 30, 2019 at 10:32 AM, Dave Schwartz wrote:

Note that it does not currently work over TCP/IP (WiFi) because Stellarium does not function with the short connection lifetime (after each interaction, OnStep closes the socket). Although Howard said that this was required for resource management on the ESP, Fabien thought this was a bizarre way to operate and had no plans to implement it.
If you look at this file, specifically line 388 and 394, you will find that the WiFi firmware explicitly closes the connection after 2 seconds.
Perhaps this can be changed somehow. One method would be timing out and closing the connection if no command received in, say, X seconds, otherwise keeping it open. X can be 10 seconds in the Config.h, and therefore can be tuned.

This will also solve the INDI problem of not working over TCP.

Not saying that Howard should do this immediately, but that someone tests it first, and prove it to work. After that Howard can merge it in the repo.

Re: New Dob Owner

T.K
 

On Sat, Oct 5, 2019 at 06:39 PM, <tj_slice@...> wrote:
I didn't want to drill the big hole in my base.  Without it, the smaller section of the pulley, that extends below the base, would have only been 10mm in diameter.  I didn't think it would be strong enough handle the load.  I figured the big hole would be hidden anyway.
I do it other way. A 10 mm diameter shaft fixed to lower disk which long enough to reach above upper disk can solve this. pulley can be fixed to shaft with a set screw. But when the mount need to be lifted, it can't overcome the lower disk weight and start sliding out of the shaft. Therefore the shaft should be threaded on both ends and fixed by nuts to withstand the weight of the lower disk.

I know this may be a more expensive solution, but it's important for me to avoid drilling in the mount. I want to make an "easy to install" design, so if anyone wants me to make one for him, he can install it without any other skill than tightening the screws.

I still don't know how your pulley fixed to lower disk. Is it only by that bolted joint?

The Az pulley is securely attached to the lower section of the mount and will not rotate.  The motor will be oriented vertically in a back corner of the mount.  If you lifted the entire thing off the ground, the lower part of the base would rotate around.  Since that will be fixed to the ground, and unable to rotate, the upper part of the mount, with the motor, will rotate instead.  I am sure the optical tube will end up being limited to around 80 degrees up when it impacts the motors, but that shouldn't be much of an issue.

Alt-Az tracking mounts have a limit at zenith which calls "zenith blind spot". I don't know how large is that circle for an arduino mega 2560 OnStep mount. Maybe Howard or more experienced users can answer. This can help us to decide if a 10 degrees overhead limit due to motor placement is worth it or not.
I want to install my motor near the edge of the disk, so it has more space vertically. but it needs a longer timing belt, which is not that important.
I want to use a sealed acid battery as a power supply because I think I won't find another source near my observing sites. These batteries are bulky and take more space, so handling a limited space between OTA, mount inner surfaces and upper disk edge is a real challenge for me.

Can anyone help how much Ah capacity for an OnStep controller (Mega 2560, two 1.3A motors and esp8266 for WiFi) is enough to tracking for at least 4 hours?


I am thinking about adding a couple of endstops to the Alt axiz.  The new pulley finished printig overnight, so I will get it installed and upload a new picture.

I'm waiting for your results. They are really helpful for me.

Re: "Align" button greyed out

Howard Dutton
 

On Sat, Oct 5, 2019 at 10:11 AM, Howard Dutton wrote:
No idea why it would happen.
...well thinking about it, perhaps you simply didn't unlock the Guide/Focus pad?  That's on the menu button (three dots, top-right of screen when in the Guide/Focus activity.)

This thing is made for working in the dark by feel so it defaults to locked so you don't accidentally trigger that button.

Re: "Align" button greyed out

Howard Dutton
 

If you were to provide me with enough information perhaps I would have a shot at reproducing the problem.

Re: OnStep v3: Cannot flash ESP8266

Howard Dutton
 

On Sat, Oct 5, 2019 at 02:57 AM, Murat Isik wrote:
My PINMAP is STM32Blue.

Note that the very same board allows me to flash the WiFi-Bluetooth addon on version 2.x
I was going on the assumption he had this fly wired to work (requires two connections, simple.)

Naturally that might not be the case.

Re: "Align" button greyed out

Howard Dutton
 

On Sat, Oct 5, 2019 at 08:18 AM, Drew 🔭📷🚴‍♂️ wrote:
When I attempt to do an alignment everything is good but the "Align" button is greyed out. It clicks but I get no "alignment successful" or other confirmation. Could this be because I start with Tracking On?
Can't reproduce this. 
No idea why it would happen.

Re: OnStep v3: Cannot flash ESP8266

Khalid Baheyeldin
 

The STM32 Blue Pill board is not wired for flashing through OnStep.

You need to take the WeMos D1 Mini out of PCB, and flash it externally using its microUSB port.

"Align" button greyed out

Drew 🔭📷🚴‍♂️
 

When I attempt to do an alignment everything is good but the "Align" button is greyed out. It clicks but I get no "alignment successful" or other confirmation. Could this be because I start with Tracking On?

Re: New Dob Owner

John K.
 
Edited

And for centering the pulley, I want to use a needle bearing around pulley's shaft and upper disk's hole. I don't want to do any drilling on my original mount.
I didn't want to drill the big hole in my base.  Without it, the smaller section of the pulley, that extends below the base, would have only been 10mm in diameter.  I didn't think it would be strong enough handle the load.  I figured the big hole would be hidden anyway.

1- When the AZ axis rotates, the bolt and nut may become stiff and put the load on belt or motor due to friction.
The Az pulley is securely attached to the lower section of the mount and will not rotate.  The motor will be oriented vertically in a back corner of the mount.  If you lifted the entire thing off the ground, the lower part of the base would rotate around.  Since that will be fixed to the ground, and unable to rotate, the upper part of the mount, with the motor, will rotate instead.  I am sure the optical tube will end up being limited to around 80 degrees up when it impacts the motors, but that shouldn't be much of an issue.

I am thinking about adding a couple of endstops to the Alt axiz.  The new pulley finished printing overnight, so I will get it installed and upload a new picture.

Re: Focuser information

Howard Dutton
 

On Sat, Oct 5, 2019 at 07:11 AM, Gianluca Galloni wrote:
#define AXIS4_DISABLE_OFF            // Pin A22 (Aux6.)  Default _OFF, use HIGH for common stepper drivers.
#define AXIS4_DISABLE HIGH
#define AXIS5_DISABLE HIGH

Is a good idea though you seem to think they have power.