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

Try hc-driver-4.9 on TEO #26

Closed
jgvictores opened this issue Nov 15, 2017 · 28 comments
Closed

Try hc-driver-4.9 on TEO #26

jgvictores opened this issue Nov 15, 2017 · 28 comments
Assignees
Labels
blocking Focus on this issue before working on issues that are blocked by it epic priority: high

Comments

@jgvictores
Copy link
Member

Try hc-driver-4.9 on TEO.

If https://github.com/munozyanez/hc-driver-4.9 works, this may affect the Distro we use, propagating to roboticslab-uc3m/yarp-devices#111 and even roboticslab-uc3m/questions-and-answers#17.

This issue originates from roboticslab-uc3m/yarp-devices#118 but is specific to TEO.

@jgvictores
Copy link
Member Author

Adding priority: high given the number of issues that are blocked by this issue and related roboticslab-uc3m/yarp-devices#118.

@rsantos88 rsantos88 added the blocked Do not focus on this issue until blocking issue is closed label Nov 30, 2017
@rsantos88
Copy link
Contributor

this issue is blocked by @jmgarciah and @smcdiaz
They are doing tests about push-recovery

@jgvictores
Copy link
Member Author

@rsantos88 Thanks for keeping us updated on this topic. It is extremely important, as this issue is keeping many other issues blocked too.

@jgvictores jgvictores added the blocking Focus on this issue before working on issues that are blocked by it label Dec 2, 2017
@jgvictores
Copy link
Member Author

jgvictores commented Dec 7, 2017

this issue is blocked by @jmgarciah and @smcdiaz They are doing tests about push-recovery

Does this refer to https://github.com/roboticslab-uc3m/TEO_push repository, or a different one (to put an announcement issue pointing somewhere)?

@AlvaroMartinezR
Copy link

@rsantos88 told me that he is preparing to install in a partition of TEO Ubuntu 16.04. I think is a good option but I want to point out that the ArmarX framework is recommended to be used in 14.04. However thinking about installing ArmarX in TEO is a long shot: first, the idea is to create a simulation of walking in a non-connected PC. And, if achieved, translate to TEO.
To conclude, my point is that my consideration should be less pondered over others for 2 facts:

  • This is a very long goal.

  • I suppose that something that works on 14.04 should work on 16.04.

@jgvictores
Copy link
Member Author

Most of our Travis CI are with Trusty (14.04.xx), so I guess it would be reasonable to go for Trusty rather than Xenial (16.04.xx).
Since this is a kind of organization-wide issue, I'd even consider another place where we're stuck with Trusty: TIAGo (all for ROS Indigo->Trusty).
So, Trusty kind of seems like the way to go, leaving Xenial as an option of a personal preference. Hopefully ArmarX, TIAGo, and Travis will all end up moving to Xenial more or less at the same pace.

@PeterBowman What is your opinion?

@PeterBowman
Copy link
Member

PeterBowman commented Dec 19, 2017

Since this is a kind of organization-wide issue (...)

Is it? We have a robot-wide discussion at roboticslab-uc3m/questions-and-answers#20, but this one is perhaps more closely related to TEO (and, by extension, to ASIBOT with regard to HicoCAN driver support). Let's break down a few points:

  • According to this blog entry, Xenial support in Travis CI is just around the corner.
  • ArmarX: I can't tell much about it. The package repository only lists Ubuntu 14.04, but have you tried installing from sources in Xenial?
  • I can't see the connection between TIAGo and this issue - how is it related to the OS aboard TEO?

One of the main concerns for moving away from Debian 6.0 to a modern SO was the C++11 support requirement dictated by YARP. This is fulfilled by Trusty, so I guess we can give it a try and defer the final upgrade to a later stage. However, please keep in mind that we are already behind YARP's expectations for supported distros: http://wiki.icub.org/wiki/YARP_Supported_Distributions#Supported_releases. There is some sort of buffer zone in our org thanks to roboticslab-uc3m/questions-and-answers#17, but we could run into trouble sooner or later.

@rsantos88
Copy link
Contributor

Ok, so I suppose we are all in agreement with using Ubuntu 14.04 LTS for all of TEO PCs

@jgvictores
Copy link
Member Author

I think it fulfills our short-term objective of trying the driver, and also enables simple tests with ArmarX, which is good.

Both @David-Estevez an I have introduced features in YARP that are on devel which will require Ubuntu 16.04. Just to think about the future, do we physically have space for (worst case scenario) 3 distros?

@AlvaroMartinezR
Copy link

AlvaroMartinezR commented Dec 20, 2017

ArmarX: I can't tell much about it. The package repository only lists Ubuntu 14.04, but have you tried installing from sources in Xenial?

No, I haven't. The computer I work with has no enough space to think about adding another partition just to test.

But as I said, for TEO my opinion should not be regarded as compulsory for my work, I was talking in a very long term.

Edited: just a miss click closing the issue

@rsantos88
Copy link
Contributor

Yes, we have enough space. More in detail, for the debian 6.0 backup, the partition is 20gb and we have approximately 100gb for the rest of distros. So, do you want to have installed in each PC.. ubuntu 14.04 LTS, ubuntu 16.04 LTS and the Debian backup?

@rsantos88
Copy link
Contributor

ok, as I told to @jgvictores , I'll install ubuntu 14.04 LTS and I'll leave a free partition with 50gb for a future distro (ubuntu 16.04)

@jgvictores
Copy link
Member Author

@rsantos88 Perfect, thanks!!

@rsantos88
Copy link
Contributor

Ok, now we have teo-manipulation and teo-locomotion PCs with this grub menu:

image
By default, it will start with the old distribution (backup 23/10/2017 with Debian 6.0).
If you select Ubuntu, you will start a clean distribution of Ubuntu 14.04 LTS located in a clean partition of 54gb.
I haven't done this for now with teo-head PC because it has 'ubuntu 15.04`

@jgvictores
Copy link
Member Author

Thank you so much! Looks very good!!

@jgvictores
Copy link
Member Author

this issue is blocked by @jmgarciah and @smcdiaz They are doing tests about push-recovery

Spoke with @jmgarciah and @smcdiaz, no longer blocked!

@jgvictores jgvictores removed the blocked Do not focus on this issue until blocking issue is closed label Jan 17, 2018
@rsantos88
Copy link
Contributor

Perfect. If you need to install something additional (libraries, repositories, etc) in that distribution, tell me.

@jgvictores
Copy link
Member Author

All we need to try is launchManipulation/launchLocomotion basic joint control.

@rsantos88
Copy link
Contributor

consider this roboticslab-uc3m/installation-guides#34

@jgvictores
Copy link
Member Author

Installing the new hico driver should be very similar to that of the old driver, probably just changing some paths: https://github.com/roboticslab-uc3m/installation-guides/blob/master/install-hcanpci.md#install-hcanpci-kernel-module-debian-60

@rsantos88
Copy link
Contributor

All we need to try is launchManipulation/launchLocomotion basic joint control.

Now launchManipulation is running perfectly with Ubuntu 14.04 !! 👍
I will update locomotion computer and document it with the new drivers :)

@jgvictores
Copy link
Member Author

Amazing!! 😎😎😎

Thanks a lot!!!

@rsantos88
Copy link
Contributor

Do you consider the possibility of storing the drivers in another repository?

@rsantos88
Copy link
Contributor

launchLocomotion now is ready too for Ubuntu 14.04
The documentation has been updated with the new drivers for Ubuntu distro here

@jgvictores
Copy link
Member Author

This is very good news!! 🎉🎉🎉

@rsantos88
Copy link
Contributor

maybe we should update this table with CanBusControlboard and CanBusHico working

@jgvictores
Copy link
Member Author

Regarding the table, note that we have roboticslab-uc3m/yarp-devices#161 open.

@rsantos88
Copy link
Contributor

Closing issue! The rest of tasks for Distro update will be tracked on #32

jgvictores added a commit to roboticslab-uc3m/yarp-devices that referenced this issue Feb 8, 2018
rsantos88 pushed a commit to roboticslab-uc3m/yarp-devices that referenced this issue Jan 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocking Focus on this issue before working on issues that are blocked by it epic priority: high
Projects
None yet
Development

No branches or pull requests

4 participants