Date   

Re: Teensy 4.1 compilation on Max PCB3 vs MaxPCB36 #onstepx #arduino #configuration #ds3231

George Cushing
 

It would seem that with a 600MHz clock the 4.1 will be no faster in pulse than square. 

Looking at the MaxPBC3.6 board I note that there is no connection for the DS3132's 32K (PPS) pin. That would explain your error.


Re: Showcase: Built With OnStep

Ahks
 

Thanks for this. You just took a ton of work off my plate. I'm gathering parts to convert my zhumell 8" and your timing couldn't have been better. I think your gear on the alt is just about exactly what I was starting to design.

The only modification I can see needing eventually is a tensioner for the alt belt. But I bet it would be quite a while until a belt that size would need it in this application.


Re: Teensy 4.1 compilation on Max PCB3 vs MaxPCB36 #onstepx #arduino #configuration #ds3231

Antoine Cesbron
 

Is it normal that Teensy 4.1 compilation require SQUARE Step wave form ?
#error "Configuration (Config.h): Setting STEP_WAVE_FORM SQUARE is required for the Teensy4.0 and 4.1"

I was trying to set it to PULSE to get faster steps rates.
Thanks.


Re: Teensy 4.1 compilation on Max PCB3 vs MaxPCB36 #onstepx #arduino #configuration #ds3231

Howard Dutton
 

On Mon, Sep 26, 2022 at 02:13 AM, Antoine Cesbron wrote:
In Constants.h, I saw :
#define MaxPCB3                     10     // improved third generation for alum. case, Teensy4.1
So, I started with it and it compile well for Teensy 4.1.This is where you should have stopped.
Don't change the source and use MaxPCB3 as indicated for the MaxPCB3.6.

The 3.0 and 3.5 are obsolete.


Teensy 4.1 compilation on Max PCB3 vs MaxPCB36 #onstepx #arduino #configuration #ds3231

Antoine Cesbron
 

H All, 

I'm new to OnStep, and like to use it on my setup (parts are shipped) :
1x-Teensy 4.1 16mb (received)
1x-DS3231
1x-D1-Mini-Pro 16mb
1x-HC-06
3x-TMC5160 v1.3
OnStepX
All will be on my own PCB

In Constants.h, I saw :
#define MaxPCB3                     10     // improved third generation for alum. case, Teensy4.1
So, I started with it and it compile well for Teensy 4.1.
Even if // Pin map for OnStep MaxPCB 3.0 and 3.5 (Teensy3.5/3.6) and not Teeny 4.1 is labeled in Pins.MaxPCB3.h. 

After some reading, I saw that MaxPCB36 seems to be more "dedicated" to Teensy 4.1.
And it's noticed // Pin map for OnStep MaxPCB 3.6 Teensy4.1 PCB in Pins.MaxPCB36.h.

So I restart with it.
I had to add #define MaxPCB36                    11     // improved third generation for Teensy4.1 in Constant.h.

But compilation fail on  TIME_LOCATION_PPS_SENSE  HIGH   in Config.h:
OnStepX\src\lib\tls\PPS.h:12:4: error: #error "Configuration (Config.h): PPS_SENSE_PIN must be defined for TIME_LOCATION_PPS_SENSE ON"
   #error "Configuration (Config.h): PPS_SENSE_PIN must be defined for TIME_LOCATION_PPS_SENSE ON

It compile only with TIME_LOCATION_PPS_SENSE  OFF  , but the DS3231 will provide the PPS, so it should be HIGH or LOW but not OFF.

I still have not the hardware to check if it work, only the Teensy 4.1 for now, but anticipation permit me to learn about OnStep.
May you please point me to the right direction?
Thanks.
 


Re: How to increase the max slewing speed from 1.0 dps to 2.0 dps?

T.L.
 

Hi Howard, Thank you so much for your quick reply.  I am sorry, but where do I enable or disable "runtime axis settings"?  -Tong


Re: Showcase: Built With OnStep

George Cushing
 

Thanks! Good ideas for these larger Dobs are always appreciated.


Re: Showcase: Built With OnStep

Alex Muzychko
 

Another 10" Dobsonian I picked off Craigslist got some motors onboard.
Lets call it Zero Woodworking GOTO Dob

Design compatible with scopes having these premium Altitude bearing adjusters:

  • Orion SkyLine 10"
  • Apertura AD10
  • Zhummel Z10

No drils, no cut-outs.

Simple clamp design allows to install/remove the GoTo system in seconds and preserves original look of the scope.


Other sizes of the same lineup (8" and 12") will require different belt length. Clamping block may possibly work on 8 and 12, but will likely require redesign to specific belt length and Dob base wall distance to the edge. 

I got partially inspired 12" Dob project by YouTube author bryanpryor (https://youtu.be/bJJGRtJXpgA?t=183)
I was not fond of his spur gears on Alt axis, but I think the friction drive pulley with O-rings deserves more attention.

Details and STLs with links to OnShape CAD:

 

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

YouTube video series on assembly, installation and testing:

  1. Part 1 - Parts and Assembly
  2. Part 2 - Installation on Scope
  3. Part 3 - First Spin

 

 

 


Re: G11/gm8 direct drive to NEMA17 motor adapter plate

gjores@...
 

Hello,
Have found this video https://www.youtube.com/watch?v=yEvuvyM_T84&t=9s it shows a very simple set up for a G11 it appears ok.I have ordered all the bits and will give it a go.No coupling!!!!
Here is a follow up video  https://www.youtube.com/watch?v=2bU0At6hK6k&t=83s

Hope this of interest.
.


Re: Wemos R32 with CNC V3 over Ethernet #wemos

George Cushing
 

Roman used these modules, which are included.
image.png


Re: Lost Steps: Square vs Pulse

Peter Boreland
 

I think I resolved the problem.  I switched from square to pulse.  I also decreased the microstepping from 32 to 16.  I've had two full nights of imaging, and no spikes. Isaw no degradation in guiding.  In fact, I got as low as 0.26" total rms per this screen shot.



Peter


Re: web server ( including smart web-server) and com port conflict in windows 10

Plamen Dimitrov
 

Thanks everyone for the support,
I solved the problem. I installed wrong  driver for CP21XX . My mistake was in windows 10 I supposed to use the universal driver but I used their driver for windows 7 and 8.
Thanks
Plamen


Re: STEPPERONLINE Nema 17 Bipolar Stepper 400 steps choice with TMC2130 #tmc2130

George Cushing
 

You can't rely on the set screws alone. 


Re: Chinese ONSTEP

George Cushing
 

Got me!


Re: Wemos R32 with CNC V3 over Ethernet #wemos

Mark Mahaffey
 

Hi George,

Thank you for the information. Yes, I would like to purchase this kit, 3 kits. I have extra ESP8266 and DS3231 (RTC) modules and I assume these two modules are the ones you are referencing?  I am able to do the soldering work so supplying the kits with the necessary components is no problem for me to solder them in. I believe I have your email and if so I'll email you shortly to work out the details.

Thanks,
Mark


Re: Vixen GP-DX motorization for Mak 180 #drv8825 #tmc5160 #esp32 #ds3231

Howard Dutton
 

On Thu, Sep 22, 2022 at 02:01 AM, Antoine Cesbron wrote:
Is it possible to set "Soft limits" in a case like mine ?
Two axis positions at a time need to be used to check  limits.
Ex :
If altitude is lower than "X deg", Azimuth can rotate 360 deg (useless but permitted)
When altitude reach "X1 deg", Azimuth rotation is maxi "Y1 deg".
When altitude reach "X2 deg", Azimuth rotation is maxi "Y2 deg".
When altitude reach "X3 deg", Azimuth rotation is maxi "Y3 deg"...
OnStep doesn't support that.


Re: How to increase the max slewing speed from 1.0 dps to 2.0 dps?

Howard Dutton
 

On Thu, Sep 22, 2022 at 03:03 AM, Howard Dutton wrote:
Max slewing speed with those settings on your hardware should be ~12 deg/s.
You limited that with a base rate of 2 deg/s, so the range settable at runtime, should be 1 to 4 deg/s.


Re: OnStep to Servo or External Step/Dir drive

Howard Dutton
 

On Sat, Aug 27, 2022 at 12:11 PM, Joe Ulowetz wrote:
If I started with a MaxPCB2 board and a Teensy 4.1 processor, would I be able to (eventually) use OnStepX for servo motor control? Or would you recommend starting somewhere else for someone new to OnStep but willing to learn?
Sorry I missed this post, it's been a while.

Generally OnStepX seems to be working fairly well now but the servo subsystem is still evolving, hopefully in the coming months work on that too will be wrapped up.


Re: How to increase the max slewing speed from 1.0 dps to 2.0 dps?

Howard Dutton
 

On Thu, Sep 22, 2022 at 02:43 AM, T.L. wrote:

Case 1:

With the total reduction ratio of 720, and AXIS1/2_DRIVER_MICROSTEPS to be 32,  and the AXIS1/2_DRIVER_MICROSTEPS_GOTO to be 8. The scope works very well at max slewing speed at 1dps (SLEW_RATE_BASE_DESIRED); but not any faster.

Max slewing speed with those settings on your hardware should be ~12 deg/s.

  I  have attached the Config-32.h (Config.h) for this case

 
Case 2:

It seems that if we reduce the total reduction ratio by half to 360; and use 64 micro steps (AXIS1/2_DRIVER_MICROSTEPS); all other to be same as the case 1; we should be able to have the same tracking accuracy (in theory)

Not the same tracking accuracy, generally 720:1 will be better.  The improvement of 64x vs. 32x is questionable at best, perhaps just a tiny gain.

but double the max slewing speed (SLEW_RATE_BASE_DESIRED) to 2.00 dps when the motor physically running at the same speed as the Case 1.
However, strangely. in this case the motors still visibly try to run at about twice of speed, and stalk most of the time.  I  have attached the Config-64.h (Config.h) for this case.

Perhaps you enabled runtime axis settings and the changes are being ignored?

// Settings for driver Microsteps, IRUN, Reverse, Limit Min, and Limit Max are stored in NV (EEPROM.) These runtime settings
// can be changed (or reverted to the defaults below) from the SmartWebServer's Config webpage.  If runtime axis settings are 
// enabled changes to these settings below may be ignored as runtime settings from NV (EEPROM) are used instead.


How to increase the max slewing speed from 1.0 dps to 2.0 dps?

T.L.
 

Hi Howard and Kahlid,

This is Tong from Hubble Optics; we are trying to use OnStep for our UL scopes. First, I want to thank Howard for the wonderful OnStep Controllers which work really well, and to Kahlid for a lot of very helpful postings here. 

 

We have made a few MaxESP (V3) controllers using TMC5160 with 4.24q release; Our newly designed GoTo drive system are largely based on Howard Banich’s wonderful 28” Dob, a friend’s (Bruce) mod on our UL20, and Tom’s 22.4 OnStep showcase scope; Tom also shared his insight and experience with me and recommended me to post my question here.

 

Case 1:

With the total reduction ratio of 720, and AXIS1/2_DRIVER_MICROSTEPS to be 32,  and the AXIS1/2_DRIVER_MICROSTEPS_GOTO to be 8. The scope works very well at max slewing speed at 1dps (SLEW_RATE_BASE_DESIRED); but not any faster.  I  have attached the Config-32.h (Config.h) for this case

 
Case 2:

It seems that if we reduce the total reduction ratio by half to 360; and use 64 micro steps (AXIS1/2_DRIVER_MICROSTEPS); all other to be same as the case 1; we should be able to have the same tracking accuracy (in theory) but double the max slewing speed (SLEW_RATE_BASE_DESIRED) to 2.00 dps when the motor physically running at the same speed as the Case 1.  However, strangely. in this case the motors still visibly try to run at about twice of speed, and stalk most of the time.  I  have attached the Config-64.h (Config.h) for this case.

I will appreciate if you and others can help me to solve this issue.

Thank you and best regards
Tong

 

1641 - 1660 of 47996