<![CDATA[UIFLOW, Core2, PIR-Sensor Blockly wrongfully assuems that the PIR-Sensor is connected to PORTB]]>

<![CDATA[UIFLOW, Core2, PIR-Sensor Blockly wrongfully assuems that the PIR-Sensor is connected to PORTB]]>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

]]>https://community.m5stack.com/topic/5547/uiflow-core2-pir-sensor-blockly-wrongfully-assuems-that-the-pir-sensor-is-connected-to-portbRSS for NodeWed, 22 Apr 2026 20:09:40 GMTFri, 04 Aug 2023 18:26:04 GMT60<![CDATA[Reply to UIFLOW, Core2, PIR-Sensor Blockly wrongfully assuems that the PIR-Sensor is connected to PORTB on Sat, 05 Aug 2023 12:02:57 GMT]]>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.

]]>https://community.m5stack.com/post/21797https://community.m5stack.com/post/21797Sat, 05 Aug 2023 12:02:57 GMT