Please Help! Meter CTD Gen2 being blocked by Yosemitech 511-a

Tagged: -9999, CTD, Gen2, interference, Meter, yosemitech

This topic has 9 replies, 4 voices, and was last updated 2023-12-15 at 1:48 PM by mbullard.

Viewing 8 reply threads

Author

Posts

2023-01-26 at 9:39 PM #17563
James_NZ
Participant
Hi everyone,

This problem has been causing me trouble for nearly a year, but it has become unworkable with installation of Gen2 Meter CTD sensors.

My problem: Meter CTD (SDI12) and

Hi everyone,

This problem has been causing me trouble for nearly a year, but it has become unworkable with installation of Gen2 Meter CTD sensors.

My problem: Meter CTD (SDI12) and Yosemitech 511-a Turbidity (MODBUS) sensors seem to interfere with each other causing the CTD to sporadically drop out return -9999 values. This only occurred at some sites (around 4 out of 10) and all coding and sensors was identical.

This was workable with the Gen1 sensor as the dropouts were less frequent. However, the Gen2 sensor has interference with every single reading making it impossible to run these two sensors off the same Mayfly board. If I remove the MODBUS wing, the CTD reads perfectly. If I replace the MODBUS wing, the CTD reads -9999 values while the 511-a returns perfect turbidity and temperature measurements.

What I think is Going On: I think the return of information from the CTD is being over-ridden by Turbidity information. The Gen1 CTD seemed to have a faster response time (https://www.envirodiy.org/topic/hydros-21-decagon-ctd-reading-error/#post-17066) which meant that the modularsensors package was amended from a wait time of 500 milliseconds to 1000 milliseconds to accommodate the Gen 2. I wonder if this longer wait time may leave the line open a bit longer which allows information from the Turbidity sensor to creep in. Perhaps my previous problems with Gen 1 sensors were due to variance in the response times of each sensor?

In very non-technical terms, I envision it like this:

The Mayfly says ‘time for a sample, information please’. The Gen 1 CTD would typically reply first ‘here’s some numbers’, followed by the same answer from the turbidity sensor. Sometimes these messages would overlap (only at some sites – perhaps due to imperfections in the sensors?) making the message garbled and only the turbidity numbers clear.

Now, with the update of modularsensors to 0.33.3, I think the Gen 2 CTD and the Yosemitech 511-a respond at the same time (i.e., the CTD responds slightly later) making every message garbled. The turbidity sensor obviously has a louder voice so only those numbers come back.

<b>Towards a Solution: </b>I am pulling my hair out trying to solve this, but I think I need help from our experts @shicks and @srgdamiano.

Is there a way to get modular sensors to ask the CTD for data and wait until the CTD responds before asking the 511-a for data? I’m wondering if splitting these calls up may solve my issue.

I’m open to anyone else’s opinion as well.

Thanks in advance for your help.

James

Previous posts about this problem can be read here:

https://www.envirodiy.org/topic/linking-two-mayfly-boards-together/

https://www.envirodiy.org/topic/hydros-ctd-10-regularly-dropping-out-9999/

More...

Less...
2023-01-27 at 11:11 AM #17564
Sara Damiano
Moderator
The ModularSensors library is running the SDI-12 sensors in “concurrent” mode and the modbus communication only happens when initiated by the logger. So the two sensors really should not

The ModularSensors library is running the SDI-12 sensors in “concurrent” mode and the modbus communication only happens when initiated by the logger. So the two sensors really should not be trying to talk to the logger at the same time. ModularSensors first asks each sensor to start taking a reading, then goes back and asks each one for its results in the order that they’re expected to be ready. You can try using the build flag -D MS_SDI12_NON_CONCURRENT in your PlatformIO.ini. That will tell it to start a reading and then wait the full time for a reading to finish before the starting the next sensor. Note that the flag only affects SDI-12 sensors.

If the same code is working in some places but not in others, I would suspect the problem is electrical, not code. That is, some combination of instantaneous voltage instabilities when both sensors are working is garbling the communication. The SDI-12 library is “bit-banged” so it’s very weak to interference. Shannon or Neil may have better ideas on ways you could try to electrically isolate the sensors from each other.

More...

Less...
2023-01-27 at 5:31 PM #17566
Shannon Hicks
Moderator
We’ve been using Y-511a sensors together with Gen 2 Hydros21 CTD sensors and have had no problems with communication, however we’re using our own modbus adapter (based on a MAX13412 chip)

We’ve been using Y-511a sensors together with Gen 2 Hydros21 CTD sensors and have had no problems with communication, however we’re using our own modbus adapter (based on a MAX13412 chip) instead of the Neil’s modbus wing. As Sara said, the sensors shouldn’t be talking the the Mayfly at the same time since the Y-511 has a 40-second warmup time, followed by a 8-second sampling time, so the Mayfly doesn’t hear anything from the Y-511a for almost a minute after it is powered up. I’m not sure if the modbus wing you’re using has a level-shifter on the SDI-12 data line, but we found that most level-shifting circuits cause inconsistent communication with the Meter Group sensors, probably because the logic high level of their sensors is only 3.6v, which in our experience is safe enough to connect directly to the Mayfly’s digital input.

More...

Less...
2023-01-29 at 11:06 PM #17569
James_NZ
Participant
Thank you both for your reply. Okay, so it seems that I may be barking up the wrong tree with that one. I will try Sara’s build flag to see if that works, but I’m not holding my breath

Thank you both for your reply. Okay, so it seems that I may be barking up the wrong tree with that one. I will try Sara’s build flag to see if that works, but I’m not holding my breath.

I have my SDI12 jumper pins for the CTS set on 5v. Could this be the problem? For some reason I couldn’t get the Gen1 CTD’s to work at 3.3v, but they worked at 5v so I set them all as that.

FYI, I am using the modbus wing-shield here:

https://github.com/EnviroDIY/Mayfly-Modbus-Wing/tree/master/Modbus-Mayfly_WingShield

Thanks again for your help.

James

More...

Less...
2023-01-30 at 2:58 PM #17573
James_NZ
Participant
@shicks, would you mind publishing your Y-511a + Gen 2 Hydros21 CTD code so I can ensure I haven’t done anything wrong on that front?

Thanks in advance.

James

2023-01-30 at 4:20 PM #17574

Shannon Hicks

Moderator

Here’s my code that has been successfully working on a Mayfly v1.1 RevB board, with a Hydros21 connected to the D4-7 Grove jack (with jumper set to the switched 3v setting) and a Y-511a and our

Here’s my code that has been successfully working on a Mayfly v1.1 RevB board, with a Hydros21 connected to the D4-7 Grove jack (with jumper set to the switched 3v setting) and a Y-511a and our custom RS485 adapter connected to the D5-6 jack and an external (non-Mayfly) 12v source supplying power for the Y-511a.

// ==========================================================================
//  Defines for the Arduino IDE
//  NOTE:  These are ONLY needed to compile with the Arduino IDE.
//         If you use PlatformIO, you should set these build flags in your
//         platformio.ini
// ==========================================================================
/** Start [defines] */
#ifndef TINY_GSM_RX_BUFFER
#define TINY_GSM_RX_BUFFER 64
#endif
#ifndef TINY_GSM_YIELD_MS
#define TINY_GSM_YIELD_MS 2
#endif
/** End [defines] */

// ==========================================================================
//  Include the libraries required for any data logger
// ==========================================================================
/** Start [includes] */
// The Arduino library is needed for every Arduino program.
#include <Arduino.h>

// EnableInterrupt is used by ModularSensors for external and pin change
// interrupts and must be explicitly included in the main program.
#include <EnableInterrupt.h>

// Include the main header for ModularSensors
#include <ModularSensors.h>
/** End [includes] */

#include <AltSoftSerial.h>      
AltSoftSerial altSoftSerial(6,5);  
#define modbusSerial altSoftSerial  // For AltSoftSerial

// ==========================================================================
//  Data Logging Options
// ==========================================================================
/** Start [logging_options] */
// The name of this program file
const char* sketchName = "DRWI_SIM7080LTE.ino";
// Logger ID, also becomes the prefix for the name of the data file on SD card
const char* LoggerID = "Logger_XXXXXX";
// How frequently (in minutes) to log data
const uint8_t loggingInterval = 10;
// 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
// Set the wake pin to -1 if you do not want the main processor to sleep.
// In a SAMD system where you are using the built-in rtc, set wakePin to 1
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] */

// ==========================================================================


// ==========================================================================
//  Wifi/Cellular Modem Options
// ==========================================================================
/** Start [sim_com_sim7080] */
// For almost anything based on the SIMCom SIM7080G
#include <modems/SIMComSIM7080.h>

// Create a reference to the serial port for the modem
HardwareSerial& modemSerial = Serial1;  // Use hardware serial if possible
const int32_t   modemBaud = 9600;  //  SIM7080 does auto-bauding by default, but
                                   //  for simplicity we set to 9600

// Modem Pins - Describe the physical pin connection of your modem to your board
// NOTE:  Use -1 for pins that do not apply

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

// Network connection information
const char* apn =
    "hologram";  // APN connection name, typically Hologram unless you have a
                 // different provider's SIM card. Change as needed

// Create the modem object
SIMComSIM7080 modem7080(&modemSerial, modemVccPin, modemStatusPin,
                        modemSleepRqPin, apn);
// Create an extra reference to the modem by a generic name
SIMComSIM7080 modem = modem7080;
/** End [sim_com_sim7080] */


// ==========================================================================
//  Using the Processor as a Sensor
// ==========================================================================
/** Start [processor_sensor] */
#include <sensors/ProcessorStats.h>

// Create the main processor chip "sensor" - for general metadata
const char*    mcuBoardVersion = "v1.1";
ProcessorStats mcuBoard(mcuBoardVersion);
/** End [processor_sensor] */


// ==========================================================================
//  Maxim DS3231 RTC (Real Time Clock)
// ==========================================================================
/** Start [ds3231] */
#include <sensors/MaximDS3231.h>

// Create a DS3231 sensor object
MaximDS3231 ds3231(1);
/** End [ds3231] */

// ==========================================================================
//  Sensirion SHT4X Digital Humidity and Temperature Sensor
//  Built in on Mayfly 1.x
// ==========================================================================
/** Start [sensirion_sht4x] */
#include <sensors/SensirionSHT4x.h>

// NOTE: Use -1 for any pins that don't apply or aren't being used.
const int8_t SHT4xPower     = sensorPowerPin;  // Power pin
const bool   SHT4xUseHeater = true;

// Create an Sensirion SHT4X sensor object
SensirionSHT4x sht4x(SHT4xPower, SHT4xUseHeater);
/** End [sensirion_sht4x] */

// ==========================================================================
//  Meter Hydros 21 Conductivity, Temperature, and Depth Sensor
// ==========================================================================
/** Start [hydros21] */
#include <sensors/MeterHydros21.h>

const char*   hydrosSDI12address = "1";  // The SDI-12 Address of the Hydros 21
const uint8_t hydrosNumberReadings = 6;  // The number of readings to average
const int8_t  SDI12Power = sensorPowerPin;  // Power pin (-1 if unconnected)
const int8_t  SDI12Data  = 7;               // The SDI12 data pin

// Create a Meter Hydros 21 sensor object
MeterHydros21 hydros(*hydrosSDI12address, SDI12Power, SDI12Data,
                     hydrosNumberReadings);
/** End [hydros21] */

//----------------------------------------------------------------------------
#include <sensors/YosemitechY511.h>

// NOTE: Extra hardware and software serial ports are created in the "Settings
// for Additional Serial Ports" section

byte          y511ModbusAddress = 0x01;  // The modbus address of the Y511
const int8_t  y511AdapterPower = sensorPowerPin;  // RS485 adapter power pin (-1 if unconnected)
const int8_t  y511SensorPower = 22;  // Sensor power pin
const int8_t  y511EnablePin   = -1;  // Adapter RE/DE pin (-1 if not applicable)
const uint8_t y511NumberReadings = 5;
// The manufacturer recommends averaging 10 readings, but we take 5 to minimize
// power consumption

// Create a Y511-A Turbidity sensor object
YosemitechY511 y511(y511ModbusAddress, modbusSerial, y511AdapterPower,
                    y511SensorPower, y511EnablePin, y511NumberReadings);

//---------------------------------------------------------


// ==========================================================================
//  Creating the Variable Array[s] and Filling with Variable Objects
// ==========================================================================
/** Start [variable_arrays] */
Variable* variableList[] = {
    new MeterHydros21_Cond(&hydros), 
    new MeterHydros21_Depth(&hydros),
    new MeterHydros21_Temp(&hydros),  
    new YosemitechY511_Turbidity(&y511),
    new YosemitechY511_Temp(&y511),
    new ProcessorStats_Battery(&mcuBoard),       // Battery voltage (EnviroDIY_Mayfly_Batt)
    new SensirionSHT4x_Humidity(&sht4x),         // Relative humidity (Sensirion_SHT40_Humidity)
    new SensirionSHT4x_Temp(&sht4x),             // Temperature (Sensirion_SHT40_Temperature)
    new Modem_SignalPercent(&modem),             // Percent full scale (EnviroDIY_LTEB_SignalPercent)
};

// All UUID's, device registration, and sampling feature information can be
// pasted directly from Monitor My Watershed.
// To get the list, click the "View  token UUID list" button on the upper right
// of the site page.

// *** CAUTION --- CAUTION --- CAUTION --- CAUTION --- CAUTION ***
// Check the order of your variables in the variable list!!!
// Be VERY certain that they match the order of your UUID's!
// Rearrange the variables in the variable list ABOVE if necessary to match!
// Do not change the order of the variables in the section below.
// *** CAUTION --- CAUTION --- CAUTION --- CAUTION --- CAUTION ***

// Replace all of the text in the following section with the UUID array from
// MonitorMyWatershed

// ---------------------   Beginning of Token UUID List   ---------------------

                        
const char* UUIDs[] =  // UUID array for device sensors
    {
        "12345678-abcd-1234-ef00-1234567890ab",  // Specific conductance (Meter_Hydros21_Cond)
        "12345678-abcd-1234-ef00-1234567890ab",  // Water depth (Meter_Hydros21_Depth)
        "12345678-abcd-1234-ef00-1234567890ab",  // Temperature (Meter_Hydros21_Temp)
        "12345678-abcd-1234-ef00-1234567890ab",  // Turbidity (YosemiTech_Y511-A_Turbidity)
        "12345678-abcd-1234-ef00-1234567890ab",  // Temperature (YosemiTech_Y511-A_Temp)
        "12345678-abcd-1234-ef00-1234567890ab",  // Battery voltage (EnviroDIY_Mayfly_Batt)
        "12345678-abcd-1234-ef00-1234567890ab",  // Relative humidity (Sensirion_SHT40_Humidity)
        "12345678-abcd-1234-ef00-1234567890ab",  // Temperature (Sensirion_SHT40_Temperature)
        "12345678-abcd-1234-ef00-1234567890ab",  // Percent full scale (EnviroDIY_LTEB_SignalPercent)
};
const char* registrationToken = "12345678-abcd-1234-ef00-1234567890ab";  // Device registration token
const char* samplingFeature = "12345678-abcd-1234-ef00-1234567890ab";  // Sampling feature UUID

// -----------------------   End of Token UUID List  -----------------------

// Count up the number of pointers in the array
int variableCount = sizeof(variableList) / sizeof(variableList[0]);

// Create the VariableArray object
VariableArray varArray(variableCount, variableList, UUIDs);
/** End [variable_arrays] */


// ==========================================================================
//  The Logger Object[s]
// ==========================================================================
/** Start [loggers] */
// Create a new logger instance
Logger dataLogger(LoggerID, loggingInterval, &varArray);
/** End [loggers] */


// ==========================================================================
//  Creating Data Publisher[s]
// ==========================================================================
/** Start [publishers] */
// Create a data publisher for the Monitor My Watershed/EnviroDIY POST endpoint
#include <publishers/EnviroDIYPublisher.h>
EnviroDIYPublisher EnviroDIYPOST(dataLogger, &modem.gsmClient,
                                 registrationToken, samplingFeature);
/** End [publishers] */


// ==========================================================================
//  Working Functions
// ==========================================================================
/** Start [working_functions] */
// Flashes the LED's on the primary board
void greenredflash(uint8_t numFlash = 4, uint8_t rate = 75) {
    for (uint8_t i = 0; i < numFlash; i++) {
        digitalWrite(greenLED, HIGH);
        digitalWrite(redLED, LOW);
        delay(rate);
        digitalWrite(greenLED, LOW);
        digitalWrite(redLED, HIGH);
        delay(rate);
    }
    digitalWrite(redLED, LOW);
}

// Reads the battery voltage
// NOTE: This will actually return the battery level from the previous update!
float getBatteryVoltage() {
    if (mcuBoard.sensorValues[0] == -9999) mcuBoard.update();
    return mcuBoard.sensorValues[0];
}


// ==========================================================================
// Arduino Setup Function
// ==========================================================================
/** Start [setup] */
void setup() {
    // Start the primary serial connection
    Serial.begin(serialBaud);

    // Print a start-up note to the first serial port
    Serial.print(F("Now running "));
    Serial.print(sketchName);
    Serial.print(F(" on Logger "));
    Serial.println(LoggerID);
    Serial.println();

    Serial.print(F("Using ModularSensors Library version "));
    Serial.println(MODULAR_SENSORS_VERSION);
    Serial.print(F("TinyGSM Library version "));
    Serial.println(TINYGSM_VERSION);
    Serial.println();

    
    // Start the serial connection with the modem
    modemSerial.begin(modemBaud);

    // Set up pins for the LED's
    pinMode(greenLED, OUTPUT);
    digitalWrite(greenLED, LOW);
    pinMode(redLED, OUTPUT);
    digitalWrite(redLED, LOW);
    // Blink the LEDs to show the board is on and starting up
    greenredflash();

    pinMode(20, OUTPUT);  // for proper operation of the onboard flash memory
                          // chip's ChipSelect (Mayfly v1.0 and later)

     altSoftSerial.begin(9600);
     modbusSerial.begin(9600);


    // Set the timezones for the logger/data and the RTC
    // Logging in the given time zone
    Logger::setLoggerTimeZone(timeZone);
    // It is STRONGLY RECOMMENDED that you set the RTC to be in UTC (UTC+0)
    Logger::setRTCTimeZone(0);

    // Attach the modem and information pins to the logger
    dataLogger.attachModem(modem);
    modem.setModemLED(modemLEDPin);
    dataLogger.setLoggerPins(wakePin, sdCardSSPin, sdCardPwrPin, buttonPin,
                             greenLED);

    // Begin the logger
    dataLogger.begin();

    // Note:  Please change these battery voltages to match your battery
    // Set up the sensors, except at lowest battery level
    if (getBatteryVoltage() > 3.4) {
        Serial.println(F("Setting up sensors..."));
        varArray.setupSensors();
    }


    /** Start [setup_esp] */
    for (int8_t ntries = 5; ntries; ntries--) {
        // This will also verify communication and set up the modem
        if (modem.modemWake()) break;
        // if that didn't work, try changing baud rate
        modemSerial.begin(115200);
        modem.gsmModem.sendAT(GF("+UART_DEF=9600,8,1,0,0"));
        modem.gsmModem.waitResponse();
        modemSerial.end();
        modemSerial.begin(9600);
    }
    /** End [setup_esp] */

    // Sync the clock if it isn't valid or we have battery to spare
    if (getBatteryVoltage() > 3.55 || !dataLogger.isRTCSane()) {
        // Synchronize the RTC with NIST
        // This will also set up the modem
        dataLogger.syncRTC();
    }

    // Create the log file, adding the default header to it
    // Do this last so we have the best chance of getting the time correct and
    // all sensor names correct
    // Writing to the SD card can be power intensive, so if we're skipping
    // the sensor setup we'll skip this too.
    if (getBatteryVoltage() > 3.4) {
        Serial.println(F("Setting up file on SD card"));
        dataLogger.turnOnSDcard(
            true);  // true = wait for card to settle after power up
        dataLogger.createLogFile(true);  // true = write a new header
        dataLogger.turnOffSDcard(
            true);  // true = wait for internal housekeeping after write
    }

    // Call the processor sleep
    Serial.println(F("Putting processor to sleep\n"));
    dataLogger.systemSleep();
}
/** End [setup] */


// ==========================================================================
//  Arduino Loop Function
// ==========================================================================
/** Start [loop] */
// Use this short loop for simple data logging and sending
void loop() {
    // Note:  Please change these battery voltages to match your battery
    // At very low battery, just go back to sleep
    if (getBatteryVoltage() < 3.4) {
        dataLogger.systemSleep();
    }
    // At moderate voltage, log data but don't send it over the modem
    else if (getBatteryVoltage() < 3.55) {
        dataLogger.logData();
    }
    // If the battery is good, send the data to the world
    else {
        dataLogger.logDataAndPublish();
    }
}
/** End [loop] */

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290

291

292

293

294

295

296

297

298

299

300

301

302

303

304

305

306

307

308

309

310

311

312

313

314

315

316

317

318

319

320

321

322

323

324

325

326

327

328

329

330

331

332

333

334

335

336

337

338

339

340

341

342

343

344

345

346

347

348

349

350

351

352

353

354

355

356

357

358

359

360

361

362

363

364

365

366

367

368

369

370

371

372

373

374

375

376

377

378

379

380

381

382

383

384

385

386

387

388

389

390

391

392

393

394

395

396

397

398

399

400

401

402

403

404

405

406

// ==========================================================================

// Defines for the Arduino IDE

// NOTE: These are ONLY needed to compile with the Arduino IDE.

// If you use PlatformIO, you should set these build flags in your

// platformio.ini

// ==========================================================================

/** Start [defines] */

#ifndef TINY_GSM_RX_BUFFER

#define TINY_GSM_RX_BUFFER 64

#endif

#ifndef TINY_GSM_YIELD_MS

#define TINY_GSM_YIELD_MS 2

#endif

/** End [defines] */

// ==========================================================================

// Include the libraries required for any data logger

// ==========================================================================

/** Start [includes] */

// The Arduino library is needed for every Arduino program.

#include <Arduino.h>

// EnableInterrupt is used by ModularSensors for external and pin change

// interrupts and must be explicitly included in the main program.

#include <EnableInterrupt.h>

// Include the main header for ModularSensors

#include <ModularSensors.h>

/** End [includes] */

#include <AltSoftSerial.h>

AltSoftSerial altSoftSerial(6,5);

#define modbusSerial altSoftSerial // For AltSoftSerial

// ==========================================================================

// Data Logging Options

// ==========================================================================

/** Start [logging_options] */

// The name of this program file

const char* sketchName = "DRWI_SIM7080LTE.ino";

// Logger ID, also becomes the prefix for the name of the data file on SD card

const char* LoggerID = "Logger_XXXXXX";

// How frequently (in minutes) to log data

const uint8_t loggingInterval = 10;

// 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

// Set the wake pin to -1 if you do not want the main processor to sleep.

// In a SAMD system where you are using the built-in rtc, set wakePin to 1

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] */

// ==========================================================================

// Wifi/Cellular Modem Options

// ==========================================================================

/** Start [sim_com_sim7080] */

// For almost anything based on the SIMCom SIM7080G

#include <modems/SIMComSIM7080.h>

// Create a reference to the serial port for the modem

HardwareSerial& modemSerial = Serial1; // Use hardware serial if possible

const int32_t modemBaud = 9600; // SIM7080 does auto-bauding by default, but

// for simplicity we set to 9600

// Modem Pins - Describe the physical pin connection of your modem to your board

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

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

// Network connection information

const char* apn =

"hologram"; // APN connection name, typically Hologram unless you have a

// different provider's SIM card. Change as needed

// Create the modem object

SIMComSIM7080 modem7080(&modemSerial, modemVccPin, modemStatusPin,

modemSleepRqPin, apn);

// Create an extra reference to the modem by a generic name

SIMComSIM7080 modem = modem7080;

/** End [sim_com_sim7080] */

// ==========================================================================

// Using the Processor as a Sensor

// ==========================================================================

/** Start [processor_sensor] */

#include <sensors/ProcessorStats.h>

// Create the main processor chip "sensor" - for general metadata

const char* mcuBoardVersion = "v1.1";

ProcessorStats mcuBoard(mcuBoardVersion);

/** End [processor_sensor] */

// ==========================================================================

// Maxim DS3231 RTC (Real Time Clock)

// ==========================================================================

/** Start [ds3231] */

#include <sensors/MaximDS3231.h>

// Create a DS3231 sensor object

MaximDS3231 ds3231(1);

/** End [ds3231] */

// ==========================================================================

// Sensirion SHT4X Digital Humidity and Temperature Sensor

// Built in on Mayfly 1.x

// ==========================================================================

/** Start [sensirion_sht4x] */

#include <sensors/SensirionSHT4x.h>

// NOTE: Use -1 for any pins that don't apply or aren't being used.

const int8_t SHT4xPower = sensorPowerPin; // Power pin

const bool SHT4xUseHeater = true;

// Create an Sensirion SHT4X sensor object

SensirionSHT4x sht4x(SHT4xPower, SHT4xUseHeater);

/** End [sensirion_sht4x] */

// ==========================================================================

// Meter Hydros 21 Conductivity, Temperature, and Depth Sensor

// ==========================================================================

/** Start [hydros21] */

#include <sensors/MeterHydros21.h>

const char* hydrosSDI12address = "1"; // The SDI-12 Address of the Hydros 21

const uint8_t hydrosNumberReadings = 6; // The number of readings to average

const int8_t SDI12Power = sensorPowerPin; // Power pin (-1 if unconnected)

const int8_t SDI12Data = 7; // The SDI12 data pin

// Create a Meter Hydros 21 sensor object

MeterHydros21 hydros(*hydrosSDI12address, SDI12Power, SDI12Data,

hydrosNumberReadings);

/** End [hydros21] */

//----------------------------------------------------------------------------

#include <sensors/YosemitechY511.h>

// NOTE: Extra hardware and software serial ports are created in the "Settings

// for Additional Serial Ports" section

byte y511ModbusAddress = 0x01; // The modbus address of the Y511

const int8_t y511AdapterPower = sensorPowerPin; // RS485 adapter power pin (-1 if unconnected)

const int8_t y511SensorPower = 22; // Sensor power pin

const int8_t y511EnablePin = -1; // Adapter RE/DE pin (-1 if not applicable)

const uint8_t y511NumberReadings = 5;

// The manufacturer recommends averaging 10 readings, but we take 5 to minimize

// power consumption

// Create a Y511-A Turbidity sensor object

YosemitechY511 y511(y511ModbusAddress, modbusSerial, y511AdapterPower,

y511SensorPower, y511EnablePin, y511NumberReadings);

//---------------------------------------------------------

// ==========================================================================

// Creating the Variable Array[s] and Filling with Variable Objects

// ==========================================================================

/** Start [variable_arrays] */

Variable* variableList[] = {

new MeterHydros21_Cond(&hydros),

new MeterHydros21_Depth(&hydros),

new MeterHydros21_Temp(&hydros),

new YosemitechY511_Turbidity(&y511),

new YosemitechY511_Temp(&y511),

new ProcessorStats_Battery(&mcuBoard), // Battery voltage (EnviroDIY_Mayfly_Batt)

new SensirionSHT4x_Humidity(&sht4x), // Relative humidity (Sensirion_SHT40_Humidity)

new SensirionSHT4x_Temp(&sht4x), // Temperature (Sensirion_SHT40_Temperature)

new Modem_SignalPercent(&modem), // Percent full scale (EnviroDIY_LTEB_SignalPercent)

};

// All UUID's, device registration, and sampling feature information can be

// pasted directly from Monitor My Watershed.

// To get the list, click the "View token UUID list" button on the upper right

// of the site page.

// *** CAUTION --- CAUTION --- CAUTION --- CAUTION --- CAUTION ***

// Check the order of your variables in the variable list!!!

// Be VERY certain that they match the order of your UUID's!

// Rearrange the variables in the variable list ABOVE if necessary to match!

// Do not change the order of the variables in the section below.

// *** CAUTION --- CAUTION --- CAUTION --- CAUTION --- CAUTION ***

// Replace all of the text in the following section with the UUID array from

// MonitorMyWatershed

// --------------------- Beginning of Token UUID List ---------------------

const char* UUIDs[] = // UUID array for device sensors

{

"12345678-abcd-1234-ef00-1234567890ab", // Specific conductance (Meter_Hydros21_Cond)

"12345678-abcd-1234-ef00-1234567890ab", // Water depth (Meter_Hydros21_Depth)

"12345678-abcd-1234-ef00-1234567890ab", // Temperature (Meter_Hydros21_Temp)

"12345678-abcd-1234-ef00-1234567890ab", // Turbidity (YosemiTech_Y511-A_Turbidity)

"12345678-abcd-1234-ef00-1234567890ab", // Temperature (YosemiTech_Y511-A_Temp)

"12345678-abcd-1234-ef00-1234567890ab", // Battery voltage (EnviroDIY_Mayfly_Batt)

"12345678-abcd-1234-ef00-1234567890ab", // Relative humidity (Sensirion_SHT40_Humidity)

"12345678-abcd-1234-ef00-1234567890ab", // Temperature (Sensirion_SHT40_Temperature)

"12345678-abcd-1234-ef00-1234567890ab", // Percent full scale (EnviroDIY_LTEB_SignalPercent)

};

const char* registrationToken = "12345678-abcd-1234-ef00-1234567890ab"; // Device registration token

const char* samplingFeature = "12345678-abcd-1234-ef00-1234567890ab"; // Sampling feature UUID

// ----------------------- End of Token UUID List -----------------------

// Count up the number of pointers in the array

int variableCount = sizeof(variableList) / sizeof(variableList[0]);

// Create the VariableArray object

VariableArray varArray(variableCount, variableList, UUIDs);

/** End [variable_arrays] */

// ==========================================================================

// The Logger Object[s]

// ==========================================================================

/** Start [loggers] */

// Create a new logger instance

Logger dataLogger(LoggerID, loggingInterval, &varArray);

/** End [loggers] */

// ==========================================================================

// Creating Data Publisher[s]

// ==========================================================================

/** Start [publishers] */

// Create a data publisher for the Monitor My Watershed/EnviroDIY POST endpoint

#include <publishers/EnviroDIYPublisher.h>

EnviroDIYPublisher EnviroDIYPOST(dataLogger, &modem.gsmClient,

registrationToken, samplingFeature);

/** End [publishers] */

// ==========================================================================

// Working Functions

// ==========================================================================

/** Start [working_functions] */

// Flashes the LED's on the primary board

void greenredflash(uint8_t numFlash = 4, uint8_t rate = 75) {

for (uint8_t i = 0; i < numFlash; i++) {

digitalWrite(greenLED, HIGH);

digitalWrite(redLED, LOW);

delay(rate);

digitalWrite(greenLED, LOW);

digitalWrite(redLED, HIGH);

delay(rate);

}

digitalWrite(redLED, LOW);

}

// Reads the battery voltage

// NOTE: This will actually return the battery level from the previous update!

float getBatteryVoltage() {

if (mcuBoard.sensorValues[0] == -9999) mcuBoard.update();

return mcuBoard.sensorValues[0];

}

// ==========================================================================

// Arduino Setup Function

// ==========================================================================

/** Start [setup] */

void setup() {

// Start the primary serial connection

Serial.begin(serialBaud);

// Print a start-up note to the first serial port

Serial.print(F("Now running "));

Serial.print(sketchName);

Serial.print(F(" on Logger "));

Serial.println(LoggerID);

Serial.println();

Serial.print(F("Using ModularSensors Library version "));

Serial.println(MODULAR_SENSORS_VERSION);

Serial.print(F("TinyGSM Library version "));

Serial.println(TINYGSM_VERSION);

Serial.println();

// Start the serial connection with the modem

modemSerial.begin(modemBaud);

// Set up pins for the LED's

pinMode(greenLED, OUTPUT);

digitalWrite(greenLED, LOW);

pinMode(redLED, OUTPUT);

digitalWrite(redLED, LOW);

// Blink the LEDs to show the board is on and starting up

greenredflash();

pinMode(20, OUTPUT); // for proper operation of the onboard flash memory

// chip's ChipSelect (Mayfly v1.0 and later)

altSoftSerial.begin(9600);

modbusSerial.begin(9600);

// Set the timezones for the logger/data and the RTC

// Logging in the given time zone

Logger::setLoggerTimeZone(timeZone);

// It is STRONGLY RECOMMENDED that you set the RTC to be in UTC (UTC+0)

Logger::setRTCTimeZone(0);

// Attach the modem and information pins to the logger

dataLogger.attachModem(modem);

modem.setModemLED(modemLEDPin);

dataLogger.setLoggerPins(wakePin, sdCardSSPin, sdCardPwrPin, buttonPin,

greenLED);

// Begin the logger

dataLogger.begin();

// Note: Please change these battery voltages to match your battery

// Set up the sensors, except at lowest battery level

if (getBatteryVoltage() > 3.4) {

Serial.println(F("Setting up sensors..."));

varArray.setupSensors();

}

/** Start [setup_esp] */

for (int8_t ntries = 5; ntries; ntries--) {

// This will also verify communication and set up the modem

if (modem.modemWake()) break;

// if that didn't work, try changing baud rate

modemSerial.begin(115200);

modem.gsmModem.sendAT(GF("+UART_DEF=9600,8,1,0,0"));

modem.gsmModem.waitResponse();

modemSerial.end();

modemSerial.begin(9600);

}

/** End [setup_esp] */

// Sync the clock if it isn't valid or we have battery to spare

if (getBatteryVoltage() > 3.55 || !dataLogger.isRTCSane()) {

// Synchronize the RTC with NIST

// This will also set up the modem

dataLogger.syncRTC();

}

// Create the log file, adding the default header to it

// Do this last so we have the best chance of getting the time correct and

// all sensor names correct

// Writing to the SD card can be power intensive, so if we're skipping

// the sensor setup we'll skip this too.

if (getBatteryVoltage() > 3.4) {

Serial.println(F("Setting up file on SD card"));

dataLogger.turnOnSDcard(

true); // true = wait for card to settle after power up

dataLogger.createLogFile(true); // true = write a new header

dataLogger.turnOffSDcard(

true); // true = wait for internal housekeeping after write

}

// Call the processor sleep

Serial.println(F("Putting processor to sleep\n"));

dataLogger.systemSleep();

}

/** End [setup] */

// ==========================================================================

// Arduino Loop Function

// ==========================================================================

/** Start [loop] */

// Use this short loop for simple data logging and sending

void loop() {

// Note: Please change these battery voltages to match your battery

// At very low battery, just go back to sleep

if (getBatteryVoltage() < 3.4) {

dataLogger.systemSleep();

}

// At moderate voltage, log data but don't send it over the modem

else if (getBatteryVoltage() < 3.55) {

dataLogger.logData();

}

// If the battery is good, send the data to the world

else {

dataLogger.logDataAndPublish();

}

/** End [loop] */

More...

2023-02-01 at 10:40 PM #17581
James_NZ
Participant
Hi @shicks and @srgdamiano. You’re not going to believe it but the additio

Hi @shicks and @srgdamiano. You’re not going to believe it but the addition of the build flag below has fixed my problem, at least for the Gen2 sensors.

-D MS_SDI12_NON_CONCURRENT

1

-D MS_SDI12_NON_CONCURRENT

I am certain it is this build flag and not the voltage pin (previously set to 5v) because I uploaded my script prior to switching the voltage pin over and it suddenly sprang into life. I have subsequently changed the pin over to 3.3v for good measure.

I will keep you updated.

James

More...

Less...
2023-12-14 at 10:39 AM #18239
mbullard
Participant
(I am placing this comment here rather than start a new topic because of similarities)

We have two stations that developed the same problem in August of 2023. One station is here:
(I am placing this comment here rather than start a new topic because of similarities)

We have two stations that developed the same problem in August of 2023. One station is here: https://monitormywatershed.org/sites/GVWA%20107/

Both were V1.0 Mayfly with the LTE Bee, Hydros21 CTD and Yosemitech 511-a Turbidity sensors with the Modbus-Mafly-Wingshield . The Hydros21 is using the new 500 and 1000 ms timings and the voltage jumper is set to 3.3 volts. The wingshield is getting 5 volts switched from the header (pin 11) and using the U3V12F9 boost regulator.

First symptoms in August were the CTD returning -9999 and -9991, which are bad measurement and low voltage error codes.

We replaced the V1.0 boards with V1.1 rev B boards this week but the problems persists. However, disconnecting one or the other of the sensors results in normal operation for the connected sensor. Is it likely that there is insufficient power getting to the sensors during sensor operation? If so, could I try:
- getting 12 volt for the 511-a from pin 9 on the header (now that the 12 volt boost has been upgraded) and removing the U3V12F9?
- the above, but also altering SJ25 to get 9 volts?
- change SJ27 and monitor for voltage sag?
It is always possible to run a jumper from the LIPO header to a second board as a workaround.

Thanks for any insights,

Mike
More...

Less...
- 2023-12-14 at 6:46 PM #18243
  Shannon Hicks
  Moderator
  The Yosemitech Y-511A needs 12v to operate, so it won’t be happy if you modify the Mayfly jumper to set the 12v output to 9v. I’m not familiar with the operation of the modbus wing you&#
  
  The Yosemitech Y-511A needs 12v to operate, so it won’t be happy if you modify the Mayfly jumper to set the 12v output to 9v. I’m not familiar with the operation of the modbus wing you’re using so I can’t comment on its operation, but we have a new modbus adapter board with it’s own beefy 12v-boost Grove adapter board that will be available in the shop in a few weeks, so I think that might be something for you to try. I can send you an email about it, and we’ll be posting examples here once they’re ready for release.
  
  More...
  
  Less...
2023-12-15 at 1:48 PM #18253
mbullard
Participant
Thank you for the quick response, we are looking forward to the new modbus adater. Meanwhile, we made some quick changes to existing wingboards to power the Y-511A from the 12v available on the V1

Thank you for the quick response, we are looking forward to the new modbus adater. Meanwhile, we made some quick changes to existing wingboards to power the Y-511A from the 12v available on the V1.1 rev B, with good results. One station is back to normal and the other should be as soon as the updated wingboard is installed. Thanks!

Edit 12/22/23: The change to the wingboards did not resolve the issue, but did change the data the Y511-a was sending from -9999 to 0.0

Edit 2/9/24: Turns out the wiper on the Y-511A was rotating outside of its normal operation and got stuck on an adjacent PVC fixture. If the wiper rotates 360 degrees instead of just wiping back and forth, the rubber wiper will overhang the stainless steel body of the Y-511A, and collide with other things. The stuck wiper was pulling a lot of current, and possibly causing voltage sag on the Mayfly. Unstuck now, and appears to be operating normally.

More...

Less...

Author

Posts

Viewing 8 reply threads

You must be logged in to reply to this topic.