[Ovmsdev] OVMS v3 framework on GITHUB

[Mark Webb-Johnson]

Attached is the board layout, if it helps.

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.

Regards, Mark.

P.S. If I ground pin #4 (ST) and power consumption drops 20mA, I’ll owe you more than a beer :-)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OVMS_V3_Board_CN_20170615.pdf
Type: application/pdf
Size: 400394 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20170703/803d41d7/attachment-0002.pdf>
-------------- next part --------------

> On 3 Jul 2017, at 3:01 PM, Edward Cheeseman <cheesemanedward at gmail.com> wrote:
> 
> 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!
> 
>> On 3/07/2017, at 6:59 PM, Edward Cheeseman wrote:
>> 
>> Have you grounded pin4 "ST" diagnostic output? It's not on the schematic, so depends what is on the pcb...
>> 
>> Edward
>> 
>>> On 3/07/2017, at 6:21 PM, Mark Webb-Johnson wrote:
>>> 
>>> 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.
>>> 
>>> 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).
>>> 
>>> 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++).
>>> 
>>> 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.
>>> 
>>> Regards, Mark.
>>> 
>>> <OVMS_V3_Layout_CN_20170615.pdf>
>>> 
>>> 
>>>> On 3 Jul 2017, at 4:16 AM, Michael Balzer <dexter at expeedo.de> wrote:
>>>> 
>>>> Mark,
>>>> 
>>>> build environment up & running, V3 framework builds without problems.
>>>> 
>>>> But I've got no DevKitC, it's unavailable here, would need to dig into
>>>> compatible ones.
>>>> 
>>>> I second the question / wish about developing directly on the V3...  :)
>>>> 
>>>> Regards,
>>>> Michael
>>>> 
>>>> 
>>>>> Am 02.07.2017 um 16:26 schrieb Mark Webb-Johnson:
>>>>> To get it up and running on a DEVKIT-C style device
>>>> 
>>>> -- 
>>>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>>>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>>>> 
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.teslaclub.hk
>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>> 
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev