iCubStartup failed

[jimingda]

Hi,

After i launched icubsrv and icub-head on yarpmanager, i failed to run the iCubStartup, as showed below. Any advice on the possible problem?

Thank you in advance.

[Nicogene]

Hi @jimingda!

can you post the log you have in yarplogger of the modules are failing to run?

[Nicogene]

Hi @jimingda have you changed the icub_all.xml?
Could you please check the status of the robots-configuration in icub-head via:

cd /usr/local/src/robot/robotology-superbuild/src/robots-configuration
git status

[jimingda]

Thank you @Nicogene

I didn't change the icub_all.xml, and i check the time-tag Apr 21 2022 of files as showed above, may these tags can confirm it.
The git status result i got as below:

icub@icub-head:~$ cd /usr/local/src/robot/robotology-superbuild/src/robots-configuration
icub@icub-head:/usr/local/src/robot/robotology-superbuild/src/robots-configuration$ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   all_robots.xml

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	iCubShanghai01/

no changes added to commit (use "git add" and/or "git commit -a")
icub@icub-head:/usr/local/src/robot/robotology-superbuild/src/robots-configuration$ git diff
diff --git a/all_robots.xml b/all_robots.xml
index 11b1be45e..cbca56c6e 100644
--- a/all_robots.xml
+++ b/all_robots.xml
@@ -69,4 +69,5 @@
        <xi:include href="./iCubPrague01/icub_all.xml" />
        <xi:include href="./iCubValparaiso01/icub_all.xml" />
        <xi:include href="./ergoCubSN000/ergocub_all.xml" />
+       <xi:include href="./iCubShanghai01/icub_all.xml" />
 </robot_database > 
icub@icub-head:/usr/local/src/robot/robotology-superbuild/src/robots-configuration$ ll all_robots.xml 
-rw-rw-r-- 1 icub icub 3734 Jun 21  2022 all_robots.xml

[Nicogene]

It is quite strange that you have in the untracked files iCubShanghai01.

Can you post the output of

cd /usr/local/src/robot/robotology-superbuild/
git status

[jimingda]

Thanks @Nicogene
Here is the output:

icub@icub-head:~$ cd /usr/local/src/robot/robotology-superbuild/
icub@icub-head:/usr/local/src/robot/robotology-superbuild$ git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

[Nicogene]

Very strange, usually the robots should stay on a superbuild tag, not on master.

Could you check the git status of the superbuild in icubsrv and git log on both icub-head and icubsrv ?
I would like to understand how old is the code you are using on the robot

[jimingda]

Thanks @Nicogene

icub-head:

icub@icub-head:/usr/local/src/robot/robotology-superbuild$ git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
icub@icub-head:/usr/local/src/robot/robotology-superbuild$ git log
commit b21c54e9353be363f3e5d4b4a72f19169730d595 (HEAD -> master, origin/master, origin/HEAD)
Author: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
Date:   Tue Jun 14 05:42:17 2022 +0000

    Bump CONDA_BUILD_NUMBER after successful Conda packages build and upload

commit 90746d4f1c99328686895ccf0b89d173b823d83b
Merge: 0d435ef 7167238
Author: Silvio Traversaro <silvio.traversaro@iit.it>
Date:   Tue Jun 14 00:40:47 2022 +0200

    Merge pull request #1169 from robotology/switchyarptocondaforge
    
    Switch to use YARP conda-forge binary package when generating conda packages

commit 0d435ef7caa1d628b8adffd59fce972ac93ef82e
Merge: 45c0fe9 cbb61d0
Author: Silvio Traversaro <silvio.traversaro@iit.it>
Date:   Mon Jun 13 21:14:03 2022 +0200

    Merge pull request #1167 from robotology/automatic-update-latest-releases-versions
    
    Automatic update of latest releases versions

commit 7167238e240b3be98558c0c1924bf9b90bbc864a
Author: Silvio Traversaro <silvio@traversaro.it>
Date:   Mon Jun 13 17:12:56 2022 +0200

    Switch to use YARP conda-forge binary package when generating conda packages

icubsrv:

icub@icubsrv:/usr/local/src/robot/robotology-superbuild$ git status
On branch releases/2022.05
Your branch is up to date with 'origin/releases/2022.05'.

nothing to commit, working tree clean
icub@icubsrv:/usr/local/src/robot/robotology-superbuild$ git log
commit 648226554bd9770c77c102fd211ca5b45bcf891b (HEAD -> releases/2022.05, origin/releases/2022.05)
Author: Silvio Traversaro <silvio@traversaro.it>
Date:   Mon Jun 13 17:12:56 2022 +0200

    Switch to use YARP conda-forge binary package when generating conda packages

commit 38d7fcc92e7f79927b5066807ee06d3b71bd2791
Merge: 6f513a4 6754cc2
Author: Silvio Traversaro <silvio.traversaro@iit.it>
Date:   Fri Jun 10 16:29:07 2022 +0200

    Merge pull request #1165 from robotology/traversaro-patch-9
    
    Add libqt5multimedia5-plugins to apt-python.txt (2022.05 backport)

commit 6754cc2e15e614ad23824410c7e4ec2a91f1b83f
Author: Silvio Traversaro <silvio.traversaro@iit.it>
Date:   Fri Jun 10 11:53:19 2022 +0200

    Add libqt5multimedia5-plugins to apt-python.txt

[jimingda]

Thanks @Nicogene

I can launch the yarprobotinterface in the begining it turned green on Yarpmanager, but it failed after a while and errors as i showed above, and it turned red on Yarpmanager'. When i clicked the DiscoveronFirmwareUpdater`, nothing appeard on the ui.

[Nicogene]

The firmware updater has to be launched from the icub-head via ssh -X.
Are you doing so?

In any case you can find here a guide on the FirmwareUpdater usage:

• https://icub-tech-iit.github.io/documentation/icub_firmware/firmwareupdater/firmwareupdater

[jimingda]

Thanks @Nicogene

After icub@icub-head:~$ FirmwareUpdater -a, then Discover the ETH, i got the following result.

[Nicogene]

Hi @jimingda, from the screenshot you posted it seems that only few boards are available, it seems a problem that requires the help of my colleagues of tech support.

Please open an issue in https://github.com/robotology/icub-tech-support reporting the the log of yarprobotinterface

[jimingda]

Thanks @Nicogene

The current problem is only few devices detected via icub-head, so i should detect all devices first?