[neilh20]

Hi @zeke – good check by Rick.

Looking at your error, it does say connection error so implies it didn’t even connect to thingspeak.

I checked this 5months ago and it worked for me. What is your channel number?. This allows a view of if any data has arrived. The channel I used for testing, a bit simplistic  https://thingspeak.com/channels/5940

You could also enable some debug and share it.

For platformIO this is
<div>
<div>build_flags =</div>
</div>
<div>
<div>    -DMS_DATAPUBLISHERBASE_DEBUG</div>
<div>    -DMS_THINGSPEAKPUBLISHER_DEBUG</div>
</div>
 

[neilh20]

Hi @zeke thanks for the qu.  I’ve got the thingspeak working as a POST, but don’t regularly test it. I believe the MQTT is a different route, and I personally haven’t used it.

For the Digi Corp LTE Cat-M1 cell modems, I do ensure that they are upgraded to the latest version with XCTU & XCTU board. It is a bit painful, but worked for me. If there is any problem with the Digi LTE modem I force a reset to defaults.

The provisioning, customizations all go in the code ~ hologram as you have it, and then in the class should have there is  mqtt.thingspeak.com . ThingSpeakPublisher.cpp

I’ll check my notes to see what I did.
If nothing else, I would enable the modem stream to see what its doing. Look for

// Use this to create a modem if you want to monitor modem communication through
// a secondary Arduino stream.  Make sure you install the StreamDebugger
// library! https://github.com/vshymanskyy/StreamDebugger
#if defined STREAMDEBUGGER_DBG

I’ll check out my notes to see what exactly I did on testing.

[neilh20]

Its often seems simple, but the practical side of it can be complex – like if certificates are needed.  AWS can scale, but that requires a lot of layers. As I understand it AWS dices and slices the options and the bills are a big surprise.

In software design the question that comes up is, what’s the functionality that is desired? How do you break the functionality into small layers.  What currently works, and what is needed.

Does it have to be AWS or can it be something else?

https://thingspeak.com/  Can do data collection, and then my experience is the API can pull it off pretty easily.  I did this with an experimental  http://azonde.org/pm2/LiveRainGauge3.htm

The code is in the browser, not that I really follow how it all works!!  and also here https://github.com/neilh10/thingspeakmultichannel-highcharts

The thingspeak costs are pretty well defined.

For the Mayfly which ever way you look at data collection, then reliably pushing data to the endpoint is also needed, which  I’ve got in my sensors, and its on my list to PR but haven’t got there yet.  https://github.com/EnviroDIY/ModularSensors/issues/194

 

[neilh20]

@dan-wachusett  I’ve used WOFpy but there are some issues. https://github.com/ODM2/ODM2DataSharingPortal/issues/445

https://github.com/ODM2/ODM2DataSharingPortal/issues/450

 

Is that the same function as pulling with a GET, or does the GET add extra value – possibly my ignorance in not understanding different methods. 🙂

[neilh20]

I know my local Sonoma State University is against devices connecting to the network. They even gone as far as removing all  ethernet sockets. As part of the local engineering capstone project using LoRa the students went off campus for testing, as the LoRa gateway needed to connect to a WiFi network

The simple answer for WiFi is what Sara described.

Because of the wider security concerns for IP based systems, there is a whole lot of technical initiatives  to manage admittance to larger local networks – so security is likely to get more proscribed.

Just an FYI, even if you got WiFi connecting, I’m still having reliability issues with the Modular Sensors S6B WiFi interface. https://github.com/EnviroDIY/ModularSensors/issues/347

 

[neilh20]

In case its of interest, I have a method of writing to the onboard EEPROM, and use it to track the revision of the board in the data file .csv on the uSD.      https://github.com/neilh10/ModularSensors/wiki/Hw-Mayfly-config-EEPROM

[neilh20]

Many thanks for the heads up on provisional dates. It helps with planning.

Its painful dealing with components that have become unavailable and locate comparables – I had to do that with the Modbus board.

[neilh20]

https://www.digi.com/products/models/xb3-c-a2-ut-001   says only 19 available at https://www.sapply.com

I just received  three from Arrow.com and they don’t have anymore stock.

[neilh20]

Hi @dan-wachusett – I’d be interested to hear how your measurements work out.

This is what I did for acceptance testing (and characterizing) on a number of different types of depth sensors for a 2013 project – https://www.envirodiy.org/measuring-low-water-in-streams-accurately/

The update since then is the hydrologists I work with use the LT-500 for reliability and accuracy, and also been moving over from the Onset U30 to using the Mayfly.

I wonder, has anybody received a specification for the Hydros-21 Gen 2? .

Typically I find that manufactures create internal releases (generation 2?) as an internal cost reduction, with the same specification. Though every manufacturer is unique, so wondering what Metergroup changes might be :)).    Insitu and Keller (and others)  have different lines of depth sensors for different measurement accuracy and methods.  The challenge for any manufacturer is the basic pressure sensor is similar – a pressure dependent resistor – piezo resistor. Temperature dependency of resistors is well studied, but challenging to work with when bumping up against a specific resistor technology’s limits – so different manufactures have different signal processing and manufacturing calibration for better linearity of the pressure sensor.

 

[neilh20]

faaaaantastic  !!!

My data looks good from the May 12.    Thankyou so much to everybody who has pulled that together.

[Author]

Posts