3.1.2 short lived connections and high data usage
I’ve had a report from a user of 3.1.2 firmware reporting short connections and high data usage (reconnecting to server every few minutes). Logs look like this: 2017-02-11 22:27:42.936568 +0800 info main: #76 - - rx MP-C 0 (redacted) (redacted) VID 2017-02-11 22:27:42.937997 +0800 info main: #76 C VID crypt session key (redacted) 2017-02-11 22:27:42.938251 +0800 info main: #76 C VID tx MP-S 0 (redacted) (redacted) 2017-02-11 22:27:42.938852 +0800 info main: #76 C VID tx (Z 0) 2017-02-11 22:27:53.634604 +0800 info main: #76 C VID rx msg D 40,0,0,9,7,9,457,1061084,0,453159,6,0,119,117,11.3,33,11.4,0,0 2017-02-11 22:27:53.636440 +0800 info main: #76 C VID msg handle D 40,0,0,9,7,9,457,1061084,0,453159,6,0,119,117,11.3,33,11.4,0,0 2017-02-11 22:29:34.076615 +0800 info main: #76 C VID got error Broken pipe Anybody else seeing anything like this? Regards, Mark.
I am seeing much shorter data session times with Hologram since AT&T killed their GPRS support, leaving us with TMobile. Here's a summary of the data session records from Hologram. Session Start Session End Bytes Carrier 2017-02-12 20:28:44 2017-02-12 20:32:34 1810 T-Mobile USA, Inc. CO 2017-02-12 01:04:36 2017-02-12 02:29:18 3095 T-Mobile USA, Inc. CO 2017-02-11 21:57:09 2017-02-12 01:04:35 7118 T-Mobile USA, Inc. CO 2017-02-11 21:32:07 2017-02-11 21:57:00 1698 T-Mobile USA, Inc. CO 2017-02-11 21:21:02 2017-02-11 21:30:34 3466 T-Mobile USA, Inc. CO 2017-02-11 10:49:44 2017-02-11 11:23:59 1176 T-Mobile USA, Inc. CO 2017-02-11 10:34:48 2017-02-11 10:49:43 840 T-Mobile USA, Inc. CO 2017-02-11 10:19:55 2017-02-11 10:34:47 840 T-Mobile USA, Inc. CO 2017-02-11 10:05:01 2017-02-11 10:19:54 840 T-Mobile USA, Inc. CO 2017-02-11 09:50:22 2017-02-11 10:05:00 756 T-Mobile USA, Inc. CO 2017-02-11 09:31:42 2017-02-11 09:46:37 840 T-Mobile USA, Inc. CO 2017-02-11 09:16:47 2017-02-11 09:31:41 840 T-Mobile USA, Inc. CO Looking at the past 20 days, I'm not seeing increased data use, but I'm also seeing much spottier reliability in terms of being able to connect to OVMS, even when the car is out of our metal-roofed garage. I'm looking forward to the new hardware so I can get back to using AT&T. Tom On 2/27/17, 6:25 PM, "Mark Webb-Johnson" <ovmsdev-bounces@lists.teslaclub.hk on behalf of mark@webb-johnson.net> wrote: I’ve had a report from a user of 3.1.2 firmware reporting short connections and high data usage (reconnecting to server every few minutes). Logs look like this: 2017-02-11 22:27:42.936568 +0800 info main: #76 - - rx MP-C 0 (redacted) (redacted) VID 2017-02-11 22:27:42.937997 +0800 info main: #76 C VID crypt session key (redacted) 2017-02-11 22:27:42.938251 +0800 info main: #76 C VID tx MP-S 0 (redacted) (redacted) 2017-02-11 22:27:42.938852 +0800 info main: #76 C VID tx (Z 0) 2017-02-11 22:27:53.634604 +0800 info main: #76 C VID rx msg D 40,0,0,9,7,9,457,1061084,0,453159,6,0,119,117,11.3,33,11.4,0,0 2017-02-11 22:27:53.636440 +0800 info main: #76 C VID msg handle D 40,0,0,9,7,9,457,1061084,0,453159,6,0,119,117,11.3,33,11.4,0,0 2017-02-11 22:29:34.076615 +0800 info main: #76 C VID got error Broken pipe Anybody else seeing anything like this? Regards, Mark. _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
I've had no report on this and found no such effect in my logs. Maybe something with his/her account balance or data plan? Regards, Michael Am 28.02.2017 um 03:25 schrieb Mark Webb-Johnson:
I’ve had a report from a user of 3.1.2 firmware reporting short connections and high data usage (reconnecting to server every few minutes). Logs look like this:
2017-02-11 22:27:42.936568 +0800 info main: #76 - - rx MP-C 0 (redacted) (redacted) VID 2017-02-11 22:27:42.937997 +0800 info main: #76 C VID crypt session key (redacted) 2017-02-11 22:27:42.938251 +0800 info main: #76 C VID tx MP-S 0 (redacted) (redacted) 2017-02-11 22:27:42.938852 +0800 info main: #76 C VID tx (Z 0) 2017-02-11 22:27:53.634604 +0800 info main: #76 C VID rx msg D 40,0,0,9,7,9,457,1061084,0,453159,6,0,119,117,11.3,33,11.4,0,0 2017-02-11 22:27:53.636440 +0800 info main: #76 C VID msg handle D 40,0,0,9,7,9,457,1061084,0,453159,6,0,119,117,11.3,33,11.4,0,0 2017-02-11 22:29:34.076615 +0800 info main: #76 C VID got error Broken pipe
Anybody else seeing anything like this?
Regards, Mark.
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
participants (3)
-
Mark Webb-Johnson -
Michael Balzer -
Tom Saxton