Forum Replies Created
-
AuthorPosts
-
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 de
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 or subsequent retrys..
For the beta verizon system, with sampling at 15minutes, and SendX=8, that is wireless connection every 2hrs, and timeout of 5seconds, there are burst of successful delivery with ack 201. The ack time is sometimes at about 1.4Seconds, but mostly when successful at about 4.5seconds. So I’m guessing this is something to do with Verizon’s network. I’m going to have to change the timeout back to the 10seconds for better characterization.
Thanks to the MMW team for finding the issues and getting it responding.!!!
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
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 pushing the 8 updates every 2hours, at an offset of 7 minutes. That is at 23:07, 01:07, 03:07. The POST timeout is tighter at 5 seconds, if it doesn’t get a response it records it as a 504. I’ve created a POSTLOG.TXT on the uSD that records all post attempts. If it doesn’t get a 201 it queues the readings and then retrys on the next sucess 201.
Looking at the POSTLOG.txt this morning, it has mostly got 504’s, with a few 201s.
The Debug Log that I got from a POST of 8 readings at PST 23:07pm (2020-08-07T07:07:00-08:00 ) were all 504
Downloading from MMW the .csv file this morning, and looking at the records, a good number 24 readings didn’t make it to the database, but those that did, all made it.
I’ll set up some more testing later today.
https://github.com/ODM2/ODM2DataSharingPortal/issues/483
https://github.com/EnviroDIY/ModularSensors/issues/194
Thanks for the headsup. I was checking yesterday so wondering what the status was. Many thanks
2020-06-19 at 10:41 AM in reply to: Campbell Scientific CS-215 SDI-12 communication issues w/ Mayfly #14257Looking at this posts as a discussion on general SDI-12, I have the Mayfly interface working for a Insitu LT500 Water Level monitor in a prototype capacity.The LT500 requires an 8-36V Excitation, so
Looking at this posts as a discussion on general SDI-12, I have the Mayfly interface working for a Insitu LT500 Water Level monitor in a prototype capacity.The LT500 requires an 8-36V Excitation, so I put in a series booster, +12V https://www.pololu.com/product/2117, and connected the other end to Grove 4pin JST-PH cable (std one cut in half)
I did use the standard SDI12 lib, and just created a header file for the InsituTrollSdi12.h for the interface. So very easy.Thanks for everyone contributing to SDI-12 to make it so easy.
I’d be happy to post back the InsituTrollSdi12.h if anybody wants.
It does take a little setup on the LT500 mapping the sensor value on polling to where the SDI12Sensors.cpp expects it – though my notes are a bit hazy on what I did.
Since the SDI-12 spec defines clamping excess voltages to ground (lightening/ESD), today I’m in the process of creating a true SDI-12 physical interface with the level shifter BSS138 ~ one side pluggable into a Grove 4pin/5V, and the other side taking the SDI-12 3wires.
Be happy to share the PCB/cct/BOM with anybody interested.
The target is to deliver the results over a Verizon signal ~ thanks to @mbarney for suggesting the Digkey SIM and data plan https://dataplans.digikey.com . It does require setting the apn to VZWINTERNET. Its not as easy as hologram to setup.
Attachments:
I could be needing about 6 Mayfly’s + 1 LTE Adapter Board – where is the best way of placing an order, many thanks Neil
I had some of the same ~ then for new sensors on a specific site, I found by changing the name and removing the ‘-‘ in the name, the new sensor + started working for me.Last week I add
I had some of the same ~ then for new sensors on a specific site, I found by changing the name and removing the ‘-‘ in the name, the new sensor + started working for me.Last week I added a new site, had a few problems, changed revisited the site/name slightly, and the I was able to add the sensors.
https://monitormywatershed.org/sites/tu_rc_test04/
I did raise an issue when I first encountered it… it is a critical show stopper bug when it happens.
Here is some new data. I had the FTDI cable connected, and seems like it was influencing things somehow. I cut the RX (always high ~ 3.5V) and that changed the way Q1 is turned on. Still not sure why.Here is some new data. I had the FTDI cable connected, and seems like it was influencing things somehow. I cut the RX (always high ~ 3.5V) and that changed the way Q1 is turned on. Still not sure why. I removed the FTDI altogether and repeated the readings.The Mayfly will now continue operating to V_batt = 3.00V, Proc resets when I drop to 2.95V (motioning with a reasonably professional Meterman 37XR voltmeter).
The overhead/buffer difference V_batt &rail3.3V is now about 0.15V, probably mostly the SPX3819.
However it does show that the mega1284 A6 measurement is only linear to about 3.5V.
The 2nd graph shows the difference between V_Batt and 3.3V rail
I’ve added the .xls with the readings.
So just checking, the Vbat voltage range. I’ve an application that doesn’t have a solar panel. I’m trying to figure out 1) can a LiSOCl2 3.6V 19Ahr be used 2) 3*D MSo just checking, the Vbat voltage range. I’ve an application that doesn’t have a solar panel. I’m trying to figure out 1) can a LiSOCl2 3.6V 19Ahr be used 2) 3*D Mn 18Ahr 3) generically characterize the LiPo measured Voltage,So I’m finding for some reason there is a need for 0.55V overhead from the processors 3.3V. Seems this the LDO and the MOSFET.
I’ve generated some data, graph below. This is a miniumium load, of the Mayfly taking a measurement every two minutes, and sleeping inbetween. Its measuring the Vbatt through uP A6 (blue line), then ADS1115 through a divider 1M/1M measuring the Vbat (orange line) and also the processors 3.3V (grey line)
I also added a low ESR 680uF cap to V_batt (Digikey 732-9079-1-ND ) to buffer any current pulls. Though under V_batt=3.45V the processor starts to reset.
My method is for an FTDI 3.3 cable to J2. I’ve disconnected J2-4/Vusb and J2-1/DTR. No USB cable. Variable power supply connected to JP1. Then vary the power supply Vbatt, measure externally with a Meterman 37XR volt meter to set the voltage, wait for a measurement to show on the TTY. Then drop the voltage and repeat.
The orangle line is accurate, the blue starts to droop under a real 4.1V, and flattens underneath a real 3.8V, as the 3.3V then starts to droop.
So I’m wonder if you have seen the same and any thoughts on the 0.55V overhead. That kinda eliminates the compact LiSOCl2 battery for me.
Attachments:
I’m added a new capability for the Mayfly to program its internal EEPROM with geographical specific pieces of information.
When a site is visited, this will allow the retrieved uSD card to be reI’m added a new capability for the Mayfly to program its internal EEPROM with geographical specific pieces of information.
When a site is visited, this will allow the retrieved uSD card to be replaced with a blank uSD card.https://github.com/neilh10/ModularSensors/wiki/1a-Feature-notes
For multiples sites that don’t have modems, and the readings are retrieved on a site visit by replacing the uSD card, I’m seeing the workflow is that the uSD cards are retrieved and stored together.
The remote site visit workflow would be to keep the the retrieved uSD cards separate from the blank uSD’s. Back in the office, the retrieved uSD cards are read, and each .csv file has unique geographical and node information on it. The site visit could be performed by one person, and then the person reading the uSD and analyzing the data, would have good traceability that uSD readings came from a specific Mayfly/geography.
Just wondering if I’ve covered all information that needs to be stored on a uSD to make it uniquely identifiable. ?
@movingplaid for the basic EC sensor above, and 10bit ADC and running at 2minutes sampling – which is way too fast for a simple DC switched EC sensor got a pretty good result. Graph below.@movingplaid for the basic EC sensor above, and 10bit ADC and running at 2minutes sampling – which is way too fast for a simple DC switched EC sensor got a pretty good result. Graph below.Next stage is to run it overnight, and for simplicity will graph it on MMW
Attachments:
-
AuthorPosts