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

motoman/377d7be: is this LIVENESS? #414

Closed
gavanderhoorn opened this issue May 19, 2021 · 6 comments
Closed

motoman/377d7be: is this LIVENESS? #414

gavanderhoorn opened this issue May 19, 2021 · 6 comments
Assignees
Labels
bug-descriptions help wanted Extra attention is needed

Comments

@gavanderhoorn
Copy link
Member

motoman/377d7be currently has a SOFTWARE:LIVENESS failure label.

Description:

description: >
The Motoman controller has to be prepared for use with ROS.
For this, you have to first install MotoROS on the controller
and afterwards a special INFORM program (INFORM is the OEM
specific programming language). The motoman driver
depends on a required handshake between the native INFORM robot
code and the MotoROS component (also running on the Motoman controller).
The MotoROS code will automatically run an INFORM job called INIT_ROS
at the start of a motion session, which will provide the required
handshaking. When installing the INFORM job on a DX200, it shows an
error: "L:****) ERROR 3200 : NOP or END instruction not found (J:INIT_ROS".
This is due to Linux line-endings in the files downloaded from Github:
the controller expects Windows line-endings. This breaks the INFORM
parser in the Motoman controller.

I would agree with that failure-code if the system ever reached a state in which it could be started, but the problem reported in the issue occurs during installation. It's impossible to load a specific part of the driver software onto the Yaskawa controller, which makes it impossible to ever start the driver.

Should this be some variant of BDO instead?

@gavanderhoorn
Copy link
Member Author

Related: #416.

@hsd-dev
Copy link
Contributor

hsd-dev commented Jun 30, 2021

If the system never was initialized properly, it would be SOFTWARE:NONE and SYSTEM:NONE I suppose.

@ChrisTimperley
Copy link
Member

SOFTWARE:BDO and SYSTEM:NONE seem appropriate to me

@hsd-dev
Copy link
Contributor

hsd-dev commented Jun 30, 2021

Currently there is only SOFTWARE:BUILD. Do we need to extend that to SOFTWARE:BDO? Though the description for BUILD is

Failures that prevent the successful completion of the build or **installation** process, such as compilation and linking errors.

@gavanderhoorn
Copy link
Member Author

gavanderhoorn commented Jun 30, 2021

It's similar to some other bugs: the system never "got control", so there doesn't appear to be any opportunity to lose it.

It's a BDO indeed (deployment in this case).

Based on the description, SOFTWARE:BUILD seems appropriate then.

@gavanderhoorn
Copy link
Member Author

Corrected in 153b315.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-descriptions help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants