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

add message definitions for State and ActionState #31

Open
wants to merge 11 commits into
base: master
Choose a base branch
from

Conversation

frothm
Copy link

@frothm frothm commented Dec 8, 2022

Some message definitions from VDA 5050 were missing, so we added them. The new definitions are based on version 1.1 of the guideline.

  • State.msg: Messages that are sent to the main controller via the "state" topic
  • ActionState.msg: Multiple ActionStates are part of a State message, in the form of an array.

@@ -2,15 +2,16 @@
int32 headerId # header ID of the message. The headerId is defined per topic and incremented by 1 with each sent
# (but not necessarily received) message.

string timestamp # Timestamp after ISO8601 in the format YYYY-MM-DDTHH:mm:ss.ssZ (e.g.“2017-04-15T11:40:03.12Z”)
string timeStamp # Timestamp after ISO8601 in the format YYYY-MM-DDTHH:mm:ss.ssZ (e.g.“2017-04-15T11:40:03.12Z”)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the document timestamp still seems to be lower case: https://github.com/VDA5050/VDA5050/blob/1.1.0/VDA5050_EN.md#actionStates Same applies to the other timestampes

@@ -2,9 +2,5 @@ float64 x # X coordinate described in the world coordinate system.

float64 y # Y coordinate described in the world coordinate system.

float64 orientation # [rad] Range [-pi...pi] Orientation of the AGV on this position of the curve.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

orientation is still present in 1.1

@ipa-pfs
Copy link
Contributor

ipa-pfs commented Aug 1, 2023

Are you referring to 2.0? Because we would pin the current version to 1.1 and would make changes for version 2.0

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

Successfully merging this pull request may close these issues.

3 participants