Schematic?

[vern.muhr]

Where can I find the schematic for the 3.0 expansion board? Also, I suggest that when you have the board assembled, you request that the rows of holes between the WiPy connector and the headers be masked so they will be free of solder. That way, headers can be inserted from the solder side so the exp. board can be plugged into a project board.

[dan]

Hi @vern-muhr,

Have you looked at this page in the documentation? The pinout and datasheet can be found there.

[vern.muhr]

@dan

Any Ides where the SCHEMATIC is?

[dan]

@vern-muhr it's a proprietary design, so I'm afraid we can't share it. If you'd like to license the technology, email sales@pycom.io

[robert-hh]

@dan PyCom is very anxious for sharing their designs. But making an expansion board is not rocket science. So it should be pretty easy to make one which serves for the purpose.

[Martinnn]

@dan If you are afraid of having your hardware pirated and sold on ebay or aliexpress (as happened to the poor Saleae guys), not publishing the schematic will probably hold up counterfeiters only for a short time.

But it really hurts us developers. Having to follow PCB traces under the microscope just to figure out how to use your boards is unacceptable. If you really want to address the professional market, you should rethink your documentation strategy.

[vern.muhr]

@dan
So be it. But, why provide a schematic for the 2.0 expansion board, but not the 3.0 board? I don't want to build my own board. I just want to know what is wired to what. I'm an EE. I care about these things.

[zeroro]

@vern-muhr : you have the extention board 2.0 schematic ? Please could you share ?

[ShanevanJ]

@vern-muhr So why don't we as the community, create an OSH expansion board to do want we want? - there must be enough interested folks to do this - I am happy to start this off - so send me a list of "must have" features and lets do it (PS. I need one for a project I am starting anyway) - so lets make something that ticks all the right boxes ?

[Carolyn Pierce]

If you really want to address the professional market, you should rethink your documentation strategy.

[Gijs]

@Carolyn-Pierce let me know what you're looking for, or missing, in the documentation and I'd be happy to help. Unfortunately I still cannot share any schematics with you, but I would be glad to help you figure out any issues or missing information.

[robert-hh]

@Gijs What happened to the promise of Daniel Campora to publish the Source Code of the Deep Sleep Shield? I know that Daniel is on his extended sabbatical, but I understood that he talked for the company.
See: https://forum.pycom.io/topic/1022/root-causes-of-high-deep-sleep-current-lopy1-wipy2-and-sipy-all-the-new-modules-do-not-have-deepsleep-issues/108?_=1617474671529

[Gijs]

I'll owe you the answer to that question. I'm sort of aware of the issue you link in and what the deepsleep shield does, but Daniel left the company before I started. Now I dont want to go back on his promise, but I cannot guarentee we're still out to deliver on it. I'll try to sort it out on Monday

[robert-hh]

@Gijs Don't hurry. It is not urgent at all. And the while discussion about expansion boards will disappear when eventually pycom will switch to the new espressif chips with built-in USB support. I guess that this will be one of the next development steps, after PyGo or with PyGo.

[livius]

@robert-hh
yes, new chips are really interesting. Reading draft version of docs are promising.
As they send some testing parts already i suppose full delivery and final version of docs will be really soon.

I am really interested if ADC will be better in new chips ;-)