Date   

Re: Vixen Super Polaris and OnStep #superpolaris #wemos

Onno Kuijken
 

Hi Chad,

If you're after an SHC using the ESP32, this might be of interest. For the basic hand controller, it seems that you don't need more than 4 pushbuttons (from the ST4 lines to ground) and of course on the OnStep side there must be pull-up resistors from the ST4 lines to 3V3.

I started from the document referenced here: https://onstep.groups.io/g/main/message/29119 that contains some pictures, but still wasn't clear enough for me. So I made a little table to keep track of everything - see attached excel. I started with the pinmap.h file for the CNC shield, then went line by line to match function with GPIO number. Some features are not defined (because I don't have a motorized focuser for instance, so in config.h AXIS3 is not enabled) or not present at all due to pincount limitation of the R32 board.

That covers columns A and B of the 'OnStep' tab. For clarity, I added all functions also to the board outline to the far right on that tab. Names in green are for my own reference, functions that I am not using today but might in the future.

Column C maps the functions/GPIO numbers to the labels on the circuit diagram (schematic) of the CNC board and column D does the smae to the labels that are printed on the CNC shield itself. Of course schematic and layout don't match :(.

Columns E and F are to identify the cables/wires going from one board to the next and are probably less relevant for you.

Column G lists to what slave (peripheral) those cables and wires are going and finally column H lists what the connection is called on the 'far' end - the peripheral to which they are going.

The 'SHC' tab in the excel file does the same but then for the internals of the SHC. Since it turned out that the internal resistance of my RJ12 wires was too high to be healthy, I cut the cable but kept the connector. That's why there are separate columns for 'colour in cable' and 'colour in connector'. The overview is for the 2.42" display that I used and that has an SSD1309 controller. Apart from supply and ground, it only requires 2 wires for I2C and 1 for reset.. Different controllers/displays may need different wiring. BTW, do make sure that the display controller is set up for I2C, not for SPI.

All wires in the SHC that come from pushbuttons in the keypad (NOT the joystick if you want to use that) require a pullup resistor to 3V3. The wires going to the display do not, and neither do the wires coming from the ST4 cable although for the ST4DE-/+ wires it might not hurt. I think I used 10 kOhm throughout

Hope this helps.

BR/Onno


Re: Stepper Strange behaviour

Louis Haarhoff <haarhoff.louis@...>
 

Thank you, will have a play with the backlash settings tomorrow.


On Sun, 28 Mar 2021 at 19:04, András <info@...> wrote:
Have a look at the backlash settings in the config h, cannot think of anything else at first glance.


Re: Stepper Strange behaviour

András
 

Have a look at the backlash settings in the config h, cannot think of anything else at first glance.


Re: wemos d1 + cnc + lv8729 #wemos

Pedro Miguel Barbosa Moutinho Nunes dos Reis
 

On Sun, Mar 28, 2021 at 04:57 AM, Mike Ahner wrote:
I suggest finish your conversion, test it inside to understand how everything works, then test under the stars. You may find that for your purposes it works just fine with the setup you have working. If not then you can figure out what will make it better and change that.
It's my plan yes. Now the focuser and the st4, but I'm still waiting for parts. But as it is is ready to get it outside as soon as I get a clear night... and time :).
So to get from home to 45º it should take about 22/23 secs, right? I need to time that to see if is on specs.

I have another mount to convert, an old gc5. It needs to be serviced first I guess. 


Re: Méga and ramp1.4/bluetooth connection

 

I'm having the same problem right now.
can't connect with the app 


Re: WeMos D1 Mini can not be flashed correctly #wemos

Mike Ahner
 

On Sat, Mar 27, 2021 at 11:00 PM, <danshid@...> wrote:
Arduino ESP32 board version from 1.06 to 1.04
Sorry Dan, that was probably the incompatibility that I was trying to remember. I believe the Wiki has a sentence with the usable versions and lists those with known problems.

Glad you got it working! 

I like OnStep 3.16 and it mostly does the job for me. However, I use a RobotDyne STM32F303CC and so I have to use OnStep ver 4 with that processor. It does have one very useful feature that you may find interesting: Spiral Search. It's so maddening to know you're close but which way to move the telescope?

After you get everything working to your satisfaction, perhaps you will want to try OnStep v 4 for other features. It seems pretty stable now, although I personally stay away from the very latest revisions & fixes.

Take care and clear skies!
-Mike


Re: bluetooth onstep mega 2560 and ramps 1,4 #superpolaris #arduinonano #define #wiki-notice #error

 

I read everything that happened there,
but I couldn't solve the problem 
I made all the connections, but he couldn't connect.


Re: WeMos D1 Mini can not be flashed correctly #wemos

 

Just loaded one today all ok,my original board that came with the kit was the problem , got two new ones and both worked first time 


On Sun, 28 Mar 2021, 5:00 pm , <danshid@...> wrote:
I use the latest stable version (OnStep 3.16). Somehow the problem is solved after I down-grade the Arduino ESP32 board version from 1.06 to 1.04 and recompile/upload OnStep stretch. The problem comes back if I upgrade it to version 1.06. I tried it several times. Looks like the issue is related to ESP32 board version. Thanks.


Re: WeMos D1 Mini can not be flashed correctly #wemos

danshid@...
 

I use the latest stable version (OnStep 3.16). Somehow the problem is solved after I down-grade the Arduino ESP32 board version from 1.06 to 1.04 and recompile/upload OnStep stretch. The problem comes back if I upgrade it to version 1.06. I tried it several times. Looks like the issue is related to ESP32 board version. Thanks.


Re: wemos d1 + cnc + lv8729 #wemos

Mike Ahner
 

On Sat, Mar 27, 2021 at 09:17 PM, Pedro Miguel Barbosa Moutinho Nunes dos Reis wrote:
I set exactly the same configurations on both setups. On the ramps it is much much slower. But, hey, it goes were is supposed to :)
If your previous board was moving the DEC 4x as far and RA 2x as far, it's also likely the motors were running 4x & 2x faster.
The Android app & I think the webpage, will show you the current step rate, which you can change to faster and slower. But the Mega is a slow processor so it does have limits on max speed that are somewhat slower than other boards & processors. 

Usually this isn't a problem, since there aren't that many slews in the night except for visual observers and especially at star parties. Photographers normally stay on only a few targets during the entire night. My Vixen GP2 will slew at 3.5 deg/sec but there isn't much difference from the default of 2.5 deg/sec.

You get slightly faster slews/better performance by using pulse mode in the Config.h file.

I also notice you're using 128 microsteps; since an LV8729 can't mode switch between tracking mode and stepping mode, you could change the microstep value down to 64 or 32, which should give you faster slews. However, it will decrease your mounts resolution because of the coarseness of your DEC & RA axis gears. You can recover those lost microsteps if you use 400 step motors but I don't really know if that will speed things up much.

I suggest finish your conversion, test it inside to understand how everything works, then test under the stars. You may find that for your purposes it works just fine with the setup you have working. If not then you can figure out what will make it better and change that.

-Mike


Re: bluetooth onstep mega 2560 and ramps 1,4 #superpolaris #arduinonano #define #wiki-notice #error

Alain K
 

Hi Sami,
Look at this page : main@onstep.groups.io | Wiki

and read the WiKi for more information.

Cheers,

Alain


Anyone has experience in building OnStep with Visual Micro?

Mike Ding
 

I'm trying to build OnStep with Visual Micro. The IDE and the board seems to be configured properly. But when F5 is pressed, I always get the following error:

Compiling debug version of 'OnStep' for 'Generic STM32F3 series'
Error compiling variant
Debug build failed for project 'OnStep'
 
arm-none-eabi-gcc*: error: C:\Users\Administrator\AppData\Local\Temp\VMBuilds\OnStep\STM32_GenF3\Debug\build_opt.h: No such file or directory

Does anyone has experience with the visual micro? 

Mike


Re: wemos d1 + cnc + lv8729 #wemos

Pedro Miguel Barbosa Moutinho Nunes dos Reis
 

On Sun, Mar 28, 2021 at 03:05 AM, Mike Ahner wrote:
"Painfully slow" is relative. I'm assuming you mean goto slew rate is slow. What rate were you using on the Wemos & what rate are you getting on the Mega? The Mega will have somewhat slower rates since the MCU is much slower, but the Wiki has suggestions for helping speed this up. The main suggestion is to try using "pulse" mode. However, slews between 2 & 3 degrees per second are pretty normal speeds. Faster than that is usually unnecessary and depending on the mechanical quality of the mount, may not be accurate gotos anyway or will stall out eventually.
I set exactly the same configurations on both setups. On the ramps it is much much slower. But, hey, it goes were is supposed to :)

Axis2 is for Declination or Altitude     AXIS1_DRIVER_ Gear Reduction      
    Stepper-Steps MICROSTEPS GR1 (Other stages) GR2 (Final stage)    
AXIS1_STEPS_PER_DEGREE 24651,85185 200 128 2,66666666666667 130    
AXIS2_STEPS_PER_DEGREE 12325,92593 200 128 2,66666666666667 65    
  <= 61200   AXIS2_DRIVER_ A planetary A worm/wheel    
      MICROSTEPS gear-box for for example. Stepper Motor shaft speeds  
AXIS1_STEPS_PER_WORMROT 0     example.   Axis1 (RA/Azm)
            115,6 RPM
            1,9 RPS
      Tracking resolution (in arc-sec)     0,4 kHz (full step)
      Calculated Estimate   Axis2 (Dec/Alt)
SLEW_RATE_BASE_DESIRED 2,00 °/s Axis1 0,15 0,91 <= 1.25 57,8 RPM
    Axis2 0,29 1,82 <= 1.25 1,0 RPS
    (servo, etc.) (stepper drive)   0,2 kHz (full step)
               
Slowest rate w/run-time adjustment 60,8 µs/step → 1°/s slew rate          
Fastest rate w/run-time adjustment 15,2 µs/step → 4°/s slew rate          
             




Re: WeMos D1 Mini can not be flashed correctly #wemos

Mike Ahner
 

By the way, what version OnStep on you using? I seem to recall there is a problem with Wemos & Wifi in version 5.x
You should try OnStep 4.x (whatever is latest) and reflash the Wemos with that Wifi code as well.

-Mike


Re: WeMos D1 Mini can not be flashed correctly #wemos

Mike Ahner
 

Then it suggests there is a wiring problem between the Wemo and the OnStep controller. You will not see the OnStep SSID until OnStep actually connects to it the first time. Later, it's possible to see the SSID even when OnStep fails to connect because that's stored in memory in the Wemos.

I would power everything off and carefully verify the solder connections on the Wemos, top and bottom, then verify the solder connections on the MaxESP. First check them visually with a magnifying glass and a good light, then I would probably just reflow each pin with a hot soldering iron, perhaps adding a drop of fresh solder. Then do the same for the ESP32s board solder joints to the MCU and even on the pcb itself.

-Mike


Re: wemos d1 + cnc + lv8729 #wemos

Mike Ahner
 

On Sat, Mar 27, 2021 at 08:55 PM, Pedro Miguel Barbosa Moutinho Nunes dos Reis wrote:
I removed everything from the board.
The blue light comes up but otherwise is dead as I cannot upload anything/etc, And the MCU becomes very hot quickly...
So the MCU is damaged & perhaps the voltage regulator as well.

"Painfully slow" is relative. I'm assuming you mean goto slew rate is slow. What rate were you using on the Wemos & what rate are you getting on the Mega? The Mega will have somewhat slower rates since the MCU is much slower, but the Wiki has suggestions for helping speed this up. The main suggestion is to try using "pulse" mode. However, slews between 2 & 3 degrees per second are pretty normal speeds. Faster than that is usually unnecessary and depending on the mechanical quality of the mount, may not be accurate gotos anyway or will stall out eventually.
-Mike


Re: Steppers and drivers & Vref - Oh my!

Mike Ahner
 

No, the voltage regulator handles ranges of voltages within it's maximum & minimum specs. You can switch between power sources easily. The only place that will see different/higher voltage is the Motor Voltage on the stepper drivers and of course the stepper motors.

-Mike


Re: wemos d1 + cnc + lv8729 #wemos

Pedro Miguel Barbosa Moutinho Nunes dos Reis
 

On Sun, Mar 28, 2021 at 02:07 AM, Mike Ahner wrote:
Did you try removing the Axis 1 driver and powering again? It's possible that only the stepper driver is damaged. I would try removing them all and anything else not needed to run just OnStep. If the onboard MCU chip gets hot without anything else plugged in, then it's likely bad or the voltage regulator on the board is bad. But other parts can be shorted out and cause the board to heat.
I removed everything from the board.
The blue light comes up but otherwise is dead as I cannot upload anything/etc, And the MCU becomes very hot quickly...


Re: Steppers and drivers & Vref - Oh my!

Tom Morris
 

I currently have tracking set to 64 and goto is set to 8.

I've got several 19v laptop adapters so could try one of those. Do I need to reset / verify the voltage regulator before switching to the new voltage?


Re: WeMos D1 Mini can not be flashed correctly #wemos

danshid@...
 

It is connected to the board (MaxESP). But I still can not see the ONSTEP SSID, blue LED is flashing and does not turn solid. MaxESP is flashed correctly, I got correct response with ":GVP#" command. Thanks.

11941 - 11960 of 43556