AVR Freaks

Indeed, I am working with AtTiny45 .

Best.

Hello to all of you,

thank you for all inputs, will have to go over each. Anyway, here are the blocks, how program is organized at the moment. Indeed, if you would like to see the code, let me know and will post it...

Mainl loop{

1) “state machine” ( here the sensor threshold timing is measured )

2) “ making a decision according to the measurements

3) make action according to decision , if certain action is found go to sleep, woken by interrupt that is set in setup(), namely isr

4) wdt reset

} //end of main loop

Again all this code works, however, I need to find a more simple, robust way of handling ifs, there is plenty of them in 3) action block, apparently I am not considering all of the possibilities...

So, the question, I am not explicitly using either reti or rjmp in isr, do I need to? And, will interrupt put me back to where the uC went to sleep or at the start of the main loop?

Best.

Hello all,

went thru the whole program and indeed, when I hard code the variables in the ISR, certain variables are overridden, therefore, I am wondering, if the variables keep the values once the uC goes to sleep? And, can I have a more complicated operation in ISR than just defining bools (true and false)? For instance, would ISR hand a simple if(), etc? Actually, how much programming can be done in ISR?

Another question, why does the uC produces certain buzzing noice, hardly audible when I am putting uC to sleep, not all of them :/ interesting, but confusing...

Best.

Thanks, when you say “programming right”, it works, even the energy consumption looks good, according to plan... was thinking to put all the ports during sleep mode in high Z and put them back when awaken, in ISR. From perspective of buzzing this could be a solution, but how to do that? In addition, why is this occurring only on some modules and not only on all of them, the layout, etc. is the same... I guess this is definitely a question of software?

Best.

Ok, let me post the code, which part do you need?

Best.

Indeed, I most certain I have the issue in synchronization :( thanks god it can be solved due to the fact it is only about bool variables :) I guess.

So, again, what could would you like me to post with regard to imterrupt code, probably best would be isr, gotosleep code and how it is awaken?

Best.

//ISR
ISR (PCINT0_vect)
{
  sleep_disable();
  ////  // set pins to original setup
  //    pinMode(7, LOW);
  //    pinMode(6, LOW);
  //    pinMode(5, LOW);
  //    pinMode(3, LOW);

  power_all_enable();    // power everything back on

  // also "wake up" enable the wdt
  wdt_enable(WDTO_2S);

  // *** state machine for measuring time of sensor level ***
  if (Sensor.getProximity() > HT) {
    currentState = WAITING_BELOW;
  }
  else {
    currentState = WAITING_ABOVE;
  }
  // *** end of state machine for measuring time of sensor level ***

  //end of interrupt output 

  // the wanted state after we wake up with interrupt
  //  1-0-0-1
  ledState = true;
  //  fading = false;
  //  fadeUp = true;

  //new
  aboveHT = 0;
  belowHT = 0;

  // end of interrupt output 

} //end of ISR

//going to sleep rutine
void goingToSleep() {

  //when led is off and brightness is 0
  // - turn on the signal led
  // - start counting towards sleep

  // turn ON led sig
  analogWrite(ledSigPin, 255);

  if (!ledState && !ledState1 && (brightness == 0) ) {
    // increase my counter
    sleepCounter++;
    // check my counter and make a decision
    if (sleepCounter >= 500) {
      //go to sleep!
      goToSleep();
      //analogWrite(ledSigPin, 120);
    }
  }
  //otherwise:
  // - turn off sinal led
  // - and reset the counter to 0
  else {
    //analogWrite(ledSigPin, 0);
    sleepCounter = 0;
  }
}

void goToSleep()
{
  // turn off the led sig
  analogWrite(ledSigPin, 0);

  //  //set pins to HighZ
  //    pinMode(7, INPUT);
  //    pinMode(6, INPUT);
  //    pinMode(5, INPUT);
  //    pinMode(3, HIGH);

  Sensor.clearInterrupt(); //this will clear sensor interrupts!
  Sensor.setProximityContinuous(true); // read prox while sleeping

  // disable wdt while sleeping
  wdt_disable();

  // turin off setting while sleeping
  set_sleep_mode(SLEEP_MODE_PWR_DOWN);
  ADCSRA = 0;            // turn off ADC
  power_all_disable ();  // power off ADC, Timer 0 and 1, serial interface
  sleep_enable();
  sleep_cpu();
}  // end of goToSleep

void loop() { //++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

  OS = Sensor.getProximity();

  currentTime = millis();

  switch (currentState) {
    case WAITING_ABOVE:
      if (OS > HT) {
        belowHT = 0;
        belowHT += currentTime - startTime;
        startTime = currentTime;
        currentState = WAITING_BELOW;
      }
      break;
    case WAITING_BELOW:
      if (OS < HT) {
        aboveHT = 0;
        aboveHT += currentTime - startTime;
        startTime = currentTime;
        //        // when proximity drops below HT then we toggle the fadeUp
        //        fadeUp = !fadeUp;

        //in fading toggle fadeUp
        if (fading) {
          fadeUp = !fadeUp;
        }
        currentState = WAITING_ABOVE;
      }
      break;
  }

  ledAction();

  //we have reached the end of program, reset the WDT
  wdt_reset();

} // +++++++++++++++++++++++++++++++++++++++++++++++++end of main loop++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

// set the led
void ledAction() {

  //led off #1
  // 0-0-0-1
  if(!ledState && !ledState1 && !fading && (fadeUp or !fadeUp) ){
    myFadeOut();

    //turn on the led sig
    //analogWrite(ledSigPin, 255);

    //going to sleep
    goingToSleep();
  }

  //led on 5
  // 1-0-0-1
  else if(ledState && !ledState1 && !fading && fadeUp){
    brightness = 50;
    analogWrite(ledPin, pgm_read_byte(&table[brightness]));

    fadeUp = true;
    fading = false;
  }
  //led on 10
  // 1-1-0-1
  else if(ledState && ledState1 && !fading && fadeUp){
    brightness = 255;
    analogWrite(ledPin, pgm_read_byte(&table[brightness]));

    fadeUp = false;
    fading = false;
  }

}

Just to let you know, definitely I have a problem due to the "interrupt" or synchronisation as pointed out by other, for example, I have tried the code without going to sleep/awake and it works perfectly.

Another thin the buzzing is related to the led which is lid while counting towards sleep... because, if I set the pwm of that led to less eg. 10% , the buzzing is lower... in addition, if the led is turned off earlier then there is no buzzing... 

ok, the buzzing seems  to be sorted, so far I have found out the, if the led is not well soldered I get the buzzing, which is not the case on the other module, however, it could as well be the led as a component is not good...

Anyway, I have posted the code, have fun and I am looking forward to your comments!

Best.

Thank you for pointing this out, I was not sure, if this was important, however, indeed, all variables that are in the isr are volatile...

Finally, I have made it to work! The main problem was that some of vars where not properly defined in the logic.

Anyway, if any of you thinks that the structure could be handled better, in the right way, etc - improvements. I am looking forward to your comments, suggestions!

Best.

You are right but sometimes the creative process does not work that way, at least with me, I go forward and code on fly, hence the errors, when it does not work I look back, correct, draw blocks, etc. I know, this is bad habit, but this is how it works for me ...

With regard to the “defined in the logic”, in this case 4 bools are used and the core of the program is changing this vars either true or false, you can imagine how many states is there (2 on power of 4) ... gets complicated doing it by hearth... so, if you missed a particular one you are fried, it does not work,

Anyway, I would be more than happy to hear other ways of dealing with such a logic, was thinking to use functions such as or, xor, etc., but somehow was not comfortable. I guess there are other ways to deal with that?

Best.

PS there is still something open, how to change the ports out/input or pull-up, etc. anybody knows the code?

Very good, did not know this could be a solution, good to know enum!

Thanks! Will have a look...

Best.