Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of 
@neilh20
Active 1 days, 21 hours agoForum Replies Created
-
AuthorPosts
-
edit to the above email: Sorry I don’t have any experience with the 12V batteries, or 12V to 5V.
I would note that the Mayfly1.0 charger is different than 0.5b, and I’m seeing that it w
edit to the above email: Sorry I don’t have any experience with the 12V batteries, or 12V to 5V.I would note that the Mayfly1.0 charger is different than 0.5b, and I’m seeing that it wants a slightly higher+5V than the Mayfly 0.5b for it to do a 0.5A charge of the LiIon battery. I am using USB charging monitor “USB Meter” to monitor the charge rate.
I definitely agree with @ckillen that whatever methods’ are used, some monitoring is required to figure out where the power goes and is it working as expected
I’m also deeply into power analysis as the way of keeping everything going. I was working with some engineering students and got them to do a spreadsheet, which I modified and added and can be uI’m also deeply into power analysis as the way of keeping everything going. I was working with some engineering students and got them to do a spreadsheet, which I modified and added and can be used to build a budget for the power that you think you need, and what the power consumers might be. I then look for the major user of the power, and let the project be driven by that. ie if its a sensor that needs 12V and consumes a lot of power then you need to have the large battery.I also reduce the power by changing how often it turns on the cell modem. ie from 15minutes to 60minutes. The project with students we are only talking about turning it on every 24 hours. However this is a lot of software that I’ve added to my fork.
I also have a battery threshold that I stop any transmission, and then when there is enough solar power harvested start transmitting the stored readings and then the new readings. Its not trivial software to do this, but it has now been well tested.
Happy to share more about power savings if its of interest.
One idea that I’ve seen with the Mayfly 1.0 and the new power routing, is that there can be the LiIon battery plugged in, with solar panel, and then a top up USB Battery pack plugged in.
However I do have to say that the Mayfly 0.5 and also 1.0 battery measurement is challenging, and I’ve tried to phrase it here. IHMO its a really basic issue, and has caused me no end of technical headaches. Mayfly 1.0A3 is more of problem than 0.5 https://github.com/EnviroDIY/EnviroDIY_Mayfly_Logger/issues/32
Attachments:
@zeke-holloman hey congrats,!!! Thanks for the posting and analysis, I could also build from that.Wow… the power of open source
@zeke-holloman hey congrats,!!! Thanks for the posting and analysis, I could also build from that.Wow… the power of open source that you can dive in and tweak it, so you can make it work. Go @zeke-holloman !!!
Just an FYI, what I do to facilitate easy maintenance, and easy future merges, I rename my customizations to a “unique name space” eg ThingSpeakPublisher3a.h/.cpp and then also the classes ThingSpeakPublisher3a.
Then if you come to do an update “git pull” and there are updates in the main line “master” ThinkSpeakPublisher.h/cpp you’ll have a smoother ride with being able to track the updates, and either adopt them or stay with your customizations.
Hi MattThe short answer :), there is a difference in hardware ports, and that can impact the interface to the modem. I expect to support the Mayfly 0.5b for the foreseeable future for devices in
Hi MattThe short answer :), there is a difference in hardware ports, and that can impact the interface to the modem. I expect to support the Mayfly 0.5b for the foreseeable future for devices in the field, and the Mayfly 1.0x features are in evolution. I appreciate the support and context of SWRC, hardware is available for purchase, software is gittable, ~ however there has been no description of regression testing or any visible plan for the Mayfly1.0 features. (The MMW has a visible plan https://github.com/ODM2/ODM2DataSharingPortal/milestones)
Sounds like you have put the software together and its worked. Probably its the default configuration of the ports. Whew!.
Looking at the schematics, the Mayfly1.0A3 v Mayfly0.5b ports are different when it comes to the modem. For Mayfly 1.0 I appreciate the better control of the modem subsystem – I so like to be able to ensure a known configuration of a complex module (the secret; periodic reset) – just to avoid long term reliability problems I’ve seen in other modules.
If there is a Mayfly 1.0 specific hardware integration issue, or usage of its new features, its going to need a specific workaround, and only used if the Mayfly 1.0 is operating.
The long answer, is I’m working towards simplifying the complex configuration of the “logger platform”. The goal I have is that the “logger platform” should be configuration driven – that is configured by reading what revision the Mayfly board is at, and also in a uSD:ms_cfg.ini file for the network/UUIDs, and in the future configure for the modem, and configure for sensors.
I have the infrastructure already built to program the onboard EEPROM for revision info, so relatively easy to read it out.
By far the biggest challenge to any software platform with 24/7 criteria is stability – embedded platform stability is even more challenging. I put together this discussion – as much about having a whole system testable – ModularSensors/Mayfly +MMW – https://github.com/ODM2/ODM2DataSharingPortal/issues/524 which is also dependent on https://github.com/ODM2/ODM2DataSharingPortal/issues/485
Stability needs to be characterized and that is white box testing. Typically for a saleable product with software on hardware, its a core customer expectation (sales contract). Simplify all the complexity, to core stability confidence.
The target for engineering, can you change one item ~ software or hardware, and still have some confidence in the whole “logger platform” stability. The poster child for this is the Digi WiFi S6, which was working (in 2019 I think) – I put a system in the field with an external WiFi antenna + WiFi gateway and it worked (then the system got stolen). I used the WiFi module as a proving ground for stability of the general Mayfly when the LTE was still evolving and also for basic interfaces to the server. I designed the core ReliableDelivery algorithms over WiFi, as the data plans where pretty expensive at that point. Then something changed, probably the tinyGsm lib, and I wasn’t watching it as I had moved to using LTE and SDI-12, and getting them stable/working. The WiFi S6 was broken for probably 6months (and still is on main release). When I got the WiFI S6 back working middle of last year, it required a fork and rework of the tinyGsm drivers. All of this is in my private fork, as to be honest stability characterization is hard/complicated. None of the known problems are reflected in the ModularSensors modems page. (https://envirodiy.github.io/ModularSensors/index.html#mainpage_modems) . What of course would be nice is what was the revision it was tested against – MS version, module hw/sw, and known problems in later releases.
Hardware also has stability characterization process – Mayfly SDI-12 implementation is a subset of https://sdi-12.org/specification – Mayfly 1.0A3 was perhaps trying for +12V generation required by the specification. Mayfly1.0A3 still claims that it can do +12V generation (with no power spec), but my versions haven’t worked with real world requirement, https://github.com/EnviroDIY/EnviroDIY_Mayfly_Logger/issues/33
The history I’ve found, with other projects and also the Mayfly, you need to deal with the real world device foibles (and availability). Last time I looked at Xbee WiFi, the Digi WiFi module was the only one with a u.fl connector for an external antenna – critical for better range. So i’ve stuck with keeping the Digi WiFI module.
Others may have something similar – but how about an objective to make it easy to change – switch one sensor LT500/SDI-12 to CTD/SDI-12
My perspective for an embedded “logger platform”, is it has a defined configuration to work and be deployed – Mayfly0.5b+carrier board Digi LTE-CATM1 modem+ antenna +4400mA battery + 3W solar panel + RS485board(for SDI12 +12V) +sensor LT500.
That configuration needs to work. If some of the components are switched out – eg to Mayfly 1.0 + Digi LTE-CATM1(less carrier board) – I would also like it to work in the same way. However Mayfly 1.0 ports interface to the Dig LTE-CATM1 differently.
So hope you don’t mind the long answer, back to reading the hardware configuration, so for software stability testing, when its loaded with a defined .hex, I’d like to be easily adjust for hardware features!! …. Mayfly 0.5b, Mayfly 1.0A3, … Mayfly 1.x
@zeke-holloman I agree with @srgdamiano, Mathworks have gone down the path of making it difficult to test a small number of devices against thingspeak, since it was added to ModularSensors publisher@zeke-holloman I agree with @srgdamiano, Mathworks have gone down the path of making it difficult to test a small number of devices against thingspeak, since it was added to ModularSensors publishers.A bit of shame since I’ve had some simple devices working reliably against it since 2013.
Also unfortunately, “the real world” is that testing is against a matrix – release ModularSensors xx.xx against thingspeak – so I think you are on the leading edge for ModularSensors Publisher v mqtt3.thingspeak 🙂
Taking a scan of their mqtt3, it seems like they are suggesting you create new devices when moving to their mqtt3 – so at a GUESS, that suggests they have a whole new server architecture and subscription management. So be great if you share results – stuff that doesn’t work is as valuable as stuff that does work.
When looking at a new service, its also useful to consider what it takes to prove how well it works and how far you want to go.
Typically new development goes in stages a) protoyping b) integration testing c) reliability/stability testing.
MMW has a lot of capability, and very mature, but in the “reliability testing” of Mayfly 0.5 and Digi LTE CAT-M1 modems, from a debug analysis, there is a possible timing problem with the tinyGSM device driver https://github.com/EnviroDIY/ModularSensors/issues/396 – which suggests that if the MMW servers response where a lot faster, faster than the current fastest 1.2seconds, it might break the current deployments with Digi LTE-CAT-M1 XB3-C-A2-UT-001. Its what happens in testing sometimes.
I’ve had very good experience so far with “reliability/stability testing” of ModularSensors 0.32.2/(Mayfly 0.5+ Digi LTE-CAT-M1), but the server response through the cellphone network is pretty slow, at its fastest 1.2seconds.
For mqtt3.thingspeak you are back to “a)prototyping”.
For another wireless protocol LoRa/Thingsnetwork, with max payload of 51bytes, which seems unlikely that it could work with MMW API, I’m checking out Arduino.cc mqtt/IoT or Adafruit mqtt as having plans for smaller devices. So I would describe I’m trying to figure how to prototype that interface.
I should note – https://github.com/EnviroDIY/ModularSensors/releases/tag/v0.32.2 doesn’t identify what features work with new Mayfly 1.0A3 boards. The modem SIM7080 , isn’t identified as being supported yet, or tested with ModularSensors – though as its open source we can all see what’s in the software. I guess, user test at their own risk.
I have only done minimal testing on Mayfly 1.0A3, as its typical for organizations to announce what they support and regression testing. My testing, is with a student capstone project as a standalone sensor so far, though they should get to cellular LTE integration soon. On paper analysis I’ve identified a potential comms issues with Mayfly1.0A3 – see https://github.com/EnviroDIY/EnviroDIY_Mayfly_Logger/issues
I’m making ModularSensors detect in runtime whether its Mayfly 0.5 or 1.0 – so the user/program doesn’t have to compile for one or the other.
In the early part of this year 2021, I did some regression testing using an Insitu LT500/SDI12 with a modbus board and telecom LTE, and I ran into a hard to find issue on the Mayfly 0.5b – theIn the early part of this year 2021, I did some regression testing using an Insitu LT500/SDI12 with a modbus board and telecom LTE, and I ran into a hard to find issue on the Mayfly 0.5b – the Uart Rx line is unterminated..When extending features, its not unusual that problems are uncovered in new ways of exercising the software.
As part of a terminal based set the date on a simple Mayfly, I introduced a command line interface.
The objective was to be able to set the Date and Time on a Mayfly when its been installed or about to be installed. Typically a connected Mayfly gets the date when it polls NIST or by special date setting program.
A command line can be very useful in other ways as I brought out here
https://www.envirodiy.org/topic/how-to-dump-contents-of-file-on-sd-card-to-serial/#post-15830
For the initial command line interface I used String.
Now, it turns out that String has some down sides, and its valuable to understand these downsides – so as not to trip over them like I did.
https://cpp4arduino.com/2018/11/06/what-is-heap-fragmentation.html
https://cpp4arduino.com/2018/11/21/eight-tips-to-use-the-string-class-efficiently.html
So I created a potential issue in the software, that for incoming characters for the UART RX, I added them to a String. The hardware unfortunately can generate a lot of random characters, and this can cause the String to use up a lot of memory.
In the process of debugging this I wrote a utility to dump the ram and showing how much stack and heap used I called it dumpFreeRam() . This gives a periodic visual of the ram allocation, and what might be using it.
The critical issue is monitoring during integration testing how much free ram is available, and what might be using it.
I did find one bug this way when a lot of ram got used up with the above usage of String. I’ve changed it to a more traditional fast circular buffer.
This utility at the end of each invocation calculates a summary “Free ram never allocated”. However this by itself doesn’t indicate when the ram actually got allocated, so the debug listing needs to be evaluated for what event caused any ram to be used.
The example below shows that a program used up to 273 bytes after running for a couple of hours. 6161-591=273bytes. Fortunately longer testing doesn’t see more ram leakage.
[2021-08-01 16:22:14.881] Free ram never allocated between (bytes dec) 6144 and 6161
and after two hours
[2021-08-01 18:20:15.013] Free ram never allocated between (bytes dec) 5888 and 5912
The output on the terminal using Teraterm looks like this (using a Nanolevel/RS485)
1234567891011121314151617181920212223242526272829303132333435363738394041[2021-08-01 16:22:14.710] dumpFreeRam from heap(low)=0x26C8to stack(high)=0x40C3) size(dec):6651[2021-08-01 16:22:14.710] 0x26C0 2D30312E 63737600 40000000 6C6C6572 ;-01.csv.@...ller[2021-08-01 16:22:14.710] 0x26D0 4E616E6F 6C657665 6C206174 206D6F64 ;Nanolevel at mod[2021-08-01 16:22:14.710] 0x26E0 6275735F 30783031 001F0000 006C6C65 ;bus_0x01.....lle[2021-08-01 16:22:14.710] 0x26F0 724E616E 6F6C6576 656C2061 74206D6F ;rNanolevel at mo[2021-08-01 16:22:14.710] 0x2700 64627573 5F307830 31001F00 00006C6C ;dbus_0x01.....ll[2021-08-01 16:22:14.710] 0x2710 65724E61 6E6F6C65 76656C20 6174206D ;erNanolevel at m[2021-08-01 16:22:14.710] 0x2720 6F646275 735F3078 3031006D 6F646275 ;odbus_0x01.modbu[2021-08-01 16:22:14.710] 0x2730 735F3078 30310061 79666C79 00000000 ;s_0x01.ayfly....[2021-08-01 16:22:14.710] UnUsed 1k 0x2740...............................................................[2021-08-01 16:22:14.710] UnUsed 1k 0x2B40...............................................................[2021-08-01 16:22:14.710] UnUsed 1k 0x2F40...............................................................[2021-08-01 16:22:14.710] UnUsed 1k 0x3340...............................................................[2021-08-01 16:22:14.710] UnUsed 1k 0x3740...............................................................[2021-08-01 16:22:14.725] UnUsed 1k 0x3B40...............................................................[2021-08-01 16:22:14.725] 0x3F40 00000000 00000000 00000000 00744800 ;.............tH.[2021-08-01 16:22:14.725] 0x3F50 C11A81E1 013F3000 04000001 61CB0069 ;.....?0.....a..i[2021-08-01 16:22:14.725] 0x3F60 EA3F9574 483F993F 993F9869 88921D88 ;.?.tH?.?.?.i....[2021-08-01 16:22:14.725] 0x3F70 921D89E2 1DD81202 00250089 E21DD80C ;.........%......[2021-08-01 16:22:14.725] 0x3F80 0088921D D80074FB 1DD875B1 1BAB0077 ;......t...u....w[2021-08-01 16:22:14.725] 0x3F90 271DB600 003F0000 0400845B 3FA90000 ;'....?.....[?...[2021-08-01 16:22:14.725] 0x3FA0 1D3FB21D F3030001 BF27C40F DF000000 ;.?.......'......[2021-08-01 16:22:14.725] 0x3FB0 0146A000 00B5D401 0200002A 073FCA40 ;.F.........*.?.@[2021-08-01 16:22:14.725] 0x3FC0 2B010140 0E402A1D F385E200 85728571 ;+..@.@*......r.q[2021-08-01 16:22:14.725] 0x3FD0 74483FFD 3FFC0000 00027448 01143FF7 ;tH?.?.....tH..?.[2021-08-01 16:22:14.725] 0x3FE0 F3007448 40180001 3838FFFD 0000FFFC ;..tH@...88......[2021-08-01 16:22:14.725] 0x3FF0 40500006 4014046E 14FFB500 0088921D ;@P..@..n........[2021-08-01 16:22:14.725] 0x4000 89E21DD8 12000025 0089E21D D80C0088 ;.......%........[2021-08-01 16:22:14.725] 0x4010 921DD800 74FB1DD8 75B11BAB 0077271D ;....t...u....w'.[2021-08-01 16:22:14.725] 0x4020 B600A040 000000A0 845B4037 00051D40 ;...@.....[@7...@[2021-08-01 16:22:14.725] 0x4030 40888892 1D8940C3 00014056 000F1429 ;@.....@...@V...)[2021-08-01 16:22:14.725] 0x4040 1E4E40C3 00016E74 4869CB1A 813D3C74 ;.N@...ntHi...=<t[2021-08-01 16:22:14.881] 0x4050 4802F302 000135CB 00744840 8F008F40 ;H.....5..tH@...@[2021-08-01 16:22:14.881] 0x4060 8B694A40 6E408D1A 80180000 0071E348 ;.iJ@n@.......q.H[2021-08-01 16:22:14.881] 0x4070 00C11A81 744869A0 1A817448 744800C1 ;....tHi...tHtH..[2021-08-01 16:22:14.881] 0x4080 001B0074 481ABB1A 814840A4 00003000 ;...tH....H@...0.[2021-08-01 16:22:14.881] 0x4090 1A9B40C3 40900500 404EAB05 2E2E402E ;..@.@...@N....@.[2021-08-01 16:22:14.881] 0x40A0 402E2E2E 404E2E2E 2E2E402E 00201440 ;@...@N....@.. .@[2021-08-01 16:22:14.881] 0x40B0 D7701A40 B64C566E 260B000B 008E261E ;.p.@.LVn&.....&.[2021-08-01 16:22:14.881] 0x40C0 001E0011 18060006 0040D000 1B2C0000 ;.........@...,..[2021-08-01 16:22:14.881] Free ram never allocated between (bytes dec) 6144 and 6161after running for two hours
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950[2021-08-01 18:20:14.715] dumpFreeRam from heap(low)=0x2721to stack(high)=0x40B9) size(dec):6552[2021-08-01 18:20:14.715] 0x2720 31150000 0032312D 30382D30 31203137 ;1....21-08-01 17[2021-08-01 18:20:14.715] 0x2730 3A32303A 30302C00 2D30312E 63737600 ;:20:00,.-01.csv.[2021-08-01 18:20:14.715] 0x2740 1D000000 5F52435F 74657374 3034625F ;...._RC_test04b_[2021-08-01 18:20:14.715] 0x2750 32303231 2D30382D 30312E63 73760078 ;2021-08-01.csv.x[2021-08-01 18:20:14.715] 0x2760 3031001F 0000006C 6C65724E 616E6F6C ;01.....llerNanol[2021-08-01 18:20:14.715] 0x2770 6576656C 20617420 6D6F6462 75735F30 ;evel at modbus_0[2021-08-01 18:20:14.715] 0x2780 78303100 00006C6C 65724E61 6E6F6C65 ;x01...llerNanole[2021-08-01 18:20:14.715] 0x2790 76656C20 6174206D 6F646275 735F3078 ;vel at modbus_0x[2021-08-01 18:20:14.715] 0x27A0 30310061 79666C79 003A3030 00003330 ;01.ayfly.:00..30[2021-08-01 18:20:14.715] 0x27B0 00050000 00323600 05000000 33300005 ;.....26.....30..[2021-08-01 18:20:14.715] 0x27C0 00000032 36000500 00003236 00000000 ;...26.....26....[2021-08-01 18:20:14.715] UnUsed 1k 0x27D0...............................................................[2021-08-01 18:20:14.715] UnUsed 1k 0x2BD0...............................................................[2021-08-01 18:20:14.715] UnUsed 1k 0x2FD0...............................................................[2021-08-01 18:20:14.731] UnUsed 1k 0x33D0...............................................................[2021-08-01 18:20:14.731] UnUsed 1k 0x37D0...............................................................[2021-08-01 18:20:14.731] UnUsed 1k 0x3BD0...............................................[2021-08-01 18:20:14.731] 0x3ED0 00000000 00000000 00000000 00005003 ;..............P.[2021-08-01 18:20:14.731] 0x3EE0 000C0040 0089201D 8A701DE3 12010025 ;...@.. ..p.....%[2021-08-01 18:20:14.731] 0x3EF0 008A701D E30C0089 201DE300 75021DE3 ;..p..... ...u...[2021-08-01 18:20:14.731] 0x3F00 75B81BB6 00772E1D C100203F 00000220 ;u....w.... ?...[2021-08-01 18:20:14.731] 0x3F10 84E93F1F 00011DC1 02000000 022022DC ;..?.......... ".[2021-08-01 18:20:14.731] 0x3F20 E53F283F E4898920 1D8A701D E3120000 ;.?(?... ..p.....[2021-08-01 18:20:14.731] 0x3F30 89201D00 251D0000 A189201D E3017502 ;. ..%..... ...u.[2021-08-01 18:20:14.731] 0x3F40 1DE324CF 1BB60104 1B89201D 8A701DE3 ;..$....... ..p..[2021-08-01 18:20:14.731] 0x3F50 12017572 1D8A701D E30C0089 201DE300 ;..ur..p..... ...[2021-08-01 18:20:14.731] 0x3F60 75021DE3 7589201D 8A701DE3 12020025 ;u...u. ..p.....%[2021-08-01 18:20:14.731] 0x3F70 008A701D E30C0089 201DE300 75021DE3 ;..p..... ...u...[2021-08-01 18:20:14.731] 0x3F80 75B81BB6 00772E1D C100003F 00000400 ;u....w.....?....[2021-08-01 18:20:14.731] 0x3F90 84E93F9F 00001D3F A81DFE03 0001BF28 ;..?....?.......([2021-08-01 18:20:14.750] 0x3FA0 FE0FE900 0000007B 480000B5 69010200 ;.......{H...i...[2021-08-01 18:20:14.750] 0x3FB0 002B963F C0402101 01400440 201DFE86 ;.+.?.@!..@.@ ...[2021-08-01 18:20:15.012] 0x3FC0 70744F3F F43FF300 03000300 02272301 ;ptO?.?.......'#.[2021-08-01 18:20:15.012] 0x3FD0 744F0174 4F401040 10000700 070006FF ;tO.tO@.@........[2021-08-01 18:20:15.012] 0x3FE0 FB012200 00C36646 00064000 2500FF00 ;.."...fF..@.%...[2021-08-01 18:20:15.012] 0x3FF0 A1210189 201D8A70 1DE30025 00FF008A ;.!.. ..p...%....[2021-08-01 18:20:15.012] 0x4000 701DE30C 0089201D E3007502 1DE375B8 ;p..... ...u...u.[2021-08-01 18:20:15.012] 0x4010 1BB60077 2E1DC100 A0400000 00A084E9 ;...w.....@......[2021-08-01 18:20:15.012] 0x4020 402D0005 1D403689 89201D8A 40B90002 ;@-...@6.. ..@...[2021-08-01 18:20:15.012] 0x4030 404C00D8 0011154F 40B90002 6E744F00 ;@L.....O@...ntO.[2021-08-01 18:20:15.012] 0x4040 C11A8CA1 01403100 01000140 31000021 ;.....@1....@1..![2021-08-01 18:20:15.012] 0x4050 4F408540 8540836A D0406440 831A8B40 ;O@.@.@.j.@d@...@[2021-08-01 18:20:15.012] 0x4060 A2000071 EA1D8A70 744F744F 1A744F6B ;...q...ptOtO.tOk[2021-08-01 18:20:15.012] 0x4070 8C1A744F 00C10830 0002FF2E 0100744F ;..tO...0......tO[2021-08-01 18:20:15.012] 0x4080 00000000 1A004030 73B94000 40000000 ;......@0s.@.@...[2021-08-01 18:20:15.012] 0x4090 AE382E38 2E382E38 2E382E38 2E382E38 ;.8.8.8.8.8.8.8.8[2021-08-01 18:20:15.012] 0x40A0 2E380074 0040D700 1E6FF740 D7204D40 ;.8.t.@...o.@. M@[2021-08-01 18:20:15.012] 0x40B0 D7702140 B64DDCA7 26181706 0006001E ;.p!@.M..&.......[2021-08-01 18:20:15.013] Free ram never allocated between (bytes dec) 5888 and 5912The utility is in my fork, search for dumpFreeRam() in following
https://github.com/neilh10/ModularSensors/commit/842eab880fdf6548d8b6d14951e4f0ad45727ecd
@aufdenkampe many thanks. Appreciate this is covering timing issues that are a bit hard to flush out.I suppose I’m the messenger in checking the system to what appears to be the bar from the
@aufdenkampe many thanks. Appreciate this is covering timing issues that are a bit hard to flush out.I suppose I’m the messenger in checking the system to what appears to be the bar from the Mayfly, but its a pretty hard area to checkout – all I can say is that as the messenger I’ve seen the challenges in other systems and was trying to give the headsup with figuring out what the best way of characterizing 5the system with https://github.com/ODM2/ODM2DataSharingPortal/issues/524
My LTE systems when responding is now doing so in 10seconds, or timing out at 25seconds.
info on https://github.com/ODM2/ODM2DataSharingPortal/issues/542
What’s nice it does appear to be getting to the database.I cleared browsing date for “cached images and files” & “browsing history” (a complete clear of everything is quite educational to recover from)
https://support.google.com/I cleared browsing date for “cached images and files” & “browsing history” (a complete clear of everything is quite educational to recover from)
https://support.google.com/accounts/answer/32050
and it worked. thanks for the tipThanks for the update. The system that I had that wasn’t reporting this morning is now reporting – https://monitormywatershed.org/sites/TUCA_PO03/ as of Dec. 10, 2021, 10:30 a.m. (UTC-08:Thanks for the update. The system that I had that wasn’t reporting this morning is now reporting – https://monitormywatershed.org/sites/TUCA_PO03/ as of Dec. 10, 2021, 10:30 a.m. (UTC-08:00)I’m logging in using FireFox for my production sites and Chrome for my test sites.
For the above it looks different under the different browsers, and the TSV is accessible under FireFox, but not under Chrome, do you want me to log an issue on it?For my status, there is one site that started uploading, OK – which is good as its about 3hours drive time.One site that hasn’t updated. Its on private land and requires permission to en
For my status, there is one site that started uploading, OK – which is good as its about 3hours drive time.One site that hasn’t updated. Its on private land and requires permission to enter the property, and its usually only done when there is a group of activities on the site. Its about one hour drive away.
Both are on verizon.For my local test system, running over verizon I monitor the output of the connection process. Its having a lot of timeouts. The timeout is set to 5seconds.
-
AuthorPosts
