[NathanStoltz]

No, I don’t think it could have been that long ago. I apologize if I led  you down an un-necessary rabbit hole – it very well could have been that the update to the library had no bearing on how the logging_to_MMW worked at all. It seemed to correlate, but I definitely have nothing definitive to point to.

[NathanStoltz]

Sara – Do you have any insight/help on why I (mostly) have success why using the logging_to_MMW program, which uses the logDataAndPublish command, but not with the double_logger program using the code you provided? It seems to print out the same information  in serial monitor of what it’s trying to do in both cases, but only returns on 201 on the logging_to_MMW program (otherwise 504).

Thanks!

[NathanStoltz]

<p class=”user-nicename”>@srgdamiano – I wish I had looked prior to updating. It was at least July/August of 19, if not late February/early March of 19. I played around with using a back-dated version of the modular sensors library (by specifying the version in the .ini file) to see if I could figure it out.</p>

[NathanStoltz]

Sara and Jim, thanks for the replies! Sara, knowing where you are now without formal coding training give me to hope to continue persevering!

Thanks for the code suggestions! The first – not creating new variables each time – worked great.

The second, for uploading to MMW at first did not work, saying modemWake and updateModemMetadata was not defined. Since I hadn’t updated the libraries in long time, I updated all libraries. Doing that fixed the errors. However, when running the program I have been receiving only 504 responses. I checked the standard logging_to_MMW.ino program with the new library  of modular sensors (0.24.5), and receive some 504s, but mostly it seems successful 201s (earlier this week before updating libraries it worked every time over ~12hrs). Sara, any suggestion why I can’t successfully log in this double_logger program?

Thanks!

[NathanStoltz]

Sara, that’s great, thanks for your response. You are correct – a primary reason I’m hoping to use a Mayfly with the Signature is the telemetry. The Isco modem, while I’m sure very nice, is prohibitively expensive and locks the user into going with telemetry the way they have it set up. I also like the ability of the Mayfly to interface with additional sensors, and potentially down the road to use the Mayfly to control the sampler for the benefit of a 2-part program (baseline and event sampling).

I hope to have time this week to test this out. A few questions – to monitor additional variables (likely a second level and velocity from an A/V sensor, maybe temperature, external voltage, etc), can I copy lines 41-60 and place within the loop, properly assigning variable names and addresses? Also, can I place this code into the ModularSensors code I’ve been using, treating the Signature as an additional sensor with the levels and velocity as logged and transmitted variables?

Thanks! I’m excited to continue to learn and to incorporate this into our sampling and monitoring program.

[Author]

Posts