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

fieldset not showing up correctly on new release 3.6.0 #408

Open
akashjinandra opened this issue Oct 24, 2024 · 2 comments
Open

fieldset not showing up correctly on new release 3.6.0 #408

akashjinandra opened this issue Oct 24, 2024 · 2 comments

Comments

@akashjinandra
Copy link

akashjinandra commented Oct 24, 2024

Hello all, I am using ROS 1 noetic and Ubuntu 20. I am using rviz to visualize the markers for the fieldsets.

In version 3.5.0 I get this:
sick-3-5-0
This is correct, there is an L shaped object is infringing the thin zone:
sick-3-5-0-with-annotation
However when I upgraded to version 3.6.0 the fieldset looked flipped compared to the lidar data:
sick-3-6-0
Here it is again with the L shaped object in the same place as in the picture from version 3-5-0
sick-3-6-0-with-annotation
I have 2 ros workspaces, one with version 3.5.0 and the other with 3.6.0. This is how I tested this change.

It seems like the lidar data is correct, but how the fieldsets are being drawn look opposite. This is confirmed when I use SICK SOPAS ET to also visualize the fields and lidar data.

Also the field reading clear or infringed is also correct, it's just that the lidar zone data is not lining up with the markers in rviz for the fieldset data.

@rostest
Copy link
Collaborator

rostest commented Oct 28, 2024

Thank you for your feedback! Due to a fieldset configuration error (internal index vs. fieldset number), the fields in the visualisation markers are displayed incorrectly. An update is provided in branch feature/issue_update_2412xx.
We have also corrected the FieldSetSelectionMethod in the ROS service /sick_tim_7xx/FieldSetWrite (#394).

Please use the update in branch feature/issue_update_2412xx and rebuild.

@akashjinandra
Copy link
Author

This feature is working for me on that branch you specified, but I will keep the issue open until it is merged into the next version, perhaps 3.6.1?

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