Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of Home › Forums › Mayfly Data Logger › Logger ID provided by Stroud?
- This topic has 5 replies, 2 voices, and was last updated 2019-10-28 at 5:20 PM by
Sara Damiano.
-
AuthorPosts
-
-
2019-10-25 at 3:00 PM #13254Hello all,
This is my first time attempting to set-up a Mayfly (with the Campbell OBS3+ sensor) and I have almost no experience so please bare with me.
I’ve been following the steps as laid ou
Hello all,This is my first time attempting to set-up a Mayfly (with the Campbell OBS3+ sensor) and I have almost no experience so please bare with me.
I’ve been following the steps as laid out in the in Mayfly sensor station manual, and right now I’m attempting to upload the DRWI_CitSci.ino sketch. The directions on the github page here: https://github.com/EnviroDIY/ModularSensors/blob/master/examples/DRWI_CitSci/ReadMe.md#set-the-logger-id
say to “Change the “XXXX” in this section of code to the loggerID assigned by Stroud:
// Logger ID, also becomes the prefix for the name of the data file on SD card
const char *LoggerID = “XXXX”;”I’m not quite sure where I can find out what my logger ID is. Any help?
-
2019-10-25 at 3:14 PM #13255If you’re not working with Stroud, you get to assign your logger any ID you want it to have. We often use the Mayfly serial number or a numeric count of it being the nth logger we’ve deplIf you’re not working with Stroud, you get to assign your logger any ID you want it to have. We often use the Mayfly serial number or a numeric count of it being the nth logger we’ve deployed. You might also want to put your site name in the logger id, since it will end up as your file name. You could also call it “Bob” if you’d prefer. 🙂
-
2019-10-25 at 3:18 PM #13256I’m sorry the directions for that example are confusing – it was originally written for people directly working with Stroud and being assigned loggers by us. If you’re making your oI’m sorry the directions for that example are confusing – it was originally written for people directly working with Stroud and being assigned loggers by us. If you’re making your own logger outside of Stroud, you don’t have to worry about Stroud assigning your logger a number.
-
2019-10-25 at 3:39 PM #13257
Ah, well that makes perfect sense. I thought somewhere along the line Stroud had produced an ID for this specific logger, but this makes it much simpler. Thank you.
-
2019-10-28 at 11:09 AM #13261While I have your attention, I have a second question if you’re ale to help.
I am now trying to edit the UUIDs in the sketch for each of my variables, except I don’t have the CTD sensor a
While I have your attention, I have a second question if you’re ale to help.I am now trying to edit the UUIDs in the sketch for each of my variables, except I don’t have the CTD sensor as part of this system. Can I simply remove those lines in the sketch for the CTD sensor, or should I leave them in place with the default UUIDs that are provided?
-
-
2019-10-28 at 5:20 PM #13264If you don’t have a CTD attached, you should remove all the lines for the CTD. If you don’t remove them, your logger will waste time trying to communicate with a sensor that doesn’tIf you don’t have a CTD attached, you should remove all the lines for the CTD. If you don’t remove them, your logger will waste time trying to communicate with a sensor that doesn’t exist and you’ll be wasting bandwidth sending empty values to the data portal.
-
-
AuthorPosts
- You must be logged in to reply to this topic.
