Date   

Re: Some pins modifications

Alain K
 

Thanks Khalid.


How do I confirm that RA tracks the sky properly and is not fast/slow? And how do I tune it?

Sam
 

Hi, I've built a MiniPCB v2 on a Vixen GP.

I have a rough polar alignment (Can't see Polaris) with a compass, some drilled holes in the ground, and latitude scale on the mount.
When I sync to a star, using a 114mm f/8 Newtonian with 20mm EP, I find that within 15 mins the star is out of view already.


Re: Meridian Flip

Jamie Flinn
 

I just ran a test and posted to INDI forum - 100% something is wrong - as I watched a flip happen, the Mount control panel in EKOS reported FLIP Completed before my nanny-cam could even detect the mount moving -  about a minute later it was complete  - there is something in the code not setting status correct  (EKOS code - not OnStep) as it looks like the INDI driver is reporting ok

Can anyone tell me if this looks normal in commands and status - search the log file for "Flip -" to find the slew command - I THINK the series of commands all look normal and are reporting good progression of state

Thanks guys!


Re: Some pins modifications

Khalid Baheyeldin
 

Alain,

After you get your modified pinmap working, copy the pinmap .h file that has the modifications
and save it somewhere outside the OnStep directory.

When you upgrade to a new version, you will need to compare the file with the new one, and redo
the changes at that point.


Re: Some pins modifications

Alain K
 

Thanks Howard for the fast answer.
I can live with that :-)
 Cheers.


Re: Autoguide camera for OnStep

Khalid Baheyeldin
 

On Mon, Aug 23, 2021 at 05:07 AM, Matteo Mantovani wrote:
only to better undestand.

So the guide can be done by connecting the camera ONLY through the USB without the ST4 cable ?
Yes. That is how I use it, and that is how the majority of OnStep users do it too.

I have the QHY5L-II-M  connected to a passive USB hub (unpowered), together with the Canon DSLR.
The QHY is attached to a 60mm F4 scope, and the DSLR is attached to the C8.
Then from the USB hub, a cable goes to the laptop.
Separately, there is another cable from OnStep to the laptop.

Note that all of the USB cables could have gone to the hub, but because OnStep is on the tripod,
and not moving with the optical tube, it was better to plug directly to the laptop.

You can see my setup in this video.

If I connect the mount to onstep with USB and camera for autoguiding to the computer with USB, then I use PHD2 or Kstar/Ekos and and is good without ST4?
Exactly.
You don't need an ST4 port.
In fact, I never wired one on the S6 controller.

But if you have an SHC, you will need an ST4 port for it, but not for guiding.

This is very interesting to use SHC and camera for autoguiding in the same time!
OnStep has super powers: it can communicate with and respond to multiple 'clients' at the same time.
Basically, in a typical OnStep setup with one USB port, and one WiFi module, it polls both serial ports
regularly. So you can have both PHD2 and a Planetarium connected via USB, a web page open on port 80,
Stellarium Mobile Plus or SkySafari on port 9998, and the Android App on port 9999. If you have an
ST4 port configured, then you can add an SHC there too.

For KStars, INDI handles the sharing of the USB port between it and PHD2 seamlessly. ASCOM provides
similar functionality from what I hear on this list.

The above is not the only way to do it. For example, you can have certain Planetariums connected over
WiFi too.

The magic that Howard created ...


Re: New G11 OnStep Conversion

Lloyd Simons
 

The belts and pulleys are both GT2 (at least that is what I ordered). I don't think it is belt tension either but I will try your twist test Drew. My understanding is to get the worm as parallel as possible (using feeler gauges to set both sides of the worm blocks to be the same distance from the mount head), and insure the worm is "level" (left to right, z axis). I'll try making some adjustments and try to get it out the next clear night. I wish there was a way to test this indoors during the day...


Re: Meridian Flip

Jamie Flinn
 

FYI I have also been having recent issues with FLIP - the latest stable 3.5.4 Kstars and INDI 1.9.1 appear to have addressed SOME of the issues in proper state between OnStep and INDI (as in park and unpark now happen properly) - however I think in the process of that "fix" the state of the OnStep mount is coming from a flag that seems to be set FAR to early - in a test last night I did my first slew from PARK at Polaris to star in cygnus near the veil - status in EKOS was almost immediate "slew complete"...lol...um no...it took 35 or more seconds to get there.  Anyway I checked My flip last night and the coordinates for the slew match the object...not that right after this kstars crashed on me during solve so no idea if it made it....see the bold 40 millisecs and EKOS had already decided the peirside was not changed - to me this is reacting to async calls as if the real response has arrived - I am not sure if it is a problem or just bad logging.
Note I never do Align Process - I simply unpark...slew to something and then do EKOS platesolve on the target...shoot and guide - I have found that if I select a star NEAR my object and I do platesolve on that before my sequence starts I have very good time getting tthe object in usually 2 rounds of platesolve - I find OnStep is very accurate in getting on target even without "alignment" process

Settings:
HA > 1.95  (whihc is .13 minutes - mount set for 8)
Pierside set for EAST - I actually hard coded this in my OnStep Code so it comes up by default
pause on home OFF
INDI Console I have auto flip = yes (radio button is for ON) - in the doc in the thread that is pointed out - I was never sure if that is OnStep auto Flip or EKOS auto Flip - it worked last night - previous night I had if OFF and I did not flip

What I see as a big issue is that a lot of tests are done with daytime flipping whihc seem to work - those test do not have ALL actors playing their parts - like guiding and Solving - I strongly suspect there is a race condition as I have posted on the INDI Forum as I have had cases where MF is clearly marked to be pending but guiding does not listen...just keeps going.

I will be digging into EKOS mount code today and see if I can spot why it is so quick to respond - If I fix it I will post


2021-08-23T00:15:07.137 EDT DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2021-08-23T00:15:07.145 EDT INFO ][           org.kde.kstars.indi] - LX200 OnStep :  "[INFO] Slewing to RA: 20:49:36 - DEC: 31:47:27 "
[2021-08-23T00:15:07.146 EDT DEBG ][   org.kde.kstars.ekos.capture] - setMeridianFlipStage:  "MF_FLIPPING"
[2021-08-23T00:15:07.290 EDT DEBG ][     org.kde.kstars.ekos.guide] - "Multistar: findTopStars returning: 0 stars, 0.48s"
[2021-08-23T00:15:07.291 EDT DEBG ][     org.kde.kstars.ekos.guide] - Capturing frame...
[2021-08-23T00:15:07.351 EDT INFO ][           org.kde.kstars.indi] - LX200 OnStep :  "[ERROR] Cannot guide while slewing or parking in progress. Stop first. "
[2021-08-23T00:15:07.492 EDT INFO ][           org.kde.kstars.indi] - LX200 OnStep :  "[INFO] Mount is unparked. "
[2021-08-23T00:15:08.513 EDT DEBG ][     org.kde.kstars.ekos.mount] - Mount status changed from  "Slewing"  to  "Tracking"
[2021-08-23T00:15:08.513 EDT DEBG ][     org.kde.kstars.ekos.mount] - Slew finished, MFStatus  "FLIP_RUNNING"
[2021-08-23T00:15:08.543 EDT WARN ][     org.kde.kstars.ekos.mount] - Meridian flip failed, pier side not changed
[2021-08-23T00:15:08.543 EDT INFO ][     org.kde.kstars.ekos.mount] - "meridian flip failed, retrying in 4 minutes"
[2021-08-23T00:15:08.545 EDT DEBG ][     org.kde.kstars.ekos.mount] - Setting meridian flip status to  "FLIP_COMPLETED"
[2021-08-23T00:15:08.545 EDT DEBG ][     org.kde.kstars.ekos.mount] - meridianFlipStatusChanged  "FLIP_COMPLETED"
[2021-08-23T00:15:08.546 EDT INFO ][     org.kde.kstars.ekos.mount] - "Meridian flip completed."
[2021-08-23T00:15:08.547 EDT DEBG ][   org.kde.kstars.ekos.capture] - meridianFlipStatusChanged:  "FLIP_COMPLETED"
[2021-08-23T00:15:08.547 EDT DEBG ][   org.kde.kstars.ekos.capture] - setMeridianFlipStage:  "MF_COMPLETED"
[2021-08-23T00:15:08.548 EDT DEBG ][     org.kde.kstars.ekos.guide] - Reset non guiding dithering position
[2021-08-23T00:15:08.548 EDT INFO ][   org.kde.kstars.ekos.capture] - "Telescope completed the meridian flip."


Re: New G11 OnStep Conversion

Drew 🔭📷🚴‍♂️
 

On Mon, Aug 23, 2021 at 11:15 AM, Lloyd Simons wrote:
The advice from the Losmandy group was to adjust the belt tension and the worm mesh.
Worm mesh, yes absolutely. Belt tension, probably not. A timing belt drives by the "tooth face" and is very tolerant of different belt tension. That is why it is called a "timing belt". Any overtightening will just stress the bearings, a too loose belt will skip. I check the tension by twisting the belt between the two pulleys. If I can twist it 90 degrees then the tension is within tolerance.


Re: New G11 OnStep Conversion

biggs@...
 

This is a long shot, but make sure your pulley gears are GT2 and not MXL.  I had a weird periodic error with GT2 belts but didn't realize my large gear was MXL.
I couldn't find the right pulley on Amazon, but did find Rubber Belts Online (no affiliation), which works great.
https://www.rubberbeltsonline.com/6mm-Bore-Timing-Pulley-2mm-Pitch-60-Teeth-6mm-Wide-p/6mm-60t-6mm-gt2-pulley.htm


Re: Ramps 1.4 GOTO Issue

James1508
 

Nailed it.

Not all that sure what I did but after I changed the overhead limit to 90 in the app it started working.
I wonder if because it starts at 90 in an "excluded zone" it was throwing things out. No idea, but it is working now anyway so I'm super pleased thanks Howard for all your help.

Eventually I plan on upgrading my electronics hardware, so all being well it'll be almost plug and play with a bit of config changing. 

Again thanks Howard, you're a top man :)

Take care


Re: Ramps 1.4 GOTO Issue

Howard Dutton
 

Running out of ideas but:

1. The screen shot of the ASCOM hub showing HA = 0 doesn't mean a whole lot.  OnStep uses refracted coordinates (default) and on the pole it's always 0 regardless of the actual mount HA.
2. Loose the ASCOM hub, eliminate a possible source of trouble.


New G11 OnStep Conversion

Lloyd Simons
 

I was finally able to get my OnStep converted G11 out under a clear sky for some testing. Of course there were a few hiccups, but I was able to get it to guide reasonably well. However, there was some obvious periodic error present in the guide graph (the last three runs in the attached log) and upon frequency analysis, the major spikes were related to the worm period (80', 120', and 240'). My conversion is similar to the one from Rockmover (see pic 1) with a 16t pulley on the stepper and 48t on the worm (3:1 GR). I have the older steel worms. I would like some help in figuring out how to eliminate this periodic error as those large spikes are going to cause some issues while imaging. I have purchased new bearings and Belleville washers for the worms but have not installed yet. The advice from the Losmandy group was to adjust the belt tension and the worm mesh. Any other comments would be appreciated.


Re: SHC CONNECTION WARNING WITH WeMos R32 with CNC V3 Shield #wemos #esp32

George Cushing
 

There seem to be two or three "brands" of the ESPduino-32 as HW calls it. Here's the schematic.
I've used two, the HW and WeMOS. They are interchangeable. The HW-707 comes with either the miniUSB or the B USB connector. If you are going to control through USB you want the B connector. Otherwise, I prefer the mini as one of the RJ12's mounting studs interferes with the USB connector and a couple of resistor pins have to be cut close to avoid contact with it. 

The HW-707 is generally a buck cheaper than the WeMOS, Although I got 10 for $4.70 a piece and 12 day delivery from AliExpress.


Re: SHC CONNECTION WARNING WITH WeMos R32 with CNC V3 Shield #wemos #esp32

Dave Schwartz
 

'Scuse me?

The pullups IN the SHC are for the pushbuttons (the larger one) and the auxiliary ST4 port on the side (the 5-pin one, doesn't need to be installed if you aren't going to use that port). The ones at the controller end must be present because transients must be controlled with as close to the MCU as possible.

On 2021-08-23 10:32 a.m., George Cushing wrote:
Actually, I've spent some time understanding Roman's shield and that note about the resistors never struck a cord before. So I took a look a Dave's SHC circuit and now it's clear. When using ST-4 guiding through the SHC, neither the CNC3 or the Hujer Shield should have pull ups. Why? because Dave has provided them.


Thus when the ST-4 signal attempts to pull down one of the direction conductors you can't have two sets of pull ups fighting it. The cap is there to deal with RF. May not make much difference. The are a 500-800 STM32 controllers out there with no RF caps on them. As a student of Roman's I've noticed he is very diligent in hunting down any possible RF possibilities. Does anyone else here use shielded RJ connectors?


Re: SHC CONNECTION WARNING WITH WeMos R32 with CNC V3 Shield #wemos #esp32

George Cushing
 

Actually, I've spent some time understanding Roman's shield and that note about the resistors never struck a cord before. So I took a look a Dave's SHC circuit and now it's clear. When using ST-4 guiding through the SHC, neither the CNC3 or the Hujer Shield should have pull ups. Why? because Dave has provided them.


Thus when the ST-4 signal attempts to pull down one of the direction conductors you can't have two sets of pull ups fighting it. The cap is there to deal with RF. May not make much difference. The are a 500-800 STM32 controllers out there with no RF caps on them. As a student of Roman's I've noticed he is very diligent in hunting down any possible RF possibilities. Does anyone else here use shielded RJ connectors?


Re: Celestron AVX NEMA Stepper Mount/Enclosure Models/STLs? #celestron #mount

George Cushing
 

Hey Ed, any photos of the LX65 conversion? I know of a few LS mounts that need help.

Virus-free. www.avg.com


Re: SHC CONNECTION WARNING WITH WeMos R32 with CNC V3 Shield #wemos #esp32

Matteo Mantovani
 

Sorry,
I find the answer checking the CNC V3 PCB wire.

This schematic is correct:


But I don't known my Wemos have a different number a double PIN 36!? 😡🤔


Re: SHC CONNECTION WARNING WITH WeMos R32 with CNC V3 Shield #wemos #esp32

Matteo Mantovani
 

Hi Guys,
My Wemos D1 R32 have this pinout :



And I don't find pin 35 needed for ST4 PIN !? 🤔

I don't known why? probably version or other thing!  🤷‍♂️
I check on the web but and I don't find a correct pinout :

For example on this schematic drawing :
PIN 36 is GPIO34 and PIN 38 in GPIO 36 (my 36 PIN!!!)

I want to check the SHC functionality without CNC V3 shield attached using wemos pins.
Can someone clarify the pinout because I don't want to make mistakes.

Thank you


Dual Focusers

Jamie Flinn
 

Hey All…

 

Does anyone have two focusers set up on your OnStep? – if so what do you see from products like INDI/KStars – do the focusers actually get listed as unique devices – for instance right now I have my LX200 OnStep AND a Moonlight that I can choose from in the focus tab of EKOS….I suspect if it actually works I would see LX200Onstep 1 and LX200 Onstep 2????

 

Before I go down the rabbit hole on this I want to know if it is even possible 😊

 

Thanks

J

 

Sent from Mail for Windows

 

8441 - 8460 of 44713