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

    Huge current drain

    Scheduled Pinned Locked Moved WiPy 2&3
    current 400maflash read err
    14 Posts 4 Posters 2.5k Views 4 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.
    • D Offline
      deadpixel
      last edited by

      @robert-hh Thanks again... I wish this Warning was on the Getting Started Section rather than notes...
      Will see if my wipy is still alive... :(

      robert-hhR L 2 Replies Last reply Reply Quote 0
      • robert-hhR Offline
        robert-hh @deadpixel
        last edited by

        @deadpixel If it is not working any more, it's probably the regulator chip which is dead. That's the smaller one of the two chips next to the RGB LED. If you unsolder it, you can supply the WiPy through the 3V3 Pin (now!).

        L 1 Reply Last reply Reply Quote 0
        • L Offline
          Les-A
          last edited by

          Thank you for this. I got mine yesterday, had real problems doing the initial update and after eventually booting to a python prompt (once) it started going haywire and almost burned out two power supplies while I tried to discover what was going on.

          1 Reply Last reply Reply Quote 0
          • L Offline
            Les-A @deadpixel
            last edited by

            @deadpixel could you tell me if you managed to get this fix to work?

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

              @robert-hh could you tell me whether, after making this mod, it is still possible to supply the device through the 5v pin or can I only now use the 3.3v pin and whichever way, is it now only safe to use a 3.3v supply?

              robert-hhR 1 Reply Last reply Reply Quote 0
              • robert-hhR Offline
                robert-hh @Les-A
                last edited by

                @les-a If you remove the voltage regulator, you MUST supply the device by the 3.3V Pin with an appropriate voltage.

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

                  @robert-hh Thank you for your help. The VR popped off easily with a sharp craft knife and I now have the python prompt. Just need to figure out why none of my typing is appearing in the putty screen.

                  J 1 Reply Last reply Reply Quote 0
                  • J Offline
                    jcaron @Les-A
                    last edited by

                    @les-a If you have upgraded to the latest 1.10.0.b1 firmware, that seems to be a recurring issue. Until a fix is released you'll have to downgrade to the previous version.

                    L 1 Reply Last reply Reply Quote 0
                    • L Offline
                      Les-A @jcaron
                      last edited by

                      @jcaron Thanks. Yes, that is the firmware I downloaded yesterday. Just done a factory reset boot and, by George!, normal service is resumed.

                      robert-hhR 1 Reply Last reply Reply Quote 0
                      • robert-hhR Offline
                        robert-hh @Les-A
                        last edited by robert-hh

                        @les-a The factory reset boot does nothing but to ignore boot.py and main.py. So if you remove boot.py or replace it with an empty on, it should work too. There seems to be a problem with duplicate setting dupterm() on uart0. That happens already in the frozen _boot.py, and sometimes that is also done in boot.py.

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

                          @robert-hh Thanks, I'll keep that in mind. As this is only day 2 I'm afraid I'm still finding my way around the documentation - so far have used Putty from R-Pi to do stuff to get round the USB problem but not yet ventured into FTP or Tools - unfortunately Atom .deb is only for AMD64 and I'm using 32 ... my heart sinks!

                          robert-hhR 1 Reply Last reply Reply Quote 0
                          • robert-hhR Offline
                            robert-hh @Les-A
                            last edited by

                            @les-a If you stay away from atom+pymakr and stick with putty and ftp tranfer, you'll save yourself a lot of trouble.

                            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