[fisherba]

Brian, when they did this color change did they give you a pinout? (I love when they do this…)

[fisherba]

Perfect. Go with a 4 pin. The 3.5 mm jack only has 4 pins/connections over the length of the jack. Here’s a photo that might help. You can find a lot about how these are mapped for audio (left, right, mic, ground) and they are mapped differently for iPhone vs other manufacturers.  https://cdn.sparkfun.com//assets/parts/7/5/4/6/11570-04.jpg

[fisherba]

Since that has 3 ground lines, wouldn’t a 4-pin work?

[fisherba]

This might also be a good resource.

https://github.com/EnviroDIY/EnviroDIY_Mayfly_Logger

[fisherba]

Hi Matt,

SDA is a data line. SCL is a clock line. Both are for the Wire library, which is an I2C protocol. These things you could find with a google search of “SCL arduino”. None of these labels are specific to the Mayfly, but they are Arduino basics.

AA is auxiliary analog, found that in the Mayfly Data Logger Features (I’ve personally never had to know what’s different about AA than the other analog ports, because I haven’t used an analog sensor in several years of data logging):

EnviroDIY Monitoring Station Manual

The thing is, there’s a huge knowledge base for all of this stuff online and I’m just doing my best to direct you to it. It’s finals week at my institution, and most of the people on these forums are volunteering their time, so it’s also tedious to answer questions that you’ve spent weeks building into a curriculum.

Beth

[fisherba]

P.S. I took a random pin label and google searched it. My search was “A1 arduino” and it turned up plain language content in the Arduino Foundations class that would lead you to know that this is an analog input pin. That class could be another good starting point, but we picked the Adafruit tutorials because they more quickly lead us through the principles that users needed to be prepared to use PlatformIO or VSCode to manage Modular Sensors code wrappers.

I am aware that many people think that PlatformIO is too much for beginners. I fully understand how not simple these IDEs are if you are not a coder. I avoided using PlatformIO for at least a year after starting my monitoring work. I invite anyone who believes that PlatformIO is “too much” to go read “The lib_deps talk” in Episode 5. The nutshell version is that we are working with actively changing software with this monitoring work, both in Modular Sensors and with many of the Arduino-framework sensors. If you are managing libraries manually, then you’ve got a lot of manual upkeep in your future if you stick with the Arduino IDE. You will need to download all of the code libraries (like software drivers) manually and keep them in a very specifically located and perfectly named directory. Keeping track of updates to libraries will be a manual task.

In contrast, keeping track of libraries using PlatformIO (or VSCode) allows the user to make a list of the libraries that are being used in an “initialization” (ini) file. This central place allows you to keep track of your libraries and their versions in a simple list in the ini file (most of the time you want to stay up to date, sometimes you will need to point to specific, older version).

What’s super awesome about “lib_deps” in PlatformIO is that the amazing developer of Modular Sensors has the libraries collected for you, which requires one line of code in the ini file and no manual downloading effort on your part. For each round of revisions she lets you know what other content you need in your ini file and includes an ini file with each example sketch.

If it doesn’t make sense to use the functionality of PlatformIO for the scope of your work, then that’s fine. But when you start spending more time managing libraries than testing sensors, it’s time to learn the joys of running it all from a simple ini file!

Beth

[fisherba]

Hi Matt,

Glad to see you are getting started with Ardino-framework monitoring. The LearnEnviroDIY link walks you through tutorials starting with the most basic ones offered by Adafruit and other sources online. Then it targets what users will need for monitoring, where the crux is often learning how to manage libraries and how to use the Modular Sensors code wrapper for coding many operations that are cooperative and efficient for monitoring. The tutorial is designed to walk you through from 0 to 100, and depending on your prior experience with coding, code editors, and managing Arduino libraries, some users may not need to do the tutorial in sequence.

Your question about 3.3 vs 5 v power is highlighted on the first image in the first lesson of the LearnEnviroDIY tutorial. We did not detail the “how to increase voltage” because it’s a hardware toggle and it depends on the sensor. The sensors we use in the tutorial are all 3.3v, and users will consult the Modular Sensors wiki to determine their sensor/wiring needs for testing/deploying sensors. In short, there are several physical toggles on the Mayfly to switch the power assigned to each port. If you have a Mayfly in your hand you can see the labels on each of these toggles. Where to connect your sensor depends on communication protocol for the sensor, and LearnEnviroDIY touches on this in a few places, starting at Episode 6. We discuss OneWire and I2C in the tutorial Episode 6.

If you want to know more about the sensors already available in Modular Sensors and their wire/pin associations, check out he wiki: https://envirodiy.github.io/ModularSensors/index.html#mainpage_supported_sensors

The details of the hardware of the Mayfly are outlined here: https://www.envirodiy.org/mayfly/hardware/features/. Learning what the pin labels mean, if I understand the question, is something that people pick up when they do the Adafruit and other tutorials, though I haven’t had a student ask yet. In general D1, D2, etc are digital pins. Tx is transmit. Rx is receive. A is analog. GND is ground. 3V3 is 3.3 volts. Sw is switched power (I think).

If these resources are not “in a language you understand” I recommend staring at the beginning of the EnviroDIY tutorial, and especially thoroughly consume the resources that we link from Adafruit, because we intentionally did not attempt to re-create the tutorial content that they have.

Similar to doing your own home repairs, doing DIY monitoring isn’t a quick and easy thing. I personally spent several months getting up to speed before I recognized the need to create the tutorial, in hopes of helping others who are non-codes learn the ways of DIY monitoring.

Beth

[fisherba]

In theory, you  could  add  the missing  pieces manually….

[fisherba]

There are smarter people at this than me, but I have  run into  two  solutions when  I have the issue you just had.

1. rebuild/compile again.  It’s lame, but it sometimes solves the error.
2. If #1 fails, I manually remove the .pio directory and rebuild the whole thing.

[fisherba]

Something to keep in mind is that our mobile phones have multiple radios and switch (mostly) seamlessly between different signals (3G, 4G, etc) but our XBee radios will only communicate on their designated protocol(s). Looks like the XBee 3 is LTE-M and NB-IoT and I don’t know anything about the latter.

This means that what we see on our mobiles is not always equivalent to what the XBees can use. So we have to dig a little deeper to know if the signals/protocols that our phones are using are accessible for the radio connected to your data logger.

(Thus we have reached the edge of my experience on this because I was able to ride on older radios through last summer.)

[Author]

Posts