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

After 4.0.0 release, extended CAN IDs fail to be transmitted #30

Closed
JWhitleyWork opened this issue Apr 18, 2019 · 1 comment · Fixed by #31
Closed

After 4.0.0 release, extended CAN IDs fail to be transmitted #30

JWhitleyWork opened this issue Apr 18, 2019 · 1 comment · Fixed by #31
Assignees
Labels

Comments

@JWhitleyWork
Copy link

The support team found that, post the 4.0.0 release (including the current 4.0.2 release), extended CAN IDs fail to transmit. This will be addressed ASAP and a new release generated after testing.

@JWhitleyWork JWhitleyWork self-assigned this Apr 18, 2019
@zoakesAStuff
Copy link
Contributor

A little more detail:

Bug present at d9ddef2 ("4.0.2") but not present at be2623a ( 3.0.0 (untagged)). After reverting to be2623a issue was no longer present

To reproduce:
Using a single-channel kvaser leaf light v2 unit set at 250kbaud:

Operation: rostopic pub to /can_rx with an ID greater than 0xffff and is_extended set to true.
Expect: kvaser unit sends message
Observe: no message sent, CAN light on kvaser unit unlit

Operation: rostopic pub to /can_rx with an ID smaller than 0xffff and is_extended set to false.
Expect kvaser unit sends message
Observe: kvaser unit sends message

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

Successfully merging a pull request may close this issue.

2 participants