Date   

Re: OnStep Configuration Generator lives on ...

Alain K
 

Hello Khalid,

I don't see the TMC5160 in the driver list ?

Thanks.


Re: Wireless SmartHandController (ESP32 - SPP bluetooth)

Tong
 

Hi Gildo Bosi
You've done a great job. I've been trying to implement this feature in vain.


Re: OnStep need help

Khalid Baheyeldin
 

On Mon, Jul 27, 2020 at 05:44 PM, Jas wrote:
The last time I was in a physics class was in 1979 and it’s  kinda foggy after all these years.
I think my last formal physics classes were a few years before. But in recent years, I re-learned (and got updated on) parts of physics, simply because astronomy and cosmology are built on top of physics.

I have learnt to solder and am slowly learning the other stuff. 
Same here.

Anyway, the OnStep Configuration Generator has been resurrected ...


OnStep Configuration Generator lives on ...

Khalid Baheyeldin
 

The OnStep Configuration Generator is now updated to work with 3.16 (stable) and 4.x (latest master).

This update was done because some people still struggle with the syntax of the configuration file, despite the format of the configuration file from version 3.x onwards was vastly improved to make it more friendly. The users who struggle with the format have no programming experience, and it is difficult to explain that it is case sensitive, it is one argument per #define line, and so on ...

The OCG does the following:
  • Asks for the version of OnStep that you are using.
  • Asks for the two gear ratios, motor steps per rotation, microsteps, ...etc. (same values from the spreadsheet)
  • Calculates the most important parameters to get you going, and validates them as per the spreadsheet formulas.
  • Sets some useful parameters to enabled.
  • Leaves a lot of the remaining parameters unconfigured, as they are in the original Config.h file.
There is no point in supporting version 2.2 or earlier, because it no longer the stable version, and new users will be using the stable or latest master.

The Configuration Generator is now online, and instructions are at the top of the page.

This is a video demonstrating the generator step by step, although for the older versions. The principles are still the same.

Your feedback is welcome.


Wireless SmartHandController (ESP32 - SPP bluetooth)

Gildo Bosi
 

I recently made a wireless smarthandcontroller, enabling bluetooth communication on the ESP32 controller.
I share the information to modify the original project and obtain a wireless SHC (see zip attachment)

For those wishing to contribute to the project, it is necessary:
-Improve connection handshake. Now in case of disconnection it is necessary to turn the SHC off and on again (disconnection is rare, the connection is very stable if it remains within bluetooth range, about 5 .. 10 meters)
-Enable the ability to scan the devices present and store the last connected.
-Enable the possibility to change the pin, default 1234. It is now statically programmed within the Arduino libraries. The change is not easy, it requires storing an address <--> pin table.
 
Gildo


Re: Warning: don’t install KStars 3.4.3

Jamie Flinn
 

Yeah...i do manual there too...check the box and move mount by hand

On Jul. 27, 2020 4:57 p.m., Rafael Barberá Córdoba <rbarberac@...> wrote:

Unfortunately the damned Polar Alignment Assistan makes profuse use of Park/Unpark. 

At the end, PAA it’s a ver good debugging tool for Ekos+OnStep. It has been caught for every problem that has appeared recently 😂😂😂



Re: Failed to init device yet again

snorowski@...
 

OnStep users,  let me first say that I'm no expert on this project, I just completed a successful BluePill build 3 days ago, and had
my own struggles getting my stm32 to flash.  My first day trying to upload OnStep, I also had "failed to init" problems, with all the same
errors and comments you were describing in this thread.  On day 2, I decided to retry, starting from ground zero,  noting all of the little
checks I did before hitting UPLOAD.  I had success on my first try that day.  Here are all the steps I took, perhaps it will work for you, too.
Experts might say some of these steps are unnecessary, but it's just a report of what I did.
Sorry for the painful details.
 
First, I'd get rid of the last usb cable you used since that one seems to have introduced com port errors.
 
1.  unplug all removable modules from the board, connect 12V just  to verify 5.0 v output from power supply. Then remove power.
2.  install STM32 module and the eprom module with a working lithium battery, plus side up. (NO motor drivers , NO wifi)
3. move jumper/switch to FLASH.
4.  Turn on 12V to board.  Red power led comes on Blue pill.
5.  Plug in usb to CP2102.  Maybe this is where I saw an led on the CP2102 but only for a few seconds.
6.  Open the windows Control Panel/View devices and printers.  Note the com port # that came alive.  
7. open com port properties, hardware properties, port settings and note the baud rate of the port,  make sure it's 9600 baud rate for this try.
8.  Open OnStep.ino, launching Arduino ,  mine is version 1.8.13,   my OnStep release is 3.16
10.  set Boards:    Tools > Board: > STM32F1Boards(STM32duino.com) > GenericSTM32F103C series.   It will take a few seconds for other options to configure in the toolbar.
11. set variant:     Tools > Variant: > STM32F103CB (20Kram 128K Flash)
12. upload method :   Tools > upload Method > serial
13  CPU speed :    Tools > cpu speed > 72Mhz normal
14. optimize :     Tools > optimize > smallest (default)
15. port :           Tools > port > com port that was noted in step 6.  Make sure it is selected.
16.  click on Tools > get board info.   a small window will open that says something like unknown board. Thats fine, its only a connection check, just close the window.
17.  This is one step I didn't do the first day I had failures, it might be what fixed my problems:
     In Arduino, click on the first tab "OnStep". scroll down a little to line 53 which says  #define NV_INIT_KEY_RESET false  
      and read the comments on what this is, I didn't read it the first day.
     Change the word false to true >>  #define NV_INIT_KEY_RESET true
18.  Then I did a SAVE, then VERIFY with no errors, and UPLOAD with no errors!! finally.
19.  Go back to line 53 and change setting back to false, per the instructions so as not to cause wear on the eprom every time onstep powers up.
20.  SAVE and UPLOAD again.
21.   power down, disconnect usb, move switch to RUN, power on, saw a blinking tracking led on stm32, celebrate, power down.
22.   Spent some time flashing the wifi according to the wikipage, OFF the board by itself.
23.  install wifi board and motor drivers, then tested everything else (wifi connection, app,  slewing with sky planetarium...)
 
Everything seems to be working, I'm still waiting for motors and I have to build my mount, but I'm very proud of myself and thankful to everyone connected to the OnStep project.
 
 
Like I said, I'm not an expert, this is my first OnStep build and my first experience with Arduino.  I just noticed all the posts
about "failed to init" and I thought I would share what worked for me,  hope it helps.
 
Stephen
 


Re: OnStep need help

Jas
 

You are absolutely right Khalid. I, for one, have very very limited experience with code. The last time I was in a physics class was in 1979 and it’s  kinda foggy after all these years. And in the intervening years been in a profession that has nothing to with the subjects on hand.  I have learnt to solder and am slowly learning the other stuff. 

Your input is invaluable.

Thanks

Jas


Re: new FYSETC S6 build

Markus Kempf
 

got my new S6 board, the 5160 stepsticks and the GPS module. Soldered
and assembled everything, loaded OnStep and everything worked perfectly.
OK, not everything, the GPS time and location set did not work with
RX3/TX3 SerialC GPSSerial3. After many tries I finally switched to
SoftwareSerial2 on Y+/X+ and this did the trick. Now all is well... Btw.
the max speed with Howard's standard gear settings and 32 microsteps, no
GOTO step switch, is 8.9deg with PULSE. No resonances or stalling with
my motors on the bench...

Next thing will be the weather module and the mechanical build of the
final gearing.

Markus

Btw. has somebody created a 3D printable box for the S6 or found a
suitable box in a catalog?


Re: Warning: don’t install KStars 3.4.3

Rafael Barberá Córdoba
 
Edited

Unfortunately the damned Polar Alignment Assistan makes profuse use of Park/Unpark. 

At the end, PAA is very good debugging tool for Ekos+OnStep. It has been caught for every problem that has appeared recently 😂😂😂


Re: Warning: don’t install KStars 3.4.3

Butchf
 

Good catch,
Thank you for the heads up.

Don


Re: Warning: don’t install KStars 3.4.3

Jamie Flinn
 

If you have already updated…follow this process to work with EKSO:

  1. Open the ONSTEP App
  2. UNPARK
  3. Open Kstars/EKOS and run your profile – you will find the status is corrcet and mountis either idle or tracking – you can use the TRACK start and stop from the Phone App and the status will be reflected
  4. Run your session as normal – DO NOT TOUCH PARK or UNPARK
  5. Disconncet INDI/EKOS and shut down that SW
  6. PARK your mount via phone app

 

I have also found you CAN use the RETURN HOME in INDI driver tabs (Site) and it will not blow up –

 

I have done full scheduled run using this pattern althogh it requires  you stay up to PARK 😊

 

 

From: main@onstep.groups.io On Behalf Of Rafael Barberá Córdoba
Sent: Monday, July 27, 2020 3:56 PM
To: main@onstep.groups.io
Subject: [onstep] Warning: don’t install KStars 3.4.3

 

It has beed discovered a problem with Ekos included in version 3.4.3 and the support on the INDI driver for weather functions. When used with OnStep, the system crashes as soon as you try to park or unpark the mount.

Ekos developers have identifier the problem as Ekos specific, not driver nor OnStep related, but they have warned about how Difficult the fix will be. So by now, it will be better to not upgrade KStars version. 


Warning: don’t install KStars 3.4.3

Rafael Barberá Córdoba
 

It has beed discovered a problem with Ekos included in version 3.4.3 and the support on the INDI driver for weather functions. When used with OnStep, the system crashes as soon as you try to park or unpark the mount.

Ekos developers have identifier the problem as Ekos specific, not driver nor OnStep related, but they have warned about how Difficult the fix will be. So by now, it will be better to not upgrade KStars version. 


Re: Backlash on Super Polaris with direct coupling of planetary gearbox? #backlash

Rafael Barberá Córdoba
 

Maybe the backlash is in the worm gear/wheel? Remove the pulleys and check by hand and see if there is wiggle.
Yes, that the problem. At least with the EQ5 “flavor” of this mount. The backlash comes from the horizontal freedom on the worm axis and from the gap between this worm and the driving crown. But the pulleys and belts usually didn’t add noticeable backlash. 


Focuser only turns one way

Geoff Nichol
 

Hi ,
When I try to use my electric focuser via the Onstep android  app the stepper motor will only turn one way. If I press the up arrow it turns clockwise, if I press the down arrow it turns clockwise?  Stepper does  move but very slow.
Any ideas, what am I doing wrong.

Skywatcher 200p with  eq5  mount
mks gen l v1.0 board
Lv 8729 on Axis4 Focuser 1
stepper motor 17hs15-1704s 200 step per rotation , belt drive 1:4 reduction
mtc2130 on Axis 1 and 2
Onstep 3.16
config file attached
shaft 4mm so 4000 * 3.142 =12,566 micron per rev  = D
motor 200 step * 32 micro step * 4.5 reduction  = 28,800  = S
axis steps per micron = 28800 / 12566   =2.29


Re: OnStep STM32 blue pill

Khalid Baheyeldin
 

On Mon, Jul 27, 2020 at 11:38 AM, Mohamed Haleem wrote:
Thanks, Khalid. I never set it until you mentioned. Now both motors are working as expected.
That is odd. I thought that having MICROSTEPS_GOTO set to a low number (2, 4) would be causing the stalls.
But if it works, then keep it the way it is  ....

I still could not find why STM32 is not turning the two DRV8825 controllers ON by itself. I am keeping the SLEEP and RESET pins connected to 5V supply. I measures the voltages at the STM32 pins to be connected to these pins on the controllers They are in the order of few tens of mA all the time and not getting close to 5V. Is it something to do with the configuration settings?
No idea.
In the PCB for the STM32 Blue Pill, the SLP and RST pins connected is something that the DRV8825 needs in order to work.

We recommend against using the DRV8825 because it is not very precise. Use the LV8729 or S109 instead. Those two pins don't need to be connected on the LV8729.


Re: OnStep STM32 blue pill

Mohamed Haleem
 

Thanks, Khalid. I never set it until you mentioned. Now both motors are working as expected. For the purpose of observing I have set the parameters as follows. The motors are NEMA 17, 1.5A, 1.8 deg.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
#define AXIS1_STEPS_PER_DEGREE    6400.0 //  12800, n. Number of steps per degree:                                          <-Req'd
                                          //         n = (stepper_steps * micro_steps * overall_gear_reduction)/360.0
#define AXIS1_STEPS_PER_WORMROT   6400.0 //  12800, n. Number of steps per worm rotation (PEC Eq mode only:)                <-Req'd
                                          //         n = (AXIS1_STEPS_PER_DEGREE*360)/reduction_final_stage
#define AXIS1_DRIVER_MODEL        DRV8825  //  OFF, (See above.) Stepper driver model.                                      <-Often
#define AXIS1_DRIVER_MICROSTEPS     16   //    OFF, n. Microstep mode when tracking.                                        <-Often
#define AXIS1_DRIVER_MICROSTEPS_GOTO   8 //    OFF, n. Microstep mode used during gotos.                                     Option

// AXIS2 DEC/ALT
#define AXIS2_STEPS_PER_DEGREE    6400.0 //  12800, n. Number of steps per degree:                                          <-Req'd
                                          //         n = (stepper_steps * micro_steps * overall_gear_reduction)/360.0

#define AXIS2_DRIVER_MODEL            DRV8825 //    OFF, (See above.) Stepper driver model.                                      <-Often
#define AXIS2_DRIVER_MICROSTEPS       16 //    OFF, n. Microstep mode when tracking.                                        <-Often
#define AXIS2_DRIVER_MICROSTEPS_GOTO  8 //    OFF, n. Microstep mode used during gotos.                                     Option

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Other AXIS# parameters are default values.

I still could not find why STM32 is not turning the two DRV8825 controllers ON by itself. I am keeping the SLEEP and RESET pins connected to 5V supply. I measures the voltages at the STM32 pins to be connected to these pins on the controllers They are in the order of few tens of mA all the time and not getting close to 5V. Is it something to do with the configuration settings?
  
Mohamed Abdul Haleem



On Sun, Jul 26, 2020 at 10:53 PM Khalid Baheyeldin <kbahey@...> wrote:
On Sun, Jul 26, 2020 at 03:49 PM, Mohamed Haleem wrote:
Now the RA motor spins while tracking. While slewing, the motors make spin for a second and then stop. There is a high pitch sound heard from the RA motor.
This means the motor is stalling when slewing.
This happens due to mid band resonance.

Are you using MICROSTEPS_GOTO (i.e. it has a number instead of OFF)?


Re: Switch off focus motor

Michael Ehemann
 

Everything OK  4.11f
I will press the donation button in the next few days!


Re: Toque requirement and choosing stepper motor - help

Markus Kempf
 

a third way would be sloppy engineering,...

simply measure the required torque with an attached stick of known length to your gear and an attached spring scale (electronic  bagage scale). Add force/weight until your gear starts to move.

Markus

Am 27/07/2020 um 16:11 schrieb Khalid Baheyeldin:

There are two ways of doing this: rigorous engineering, and experience.

I will describe the experience way, which basically draws on what people have converted in the past.

Your gear reduction is close to the G11 (360:1), which people convert using direct drive.
If you add in a 5:1 timing pulley, then this most tried and tested motor should do the job more than
adequately.

Why? Because people who convert EQ5 motors have 144:1 + 3:1 and it works well.
You have more reduction, so you have more torque.

I don't see a reason for NEMA 23, or anything other than the motor I linked to.


Re: OnStep need help

Khalid Baheyeldin
 

There are recent posts of a few people struggling to edit the Config.h, even after the changes in 3.x making it easier.
This is inevitable as the OnStep user base grows, with more people who have no programming experience.

Maybe I will change the Online Configuration Generator to work with the new format of Config.h.
This should reduce user frustration and make for less support requests.

Still, for robert utecht, I am waiting for the driver model, then I can send you a working Config.h file.