Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different RPM Speed in Home and Settings-Screen #12

Open
Caliban2017 opened this issue Nov 11, 2021 · 5 comments
Open

Different RPM Speed in Home and Settings-Screen #12

Caliban2017 opened this issue Nov 11, 2021 · 5 comments
Labels
question Further information is requested

Comments

@Caliban2017
Copy link

Hello again,

i noticed another strange behaviour in this Script. The RPM Speed is a different in the Settings Screen, where i can set the Min and Max Position for the Blind then in the Home-Screen, where i actually control the Blinds. It is in the Settings always faster then in the Home Screen, it may cause the Problem the Motor will skip steps or have not enough Torgue to lift the Blind, when not running on 12v. For example i set the RPM to 30 in the Setup Routine, it can raise and lower the Blind in the Homescreen but when i try to lower the Blind in the Settingsscreen to set max Positions, the Motor has another higher pitched Sound and it runs faster but sometimes it stops for a Second and then it moves again. This is causing the Problem the min and max Position is not correct at the End. Its just running to fast. But it seems to depent on the set RPM in the Setup. Maybe there is a Value added to the RPM Value for the Setup-Screen? It feels always like i set 30 RPM and it moves like 30+20 RPM in the Settings Screen. Or maybe 30*2.

I tried to find something in the Code that is causing that, but my knowlegde seems to be on the limit, so i don't find it.

Maybe you can give some sort of Info how to fix it or fix it in your Code? It would be much easier to setup the Blinds at higher RPM without loosing Steps.

Greetings,
Caliban

@eg321
Copy link
Owner

eg321 commented Nov 17, 2021

Hi,

Usual operations and settings screen uses the same Stepper object with same RPM settings.
One difference only: "Settings" screen uses synchronous control of stepper, because no needs to process other steppers during this period. So, it's like exclusive access to controller.

I've checked at my installation (ESP32 + 12v Steppers) and do not see any difference in speed (Home / Settings screen).
As I remember, you're using ESP8266. Can you try your steppers with ESP32?

@eg321 eg321 added the question Further information is requested label Nov 17, 2021
@Frank1604
Copy link

I have exact the same issue here with an ESP8266. In the settings screen, the motor (12V, ULN2003) ist stuttering and sounds weird.
I tried with an ESP32 and this works fine.

@Caliban2017
Copy link
Author

Hello,

Yes, i use the ESP8266 and the 5V Stepper with ULN2003. The ESP32 works finde in this case. But i swapped out the ESP32 to two Wemos D1, because it is much faster with the 5V Motors. The ESP32 is just to slow to control more than two Motors. When all is set up correct, the Script is working so nice, it is already Part of my daily Smart Home use and always works like a charm. But the Setup is really annoying because of the Wipe Settings Thing and this Problem with the different RPM which causes the Stepper to slip/lose Steps.

@eg321
Copy link
Owner

eg321 commented Nov 29, 2021

Guys, regarding initial issue - different speed (and sound) at "home" and "settings" screens are ok, because they uses different methods as I mentioned above.
Codebase for ESP32 and ESP8266 almost the same. Sorry, I don't have ideas and time to look deeper now. Maybe it's some issue at used library... maybe not.

@Caliban2017 Anyway, "ESP32 is just to slow to control more than two Motors" looks strange for me. I'm using ESP32 with 3 motors connected everyday (12v). There is not many difference in speed between 1-2-3 motors in parallel. Can you check your installation with timer to be absolutely objective (1-2-3 steppers in parallel)? What mechanic are you using?

@Antikillerbm
Copy link

It's because in setup mode motor running with blocking sketch, intill the interrupt
In auto mode motor do the step, then do the sketch, then do another step. Probably esp32 working a bit faster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants