A sketch that worked and now it doesn't

[edoardo7152]

@UKHeliBob

So you leave the project powered up at all times and never touch it between tests on different days ? How is the project powered by the way ?

No the project I always unplug it overnight and it is powered via USB

@UKHeliBob

Does the environment change in any way. Hotter/colder more/less humid ?

No, always the same environment. The temperature ranges from 18C to 23C. Humidity around 45-50%

@UKHeliBob

Do you always test it at the same time of day or is it sometimes lighter/darker day/night ?

Generally, I always do the first test in the morning. When it doesn't work the first time, the whole day doesn't work

@UKHeliBob

Do you ever upload the code when the project is not working and it works afterwards or maybe vice versa ?

Yes I have tried many times to reload the sketch when it doesn't work and it often tells me "Can't access COM 7". I have to restart the PC for the IDE to load the sketch, but even when it manages to load it, it doesn't work.

@UKHeliBob

Do you always connect using the same USB port and USB lead and are the same other components (mouse, keyboard etc) always plugged in when you test it ?

I changed 2 USB cables. Keyboard, mouse, sound card, etc. are always connected, both when it goes and when it doesn't. I tried to change all the USB on my pc but that's not the problem.

@UKHeliBob

Have you measured the voltage on your project power lines ? Are they always correct and are they consistent ?

Yes, checked 5 times. Everything perfect (when it works)

@UKHeliBob

Have you put a print statement in setup() so that you know that the code is actually starting ? Maybe blink an LED using the BlinkWithoutDelay technique in loop() so that you can tell whether the code is actually running

I added a Serial.print (__FUNCTION__);

yesterday like you told me

[UKHeliBob]

@edoardo7152

the project I always unplug it overnight and it is powered via USB

That runs the risk of disturbing the wiring

@edoardo7152

"Can't access COM 7".

There maybe a clue there

@edoardo7152

Everything perfect (when it works)

What about when it doesn't work ?

@edoardo7152

I added a Serial.print (__FUNCTION__);

What did it print ?

[edoardo7152]

I found something interesting.

This morning I brought everything into the box and connected similar cables with terminal blocks.

Specifically I connected

RTC
LDR
LCD
BUTTON

Everything was perfect.

I therefore decided to link too

DHT11
SOIL SENSOR

as soon as I connected ARDUINO to the PC I heard the Windows sound of the disconnected devices.

From the IDE I could no longer select any COM port. Even after restarting the PC, still the same problem. I changed USB cable but nothing. I changed the door but nothing.

So I tried to power everything up and check all the connections with a DMM: everything is ok.

So I unplugged DHT11 and SOIL SENSOR and restarted the PC.

Now I can select the port and upload the sketch to Arduino, but it still doesn't work.

The serial monitor prints only

loop
select mode
loop
select mode
loop
select mode

[TomGeorge]

Hi,
Can you please post some images of your project please?

What is powering your project?

Thanks.. Tom...

[edoardo7152]

The project is powered via USB.

I took a picture of the project in its current state, I couldn't do better because everything is fixed in the box.

Now the project works and I hadn't touched anything since my last post yesterday.

I tried to analyze the differences of the serial monitors (when it works and when it doesn't)

When the sketch works, the serial monitor prints

loop
selectMode
handleLight
"light value"

When it doesn't work, it just prints

loop
select mode
loop
select mode

It looks like it gets stuck in the "select mode" function, which in my opinion is a different function than "select Mode"

For me it get stuck here

void setup() {
  Serial.begin(115200); Serial.println();
  Serial.println(__FUNCTION__);

  if (! rtc.begin()) dieHere("Couldn't find RTC");
  if (! rtc.isrunning()) rtc.adjust(DateTime(F(__DATE__), F(__TIME__))); // careful will be the time when you compiled the sketch
}

void loop () {
  Serial.println(__FUNCTION__); 
  selectMode ();

And when it works it goes there

void selectMode() {

  Serial.println(__FUNCTION__);
  static unsigned long lastChange = 0;
  easyRun();
  if (modeButton || (millis() - lastChange >= autoChangePeriod)) {
    
    // passare ad un altra funzione
    
   for (int i = 0; i <NUMPIXELS; i ++) pixels.setPixelColor (i, pixels.Color (0,0,0));      // turn LEDs off
    pixels.show ();
    
    lastChange = millis ();
    switch (mode) {
      case LIGHT: mode = SOIL; break;
      case SOIL: mode = TEMPERATURE; break;
      case TEMPERATURE: mode = LIGHT; break;
    }
  }
}

[UKHeliBob]

Sorry, but what you are reporting is not correct

You say

@edoardo7152

When it doesn't work, it just prints

loop
select mode
loop
select mode

but what it actually prints, as can be seen from the screenshot (please don't post screenshots) is that it prints selectMode despite what you say

If you are printing teh function name at the start of each function then I would agree that it is just calling selectMode() from loop(), detecting no input then returning to loop()

The obvious conclusion is that either the code is not reading the button input or that the button itself or the wiring to it is faulty so that is the area to concentrate on.

• Is the button wiring firmly connected ?
• is the button connected correctly. You have to choose the correct terminals, not just any two
• does the button work consistently or does it sometimes fail to close its contacts ?
• check the voltage at pin 3 with the button pressed and not pressed. Are they what you expect ?

[TomGeorge]

Hi,
Have you checked that the button actually shorts the two wires together?
Usually you connect diagonally opposite connections on the switch to ensure you have the operating contacts.

Thanks.. Tom...

[edoardo7152]

@edoardo7152

When the sketch works, the serial monitor prints

loop
selectMode
handleLight
"light value"

The screenshot referred to the working sketch

As for the button, I checked several times with the DMM that the connected contacts were the correct ones. At pin 3 everything is regular.

Proof of this is the fact that I have now connected all the sensors and it works as it should.

I have never changed the contacts on the button

[edoardo7152]

I have now hot glued the button contacts to prevent touching, however I checked with the DMM that the connections were correct