Adding *my* drivers to github about rock-package_set HOT 5 CLOSED

Hey. You'll have to be more explicit about the packages you want to move since so far the Owners are the ones that can create the repositories

from rock-package_set.

In bullet 2) I will move the drivers I am the owner in gitorious. IMU drivers: stim300 and imar.
When finished I will pull request to include them in the rock-package_set together with the new trimble_bd970 driver.

from rock-package_set.

About the trimble driver: will it really be only for the BD970 ? Won't it be more generic than that ? (i.e. won't it apply to all trimble GPS units in the long run ?). Just to avoid costly renaming / really bad naming ...

from rock-package_set.

Yes. This is because we (here at ESA) are thinking to name it. gnss_trimble for all trimble gnss receivers. http://www.trimble.com/gnss-inertial/gnss-receivers.aspx (BD9xx and BX9XX).

A colleague at ESA and I started to communicate with the receiver using the standard NMEA protocol. The library is finished. Nowadays receivers have Web control GUI, and the RTK corrections is much easier to configure and monitor than at the times of the mb500.

The question raises about how much of your stuffs from the mb500 can be reused? mb500 receiver is not longer available in the marker. Trimble bought/distributes Magellan and the closest receiver to the old mb500 is the mb800. However, the mb500 rock driver is good and very generic. We are thinking to reuse stuff but not in the library (PASH protocol) more in the component level (i.e.: UTM coordinates, gdal, etc...)

Regarding the oroGen component, since in principle rock convention is one task per component. and the existing orogen-gps used for the mb500 driver does not follow the convention. The best solution IMO is:
gnss_trimble and orogen-gnss_trimble and let's see how this evolves in the future.

At the moment the gnss_trimble is only for the rover (no base station) and the RTK corrections come from a Virtual Reference Station (VRS) provided from a Dutch supplier via NTrip.

from rock-package_set.

+1 with all your comments ;-)

On Thu, Aug 21, 2014 at 5:16 AM, Javier Hidalgo [email protected]
wrote:

Yes. This is because we (here at ESA) are thinking to name it.
gnss_trimble for all trimble gnss receivers.
http://www.trimble.com/gnss-inertial/gnss-receivers.aspx (BD9xx and
BX9XX).

A colleague at ESA and I started to communicate with the receiver using
the standard NMEA protocol. The library is finished. Nowadays receivers
have Web control GUI, and the RTK corrections is much easier to configure
and monitor than at the times of the mb500.

The question raises about how much of your stuffs from the mb500 can be
reused? mb500 receiver is not longer available in the marker. Trimble
bought/distributes Magellan and the closest receiver to the old mb500 is
the mb800. However, the mb500 rock driver is good and very generic. We are
thinking to reuse stuff but not in the library (PASH protocol) more in the
component level (i.e.: UTM coordinates, gdal, etc...)

Regarding the oroGen component, since in principle rock convention is one
task per component. and the existing orogen-gps used for the mb500 driver
does not follow the convention. The best solution IMO is:
gnss_trimble and orogen-gnss_trimble and let's see how this evolves in the
future.

At the moment the gnss_trimble is only for the rover (no base station) and
the RTK corrections come from a Virtual Reference Station (VRS) provided
from a Dutch supplier via NTrip.

—
Reply to this email directly or view it on GitHub
#14 (comment)
.

from rock-package_set.