A Forum run by Enthusiasts of MidNite Solar

MidNite Solar Monitoring software and hardware => My MidNite online monitoring => Topic started by: heinburgh on May 08, 2015, 01:01:52 AM

Title: Classic Data Usage
Post by: heinburgh on May 08, 2015, 01:01:52 AM
Has anyone figured out just how much data a classic uses when talking to the mymidnite server? Our only available internet is through cellular providers, data going at $13/Gb. I guess the exchange is a bit more with the new test site having a higher update frequency.
Title: Re: Classic Data Usage
Post by: atop8918 on May 10, 2015, 02:21:19 PM
Yeah I have these figures somewhere in my design documents but I keep losing track of them. I'll see if I can dig them up. The latest Alpha firmware uses substantially less than the older firmware even with the increased polling time. The polling time will also get dialed back a bit for general release to reduce the load on the server.
Title: Re: Classic Data Usage
Post by: atop8918 on May 10, 2015, 02:40:19 PM
The Classic uses approximately 2,019 bytes every time it dumps data to the mymidnite server. This is approximate because there are mitigating factors like additional HTTP headers added by inter-router hops, packet splitting and reassembly, bad connections, etc. This number includes all the TCP traffic such as SYN, ACK and FIN packets as well.

Title: Re: Classic Data Usage
Post by: heinburgh on May 11, 2015, 02:07:51 PM
Thanks. How often does it send this?
Title: Re: Classic Data Usage
Post by: atop8918 on May 11, 2015, 02:48:27 PM
On the test server it's once every 5 minutes or so, when we go to production it will be more like 10-15 minutes.
Title: Re: Classic Data Usage
Post by: heinburgh on May 12, 2015, 09:31:15 AM
So it's the server determining when it pulls data, not the classic pushing at a set interval?
Title: Re: Classic Data Usage
Post by: atop8918 on May 12, 2015, 09:33:54 AM
When released for production the Classic will try to log in to the server every 5-10 minutes, the server will either let it continue to log in or deny the log in  based on its own configuration.  Only after a successful login will the Classic dump its data to the server.