To add some extra information to Ryan's post above.
- Is there currently support for the new Turtlebot in Fuerte?
We are currently hacking on the code in fuerte - you can track the development branches on github. I am planning to upgrade the development for groovy relatively quickly - mostly due to catkin and the fact we need to do quite alot of our new development for turtlebot around catkin as well and these won't be compatible with fuerte.
So groovy would seem to be a better long term fit for turtlebot2 and I'll certainly make sure groovy installs are manually possible whilst we transition.
- To what degree will code for the new Turtlebot be backward compatible with the old Turtlebot. Will the existing Turtlebot node still work with the new base? Or will there be a new stack?
The new code on github is currently using environment variables to define various hardware parts which would be different (currently TURTLEBOT_BASE, TURTLEBOT_STACKS, TURTLEBOT_3D_SENSOR). These get used to launch the appropriate drivers and nodes. This may change, but the launching concept should remain somewhat similar.
My perspective is that the new software being developed on github is essentially what defines 'Turtlebot2'. That software is reconfigurable to run with whatever turtlebot-compatible hardware you have.
- It looks like the new Turtlebot is designed to provide power to a laptop. What laptop(s) will be supported? I've been looking at the Acer Aspire One AO756-4854.
We (Yujin Robot) are in the same situation. Currently we are looking at shipping the ASUS1225B until further notice (not yet fixed).
- Is the low-level interface to the Kobuki base compatible with the interface to the Create? Is there a published specification for the Kobuki interface?
We're still developing the kobuki driver. It is important to note that there is an REP for the turtlebot - REP 119. This is not yet completely polished, though it attacks the major points. The kobuki and create drivers both do the basics - they provide consistent /odom and /cmd_vel topics and the official turtlebot applications are ok. Some of the sensors (e.g. bump sensors) could be made compatible if there is demand for it. If you'd like to get your voice heard, probably the best place to do so is the turtlebot sig.
This week we are also finalising some contact points for Kobuki - mailing list, email, blog, twitter and rebuilding the official web site. I will advertise information for these once done (expect early next week). These should help fill in some holes for people.