[Jim Moore]

@adamgold

Hi Adam-

Thanks for getting back to me.  Since my software expertise is limited and I don’t understand how all the code in ModularSensors works I have not been able to get “calculated variable” to compile in my simple_logging.ino code.  I have been successful in getting the code to work with external_voltage and the Atlas EZO circuits (EC and pH).  I attached a screenshot of what works with the calculated variable code commented out.  I suspect my problem has something to do with pointers.

Your help would be appreciated.  I probably need step by step instructions of if there simple fix to my code that would be great!

Thanks

-jim

Attachments:

1. 

   simple_logging-scrn-shot.png
   

[Jim Moore]

@adamgold  Hi Adam-

Dave Bressler suggested I contact you for my issues noted above.

Thanks

-jim

[Jim Moore]

Hi Sara @srgdamiano

I think I have gone as far as I am able on my Low Cost EC sensor project.  I added #include <sensors/ExternalVoltage.h> to the DRWI_CitSci code and registered GMI_test site using new ExternalVoltage_Volt(&extvolt) from the Sensorex RTD votage divider as a proxy for temperature.  I need to apply a simple linear correction (y=mx + b) to have the readings on MonMW in ºC rather than voltage.

Is there anyway to do this in the main code or do I need a new #include <AtlasSensorex.h> to do the job?

If so how hard would this be or more to the point could you add this to the ModularSensors library?

Thanks

-jim

[Jim Moore]

I had the same problem trying to fill in gaps for SL150 when the modem wasn’t connecting.  See the following issue https://github.com/ODM2/ODM2DataSharingPortal/issues/430

I think its a know problem that is on the ToDo list.

[Jim Moore]

I seem to have “detached” my screen shot

Attachments:

1. 

   src_dir-correction-1.jpg
   

[Jim Moore]

@srgdamiano I decided to go back to basics with ModularSensors – getting started but took a while to get PCsync to load.  See attached screenshot with the corrections I had to make on the src_dir.

What is the function of the .pio folder and is it automatically populated when creating a new project?  I had to manually load the .pio/mayfly folder from another project to get PCsync to load.

I finally got that all working and reporting the time on the serial monitor but when I launched PCsync.exe it responded with “no FTDI found” and I did have the code running in the mayfly and connected to my PC (Windows 10).  Any thoughts where my problem may be?

Thanks

[Jim Moore]

I noticed a similar issue regarding response codes when I first got my project uploading to MonMW.

Copy of my response on another forum thread:

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!
Thanks

[Jim Moore]

I don’t understand all the details but I get your point and no need to worry about baud rate!  I can change the pin connections on my proto-shields to the SDA and SCL pins, no problem.  However calculating temperature from the RTD on the Sensorex probe and correcting the EC reading of the Atlas EZO will be a challenge for me.

I posted more details as a new topic on the forum.  My low cost EC sensor station is described in a recent blog for reference

[Jim Moore]

@stoltzfus-12osu-edu/ I am in a similar situation with my low cost EC sensor station project.  I need to tweek the AtlasScientific sensor library to fit my hardware.  I am using an AtlasSci EZO circuit set for UART mode and a sensorex conductivity probe with internal RTD which I use to report temperature as well as correct the EC reading to 25ºC.

I am a retired EE (Cornell BEE ’62) and not a comp Sci major and my preferred programing language is solder!  It would be great to be able to provide functional specs for a particular instance of sensor hardware and someone with a CompSci background  (Sara?) write the code for the Modular Sensors library that could be pasted into the DRWI_citSci.ino code.  I plan to post details in this forum under a new topic.

[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!

Thanks

-jim

[Author]

Posts