Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Motoman Ros I/O read/write error #571

Closed
Avgrobo opened this issue Nov 8, 2023 · 1 comment
Closed

Motoman Ros I/O read/write error #571

Avgrobo opened this issue Nov 8, 2023 · 1 comment

Comments

@Avgrobo
Copy link

Avgrobo commented Nov 8, 2023

We're trying to control Festo make gripper integrated with Yaskawa GP12 robot via ROS using rosservice. On calling the service execution error states that Its illegal to write or read the address.
control error

Kindly support on resolving the error to control.
Thanks

@gavanderhoorn
Copy link
Member

gavanderhoorn commented Nov 8, 2023

First: please don't post screenshots of terminal output. It's all text, so please copy-paste it into a fenced code block instead.

Having written that: every robot controller supported by MotoROS1 only allows a few ranges of addresses to be written to. See the service documentation for information:

# Write 'value' to the IO element at 'address'.
#
# This service does not return anything.
#
# Addresses are plain, base-10 integers, as used and displayed by the controller
# (on the teach pendant for instance).
#
# Only the following addresses can be written to:
#
# - 27010 and up : Network Inputs (25010 and up on DX100 and FS100)
# - 10010 and up : Universal/General Outputs
#
# Refer also the Yaskawa Motoman documentation on IO addressing and
# configuration.

PS: and you most likely already know, but ROS Melodic has been EOL since June this year, so will not see any updates nor enhancements any more.

@ros-industrial ros-industrial locked and limited conversation to collaborators Nov 8, 2023
@gavanderhoorn gavanderhoorn converted this issue into discussion #572 Nov 8, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Development

No branches or pull requests

2 participants