![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgsRPCtUnW4eMAhwQCz0nMjwN3injU_yddDN83rSzMniucArdJ8wziNbkX48S0QSxy5VDLE7mKTvhWHsJl0AFcpovkyZlD69hdC7cI9TZ5LKSZ6R_Ae_WP6Dg7Vq84Cf5-r0pZGMiQ1rep8/s400/launch_rovers.png)
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhXFZiE4JUFXbuOkFsPsTD9liZU9nlQggf5z3vKw0gdI05MXdKrHzBWi4fw6XslCIqmxpK1d2cnPvmF62ZryNCkZg2MVFsEvuzB04BreSrAydMA7GGZPte_kLY96ijbDm9y3dxH_0afEeNZ/s400/overlap2.png)
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgsCFrRjUJYWnbnERiEzNvTEskEOKzhzpza0Y3wiOeNIJrs8TXmUq6iyYPKGxRAys8iQMyaVKgvnPe1fsYAA8N-7z3253m95D9JU1g7Felu7nkSevMUAxQPcS12nRT5_JoAEq2NP2Mc9rWI/s400/overlapping.png)
I have been playing with the fixed and the target frames as can be appreciated in the screenshots. I, however, get the same result always: overlapping of the map.
I have noticed that during this process the mobile frame isn't able to fully rotate when it is necessary and this is what I think is causing the overlapping.
I have several suppositions for the generator of this problem:
1. Odometry isn't being correctly actualized.
2. Gmapping has an error (which I have no idea about).
3. The time ins ROS isn't properly actualized nor the buffer is properly being cleaned out when necessary.
I hope the question I placed at the mailing list is soon answered.
No hay comentarios:
Publicar un comentario