FlowBotics Studio v2.0.3 AL5-D demo bug?

Help & Support Apps & Software
1

Looks like there’s a bug when reading the input state of SSC-32 ports A, B, C, and D from within the FlowBotics Studio v2.0.3 AL5-D demo. When port A on the SSC-32 is brought low, the GUI properly shows LED A lighting up. However, bringing port B on the SSC-32 low also lights LED A instead of B on the GUI. Similarly, bringing SSC-32 port C low causes GUI LED B to light instead of C, and bringing SSC-32 port D low causes GUI LED C to illuminate, not D.

I took a brief look at the “Input LEDs” FlowStone module in the demo, but didn’t spot the problem (I’m new to FlowStone, so it could be staring me right in the face!) I hope someone can verify that this is actually incorrect demo behavior and explain the fix in FlowStone. And if it’s not a bug, can you explain the logic of what I’m seeing in my tests of the SSC-32 A-D ports? TIA.

2

Hi Greg,

You did indeed find a bug! Thanks for bringing it to our attention and we’ll fix it in the next version.

However, you can also make the fix yourself: that’s the power of the FlowStone language! If you go in edit mode and open the main ArmControl, open the main component there, and open the Input LEDs module in the bottom right quadrant, you will see an Int component with the value 2: change it to 1 and that will fix everything.

For the other FlowBotics projects, input A is used in the analog mode (which requires a value of 2) but, for the AL5 Arm project, input A is used in digital mode and therefore the value of 1 is required.

Thanks for choosing RobotShop,