Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of WikiWatershed, an initiative of Stroud Water Research Center designed to help people advance knowledge and stewardship of fresh water.
New to EnviroDIY? Start here

Reply To: PlatormIO: ..Python 2.7 interpreter error

Home Forums Mayfly Data Logger PlatormIO: ..Python 2.7 interpreter error Reply To: PlatormIO: ..Python 2.7 interpreter error

Jim Moore
    Hi Scott-
    I was able to get my LowCostEC sensor station uploading to MonMW using the AtlasScientific library.  However what I really need is a <LowCostEC.h> library file that will address the Atlas EZO circuit in UART mode, read and calculate temperature, and apply correction coefficients.  I looked at the  AtlasScientificEC.h code and its way above my pay grade in terms of rewriting it to work with my sensor stations.
    I now have two of my stations (GMI_EC1 and GMI_EC2) running the DRWI_CitSci code with #include AtlasScientificEC.h. I reconfigured my EZO circuit to I2C so it is reporting uncompensated EC data but the sensorex temp reading is really the modem RSSI.
    I was pleasantly surprised to load the UUID’s into the code, activate my SIM card, and plug in the GPRSbee. Data appeared on MonMW!  Couple of questions:
    • I noticed several different response codes from the server – 20x(good) 40x(eror).  Yet the data uploaded successfully in both cases.  Are these related to signal strength or slow response of the server?
    • Data seems to be uploaded with a 2G signal of -95 dBm so what is the noise floor of the GPRSbee modems?
    • In attempting to solve the missing data issue I deleted GMI_EC2 and reconfigured it and when I uploaded data with the DRWI_CitSci code it showed all four variables.  I tried several months ago and that didn’t work.  Can anyone explain what’s going on?  Perhaps the DRWI_CitSci code has some magic incantation that I missed in my earlier attempts!