Revision history [back]

Is it practical to try to use this driver for Indigo?

in my opinion that depends on the effort required to get it to run (ie: update it) versus the amount of time you'd spend creating something new. In almost all cases, starting with something existing will be faster (but this does depend on the quality of what you're starting with).

I'm not sure where to start. Would I need recompiled source, or is it something simpler than that?

Looking at the page you linked, and then following that to the GitHub repository, it would seem that driver has already been updated to work with Hydro (it has also been released as binaries on Hydro: see the wiki page (it has the released badge) and debbuild/hydro.html?q=applanix).

The changes between Hydro and Indigo aren't too great, so I'd expect that package to work on Indigo as well. You'll want to clone the repository to your own catkin_ws/src and then build it.

There could be some outstanding issues, so make sure to check the issue tracker.

PS: what made you think the driver was only compatible with Fuerte?

Is it practical to try to use this driver for Indigo?

in my opinion that depends on the effort required to get it to run (ie: update it) versus the amount of time you'd spend creating something new. In almost all cases, starting with something existing will be faster (but this does depend on the quality of what you're starting with).

I'm not sure where to start. Would I need recompiled source, or is it something simpler than that?

Looking at the page you linked, and then following that to the GitHub repository, repository, it would seem that driver has already been updated to work with Hydro (it has also been released as binaries on Hydro: see the wiki page (it has the released badge) and debbuild/hydro.html?q=applanix).

The changes between Hydro and Indigo aren't too great, so I'd expect that package to work on Indigo as well. You'll want to clone the repository to your own catkin_ws/src and then build it.

There could be some outstanding issues, so make sure to check the issue tracker.

PS: what made you think the driver was only compatible with Fuerte?

Is it practical to try to use this driver for Indigo?

in my opinion that depends on the effort required to get it to run (ie: update it) versus the amount of time you'd spend creating something new. In almost all cases, starting with something existing will be faster (but this does depend on the quality of what you're starting with).

I'm not sure where to start. Would I need recompiled source, or is it something simpler than that?

Looking at the page you linked, and then following that to the GitHub repository, it would seem that driver has already been updated to work with Hydro (it has also been released as binaries on Hydro: see the wiki page (it has the ✓ released badge) and debbuild/hydro.html?q=applanix).

The changes between Hydro and Indigo aren't too great, so I'd expect that package to work on Indigo as well. You'll want to clone the repository to your own catkin_ws/src and then build it.

There could be some outstanding issues, so make sure to check the issue tracker.

PS: what made you think the driver was only compatible with Fuerte?

Is it practical to try to use this driver for Indigo?

in my opinion that depends on the effort required to get it to run (ie: update it) versus the amount of time you'd spend creating something new. In almost all cases, starting with something existing will be faster (but this does depend on the quality of what you're starting with).

I'm not sure where to start. Would I need recompiled source, or is it something simpler than that?

Looking at the page you linked, and then following that to the GitHub repository, it would seem that driver has already been updated to work with Hydro (it has also been released as binaries on Hydro: see the wiki page (it has the ✓ released badge) and debbuild/hydro.html?q=applanix).

The changes between Hydro and Indigo aren't too great, so I'd expect that package to work on Indigo as well. You'll want to clone the repository to your own catkin_ws/src and then build it.

There could be some outstanding issues, so make sure to check the issue tracker.

PS: what made you think the driver was only compatible with Fuerte?

Is it practical to try to use this driver for Indigo?

in my opinion that depends on the effort required to get it to run (ie: update it) versus the amount of time you'd spend creating something new. In almost all cases, starting with something existing will be faster (but this does depend on the quality of what you're starting with).

I'm not sure where to start. Would I need recompiled source, or is it something simpler than that?

Looking at the page you linked, and then following that to the GitHub repository, it would seem that driver has already been updated to work with Hydro (it has also been released as binaries on Hydro: see the wiki page (it has the ✓ released badge) and debbuild/hydro.html?q=applanix).

The changes between Hydro and Indigo aren't too great, so I'd expect that package to work on Indigo as well. You'll want to clone the repository to your own catkin_ws/src and then build it.

There could be some outstanding issues, so make sure to check the issue tracker.

PS: what made you think the driver was only compatible with Fuerte?

I've now cloned a copy of the Hydro version and built it. Now I'm stuck on the step that says: " roslaunch applanix_launch example.launch " The only launch file I got was applanix_bridge.launch, and that seems to be a sort of adapter between applanix messages and ros. Is there something I need to add to the catkin_make command, or something else to import to get the example?

I'm not sure I understand what you're trying to say: the nodes in applanix_driver essentially only provide an interface to the hardware. What did you expect the package to do it isn't doing now?