Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of WikiWatershed, a web toolkit designed to help citizens, conservation practitioners, municipal decision-makers, researchers, educators, and students advance knowledge and stewardship of fresh water. New to EnviroDIY? Start here

logging to mmw with GPRSbee rev.7, issue wake/sleep and server response 504

Home Forums Mayfly Data Logger logging to mmw with GPRSbee rev.7, issue wake/sleep and server response 504

This topic contains 1 reply, has 2 voices, and was last updated by  fisherba 1 day, 16 hours ago.

  • Author
    Posts
  • #12897

    Bernard
    Participant

    Dear all,

    I am trying to run an almost identical sketch “logging_to_mmw.ino” from the modular_sensor examples using a sodaq GPRSbee rev 7. If I am correct the rev.7 uses the same wake functions as the GPRSbee rev 6. So I assumed that I had to define both the sim800 and rev.6 modem in the sketch. See below:

    // ==========================================================================
    // Wifi/Cellular Modem Main Chip Selection
    // ==========================================================================

    // Select your modem chip – this determines the exact commands sent to it
    #define TINY_GSM_MODEM_SIM800 // Select for a SIMCOM SIM800, SIM900, or variant thereof
    #define SIM800_GPRSBEE_R6 // Select with SIM800 for – these use atypical sleep and wake fxns

    using these settings most of the system seems to work. I have a signal strength of approximately 40% to 60%, it syncs with NIST and it goes into sleep mode after the initial setup. However, there seems to be an issue with powering up and going into sleep mode during the actual measurement runs. Every even run is successful in doing a measurement on the SIM800. It seems to me that powering on/waking takes just more time than expected (as it just stays on after the first run, and goes down in the second). I attached the entire debugging output (masking tokens with ###). Could anyone guide me in which direction I have to search for a solution.

    The second thing that concerns me is the server response if a successful run was finished. The response code is 504, i.e. a gateway timeout, “the server was acting as a gateway or proxy and did not receive a timely response from the upstream server” (according to the wiki https://en.wikipedia.org/wiki/List_of_HTTP_status_codes)
    Anyone familiar with this response?

    Bernard

  • #12900

    fisherba
    Participant

    Are your UUIDs all correct? If you are not sending a parameter, such as modem status, it still needs to have a full string in the “shape” of a UUID.

    …first guess without more information…

You must be logged in to reply to this topic.