Date   

Re: wemos d1 + cnc + lv8729 #wemos

Pedro Miguel Barbosa Moutinho Nunes dos Reis
 

On Sun, Mar 28, 2021 at 08:22 PM, Mike Ahner wrote:
Try these changes before you spend more money on different stepper drivers. I don't think the TMC2130s will make enough difference in your situation to be worth the money. Maybe when you get a faster controller board later.
OK, thanks for the advice.


Re: Alt Az Tracking Adjustment Question

Ken
 

I edit the config.h file directly in the IDE with the new Steps per Degree that is generated via the spreadsheet, then save it, and upload to the controller board. Here is a pic of my prototype. I am not sure how to churn aluminum into something similar nor do I have a 3d printer to create something more accurate. Ignore the nails at each end this was a pic as the belt was glueing and there were only there to keep it in place. I’d would almost rather try a circular pulley but I haven’t found an affordable one with a diameter I want. 


Wi-Fi loose connection #wemos

lukewas77@...
 

Dear all, 
I start to have issue with the wifi...from phone or from pc I loose often the connection...I mean...Wi-Fi remain connected but thé webpage show me error to the connection or page not found...after 2-3 times it restart...maybe full page maybe half page...did you have this type of issue?


Re: wemos d1 + cnc + lv8729 #wemos

Mike Ahner
 

On Sun, Mar 28, 2021 at 01:39 PM, Pedro Miguel Barbosa Moutinho Nunes dos Reis wrote:
But I believe the ramps have only jumpers like the cncv3.
Pedro,
First, change the step waveform to PULSE in the Config.h file:
// MOTION CONTROL -------------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#MOTION
#define STEP_WAVE_FORM             SQUARE // SQUARE, PULSE Step signal wave form faster rates. SQUARE best signal integrity.  Adjust
Test that, then change the jumpers to use a different microstep rate: for example 64, 32 or even 16 microsteps. It will speed up slewing considerably, although it will reduce the resolution overall. As I mentioned before, keep in mind the EQ3-2 isn't designed for much more than visual observing anyway.

Try these changes before you spend more money on different stepper drivers. I don't think the TMC2130s will make enough difference in your situation to be worth the money. Maybe when you get a faster controller board later.


Re: Encoders

bjaffa Jaffa
 

John,

I would like to reflash my EthernetAddOn with the latest stable changes you have for the board that would work with MaxPCB v3.16q but I have lost track of what
source I should be using with all the changes going on.  I am using a Teensy 4.0 with the W5500 module.

Thanks,

Brent


Re: wemos d1 + cnc + lv8729 #wemos

Khalid Baheyeldin
 

On Sun, Mar 28, 2021 at 02:39 PM, Pedro Miguel Barbosa Moutinho Nunes dos Reis wrote:
I'm on the Ramps now... the cncv3/wemos combo fried last night. At least the wemos.
But I believe the ramps have only jumpers like the cncv3.
Which means the LV8729 cannot mode switch on these two boards, although it can on others (e.g. Blue Pill, ...etc.)

Reflashed it with desired slew rate set to 4.0. No difference. As of now, the normal rate is 0.4º/s, then 5 and the fastest rate is 0.7º/s.
So it is the speed limit of the microcontroller.
You are better off with a faster MCU.

There is a tmc2130 that could speed up this a little right? 
The spi mode right?
Should speed things up a bit.
Depending on how reliably you can get different microsteps, and how far apart are they.
There is a formula in the code that does that calculation, and I extracted it in a previous thread.


Re: wemos d1 + cnc + lv8729 #wemos

Pedro Miguel Barbosa Moutinho Nunes dos Reis
 

On Sun, Mar 28, 2021 at 07:05 PM, Khalid Baheyeldin wrote:
They can, as far as the driver itself is concerned.
But the question is : is the board wired for dedicated pins going to each of MS0/MS1/MS2 for each axis?
Usually, the 3D printer and CNC boards use jumpers for that, so the microcontroller cannot control these 6 pins directly.
Does the CNCv3 board allow for that? I don't know, and I don't use it.
Someone who is more familiar with the schematic can pitch in.
I'm on the Ramps now... the cncv3/wemos combo fried last night. At least the wemos.
But I believe the ramps have only jumpers like the cncv3.

Reflashed it with desired slew rate set to 4.0. No difference. As of now, the normal rate is 0.4º/s, then 5 and the fastest rate is 0.7º/s.
There is a tmc2130 that could speed up this a little right? 
Like if I buy one of these
https://www.aliexpress.com/item/1005002249362653.html?spm=a2g0o.cart.0.0.6ed13c00qgWdXo&mp=1
The spi mode right?
I must think about it.


Re: Alt Az Tracking Adjustment Question

Ed Eastburn
 

Thank you for the info Ken.  I do have to adjust the backlash settings still.  That has some impact on tracking.  I am going to pin down the exact radius of the Alt bearing today, and with that info, have my machines make a new bearing out of 10mm aluminum.  The birch plywood bearing was a proof of concept prototype.

My first night out, I tried a 3 star alignment.  The first 2 stars were ~ 12 degrees off, mostly in Alt it appeared.  After the 3'rd alignment star the scope could repeatedly return to that star.  

I'm working out a procedure sheet, so that on the next sky test, I can check for proper setup of the scope, do a backlash adjustment, check for proper tracking, do an alignment, and then have specific stars picked out for that night to test for accurate gotos solely in Az and Alt.

Ken, are you creating a new Config.h file after each GR2 adjustment, or do you plug the new Steps per Degree, generated by the spreadsheet, into the existing Config.h file then doing a save?


Re: wemos d1 + cnc + lv8729 #wemos

Khalid Baheyeldin
 

On Sun, Mar 28, 2021 at 02:01 PM, Mike Ahner wrote:
it seems the LV8729 drivers can mode switch on the fly
They can, as far as the driver itself is concerned.
But the question is : is the board wired for dedicated pins going to each of MS0/MS1/MS2 for each axis?
Usually, the 3D printer and CNC boards use jumpers for that, so the microcontroller cannot control these 6 pins directly.
Does the CNCv3 board allow for that? I don't know, and I don't use it.
Someone who is more familiar with the schematic can pitch in.


Re: wemos d1 + cnc + lv8729 #wemos

Mike Ahner
 

Hi Pedro, I may have been wrong, it seems the LV8729 drivers can mode switch on the fly, according to the Wiki Step Stick Driver summary

If true, then changing the microsteps used during goto/s will speed up your slews noticeably. You change the 2 lines in Config.h to something less than 128, try 32 or 16, then reflash the Mega board and test. Keep in mind, an EQ3-2 will not slew as fast as a higher quality mount.

#define AXIS1_DRIVER_MICROSTEPS_GOTO  OFF //    OFF, n. Microstep mode used during gotos.                                     Option
#define AXIS2_DRIVER_MICROSTEPS_GOTO  OFF //    OFF, n. Microstep mode used during gotos.                                     Option


Re: Vixen Super Polaris and OnStep #superpolaris #wemos

Chad Gray
 

Hi Larry, thanks for the response. I am using my laptop computer with chrome browser.  I have a feeling whatever image of wiring everyone is referring to is missing now.

Chad

On Sun, Mar 28, 2021 at 12:59 PM larry leonard <tacnuke2011@...> wrote:
If you are viewing it on a phone or mobile device you have to view the Onstep page as a desktop site.


Re: Vixen Super Polaris and OnStep #superpolaris #wemos

Chad Gray
 

OH wow!  Yes!  This helps me a lot!  I will start reading it and planning out!

I am also using the Wemos and CNC because i am building the "micro scope"

Thanks so much Onno!

On Sun, Mar 28, 2021 at 11:28 AM Onno Kuijken <onno.kuijken@...> wrote:
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: wemos d1 + cnc + lv8729 #wemos

Pedro Miguel Barbosa Moutinho Nunes dos Reis
 

On Sun, Mar 28, 2021 at 06:17 PM, Khalid Baheyeldin wrote:
- You can speed this up by using Faster and Fastest from the Android App.

- What is your SLEW_RATE_BASE_DESIRED set to? Try setting it to 3.0 or 4.0 degrees.
The Arduino Mega2560 may not be able to do it, but you will know what the maximum speed will be for your steps/degree for that board.
That is after I set in fastest. But I'll recheck it.
I have the Slew rate set to 2.0 in the config. I'll try that tks


Re: wemos d1 + cnc + lv8729 #wemos

Khalid Baheyeldin
 

On Sun, Mar 28, 2021 at 01:15 PM, Pedro Miguel Barbosa Moutinho Nunes dos Reis wrote:
Based on the info on the webservers, I'm getting a max goto speed of 0.7º/s
Two notes:

- You can speed this up by using Faster and Fastest from the Android App.

- What is your SLEW_RATE_BASE_DESIRED set to? Try setting it to 3.0 or 4.0 degrees.
The Arduino Mega2560 may not be able to do it, but you will know what the maximum speed will be for your steps/degree for that board.


Re: wemos d1 + cnc + lv8729 #wemos

Pedro Miguel Barbosa Moutinho Nunes dos Reis
 

Based on the info on the webservers, I'm getting a max goto speed of 0.7º/s


Re: Vixen Super Polaris and OnStep #superpolaris #wemos

larry leonard
 

If you are viewing it on a phone or mobile device you have to view the Onstep page as a desktop site.


Re: Vixen Super Polaris and OnStep #superpolaris #wemos

Onno Kuijken
 

Hi Mod,

I have this in my config.h file:

// TIME AND LOCATION -------------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#TLS
#define TIME_LOCATION_SOURCE          DS3231 //    OFF, DS3231 (I2c,) DS3234 (Spi,) TEENSY (T3.2 internal,) or GPS source.       Option
                                          //         Provides Date/Time, and if available, PPS & Lat/Long also.

...

#define PPS_SENSE                     ON //    OFF, ON* enables PPS (pulse per second,) senses signal rising edge.           Option
                                          //         Better tracking accuracy especially for Mega2560's w/ceramic resonator.

For the wiring: I used this small module that is really intended for RasPi s


It has connections for supply and ground, and SCL/SDA for I2C. The fifth one is NC (Not Connected). From this pin I soldered a resistor to supply and a small piece of wire to pin 3 of the IC that is on the board. This pin is the INT/SQW pin and carries the 1 PPS signal





and the electrical connection to the OnStep controller is as follows



BE AWARE that the SDA and SCL lines on the OnStep controller are NOT the pins on the CNC shield that are labelled SDA/SCL, but the SDA/SCL pins on the R32 board itself.

Hope this helps,

BR/Onno


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

Khalid Baheyeldin
 

On Sun, Mar 28, 2021 at 11:48 AM, sami wrote:
Could the Bluetooth not be connected to the app because the motors are not connected?
No.
OnStep should work without any motors connected.


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

 

Could the Bluetooth not be connected to the app because the motors are not connected?


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

13081 - 13100 of 44715