Could not wake modem for clock sync.

This topic has 8 replies, 3 voices, and was last updated 2025-07-29 at 1:25 PM by Heather Brooks.

Viewing 8 reply threads

Author

Posts

2025-07-25 at 3:22 PM #19203
okamran
Participant
I believe I’ve been following all the steps correctly on making our water sensing station, but I can’t get any data to be sent to MonitorMyWatershed. I have just a Hydros 21 Meter sensor and ClariVue 10 sensor, and both read fine, but the data is only being written to my SD card and not online. The EnviroDIY LTE Bee seems to be situated well, and I’m fairly certain I put the Hologram SIM card correctly (notch inwards, white part facing up).

I’ve tried running the DRWI_SIM7080LTE sketch at least 10 times now, but to no avail. Also, the sync session says that “This may take up to two minutes!” but usually gives me that “could not wake modem” message after only 20-30 seconds. Would the “LTExBee_FirstConnection” and “LTExBee_FirstConnectionBypass” sketches be of any help perchance?
2025-07-25 at 4:24 PM #19204
Sara Damiano
Moderator
If you’re getting a “could not wake modem” error it means there’s something wrong with the modem power or connection between the modem and your main board. Are your modem lights turning on? There should be a solid red light and a flashing blue light? Make sure your board is in the socket correctly with the cut corners at the top and all the pins securely in the socket.

What is your main board? What version? (ie Mayfly 1.1) What pin numbers do you have selected for modemVccPin, modemStatusPin, ModemSleepRqPin, and modemLEDPin? What baud rate (modemBaud) have you selected?

Which version of the ModularSensors library are you using?

The LTExBee sketches will not help you.
2025-07-25 at 5:11 PM #19205
okamran
Participant
On the LTE Bee I see more of a carrot orange light and a flashing blue light. Is that what you mean?
Attachments:
1. IMG_0713-scaled.jpeg

2025-07-25 at 5:20 PM #19207

Participant

Additionally, I have arduino 1.8.19 and it says I have the EnviroDIY Mayfly 1284p on /dev/cu.usbserial-0001. These boards were bought fairly recently. My baud is 57600. I believe I kept most of the pins the same as in the original code. I have my apn set to “hologram”, and the UUIDs are in place and are in the same order as the variables.

// How frequently (in minutes) to log data
const uint8_t loggingInterval = 1;
// Your logger's timezone.
const int8_t timeZone = -5;  // Eastern Standard Time
// NOTE:  Daylight savings time will not be applied!  Please use standard time!

// Set the input and output pins for the logger
// NOTE:  Use -1 for pins that do not apply
const int32_t serialBaud = 57600;  // Baud rate for debugging
const int8_t  greenLED   = 8;      // Pin for the green LED
const int8_t  redLED     = 9;      // Pin for the red LED
const int8_t  buttonPin  = 21;     // Pin for debugging mode (ie, button pin)
const int8_t  wakePin    = 31;     // MCU interrupt/alarm pin to wake from sleep
// Mayfly 0.x D31 = A7
const int8_t sdCardPwrPin   = -1;  // MCU SD card power pin
const int8_t sdCardSSPin    = 12;  // SD card chip select/slave select pin
const int8_t sensorPowerPin = 22;  // MCU pin controlling main sensor power
/** End [logging_options] */
---
const int8_t modemVccPin = 18;
// MCU pin controlling modem power --- Pin 18 is the power enable pin for the
// bee socket on Mayfly v1.0, use -1 if using Mayfly 0.5b or if the bee socket
// is constantly powered (ie you changed SJ18 on Mayfly 1.x to 3.3v)
const int8_t modemStatusPin  = 19;  // MCU pin used to read modem status
const int8_t modemSleepRqPin = 23;  // MCU pin for modem sleep/wake request
const int8_t modemLEDPin = redLED;  // MCU pin connected an LED to show modem
                                    // status

// How frequently (in minutes) to log data

const uint8_t loggingInterval = 1;

// Your logger's timezone.

const int8_t timeZone = -5; // Eastern Standard Time

// NOTE: Daylight savings time will not be applied! Please use standard time!

// Set the input and output pins for the logger

// NOTE: Use -1 for pins that do not apply

const int32_t serialBaud = 57600; // Baud rate for debugging

const int8_t greenLED = 8; // Pin for the green LED

const int8_t redLED = 9; // Pin for the red LED

const int8_t buttonPin = 21; // Pin for debugging mode (ie, button pin)

const int8_t wakePin = 31; // MCU interrupt/alarm pin to wake from sleep

// Mayfly 0.x D31 = A7

const int8_t sdCardPwrPin = -1; // MCU SD card power pin

const int8_t sdCardSSPin = 12; // SD card chip select/slave select pin

const int8_t sensorPowerPin = 22; // MCU pin controlling main sensor power

/** End [logging_options] */

---

const int8_t modemVccPin = 18;

// MCU pin controlling modem power --- Pin 18 is the power enable pin for the

// bee socket on Mayfly v1.0, use -1 if using Mayfly 0.5b or if the bee socket

// is constantly powered (ie you changed SJ18 on Mayfly 1.x to 3.3v)

const int8_t modemStatusPin = 19; // MCU pin used to read modem status

const int8_t modemSleepRqPin = 23; // MCU pin for modem sleep/wake request

const int8_t modemLEDPin = redLED; // MCU pin connected an LED to show modem

// status

2025-07-25 at 5:25 PM #19208
okamran
Participant
Oh and I’m using the libraries from like May 2024. Also what do you mean by “cut corners”? Is this the notch in the SIM card? The pins seem to be pretty fine.
2025-07-28 at 2:20 PM #19216
okamran
Participant
I tried soldering the SJ16 and SJ17 jumpers on the 1.1 Mayfly, and I’m able to get the Bee power LED to turn on a white color, but the Bee network status LED isn’t showing up (though I am using the SIM7080 LTE Bee which perhaps doesn’t offer status outputs?)
2025-07-28 at 2:55 PM #19217
okamran
Participant
I’ve now uninstalled the libraries I had previously and redownloaded them. The only thing I have in there is from v.036.0 from ModularSensors. Still no dice.
2025-07-28 at 11:43 PM #19220
okamran
Participant
Turns out I did have my sim card upside down! The gray part of the hologram is supposed to be facing upwards, not the white part. Now nothing is broken, except for my pride…
2025-07-29 at 1:25 PM #19221
Heather Brooks
Keymaster
@okamran Glad you were able to find and correct the issue! We appreciate you taking the time to post on the forum. It adds to the archive for other Mayfly users searching for solutions.