I looked at that but the limitation was the pulley size. I could not fit greater than 30 tooth inside. outside I put 60tooth and have room for 80+

I use the same wiring design from my CGE.PRO. 18awg 4wire and shield to aircraft plugs. 4pin for stepper 8 or 10 pin for switches. I don't use connectors at the head unit, only at the controller. Cont

Sure, I agree, but why not use a proper design anyway. Sorry, the engineer in me leaks.

Yes it works on Dec as well. I am concerned about clearance. I will have to measure it now that it is working.

Literally, I switched the direction of the worm so the shaft is on the other side, so I would not have gouge out the inside. I also retain the home and limit switches. Then i noticed that I could moun

I use the same steppers with 90lbs on a cge.pro I use 2130 drivers. I use 24v. Try 24v.

#wemos #S6 #EQ3 #fysetc #wifi

Did maiden of avx I converted last night. Stepper 400, Microsteps 16, pulley 3.75, worm 144. Three OnstepX modules to test, S6, ESP32, Teensy

well, i got the same issue on another PC. You have never been wrong, so I will believe I have something weird, and some day I will find it. Cheers and sorry for wasting time. Thanks for checking. CW

to reproduce: set location and utc to 0 in sws or use :ENVRESET# fire up SP with location set to salinas, ca. look at utc it only happens in the case of zero utc and only in sp. I set nothing in prope

Vlad, I don't have a problem setting time. I am trying to report a bug In sp Yes ascom, android, sws etc all set time fine.

Sky Planetarium sets my utc to -8. If I try to set time using android or sws after SP, I end up in wrong time

Then I need to report a bug in SP. Do the following. ":ENVRESET#" OR using SWS set the location and UTC to all zeros. fire up SP. it set my UTC to -8 seen on the SWS.

I live in California. I have set location in Sky Planetarium to Salinas, CA. So I do a new compile, then ":NVRESET#" and bring up SP with it set to update location and time. SP sets the UTC offset to

if you look at the comment line for Pinmap in config.h you can see that there is a choice including "MiniPCB2" so there must be a difference somewhere.

#mini

I assume from this issue that you use windows. If so it often loses track of the devices plugged in. I still have a RC controller that cannot be recognized by only one of my PC after a year of didling

Also dont you need to set the pinmap to MiniPCB2 for the 4.0

#mini

i just used 10.5.J and the external NVram tick no longer works. I am giving up on the S6.

I just looked at the pins. they are different. did you go to MiniPCB2? or just stick in the 4.0 chip?

#mini

Based on your success I retested my setup. Good news 2.2 library works with one i2c device and stock nvram. It fails if you add a second device. Add a MCP23017 or ds3231 and it locks up reading the nv