Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login
    1. Home
    2. Tags
    3. expansionboard

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

    Log in to post

    • All categories
    • M

      I2C PINOUT QUESTION

      Watching Ignoring Scheduled Pinned Locked Moved Expansion Board wipy 2.0 i2c expansionboard
      6
      0 Votes
      6 Posts
      2k Views
      M
      @jmarcelino Thanks - that worked a treat (pull ups on P9/10 seem to be enabled by default which made life easier)
    • C

      Schematics of WiPy 2.0, ExpansionBoard 2.0 etc.

      Watching Ignoring Scheduled Pinned Locked Moved Discussion wipy 2.0 expansionboard hardware schematics
      3
      0 Votes
      3 Posts
      3k Views
      P
      I am looking the shematic of the expansion board forWipy 2.0. Somebody can help me ?
    • J

      Expansion board 1.0 layout

      Watching Ignoring Scheduled Pinned Locked Moved WiPy 2&3 wipy 1 expansionboard
      1
      0 Votes
      1 Posts
      883 Views
      No one has replied
    • J

      Future Expansion Board suggestions

      Watching Ignoring Scheduled Pinned Locked Moved MicroPython expansionboard suggestions
      4
      5 Votes
      4 Posts
      2k Views
      B
      After a week playing with my new LoPy modules and the expansion board, here is my list of suggestions: I found very confusing the difference in numbering between the LoPy pinout (Pxx, GPIOxx, pin numbers... and the expansion board (Gxx). @jmarcelino has mentioned this already. I don't really understand why the user button and the LED are mapped on the same pins used for I2C. Why not any pin on the right hand side not used for other functions P12-P22? It would be great to add a couple of Grove connectors mapped to the I2C pins and two other GPIO pins. They are pretty much the standard these days and there are plenty of sensor modules available. A solar charging circuit and connector would be awesome for so many projects. Using a solar panel on the USB is kind of risky and definitely not ideal.
    • I

      WiPy 2.0 + Expansion Board 2.1A I²C & Button

      Watching Ignoring Scheduled Pinned Locked Moved WiPy 2&3 expansionboard wipy2.0 i2c
      7
      0 Votes
      7 Posts
      3k Views
      I
      @robert-hh A usage of the I2C hardware implementation was just a guess because I2C with the 8266 was such a mess. I wanted to use a MPU9250 and checked the clock bus using an TDS2024B oscilloscope. Every pulse of the clock signal was a mess (and different from each other!) so I thought that the WiPy with the ESP32 uses the hardware implementation because it worked out of the box. @jmarcelino Thank you for clearing things up!
    • C

      External SD Card with WiPy - LoPy etc

      Watching Ignoring Scheduled Pinned Locked Moved MicroPython wipy2.0 lopy sdcard expansionboard
      2
      0 Votes
      2 Posts
      1k Views
      J
      @constantinos The pins are on the Expansion Board data sheet: https://docs.pycom.io/pycom_esp32/_downloads/exp_v03_pinout_v13.pdf SD_CMD, SD_DATA, SD_CLK
    • S

      Code only runs fully with USB plugged in - SOLVED

      Watching Ignoring Scheduled Pinned Locked Moved WiPy 2&3 wipy2.0 expansionboard usb error
      14
      0 Votes
      14 Posts
      4k Views
      S
      SOLVED - I powered the stepper motor separately and all is good. I'm guessing there were transient demands in excess of the 800mA I could measure that were causing problems.
    • J

      expansion board 2.1a

      Watching Ignoring Scheduled Pinned Locked Moved Expansion Board lopy expansionboard
      7
      0 Votes
      7 Posts
      3k Views
      J
      hi all, thx for all the responses, i've got the exp. board (in combination with the lopy) working. the vcp driver did the trick :) thx :) :)
    • M

      Expansion board (WiPy/LoPy) and WiPy mismatch

      Watching Ignoring Scheduled Pinned Locked Moved Expansion Board wipy expansionboard
      4
      0 Votes
      4 Posts
      1k Views
      M
      seems that is exactly what happened, the description on amazon said the expansion would fit either version, I honestly didnt know I was ordering the old version of the WiPy it didnt have a version number on the description. I rma'd the 1.3 board and ordered a 2.0 board. They should put better description on Amazon for both items to avoid this stuff. https://www.amazon.com/Pycom-C1002-WiPy/dp/B01HFAKK5C/ref=sr_1_1?ie=UTF8&qid=1489281512&sr=8-1&keywords=WiPy
    • R

      3D model ExpansionBoard V2

      Watching Ignoring Scheduled Pinned Locked Moved Expansion Board expansionboard
      1
      4 Votes
      1 Posts
      1k Views
      No one has replied
    • L

      Can't seem to fint the I2C pins on the expansion board (using SiPy)

      Watching Ignoring Scheduled Pinned Locked Moved Expansion Board i2c sipy expansionboard
      5
      0 Votes
      5 Posts
      2k Views
      L
      Thanks to Livius. That worked!
    • K

      Detecting an inserted SD card

      Watching Ignoring Scheduled Pinned Locked Moved WiPy 2&3 wipy help expansionboard sdcard
      7
      0 Votes
      7 Posts
      2k Views
      L
      @daniel I just test this and the behaviour is still as before. Trying to initialize the SD card without a SD inserted raises a OSError exception, which is OK. my English is bad and when i wrote Something was changed. than this was only assumption - i do not test this with current 1.6.3 firmware i tested this on 1.5.0 and it worked - and if for @kanu it does not work then i supposed that he tested this with current firmware Card detection is simply done via a GPIO pin good point - i must connect it :)
    • T

      Mapping G and P pin numbers

      Watching Ignoring Scheduled Pinned Locked Moved LoPy lopy pin numbering expansionboard
      3
      0 Votes
      3 Posts
      4k Views
      T
      @rskoniec Great! Thanks a lot
    • 1
    • 2
    • 2 / 2