🤖Have you ever tried Chat.M5Stack.com before asking??😎
    M5Stack Community
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    UIFLOW, Core2, PIR-Sensor Blockly wrongfully assuems that the PIR-Sensor is connected to PORTB

    UIFlow
    2
    2
    1.4k
    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.
    • N
      Nestor89
      last edited by

      Hi,

      there is kind of a bug in uiflow on core2. if you connect the pir sensor the template code generated by blockly does not work.

      the generated phython code looks like that:
      from m5stack import *
      from m5ui import *
      from uiflow import *
      import unit

      setScreenColor(0x000000)
      pir0 = unit.get(unit.PIR, unit.PORTB)

      BVlockly assumes that the sensor is connected to PORTB. However the Port of Core 2 is named PORTA. If you change the value to PORTA, the code works. However oyu cant switch beack to blockly because blockly wants to habve the value as PORTB. Can this be fixed in uiflow2?

      Best regards,
      Nestior

      1 Reply Last reply Reply Quote 0
      • ajb2k3A
        ajb2k3
        last edited by

        That is because the PIR sensor is a port B device (black connection and by default is assigned to PortB, however, when you select the Unit In Uiflow2, you have the option to change the port.

        UIFlow, so easy an adult can learn it!
        If I don't know it, be patient!
        I've ether not learned it or am too drunk to remember it!
        Author of the WIP UIFlow Handbook!
        M5Black, Go, Stick, Core2, and so much more it cant be fit in here!

        1 Reply Last reply Reply Quote 1
        • First post
          Last post