Date   

CGE Pro Motor Mounts

Jeff Latsch
 

Almost ready....
MiniPCB and Hand Control soldered. Thank You George.  Pulleys and belts here Friday. Finished the motor mounts tonight.   The motor mounts were designed to allow belt adjustment and if need be I can put the OEM motors back on temporarily. If I use a 64mm belt I should be able to reinstall the unaltered OEM covers.

I would gladly provide the cad file to anyone interested. 


Re: MKS GenL1 with TMC2130 SPI mode switch problem

Howard Dutton
 

On Tue, Jul 14, 2020 at 12:59 PM, Markus Kempf wrote:
What could be the reason for this? I have checked the SPI cabling many times and believe there is no fault.
I've suspected the new / fancy micro-step mode switching code in the master branch had a bug WRT mode switching on the Mega2560 (only.)  I've seen others struggle but never got solid feedback as to if it worked or not (simultaneous new user mistakes going on muddying the waters.)

So I took another careful look at the HAL again and found the problem (or a problem anyway) there was an erroneous register bit pattern in AXIS2.

Download and try again.


MaxESP32 board USB jumper

Drew 🔭📷🚴‍♂️
 

Before I butcher one of my micro-USB cables I thought I should ask. Is there a commercial jumper cable available to go between the micro-usb on the chips (ESP32 or Wemos 8266 and the 3 pin dupont jack on the MaxESP boards (and I am sure several others)?


Re: Problem connecting to wemos d1 mini pro with android devices

schinos@...
 

Hi Howard,

I basically believe that also, that is that i have done something "unique" exactly because no one else has had this problem so far.
I hope that is not something stupid enough to say we have thrown so many hours to the garbage.
Those are the reasons why i have tried all the above.
To the matter now: i have downloaded the latest master and changed in the ONSTEP config all setting relevant to my setup but not baud rates. In the wifi config nothing was changed. All flashed successfully and the esp8266 board firmware was left to 2.4.2
Flashing blue led for 35 - 42 seconds (average).
First attempt to connect with the mobile device accepted the passphrase but stuck on "Obtaining IP Address" were after a while it just dropped trying and connected to me home ssid. The rest hand triggered retries to connect to the wifi went form "Connecting" to "Saved" again and again.
The second mobile device never even moved form the passphrase screen saying "could not connect to network" but on the wifi list it said "Authentication error occurred". I tried powering off and on again Maxpcb2 but same results.

Then downloaded firmware 2.7.2 and reflashed the wemos board.
More or less the same time flashing blue until solid.
None of the mobile device accepted the passphrase. The first mobile device reappeared the passphrase screen after i entered it for the first time. Consecutive MaxPCB power off and on did not change the behavior.

Is there a way to get extended wifi debug info from the wemos just in case something stands out and points to the problem?

Thank you very much
Konstantinos


Re: MKS GenL1 with TMC2130 SPI mode switch problem

Khalid Baheyeldin
 

On Tue, Jul 14, 2020 at 03:59 PM, Markus Kempf wrote:
So I enabled MICROSTEPS_GOTO with 1
Using 1 means full step which is very rough and may cause resonance.
Are you sure the DEC axis is not emitting a high pitched sound when it is not moving?
If it does, then it is stalling, and you need to use 1/4 microstep (or less) for MICROSTEPS_GOTO.


MKS GenL1 with TMC2130 SPI mode switch problem

Markus Kempf
 

with MICROSTEPS_GOTO OFF both axes show normal behaviour although with the default gear settings and 32 Microsteps I get only 1deg/s slew rates. So I enabled MICROSTEPS_GOTO with 1, resulting in slew speeds of 4 deg/s. Exercising the motors to a target with about equal distance in RA/DEC, the RA axis shows the expected movements and ramps up and down nicely. The DEC axis shows the same slow movement as in MICROSTEP_GOTO OFF but pretends that it moved the same distance. There are no error messages (DRIVER_STATUS TMC_SPI). What could be the reason for this? I have checked the SPI cabling many times and believe there is no fault.

Markus


Re: STM32 and Skysafari goto setup

Khalid Baheyeldin
 

On Tue, Jul 14, 2020 at 01:13 PM, Khalid Baheyeldin wrote:
the STM32 can do 3.75 deg/secs slewing at Fastest setting.
Not the Fastest. Just Normal. And these are set from the Android app. No idea what Sky Safari can or cannot do.

In your Config.h, change the following:

#define STEP_WAVE_FORM        PULSE

#define SLEW_RATE_BASE_DESIRED 3.75
#define AXIS1_DRIVER_MICROSTEPS_GOTO   8
#define AXIS2_DRIVER_MICROSTEPS_GOTO   8

Then try again, and see if it is faster.
You may need to adjust the last 3 ones after you actually test the motors, in case they are stalling.


Re: STM32 and Skysafari goto setup

Khalid Baheyeldin
 

With the parameters I mentioned before (400, 64, 1, 36), the STM32 can do 3.75 deg/secs slewing at Fastest setting.

That is without MICROSTEPS_GOTO. If you use that, and set it to 4 or 8, you will be able to have faster slewing.
You can also make it go faster by changing the WAVE_FORM to PULSE.

Try those and let us know.


Re: STM32 and Skysafari goto setup

 

使用Skysafari goto时反应很慢,不知道是不是使用STM32板的关系,也许是极限了吧。

Using skysafari GOTO feel response feel very slow, wonder is STM32 processing speed reach the max limits.


Re: GPS compile error with MKS Gen L1

Markus Kempf
 

added

#define SerialGPSBaud 4800

still no function. Will wait for my new module.

Markus
Am 14/07/2020 um 13:06 schrieb Howard Dutton:

Is this a 9600 baud device?  Remember there is a setting for that too.


Re: new FYSETC S6 build

Markus Kempf
 

Howard,

just tried it with this little change to the Pins.Ramps14.h file:

#define LEDnegPin            13 \\Aux0 = 11

and it works beautifully and does no harm. It lights up the little blue LED. Would be nice to have this in the config.h as an option (eg. EnablePCBStatusLed = ON changes Aux0 to 13). It could even be in parallel to the regular Aux0 pin (11) with some code changes.

Markus

Am 14/07/2020 um 13:27 schrieb Howard Dutton:

On Tue, Jul 14, 2020 at 04:14 AM, Markus Kempf wrote:
Same thing on the MKS GenL, that has also the D13 pin to switch the LED next to the power led to be used as a OnStep status LED
Not something I want to get into.


Re: OnStep + ESP32 (WemosD2R32) + Motor Shield V3 + Wii Nunchuk

chris
 

Oh NOOOOOOOOOOO. after several Months waiting and several hours trying to understand why the program would not compile I have realized they have sent the incorrect board. they have sent a Wemos D1R2 not a D1R32.  AGGGGGGHHHHHHHHHHHHHHHHHHHGGG.


Re: stand alone operation

Howard Dutton
 

On Tue, Jul 14, 2020 at 04:35 AM, <gsmclean2@...> wrote:
I will go back an look at my scratching of this connection. The location shown in the picture is unclear to me
Without cutting that trace on the Teensy the MiniPCB2 will "power up" with just the USB plugged in (5V and 3.3V become available but the motors will no run.)  I.e. you will see the power LED light.

Either way, trace cut or not, plugging into the coaxial DC connector should power up (again that power LED will light.)


Re: stand alone operation

Gary McLean
 

I will go back an look at my scratching of this connection. The location shown in the picture is unclear to me.
I was thinking the same and have gone back to that connection a number of times. Will head that way again.
Thanks Howard for all of your great work.
Gary
 


Re: new FYSETC S6 build

Howard Dutton
 
Edited

On Tue, Jul 14, 2020 at 04:27 AM, Howard Dutton wrote:
On Tue, Jul 14, 2020 at 04:14 AM, Markus Kempf wrote:
Same thing on the MKS GenL, that has also the D13 pin to switch the LED next to the power led to be used as a OnStep status LED
Not something I want to get into.
The heater outputs are supported in OnStep as auxiliary features, dew heaters, switching EL panels for flats, etc.
Mapping status LED's over that is not the way to go.


Re: new FYSETC S6 build

Howard Dutton
 

On Tue, Jul 14, 2020 at 04:14 AM, Markus Kempf wrote:
Same thing on the MKS GenL, that has also the D13 pin to switch the LED next to the power led to be used as a OnStep status LED
Not something I want to get into.


Re: stand alone operation

Howard Dutton
 
Edited

On Tue, Jul 14, 2020 at 04:23 AM, <gsmclean2@...> wrote:
My MiniPCB2 requires both motor power connection and a usb to computer connection to power up.
Is this normal or have I missed something.
Should power up with just the coaxial DC connection.

Power from the USB into the Teensy should have been physically disconnected as instructed in the MiniPCB2 Wiki.


stand alone operation

Gary McLean
 

My MiniPCB2 requires both motor power connection and a usb to computer connection to power up.
Is this normal or have I missed something.  MiniPCB2 and SHC working. WIFI  working.
Thanks to all
Gary


Re: GPS compile error with MKS Gen L1

Markus Kempf
 

should be a 9600 baud device, but will try 4800 baud to be NMEA compliant.

Markus

Am 14/07/2020 um 13:06 schrieb Howard Dutton:

Is this a 9600 baud device?  Remember there is a setting for that too.


Re: new FYSETC S6 build

Markus Kempf
 

if nothing is connected to the heater or fan terminals, it should not matter if the FET's get switched but the LED will turn on (if I read the schematics right). Therefore it could be possible to use them for the OnStep status leds without having the need to solder a LED and a resistor. Same thing on the MKS GenL, that has also the D13 pin to switch the LED next to the power led to be used as a OnStep status LED. Just ideas if you can find the time...

Markus

Am 13/07/2020 um 11:54 schrieb Howard Dutton:

On Mon, Jul 13, 2020 at 01:05 AM, Markus Kempf wrote:
Btw. is it possible to switch the (BED/E0/E1/E2) LEDs in software? Would be nice if OnStep could use them.
Those are coupled to the heater MOSFET's.  When you use those to switch something, like a dew heater, the corresponding LED should turn on.