Timers interfere about duetimer

[ivanseidel]

Could you post the entire sketch code so that I can investigate it deeper?

[ast]

I did some changes but I still get unexpected behavior. messageTestis called 1000/s. handleris not called at all.

#include <CmdMessenger.h>
#include <DueTimer.h>

CmdMessenger cmdMessenger = CmdMessenger(Serial);

enum
{
  kSetFreq              , // Command to request led to be set in specific state
  kStatus               , // Command to report status
};

// Attached callbacks
void attachCommandCallbacks()
{

}

void setup() {
  // DAC resolution in bits
  analogWriteResolution(12);

  // Start serial
  Serial.begin(9600);
  cmdMessenger.printLfCr();

  // Timer
  Timer.getAvailable().attachInterrupt(messageTest).start(10);
  Timer.getAvailable().attachInterrupt(handler).start(1000);


  cmdMessenger.sendCmd(kStatus,"Ready.");
}

void messageTest() {
  cmdMessenger.sendCmd(kStatus, (int)1);
}

// Generator function
inline double f(float t) {
  double r, w;

  w = TWO_PI * 1.3;

  r = 1.8 + sin(w * t) + 0.8 * sin(2*w*t) + 0.4 * sin(3*w*t);
  return r;
}

void handler() {
  static double t = 0.;
  t += 0.001;

  //Serial.println((int) (2000. * f(t)));

  analogWrite(DAC0, (int) (1000. * f(t)));
}

void loop() {
  // Process incoming serial data, and perform callbacks
  cmdMessenger.feedinSerialData();
}

[ivanseidel]

Oh, now I see ^^

Notice that the start(microsseconds = -1) uses "microseconds" as parameter, not the frequency. If you want to set the frequency instead, try something like this:

Timer.getAvailable().setFrequency(10).attachInterrupt(handler).start();

The reason why (what I think) 10microseconds didn't worked, is because it's too fast for the Due, but I'm not shure.

[ast]

My bad. Muito obrigado!

[ivanseidel]

De nada =]
Did it worked?

[ast]

Didn't try to be honest. I was just using the second timer for debugging so I found another way.
Might come in very handy in the future though! Great library, thanks a lot!!