<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Oh, crap.<div class=""><br class=""></div><div class="">Someone (probably me) made a typo on the layout.</div><div class=""><br class=""></div><div class="">It seems the guys in China working on testing power consumption removed BOTH the BTS452R and R17/R18 voltage divider network and saw a 20mA drop in consumption (and assumed the cause was the BTS452R).</div><div class=""><br class=""></div><div class="">Turns out the problem is the R17/R18 voltage divider network. According to simulators:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class="" style="font-family: Arial; font-size: 14px;">With 475R and 100R, current is 17.39mA.</div><div class="" style="font-family: Arial; font-size: 14px;">With 475K and 100K, current is 17.39uA.</div></div></blockquote><div class=""><br class=""></div><div class="">A typo “R” not the same as “K”, and that was about 20mA.</div><div class=""><br class=""></div><div class="">With that (silly, annoying, crazy, typo) fixed (changing to 500K and 100K for the voltage divider), we’re now about 13mA, or about 2mA without the MCP2515 and transceivers connected. I think the remaining 10mA or so is the MCP2515 not in sleep mode. But, I’m still fighting the SPI bus control on those. Hopefully will have this final bit nailed in the next 24 hours.</div><div class=""><br class=""></div><div class="">Regards, Mark.</div><div class="">(and thanks to Edward for stepping in to help)</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 3 Jul 2017, at 3:59 PM, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net" class="">mark@webb-johnson.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Thanks. That makes sense. I’ve passed this on to the China side to see what they suggest as the simplest solution.<br class=""><br class="">The good news is we’ve found the issue with the CP2102. We’ve now re-worked that to be purely USB powered, and now when we power from 12V, that consumption falls to ZERO. So in the normal use case of 12V power from the car, the CP2102 will be powered off completely. That saves us 5mA in deep sleep.<br class=""><br class="">Regards, Mark.<br class=""><br class=""><blockquote type="cite" class="">On 3 Jul 2017, at 3:51 PM, Edward Cheeseman <<a href="mailto:cheesemanedward@gmail.com" class="">cheesemanedward@gmail.com</a>> wrote:<br class=""><br class="">No I think ST shouldn't be connected to ground. The pcb output didn't have the ground net so couldn't tell so check to make sure.<br class=""><br class="">What is more likely the problem is the device has an input resistance and constant current sink. The max7137 output is open drain with the 10k pull-up. 10k may be upsetting the mosfet charge pump. Try removing R9 to see if current consumption drops. Unfortunately it looks like you need to drive the pin high with an output. Maybe use a pmos (e.g. bss223bw) connected D-> IN pin, S->3V3, G-> R9 and max7137.<br class=""><br class="">Edward<br class=""><br class=""><blockquote type="cite" class="">On 3/07/2017, at 7:17 PM, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net" class="">mark@webb-johnson.net</a>> wrote:<br class=""><br class="">Attached is the board layout, if it helps.<br class=""><br class="">Thanks for the hints. I will check on the physical board with a multi-meter. From my memory, the tab went to Vbb and pin #3 was floating in the air.<br class=""><br class="">Regards, Mark.<br class=""><br class="">P.S. If I ground pin #4 (ST) and power consumption drops 20mA, I’ll owe you more than a beer :-)<br class=""><br class=""><OVMS_V3_Board_CN_20170615.pdf><br class=""><br class=""><blockquote type="cite" class="">On 3 Jul 2017, at 3:01 PM, Edward Cheeseman <<a href="mailto:cheesemanedward@gmail.com" class="">cheesemanedward@gmail.com</a>> wrote:<br class=""><br class="">Also, as pin3 is a stub that doesn't reach the board, is the tab connected in its place? Plenty to go wrong between schematic and pcb with missing pin devices!<br class=""><br class=""><blockquote type="cite" class="">On 3/07/2017, at 6:59 PM, Edward Cheeseman wrote:<br class=""><br class="">Have you grounded pin4 "ST" diagnostic output? It's not on the schematic, so depends what is on the pcb...<br class=""><br class="">Edward<br class=""><br class=""><blockquote type="cite" class="">On 3/07/2017, at 6:21 PM, Mark Webb-Johnson wrote:<br class=""><br class="">I feel your pain. The board I have is working fine - but I just need to be 100% sure we can get the power consumption down to near-zero in a deep sleep, before I ask China to build a bunch. I don’t want to deliver boards to you that need hardware modification in the long-term.<br class=""><br class="">For that, I need to get all the peripherals to sleep, and for that I need SPI working, and for that … you get the idea. I’m close. MAX7317 SPI is now working, so I’m now on MCP2515 SPI (which is a lot more complex, as it relies on the unified CAN framework and that means esp32can library).<br class=""><br class="">Anyway, I’ll know maybe tonight / tomorrow whether the SPI peripherals can be powered down. That just leaves the CP2102 (USB/UART) and BTS452R. I originally thought the problem was with the CP2102, but that seems to be only 5mA of the problem. We’re also seeing 20mA on the BTS452R, but that makes no sense at all (as it is just a smart mosfet++).<br class=""><br class="">If there any hardware gurus here who want to look at the circuit layout and tell me what’s wrong with the BTS452R arrangement, I’ve attached the latest layout diagram.<br class=""><br class="">Regards, Mark.<br class=""><br class=""><OVMS_V3_Layout_CN_20170615.pdf><br class=""><br class=""><br class=""><blockquote type="cite" class="">On 3 Jul 2017, at 4:16 AM, Michael Balzer <<a href="mailto:dexter@expeedo.de" class="">dexter@expeedo.de</a>> wrote:<br class=""><br class="">Mark,<br class=""><br class="">build environment up & running, V3 framework builds without problems.<br class=""><br class="">But I've got no DevKitC, it's unavailable here, would need to dig into<br class="">compatible ones.<br class=""><br class="">I second the question / wish about developing directly on the V3... :)<br class=""><br class="">Regards,<br class="">Michael<br class=""><br class=""><br class=""><blockquote type="cite" class="">Am 02.07.2017 um 16:26 schrieb Mark Webb-Johnson:<br class="">To get it up and running on a DEVKIT-C style device<br class=""></blockquote><br class="">-- <br class="">Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal<br class="">Fon 02333 / 833 5735 * Handy 0176 / 206 989 26<br class=""><br class="">_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></blockquote><br class="">_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></blockquote></blockquote>_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></blockquote><br class="">_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></blockquote>_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></blockquote><br class="">_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></div></div></blockquote></div><br class=""></div></body></html>