Activity

I repeated my test for another ~48 hour run, sampling every 5 minutes, but this time using WiFi instead of XBee3 cellular. All of my 548 sample points made it to the MMW database, and all POST messages sent by the Mayfly received successful response code 201. So data upload via cellular appears to be significantly less reliable, even when cell…[Read more]

Over the last couple of days I’m getting very good response when using a WiFi, and the response time for 201 ack is sub 1second.

This is a fast check with 2min sampling time, and SendX=2, so delivery every 4minutes. I get a response typically under 0.5seconds, and occasionally ~ 0.6Seconds. So for 1250 messages all have been delivered, 1st time…[Read more]

Hey good to hear.

I haven’t been able to do a lot of testing, and I was out yesterday but I enabled a laptop computer to monitor one beta system overnight that is using verizon starting at 9pm PST. (though I forgot to add the power cord to the laptop and it turned off after 2hrs !!   ).    Its sampling at 15minutes, taking 8 readings, and pus…[Read more]

Not sure why it’s not working based on what’s visible in the sketch you posted. But I’m guessing there’s something happening in the TM1637Display library that is looking for return data or confirmation from the display in order for the sketch to continue, so without the display plugged into your Stalker, the sketch hangs and stops, rather than…[Read more]

Matt is correct, the pullup resistors on the I2C bus on the Mayfly board are soldered to the board and can’t be disabled unless you want to unsolder them, which will cause issues if you try to use I2C devices on the Mayfly like the DS3231 clock or the ADS1115 aux A/D.

I just read through various manuals and datasheets for the K30 sensor, and it is technically possible to change the I2C address of the sensor, but it’s not easy so I wouldn’t suggest it. But the manual says the board also does serial UART output so you can just follow their example code for Arduino UART to modify it for working with the Mayfly’s…[Read more]

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]

The address of the DS3231 isn’t changeable – it’s permanently set when the chip is manufactured.  Is there any other way your sensor can communicate?  Does it have a physical addressing method?  Many I2C sensors have an “addr” pin that you can set to be high or low to change the address.  Can it communicate via SPI or UART so you can use one of…[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]

We think we found and fixed the major issue with slowness and 502/504 Gateway errors that have been increasing since this spring!

Please let us know if you see any slowdowns from the web-browser or gateway errors from devices trying to post data, just in case there’s yet another issue we didn’t notice.

@tslawecki , @htaolimno and Lim…[Read more]

Hello. I’m currently trying to get a sensor working using I2c protocol, and I have a question about the 2.2 kohm resistors on the SDA and SCL lines. Are those resistances automatically enabled, or is there a line of code that would enable them? Otherwise, if the pull-up resistors are automatically enabled on the Mayfly, is there any way to disable…[Read more]

Hello,

I’m sorry to dig up this old post but it seems the right place to post. Tell me if it’s better to create a new post.
So here’s my problem :

I plugged the MB7363 Sonar sensor from Maxbotix to the Seeeduino Stalker v3.1 . I used the analog pin of the sonar (pin 3) and I connected it to the analog A1 input of the Seeeduino Stalker, Vpin t…[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]

I would be interested to know if anyone can find these and will keep an eye on this thread.

I have not been able to easily find them and have resorted to cutting them off the ready-made cables when needed:
(ex. https://www.robotshop.com/en/grove-universal-4-pin-unbuckled-20cm-cable-5-pack.html)
Fairly cheap until you start adding up shipping…[Read more]