Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • in reply to: module hang-up e220 #29329
    L33t331
    Participant

      I will try to find time for this, my friend, and I also need time for all these tests)

      in reply to: module hang-up e220 #29327
      L33t331
      Participant

        There is nothing particularly interesting there, sending structures and output to oled.
        For now, I’m just testing how it will work for 7 days without any problems – I’ll share it!
        I am currently working on a small filter, otherwise noise in the data sometimes arrives.
        I also want to test the declared operating temperatures in the climate chamber (including up to -40 degrees) while searching for this camera in my city, as soon as I collect all the information, I can unsubscribe and share!)

        in reply to: module hang-up e220 #29324
        L33t331
        Participant

          Hi, you were right, the problem is gone.
          50 hours of running time without problems.
          Thanks, good luck!

          in reply to: module hang-up e220 #29306
          L33t331
          Participant

            Do you mean rsc.close();?

            in reply to: module hang-up e220 #29304
            L33t331
            Participant

              Hello, this piece of code for getting the structure has a problem with a leak, I can’t share anything, I’ve tried a lot, what I know, I’ve run out of ideas, maybe you can help me?
              I assume that the error is in the library, because the leak occurs even if the module that should send messages is turned off.

              if (e220ttl.available()>1) {
              #ifdef ENABLE_RSSI
              rsc = e220ttl.receiveMessageRSSI(sizeof(Message));
              #else
              rsc = e220ttl.receiveMessage(sizeof(Message));
              #endif
              if (rsc.status.code!=1){
              }else{
              Message message = *(Message*) rsc.data;
              #ifdef ENABLE_RSSI
              Serial.print(“RSSI: “); Serial.print(rsc.rssi, DEC);
              #endif
              }
              }

              —–but!!!!!!—–
              When receiving STRING – there are no such problems! no leakage, regardless of module settings, leakage only on struct.

              if (e220ttl.available()>1) {
              // read the String message
              #ifdef ENABLE_RSSI
              rscc = e220ttl.receiveMessageRSSI();
              #else
              rscc = e220ttl.receiveMessage();
              #endif
              if (rscc.status.code!=1){
              Serial.println(rscc.status.getResponseDescription());
              }else{
              Serial.println(rscc.data);
              #ifdef ENABLE_RSSI
              Serial.print(“RSSI: “); Serial.println(rscc.rssi, DEC);
              #endif
              }
              }

              All code is taken from examples.

              in reply to: module hang-up e220 #29299
              L33t331
              Participant

                Look at the photo of this after 10 minutes of work, we have the following:
                -start – the amount of memory at the beginning of work.
                -now – is the current amount of memory.
                -diff – is the difference between the last measurement and the current one.
                -loss – is the difference between start (initial) and now (current) memory.
                Now the loss is twice as much (2144 bytes)…

                • This reply was modified 10 months, 1 week ago by L33t331.
                Attachments:
                You must be logged in to view attached files.
                in reply to: module hang-up e220 #29298
                L33t331
                Participant

                  After a minute of operation, after each received message from another module, 52-104 bytes disappear in memory, I read ESP.getFreeHeap().
                  I’ll leave the module running for a day.

                  in reply to: module hang-up e220 #29295
                  L33t331
                  Participant

                    Hello, friend! I had the same assumptions about memory, but for some reason I discarded them, thinking that it was definitely not memory.
                    now the module is stuck for 18 hours of operation, the data does not reach it, the past value is = nan.
                    and there are two manual commands:
                    lora.begin – re-initialization
                    of serial2.flush.
                    if they don’t help, I’ll watch the memory.
                    do I understand correctly that you are talking about free esp memory? tell me the command to watch it, and I won’t make a mistake, I’ll display this value on the OLED screen, and leave the modules on for a day again.

                    in reply to: module hang-up e220 #29288
                    L33t331
                    Participant

                      an important clarification, I only rebooted the esp, via the reset button, without resetting the power.
                      maybe I should try using one of these commands once every half hour:
                      -serial 2.flush or
                      -LoRa_E220:: flush or
                      -LoRa_E220:: cleanUARTBuffer or
                      -LoRa_220::reset ??

                    Viewing 9 posts - 1 through 9 (of 9 total)