Matt Barney

Great news, @aufdenkampe! Thanks to you and your team.

I ran a test overnight, with a Mayfly sampling every 5 minutes. Out of 179 samples sent to MMW, only one received Response Code 504, at 04:30 MST, Aug 7th. All other POST messages received successful response codes (201). The 04:30 point did not get saved to the MMW database. What I’ve…[Read more]

I’m not an expert, but based on the Mayfly schematic (see pins 19 and 20 on the ATMega1284P, upper left), it looks like SDA and SCL are pulled high via external resistors on the board, so there is no way to disable them in code.

Reading a tutorial at Adafruit, it looks like that is an inherent part of the design of the I2C protocol:

The I2C clock…

[Read more]

I think my code must not be catching the interrupt properly. It doesn’t get beyond this line in MaxBotixSonar.cpp:

result = _stream->parseInt();

I am able to get it working by using AltSoftSerial (Rx on pin 6), but am unable to get NeoSWSerial to read from the MaxBotix sensor.

Any help is appreciated.

Thanks,
Matt

I’ve probably done something dumb in my code, but can’t see what it is, so I could use another set of eyes on it…

I’ve got a MaxBotix MB7589 SCXL-MaxSonar-WRMT and have it communicating via NeoSWSerial on pin 7. Using the single_sensor.ino example, it works fine. Now I’m trying to integrate it a logging sketch, based on DRWI_NoCellular.ino, and…[Read more]

OK, thanks Sara. I really like the look and layout of the new Doxygen docs. Thanks for all your efforts!

Matt

Apologies for resurrecting an old thread, but it is exactly on-topic for my situation.

I’m confused about wiring the MaxTemp. The ModularSensors documentation says to connect the red wire from MaxTemp to the MaxSonar’s pin 6 (V+). However, the MaxBotix datasheet shows no connection of the MaxTemp to V+. Likewise, @fisherba Beth’s photo above…[Read more]

Thanks, Anthony, for this informative post! It speaks to some questions we at Trout Unlimited have had about MMW, its current performance, and future direction, as we look to expand our Mayfly deployments.

Matt

(cc @jlemontu-org)

Me too. The problem seemed to be specific to the one browser tab; when I opened a second (non-incognito) tab, it worked. Never had that happen before with MMW.

Thanks again,
Matt

Hi Robert,

Hmm looks like it is browser-related. I tried again just now and still didn’t work, but it does work in an Incognito window, so not sure what’s up. My colleague reported that it wasn’t working for him this morning, so I checked and it didn’t work for me at that time either.

Thanks for your reply,

Matt

Hi Neil,

Thanks for opening up this important topic, and for sharing your work!

This idea of scaling up one’s Mayfly installations is really coming to the fore at my organization, Trout Unlimited (TU). My colleague Jake (@jlemontu-org) has been working with Stroud for a couple of years now to deploy Mayflys with volunteer groups in Michigan,…[Read more]

Today I re-tested, using new hardware: Mayfly, modem, antenna, and LTEBee adapter. I’m still seeing the same problems: both Response Code 504 from MMW, as well as what I described above, where there was apparently(?) no attempt by the Mayfly to upload data after saving it to the SD card based on the messages it logged. I’ll attach the log file.…[Read more]

Hi Robert,

I just now tried and am also unable to upload a CSV. In the past, I had trouble due to formatting or due to files that were too long, but once I figured that out, I saved examples of files that I’ve successfully uploaded. However, those are now failing as well. Sample csv attached, FWIW.

Matt

Hi again.

I ran another test overnight, again using a 2 minute sampling interval, with no code changes, but I removed the build flags for modem debugging from the platformio.ini. Here are the results:

• 427 total samples taken
• 52 sample events received a Response Code 504.
• 246 sample events received a Response Code 201.
• 155 of the samples…

[Read more]

Hi Anthony, Thanks for that, and will keep the tracert in mind!

Hi Neil, Yep, that’s software development; I’ve got the grey hairs too! I am interested in learning more about your thoughts and approaches to reproducibility, so will start a thread on that soon. Your progressive testing approach sounds great, and is what I’m trying to work toward…[Read more]

Hi Neil,

Thanks for your good explanations and ideas. As you’ve described, the Mayfly->MMW system in its current form would need additional engineering effort to be able to support a high-reliability communication system with built-in buffering, retries, etc.

At the moment, I’m trying to understand why our Mayfly systems’ reliability has dropped…[Read more]

Thank you, Neil!

Here is more information, from a test I ran overnight using a 2 minute sampling interval, from 04-01 15:32 to 04-02 08:08 MST (UTC-7:00):

• 498 total samples taken, of which 7 failed to get inserted into the MMW database.
• 55 sample events received a Response Code 504.
• 1 event received RC 400.
• The remainder received RC 201…

[Read more]

I’ve been getting a lot of 504 (Gateway Timeout) HTTP responses to the POST messages sent to MMW. I ran a test today with my Mayfly sampling every 2 minutes, and out of 111 samples, I got 34 successful (201) response codes and 76 response codes of 504. I also got one 502-Bad Gateway, and that datapoint didn’t make it up to MMW; the rest did. My…[Read more]