PWM and tone() incompatibility

[davidevertuani]

Basic Infos

Hardware

Hardware: NodeMCU ESP8266
Core Version: 2.4.0

Description

Hi. I'm having trouble using tone() and analogWrite() on the NodeMCU ESP8266.
Calling only tone() works fine, however calling analogWrite() on another pin, setting it to LOW and then calling tone() (on a different pin) only produces an annoying noise.

Sketch

void setup() {
  int pin = 12;
  pinMode(pin,OUTPUT);
  pinMode(14,OUTPUT);
  
  tone(pin,440);
  delay(1000);
  noTone(pin);
  //the tone is emitted correctly
  
  delay(1000);
  
  analogWrite(14,200);  
  delay(1000);
  analogWrite(14,0);
  
  tone(pin,440);
  delay(1000);
  noTone(pin);  
  //no tone is emitted
}

void loop() {
}

[minida28]

I have the same problem too.

Hardware: NodeMCU V1.0 (but I chose "Generic ESP8266 Module in Arduino IDE, v1.8.5)
Core: 00000000
SDK: 2.2.1(cfd48f3)
CPU Freq: 160

[minida28]

I tested with core 2.3.0 and it works!

Hardware: NodeMCU V1.0 (but I chose "Generic ESP8266 Module in Arduino IDE, v1.8.5)
Core: 2_3_0
SDK: 1.5.3(aec24ac9)
CPU Freq: 160

[AlfonsMittelmeyer]

A have the same problem too. After "tone" on one pin and then "analogWrite" on another pin, "tone" doesn't work anymore, when I use core version 2.4.1 for NodeMCU 1.0 (ESP-12 Module). When I use core version 2.3.0 the behavior is different, but also not usable: after "tone" on one pin "analogWrite" works correct at another pin, but after "noTone" "analogWrite" doesn't work anymore. I don't know, how to flash the "Generic ESP8266 Module" for my NodeMCU. All four flash modes caused an upload error.

[minida28]

Personally in my current project I prefer the tone(), so I have removed all analogWrite lines in my code.
I will wait for the solid solution then I will insert those lines again.

I don't know, how to flash the "Generic ESP8266 Module" for my NodeMCU.

I am on fairly recent Git core, and assuming you are using Arduino IDE like me, this is how I flash my NodeMCU V1.0.

I also have a NodeMCU V3 Lolin, not sure if it is a clone or genuine. I can flash it with the above settings but it won't run (won't work). But simply change the flash mode from DIO to QIO, then it works.

[AlfonsMittelmeyer]

Thank you, may be I had forgotten the Reset Method: "nodemcu". But the behavior is the same as with Nodecmu v1 core version 2.3. After using tone and then analogWrite and tone once more, analogWrite doesn't work anymore. Best would be, if I would write an own tone and analogWrite function, which work both together. But if I therefore would use timer1 probably the serial connection wouldn't work anymore.

[AlfonsMittelmeyer]

I wrote an own tone and noTone function with names itone and noItone. itone works with frequencies beginning with 1 Hz. But with core 2.4.1 itone has the same behavior as tone after using analogWrite. analogWrite is very aggressive. If called only once timer1 can't be used nomore for other purposes. analogWrite always grabs timer1 back. This means, if I need timer1, and I need it for precise measurements, then analogWrite mustn't be used.

These are my itone and noItone functions:

/*
    ESP8266 example for tone via timer1
    Hardware: NodeMCU
    2018
    tone using Timer
*/

#define ITONE_CYCLE 2500000 // 1 second cycle in 1/16 CPU clock (1/5 µs) for 80 MHz
// #define ITONE_CYCLE 5000000  // 1 second cycle in 1/16 CPU clock (1/5 µs) for 160 MHz
 
//=======================================================================
//       itone, noItone
//=======================================================================
byte _itonepin = D0;
byte _itoneval = HIGH;

void ICACHE_RAM_ATTR _onItoneTimerISR(){
  _itoneval ^= 1;
  digitalWrite(_itonepin,_itoneval);  //Toggle LED Pin
}
void itone(byte pin,unsigned long frequency) {
  timer1_detachInterrupt();
  timer1_attachInterrupt(_onItoneTimerISR);
  timer1_enable(TIM_DIV16, TIM_EDGE, TIM_LOOP);
  _itoneval = HIGH;
  _itonepin = pin;
  pinMode(pin,OUTPUT);
  digitalWrite(pin,HIGH);
  timer1_write(ITONE_CYCLE/frequency);
}

void noItone() {
  timer1_detachInterrupt();
}

//=======================================================================
//                               Setup
// we test the serial connection during itone running
// result: it still works
//=======================================================================
void setup()
{
  Serial.begin(115200);
  itone(D0,1); // LED blinks with 1 Hz
}
//=======================================================================
//                MAIN LOOP
//=======================================================================
void loop()
{
}

In the same kind also an analogWrite function could be written, which is compatible with a modified itone function.

Oh, the serial connecton still works, when timer1 is used for itone.

[santhosh000]

hi sir my linux arduino ide using to program nodemcu but port always not enable u have any solution for this problem sir

…

On Mar 22, 2018 6:22 PM, "AlfonsMittelmeyer" ***@***.***> wrote: I wrote an own tone and noTone function with names itone and noItone. itone works with frequencies beginning with 1 Hz. But with core 2.4.1 itone has the same behavior as tone after using analogWrite. analogWrite is very aggressive. If called only once timer1 can't be used nomore for other purposes. analogWrite always grabs timer1 back. This means, if I need timer1, and I need it for precise measurements, then analogWrite mustn't be used. These are my itone and noItone functions: /* ESP8266 example for tone via timer1 Hardware: NodeMCU 2018 tone using Timer */ #define ITONE_CYCLE 2500000 // 1 second in 1/16 CPU clock for 80 MHz // #define ITONE_CYCLE 5000000 // 1 second in 1/16 CPU clock for 160 MHz //======================================================================= // itone, noItone //======================================================================= byte _itonepin = D0; byte _itoneval = HIGH; void ICACHE_RAM_ATTR _onItoneTimerISR(){ _itoneval ^= 1; digitalWrite(_itonepin,_itoneval); //Toggle LED Pin } void itone(byte pin,unsigned long frequency) { timer1_detachInterrupt(); timer1_attachInterrupt(_onItoneTimerISR); timer1_enable(TIM_DIV16, TIM_EDGE, TIM_LOOP); _itoneval = HIGH; _itonepin = pin; pinMode(pin,OUTPUT); digitalWrite(pin,HIGH); timer1_write(ITONE_CYCLE/frequency); } void noItone() { timer1_detachInterrupt(); } //======================================================================= // Setup // we test the serial connection during itone running // result: it still works //======================================================================= void setup() { Serial.begin(115200); itone(D0,1); // LED blinks with 1 Hz } //======================================================================= // MAIN LOOP //======================================================================= void loop() { } In the same kind also an analogWrite function could be written, which is compatible with a modified itone function. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4349 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ajj29SVBP_1HaHI3hjtvH2gNU3vG69ABks5tg55zgaJpZM4SBV0J> .

[AlfonsMittelmeyer]

I use the arduino ide on my raspberry pi3 and port /dev/ttyUSB0 works without any problems. You should try this command without NodeMCU connected and after with NodeMCU connected:

ls /dev/tty*

then you may compare, whether the serial connection was detected and with which name

[santhosh000]

ls /dev/tty* am try this one in terminal but output is lot more to come like this

…

On Mar 23, 2018 12:26 AM, "AlfonsMittelmeyer" ***@***.***> wrote: I use the arduino ide on my raspberry pi3 and port /dev/ttyUSB0 works without any problems. You should try this command without NodeMCU connected and after with NodeMCU connected: ls /dev/tty* then you may compare, whether the serial connection was detected and with which name — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4349 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ajj29bruoe04s6rgsQQikY4Cxb_lrh-6ks5tg_PcgaJpZM4SBV0J> .

[AlfonsMittelmeyer]

yes, you see a lot beginneng with /dev/tty and you should try this with and without the NodeCMU connected and then you can compare, whether there is one more with connected NodeCMU.

[santhosh000]

ok sir you are in whatsapp or Skype because its useful for my further doubts am more interested in using microcontroller like arduino ,nodemcu and raspberry pi

…

On Mar 23, 2018 3:13 PM, "AlfonsMittelmeyer" ***@***.***> wrote: yes, you see a lot beginneng with /dev/tty and you should try this with and without the NodeCMU connected and then you can compare, whether there is one more with connected NodeCMU. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4349 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ajj29b5Aeuz-OvUT_lPjt0nZAl8yjOZoks5thMOxgaJpZM4SBV0J> .

[AlfonsMittelmeyer]

was there one one /dev/tty* ? The raspberry po3 is my favored desktop py and I don't like to use its GPIO ports. What if I would destroy my raspberry? But if something would happen to the NodeCMU, that's not any problem.

[davidevertuani]

Please @AlfonsMittelmeyer @santhosh000 stop, this is an esp8266 issue not a Raspberry support forum.

[AlfonsMittelmeyer]

I don't want to talk about the raspberry specially, because it's only my favored linux pc. And talked about connecting the NodeCMU with a linux pc.

[santhosh000]

great

…

On Mar 23, 2018 3:38 PM, "AlfonsMittelmeyer" ***@***.***> wrote: I don't want to talk about the raspberry specially, because it's only my favored linux pc. And talked about connecting the NodeCMU with a linux pc. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4349 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ajj29XewF9KkMFt46ZQAkcwwAcPtCUlUks5thMmpgaJpZM4SBV0J> .