Button on pytrack/pysense

  • What is the rationale to use:

       # from the pytrack software
       def button_pressed(self):
          button = self.peek_memory(PORTA_ADDR) & (1 << 3)
          return not button

    instead of reading the button P14 via a machine.Pin('P14').value() which seems a lot simpler, not to say doesn't use the I2C bus for peeking...

  • @Emmanuel-Goudot I sincerely hope Pycom will release the schematics.

    I have asked them a few times now and no response. IMHO This will do more harm than good for Pycom. It is not rocket science and it is crazy I see so many posts on people trying to reverse engineer the board(s) and even patch the firmware of the PIC by hand? The documentation is not complete or different depending on what file you read. To much time is already spend on finding out all the connections and how it works and even then it is not sure if it is correct or what side effects are possible. PYCOM: let us help you, there is a big community of enthusiastic users that can help you forward.

    I just finished comparing pysense/track/lopy wiring diagrams to find out which pins can be used.

  • According to this I understand that button is connected to

    • lopy/sipy P14
    • PIC (on pytrack/pysense) PA3 of PORT A
      When will we get schematics of pytrack/pysense instead of working on a blackbox ???

Log in to reply

Pycom on Twitter