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

ROS2: Publish an array with rqt #244

Open
George-Gi opened this issue Feb 9, 2021 · 2 comments
Open

ROS2: Publish an array with rqt #244

George-Gi opened this issue Feb 9, 2021 · 2 comments

Comments

@George-Gi
Copy link

Hi everyone, I have been using rqt to publish messages to test my applications, however I still haven't found a way to publish a message that includes an array.
In my custom message I have a variable size array declared as uint8[]. I notice in rqt that the expected type is "sequence".
I have tried different expressions, but couldn't figure out the correct one. Could someone provide an example please?

@RyanDelGizzi
Copy link

RyanDelGizzi commented Mar 13, 2021

Hi @giwrgosG,

I created the original question on ROS Answers and set out to resolve the issue. Same issue here for rqt_publisher.

One problem is how get_slot_types handles array message types. Since Crystal, the string for array type has changed, using a <> syntax instead of a [] syntax. And such, the parsing of that info needs to change.

I have a fix for this repo, and also one for rqt_publisher which allows us to publish arrays. However, @mlautman has a (massive) PR #224 that addresses this issue along with a myriad of other crystal->foxy differences. I don't think it makes sense for me to submit a PR on this repo to address a small change that is already addressed in another PR. There are still changes that need to be made to rqt_publisher to support the changes in this repo, but they are rather small.

@mlautman I would love to help move this along as well getting rqt_publisher working as well. If there is a way I can assist, please let me know!

@ijnek
Copy link

ijnek commented May 15, 2021

Hi @RyanDelGizzi
👍 to your suggested fix, this would be quite desirable. Considering #224 hasn't had any updates in a while, it would be great if you could consider putting a PR up with your changes!
Thanks!

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

3 participants