Let's Control It

Posted: **26 Feb 2021, 12:09**

Hi,

anyone used easydriver with espeasy?

TIA?

Posted: **26 Feb 2021, 12:22**

I think you need to give slightly more information here

No idea what "easydriver" is.
Any link?

Is it this board? https://www.sparkfun.com/products/12779

Posted: **26 Feb 2021, 15:09**

https://www.schmalzhaus.com/EasyDriver/

you can use it without specific libraries,

Posted: **26 Feb 2021, 20:07**

TD-er wrote: ↑26 Feb 2021, 12:22 I think you need to give slightly more information here

No idea what "easydriver" is.
Any link?

Is it this board? https://www.sparkfun.com/products/12779

yes, this one. WIth one advantage: also works with 3V3. See specs.

Posted: **27 Feb 2021, 13:16**

How could i loop this in espeasy?

Code: Select all


defs:

// variables will change:
long previousmotorMicros = 0; // will store last time motor was updated

// the follwoing variable is a long because the time, measured in milliseconds
// will quickly become a larger number than can be stored in an int.
long motorinterval = 120;     // microseconds high low step original 180
long previousldrMicros = 0;
long ldrreadinterval = 10000000; // 10 seconds
long currentMicros;


loop:

if (motor_mode == 'R') {
    digitalWrite(MotorEnable, LOW);
    digitalWrite(MotorSleep, HIGH);

    if (dir != prevdir) {
      prevdir = dir;
      delay(1500); // pause to change direction run
    }

    if (currentMicros - previousmotorMicros > motorinterval) {
      previousmotorMicros = currentMicros;
      if (stepp == LOW)
        stepp = HIGH;
      else
        stepp = LOW;
      digitalWrite(MotorDir, dir);
      digitalWrite(MotorStep, stepp);
    }
  }
  if (motor_mode == 'S') {
    digitalWrite(MotorEnable, HIGH);
    digitalWrite(MotorSleep, LOW);
  }
}

Posted: **28 Feb 2021, 19:06**

TD-er wrote: ↑26 Feb 2021, 12:22 I think you need to give slightly more information here

No idea what "easydriver" is.
Any link?

Is it this board? https://www.sparkfun.com/products/12779

any hint?

Posted: **28 Feb 2021, 20:34**

I don't think I do understand what you're asking here.

Posted: **28 Feb 2021, 23:42**

TD-er wrote: ↑28 Feb 2021, 20:34 I don't think I do understand what you're asking here.

how to have it working with espeasy? and hoe could i adapt the code (previous post) to it?

Posted: **01 Mar 2021, 09:29**

Where does this code come from? It is not part of the ESPEasy code.

Judging the code you posted, you need 4 GPIO pins for it, and I don't know any example plugin which you can easily modify for this.
The Wemos motorshield does use I2C to communicate.

Also the code is using "delay(1500)", which is not a really good idea to use in ESPEasy plugin code, so I guess it is not as simple as cut-and-paste somewhere in the code to get it to work.

Maybe on the playground there is a plugin already resembling what's needed for this?

Posted: **01 Mar 2021, 14:08**

TD-er wrote: ↑01 Mar 2021, 09:29 Where does this code come from? It is not part of the ESPEasy code.

Judging the code you posted, you need 4 GPIO pins for it, and I don't know any example plugin which you can easily modify for this.
The Wemos motorshield does use I2C to communicate.

Also the code is using "delay(1500)", which is not a really good idea to use in ESPEasy plugin code, so I guess it is not as simple as cut-and-paste somewhere in the code to get it to work.

Maybe on the playground there is a plugin already resembling what's needed for this?

this code is the motor driving of what i have working on a arduino nano for curtains control. now i want to migrate it to espeasy to integrate it with HA. simple.

the question was about using the same driver (easydriver) and how to adapt the code to the espeasy rules, with gpio,N,1 or gpio,N,0 to make it run......

i purchased an adafruit motor driver, and well, let's see how ti work.

but i would not discard the espeady, as it is quiet powerfull.

Posted: **01 Mar 2021, 14:18**

I for sure can understand why you would like to use it with ESPEasy.
It is just that support for that driver may require a bit more work than just copy/paste of that code into an existing plugin.

Posted: **01 Mar 2021, 19:45**

ok, i purchased the https://www.letscontrolit.com/wiki/inde ... ield_v2%22

as soon i receive it, i will ask you for help. Is it possible?

TIA

Posted: **01 Mar 2021, 19:51**

TD-er wrote: ↑01 Mar 2021, 09:29 Where does this code come from? It is not part of the ESPEasy code.

Judging the code you posted, you need 4 GPIO pins for it, and I don't know any example plugin which you can easily modify for this.
The Wemos motorshield does use I2C to communicate.

Also the code is using "delay(1500)", which is not a really good idea to use in ESPEasy plugin code, so I guess it is not as simple as cut-and-paste somewhere in the code to get it to work.

Maybe on the playground there is a plugin already resembling what's needed for this?

Is the wemos motorshield suitble for steppers?

Posted: **01 Mar 2021, 22:57**

Doesn't look like it is.
But P048 for the AdaFruit motorshield v2 looks like it is also supporting stepper drivers.
If I'm not mistaken, there are also clone boards for that shield if AdaFruit is not selling it anymore.

Posted: **02 Mar 2021, 13:27**

thx. regarding the P048, can ypu please share the connection scheme? and the command set to use?

Posted: **02 Mar 2021, 14:36**

pw444 wrote: ↑02 Mar 2021, 13:27 thx. regarding the P048, can ypu please share the connection scheme? and the command set to use?

Commands are documented in the RTD documentation: https://espeasy.readthedocs.io/en/lates ... #p048-page
Adafruit usually does have quite extensive tutorials: https://learn.adafruit.com/adafruit-mot ... o/overview

Posted: **03 Mar 2021, 14:18**

Ok,

having this instruction, how to have it looping?

MotorShieldCMD,Stepper,1,Forward,1,Interleave

My logic is simple.... motor instructions will keep looping, either Release, Forward or Backward, depending on two variables: RUN and DIRECTION. RUN can be 1,2 or 3 and direction 1 or 2.

But i'm a little lost.

Posted: **03 Mar 2021, 14:41**

Maybe the (recently added) loop timer can be of any help here?
https://espeasy.readthedocs.io/en/lates ... oop-timers.

For performance reasons I would not try to set the loop timer to a very short interval.
So maybe in the rules when handling this timer you may determine the number of steps needed and call for a command to make those steps (e.g. not trying to loop every 10 msec for example to make 1 step)

Posted: **03 Mar 2021, 16:03**

thx. my motor shield shall arrive the next days,...

i'll let you know.

any other steppers plugins available?

Posted: **03 Mar 2021, 23:03**

pw444 wrote: ↑03 Mar 2021, 16:03 [...]
any other steppers plugins available?

Not that I am aware of.

Posted: **10 Mar 2021, 17:35**

Hi, i tried to make it work, but no luck.

It worked only as a shield on the Arduino Uno board.

Can you please share the connection diagram used when it worked at development?

Thx in advance.

Posted: **10 Mar 2021, 21:38**

I did not develop that plugin.

Posted: **13 Mar 2021, 14:12**

i got it. will later draw it. now i will start to make it work.

Posted: **15 Mar 2021, 13:20**

TD-er wrote: ↑03 Mar 2021, 14:41 Maybe the (recently added) loop timer can be of any help here?
https://espeasy.readthedocs.io/en/lates ... oop-timers.

For performance reasons I would not try to set the loop timer to a very short interval.
So maybe in the rules when handling this timer you may determine the number of steps needed and call for a command to make those steps (e.g. not trying to loop every 10 msec for example to make 1 step)

Hya,

tried the following:

Code: Select all

On System#Boot do    //When the ESP boots, do
  looptimerset_ms,1,1     // Start loop timer 2, 2500 msec interval
endon


On Rules#Timer=1 do
    MotorShieldCMD,Stepper,1,Forward,20,double
    loopTimerSet_ms,1,1
    timerResume,1
endon

But it stops for 1 second.

The idea is to have the motor running on a loop, back or forward until it's demanded to stop. any hint?

Posted: **15 Mar 2021, 13:25**

A looptimer doesn't need to be restarted, nor resumed in the handler that handles the (loop) timer.
And like I said before you should use a slightly longer interval.
For example start first with an interval of like 100 or 500 msec to see if the rules are working.
Wouldn't be surprised if this may crash the unit, when running at 1 msec interval.

Posted: **17 Mar 2021, 20:00**

I have now the follwing:

Code: Select all

On System#Boot do    //When the ESP boots, do
  looptimerset_ms,1,10     // Start loop timer 2, 10 msec interval
endon

On Rules#Timer=1 do
    if %v1%=1
       MotorShieldCMD,Stepper,1,Forward,50,single
    endif
    if %v1%=0
       MotorShieldCMD,Stepper,1,Backward,50,single
    endif
endon

on OPEN#status do
   if %eventstatus%=0
      let 1,1
    else
      let 1,0
   endif
endon

problem: by status chance, so %v1% change, motor dos not change direction.

i can see status change by devices.

Posted: **17 Mar 2021, 20:08**

Code: Select all

on OPEN#status do
   if %eventstatus%=0
      let 1,1
    else
      let 1,0
   endif
endon

Replace %eventstatus% with %eventvalue% (or %eventvalue1% to make it more consistent when using multiple event values)

Posted: **18 Mar 2021, 13:59**

you're right. i miread the error. sorry for such stupid question.

Posted: **18 Mar 2021, 17:42**

pw444 wrote: ↑18 Mar 2021, 13:59 you're right. i miread the error. sorry for such stupid question.

Nope, not stupid... or else I would also be stupid as it happens to me all the time too

Posted: **18 Mar 2021, 22:02**

i'm trying this one, but there is a pause on next loop.

Is there a way to keep it running, without pause beween?

Code: Select all

On System#Boot do    //When the ESP boots, do
  let,1,0
  let,2,0
  asyncevent,loop // Trigger the loop
endon

on loop do
    if %v1%=0
       MotorShieldCMD,Stepper,1,Forward,100,single
    endif
    if %v1%=1
       MotorShieldCMD,Stepper,1,Backward,100,single
    endif
    asyncevent,loop
endon

on OPEN#status do
   if %eventvalue%=1
      let,1,1
      asyncevent,loop
    else
      let,1,0
      asyncevent,loop
   endif
endon

Posted: **18 Mar 2021, 22:16**

Have you looked at the log via usb?
How long is that delay?

Posted: **18 Mar 2021, 22:43**

Why don't you use the loop timer?

See: https://espeasy.readthedocs.io/en/lates ... =looptimer

Posted: **19 Mar 2021, 07:30**

TD-er wrote: ↑18 Mar 2021, 22:43 Why don't you use the loop timer?

See: https://espeasy.readthedocs.io/en/lates ... =looptimer

He had that, see:

pw444 wrote: ↑17 Mar 2021, 20:00 I have now the follwing:
Code: Select all
On System#Boot do    //When the ESP boots, do
  looptimerset_ms,1,10     // Start loop timer 2, 10 msec interval
endon

...(partially removed, Ath)

but I think the 10 msec interval just was a bit too much for an ESP,
or else I don't know why that solution was abandoned

Posted: **19 Mar 2021, 10:43**

Ah yes, I remember about the looptimer.

I'm not sure if the rules can process events fast enough as is required here.
Maybe the only thing that makes sense here, is to add a new command to the motorshield to set a continous speed and thus calling it from the PLUGIN_TEN_PER_SECOND or maybe even PLUGIN_FIFTY_PER_SECOND.
Then the rules only have to act on changes.
Or maybe a non-blocking call to make exactly N steps and get an event with the number of steps made when you stop it. (or when the run is interrupted)
I don't think making lots of small steps via rules is doable.

Posted: **19 Mar 2021, 13:55**

add a new command to the motorshield to set a continous speed and thus calling it from the PLUGIN_TEN_PER_SECOND or maybe even PLUGIN_FIFTY_PER_SECOND.

and how?

what i want: forward, backward and release. that's all.

it will move curtains, 1 meter long or 10 meter long, so, i want to open, close, stop anywhere in the way.

Posted: **19 Mar 2021, 14:14**

Do you have timing stats of your run with the PLUGIN_WRITE call of the P048 motorshield plugin?
Problem is that the steps are done in a loop, so a single call to the MotorShieldCMD is blocking.
This means it will never run smooth if we run it in various calls.

So I was wondering if it is acceptable if we run it in let's say 50 single steps a second.

Another way can be to add some kind of stepper motor worker to regularly feed the stepper library a new call (e.g. in every loop() call of ESPEasy)

What I find intriguing is that it does have a controller, but the libray only allows to perform a single step at a time.
So why not implement a bit more high level command on that controller to allow to make N steps on the controller.

Posted: **19 Mar 2021, 15:24**

on loop do
if %v1%=0
MotorShieldCMD,Stepper,1,Forward,100,single
endif
if %v1%=1
MotorShieldCMD,Stepper,1,Backward,100,single
endif
asyncevent,loop
endon

i'm using asyncevent as from example. but as docs, asyncevent goes to a quee.

What the oposit of asyncevent, thus making it run without going to the queue?

Posted: **19 Mar 2021, 15:28**

Ath wrote: ↑18 Mar 2021, 22:16 Have you looked at the log via usb?
How long is that delay?

the log, showing the intervals.

Code: Select all

136357: Stepper1->Forward Steps: 100 SINGLE
136717: ACT  : asyncevent,loop
136731: EVENT: loop
136746: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
136758: Stepper1->Forward Steps: 100 SINGLE
137122: ACT  : asyncevent,loop
137140: EVENT: loop
137155: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
137167: Stepper1->Forward Steps: 100 SINGLE
137558: ACT  : asyncevent,loop
137573: EVENT: loop
137588: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
137600: Stepper1->Forward Steps: 100 SINGLE
137959: ACT  : asyncevent,loop
137973: EVENT: loop
137988: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
138000: Stepper1->Forward Steps: 100 SINGLE
138394: ACT  : asyncevent,loop
138410: EVENT: loop
138425: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
138438: Stepper1->Forward Steps: 100 SINGLE
138820: ACT  : asyncevent,loop
138840: EVENT: loop
138855: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
138867: Stepper1->Forward Steps: 100 SINGLE
139249: ACT  : asyncevent,loop
139263: EVENT: loop
139278: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
139290: Stepper1->Forward Steps: 100 SINGLE
139673: ACT  : asyncevent,loop
139689: EVENT: loop
139703: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
139715: Stepper1->Forward Steps: 100 SINGLE
140101: ACT  : asyncevent,loop
140118: EVENT: loop
140133: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
140145: Stepper1->Forward Steps: 100 SINGLE
140526: ACT  : asyncevent,loop
140540: EVENT: loop
140555: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
140567: Stepper1->Forward Steps: 100 SINGLE
140934: ACT  : asyncevent,loop
140947: EVENT: loop
140984: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
141000: Stepper1->Forward Steps: 100 SINGLE
141361: ACT  : asyncevent,loop
141374: EVENT: loop
141389: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
141401: Stepper1->Forward Steps: 100 SINGLE
141790: ACT  : asyncevent,loop
141809: EVENT: loop
141824: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
141837: Stepper1->Forward Steps: 100 SINGLE
142195: ACT  : asyncevent,loop
142209: EVENT: loop
142225: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
142237: Stepper1->Forward Steps: 100 SINGLE
142624: ACT  : asyncevent,loop
142640: EVENT: loop
142655: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
142667: Stepper1->Forward Steps: 100 SINGLE
143031: ACT  : asyncevent,loop
143045: EVENT: loop
143061: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
143073: Stepper1->Forward Steps: 100 SINGLE
143458: ACT  : asyncevent,loop
143472: EVENT: loop
143490: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
143502: Stepper1->Forward Steps: 100 SINGLE
143882: ACT  : asyncevent,loop
143896: EVENT: loop
143911: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
143926: Stepper1->Forward Steps: 100 SINGLE
144308: ACT  : asyncevent,loop
144321: EVENT: loop
144335: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
144349: Stepper1->Forward Steps: 100 SINGLE
144732: ACT  : asyncevent,loop
144750: EVENT: loop
144765: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
144779: Stepper1->Forward Steps: 100 SINGLE
145159: ACT  : asyncevent,loop
145171: EVENT: loop
145188: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
145200: Stepper1->Forward Steps: 100 SINGLE
145582: ACT  : asyncevent,loop
145598: EVENT: loop
145614: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
145626: Stepper1->Forward Steps: 100 SINGLE
146009: ACT  : asyncevent,loop
146022: EVENT: loop
146037: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
146049: Stepper1->Forward Steps: 100 SINGLE
146433: ACT  : asyncevent,loop
146447: EVENT: loop
146462: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
146474: Stepper1->Forward Steps: 100 SINGLE
146857: ACT  : asyncevent,loop
146871: EVENT: loop
146886: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
146898: Stepper1->Forward Steps: 100 SINGLE
147281: ACT  : asyncevent,loop
147296: EVENT: loop
147314: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
147327: Stepper1->Forward Steps: 100 SINGLE
147712: ACT  : asyncevent,loop
147726: EVENT: loop
147744: ACT  : MotorShieldCMD,Stepper,1,Forward,100,single
147758: Stepper1->Forward Steps: 100 SINGLE

Posted: **19 Mar 2021, 15:46**

No that's not what I meant.
I mean the "timing stats" from the timing stats page (if it is present in your build, should be either "custom" or "normal" build)

Posted: **19 Mar 2021, 16:09**

the build: ESP_Easy_mega_20201227_test_ESP8266_4M1M_VCC

where do i find timing stats?

Posted: **19 Mar 2021, 16:35**

That's a build with "test" in the name, so that one doesn't have the timing stats page to limit build size a bit to make it all fit.

Posted: **19 Mar 2021, 16:40**

ok, builds with P048 plugin? i only found on this test one.

Posted: **19 Mar 2021, 17:40**

but I think the 10 msec interval just was a bit too much for an ESP,
or else I don't know why that solution was abandoned

because i cannot get it smoth, also makes delays between steps.

Let's Control It

easydriver stepper driver

easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver

Re: easydriver stepper driver