Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    Schematic?

    Scheduled Pinned Locked Moved Ideas
    expansionboard
    15 Posts 9 Posters 1.9k Views 10 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M Offline
      Martinnn @dan
      last edited by

      @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.

      1 Reply Last reply Reply Quote 2
      • V Offline
        vern.muhr @dan
        last edited by

        @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.

        Z ShanevanJS 2 Replies Last reply Reply Quote 1
        • Z Offline
          zeroro @vern.muhr
          last edited by

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

          1 Reply Last reply Reply Quote 0
          • ShanevanJS Offline
            ShanevanJ @vern.muhr
            last edited by

            @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 ?

            Design | Develop | Deploy

            1 Reply Last reply Reply Quote 0
            • C Offline
              Carolyn Pierce
              last edited by

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

              1 Reply Last reply Reply Quote 0
              • G Offline
                Gijs
                last edited by

                @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-hhR 1 Reply Last reply Reply Quote 0
                • robert-hhR Offline
                  robert-hh @Gijs
                  last edited by

                  @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

                  1 Reply Last reply Reply Quote 1
                  • G Offline
                    Gijs
                    last edited by

                    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-hhR 1 Reply Last reply Reply Quote 0
                    • robert-hhR Offline
                      robert-hh @Gijs
                      last edited by

                      @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.

                      L 1 Reply Last reply Reply Quote 0
                      • L Offline
                        livius @robert-hh
                        last edited by

                        @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 ;-)

                        think about people first, then computers

                        1 Reply Last reply Reply Quote 0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better 💗

                        Register Login
                        • 1 / 1
                        • First post
                          Last post

                        Pycom on Twitter

                        Pycom