Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runutime Control Display bug #47

Closed
zengxiaolei opened this issue Dec 13, 2019 · 4 comments
Closed

Runutime Control Display bug #47

zengxiaolei opened this issue Dec 13, 2019 · 4 comments
Assignees

Comments

@zengxiaolei
Copy link

zengxiaolei commented Dec 13, 2019

What I have done is as follows:

  1. Use flexbe_app to run behavior_1
  2. After bahavior_1 is completed, keep flexbe_app opening, but run behavior_2 by calling action (http://wiki.ros.org/flexbe/Tutorials/Running%20Behaviors%20Without%20Operator).
  3. After behavior_2 is completed, run behavior_1 again by flexbe_app. Behavior works, but no runtime control display in the app. As shown by Fig. 1, on-board status is running and initialization is done, which is really done. Since the display is empty, I cannot continue the next state since a high-level outcome is to be verified as shown in Fg. 2.

image
Fig. 1

image
Fig. 2

I tried to stop Execution and restart behavior for many times, but problem remains.

@pschillinger
Copy link
Member

Thanks for reporting, I can reproduce this bug and will look into it.

@pschillinger pschillinger self-assigned this Dec 13, 2019
pschillinger added a commit to team-vigir/flexbe_behavior_engine that referenced this issue Dec 13, 2019
@pschillinger
Copy link
Member

It turned out that the FlexBE App worked as intended, but the issue was caused by flexbe_mirror due to improper release of its thread lock. Consequently, it did not send any behavior updates to the App afterwards.

I fixed it with the above commit.

@zengxiaolei
Copy link
Author

It works!

@pschillinger
Copy link
Member

Fixed in flexbe_behavior_engine version 1.2.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants