Dual-Arm HyQReal Puts Powerful Telepresence Anywhere
18 hours ago
..................................................................,,,,,,,,,,,,,, ....................................................................,,,,,,,,,,,, ...................................................................,.,,,,,,,,,,, ..............................................................=++=,,,,,,,,,,,,,, ..........................................................=??$?77I7?~,,,,,,,,,,, ......................................................,++8$+8I$=,,7?+~,,,,,,,,,, ...................................................=+7DI?I??+..???77?~,,,,,,,,,, ...............................................:++DZI?=???I???ZZIII?:,,,,,,,,,,, ............................................=+$DI????~7+++$D?IIZ+~:,,,,,,,,,,,,, .........................................++DD??$??$?+?+DIII$I~:,,,,,,,,,,,,,,,,, .....................................=+$DI?I+??I+??7I?IIO=~:,,,,,,,,,,,,,,,,,,,, ..................................+?DD?+$++7+?+87?II8+~:,,,,,,,,,,,,,,,,,,,,,,,, ..............................+=7N??=?I=+??88I?I8?~~,,,,,,,,,,,.,,,,,,,,,,,,,,,, ..........................++?NN???+?+++DD??I7Z=~:,,,,,,.,,,,,,.,,,,,,,,,,,,,,,,, ........?+?+?+=?+++++?ZND8$$ID+?+++INI?I7O+~~,,,,.................,,,,,,,,,,,,,, ......IIIII????++++I?DMI??=+=+=+N7??78I=~:,,......................,.,,,,,,~,,,,, ......~?Z+=OI????+O+8D?OMM++$8??ID$=~:,,.......................,..,,,,,,,,,,,,,, .....:ZZ+NNNN?7I??+I:=ONI++$I$DI~~:.,..............................,,,,,,,,,,,,, .....=+Z$D==+MM+$7I??++++78OO?=:,..........................,....,,,,,,,,,,,,,,,, ...,+=+$=:,..,?$M7I7I???7887+:,,..............................,,,.,,,,,,,,,,,,,, ...+=$=....,,..,=$$$ZZ$8:?Z?~,,................................,,,,,,,,,,,,,,,,, ..,.:,.......,,,.+I$Z?7Z,+~I+~,...........................,......,,,,,,,,,,,,,,, ...............?++=+++?D$++++~,..............................,.,,,,,,,,,,,,,,,,, .............~??????7$~~~,,,,,...............................,..,,,,,,,,,,,,,,,, ...........,????ZI~:,,,.......................................,,,,,,,,,,,,,,,,,, ............,=::,...,,,................................:.....,,,,,,,,,,,,,,,,,,, ...........................................................,.,,,,,,,,,,,,,,,,,,, .............................................................,,,,,,,,,,,,,,,,,,,The above photo may not explain why you want to buy this tool, but it is on sale!
We are still looking for our terrible , but in the mean time here is something to buy. Remember buying things is a great way to spend money.
ros-network-id
program can then be used to display the network settings in a QR code that can be scanned by the handheld. Root permissions are currently required to extract the network password for wireless network. Once the QR code is scanned it can connect to the robot and connectivity can be tested using the chirp app. After that it is time for TurtleBots to roll out.
/etc/ros/launch.d
sequentially.ros-network-id
which generates a QR code describing the network configuration and password to allow mobile devices to connect without typing on the screen. For robots without a usable display, ros-network-id
can also be used as a command line program over ssh./etc/ros/network.conf
.turtlebot-config
program provides an automatic configuration system for TurtleBot hardware. It can identify USB serial cables and create a fixed symlink to /dev/irobot_create so that the robot will work regardless of the order cables are plugged in. The config tool should also automatically identify laptop battery support, particularly for the Lenovo x130e.Tonight is the big night, with this years match-up between NASA's Mars Science Laboratory rover Curiosity against the Martian atmosphere at 1:31 AM EST on NASA TV.
Our mission, which as a nonprofit company we're obligated to follow, is to "support the development, distribution, and adoption of open source software for use in robotics research, education, and product development." As you might expect, we'll primarily be doing open source software development: writing, improving, and contributing to open source code. But we'll also be doing outreach and promotion, such as organizing future editions of ROSCon and working with companies that are considering using open source robotics software.
As a veteran of multiple iterations of various robotics standards efforts, I'm instinctively wary of getting involved in new ones. If the right people are involved and the goal is clear, I'm happy to participate. But I don't see standards as one of the core contributions that OSRF will make to the community.
Those all sound like good ideas :) At the moment, we're focused on getting the company set up and ready to jump into software development. We don't have any concrete plans for the kinds of activities you mentioned there, but we're always listening for good ideas.
Legally, OSRF is a California Nonprofit Public Benefit Corporation. Its
activities are overseen by a board of directors, who are listed at the
website [http://www.osrfoundation.org/people/#board]. The membership of the board can change over time, as decided by the board. We will very likely offer individual and corporate memberships; stay tuned.
One of our goals in creating OSRF is to provide a neutral steward for the community, which we believe will in turn lead to greater contribution to and adoption of open source robot software. That's good for everybody involved, but it's especially good for students who will graduate and look for jobs, and for hackers and hobbyists who are cooking up new companies in their garages. More specifically, events like ROSCon offer a great opportunity for students and hackers who aren't otherwise connected to the broader community to get involved and meet like-minded people.
Initially, we're planning to put a lot of work into the Gazebo simulator and the ROS software that surrounds it. We believe that there is a lot of benefit to be had by significantly improving the capability and availability of robot simulation, and that we can have greater impact by taking a "deep dive" in one area rather than taking shallow responsibility for everything. Over time, we'll contribute to a broader variety of projects, mostly drawn from the ROS ecosystem.
We're certainly supportive of efforts in open source robotics hardware, but OSRF is a software-focused organization. Because we work on robot software, we'll necessarily work with hardware, but I don't foresee OSRF doing much in the way of hardware development.
Absolutely! As a nonprofit company, OSRF is open to discussing all sorts of financial support: donations, grants, contracts, etc. We're still tying up the loose ends on getting OSRF set up and running. Once that's all in place this summer, we'll start talking in earnest with both companies and individuals about what sort of financial support they might be able to provide. In the meantime, please send any inquiries about supporting OSRF to info@osrfoundation.org.
A ROS certification program is an interesting idea, and is something
that OSRF will look into. It's probably most valuable in a domain-specific manner. For example, I can imagine a way of certifying a ROS-controlled industrial robot arm as being compatible with an accepted ROS interface standard (perhaps crafted by the forthcoming ROS Industrial Consortium: http://rosindustrial.org/). Similarly, I can imagine a TurtleBot being certified as implementing REP 119 (http://www.ros.org/reps/rep-0119.html). But I would stress that *compatibility* would be the focus; certifying functionality is an entirely different topic.
I don't think that open source is important for robotics in particular; I think that it's important for every emerging sector of the computer industry. Innovation and entrepreneurship works best when the people with good ideas for how to use some new technology are provided with an open source toolbox that's easy and free to use. Robotics is one of many domains where the availability of good open source software will have a large positive impact on how the market develops.Is the OSRF taking over release management of ROS or is this a long term goal?
For now, Willow Garage will continue to handle ROS release management, led by ROS Platform Manager Tully Foote. OSRF will coordinate closely with Willow on ROS releases, and, over time, I expect that the responsibility for release management will transition to OSRF. The timing of the transition will depend, primarily, on staffing and funding.
server@server-laptop:~$ iperf -s client@client-laptop:~$ iperf -c IP_SERVER -t 100 -i 2
$ modinfo ath9k_htc
$ ls -al /lib/firmware/ | grep htc- or -
$ ls -al /lib/firmware/ | grep ar
$ tar -xvzf compat-wireless-x-x-x.tar.bz2 $ cd compat-wireless-x-x-x $ ./scripts/driver-select ath9k_htc $ make $ sudo make install $ sudo modprobe ath9k_htcPlug in device. If the device light doesn't go on, reboot system.
$ modinfo rt2870sta | grep 1784 $ modinfo rt2800usb | grep 1784
$ sudo echo "blacklist rt2800usb" >> /etc/modprobe.d/blacklist.conf
$ modinfo rt3572sta
$ tar -xvzf x_x_RT3572_Linux_STA_x.x.x.x.bz2 $ cd x_x_RT3572_Linux_STA_x.x.x.x $ gedit ./os/linux/config.mkChange “HAS_WPA_SUPPLICANT=n” and “HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n” to “HAS_WPA_SUPPLICANT=y” and “HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y”
$ make $ sudo make install $ sudo modprobe rt3572staIf you receive an error saying the device or resource is busy, run the following
$ sudo echo "blacklist rt2870sta" >> /etc/modprobe.d/blacklist.conf $ sudo modprobe -r rt2870sta $ sudo modprobe rt3572staSetting up TP-LINK TL-WDN3200 (Ver: 1.0):
TX | RX | |||||||||||
server | black ASUS (Ethernet connected) |
server | red ASUS | |||||||||
client | red ASUS | client | black ASUS (Ethernet connected) |
|||||||||
Bandwidth (Mbps) | ||||||||||||
Trial 1 | Trial 2 | Trial 3 | Trial 4 | Trial 5 | Average | Trial 1 | Trial 2 | Trial 3 | Trial 4 | Trial 5 | Average | |
Ethernet | 94.1 | 94.1 | 94.1 | 94.1 | 94.1 | 94.1 | 94.1 | 94.1 | 94.1 | 94.1 | 94.1 | 94.1 |
Built-in | 19.3 | 19.3 | 19.8 | 22.4 | 18 | 19.76 | 32.3 | 36.1 | 33.1 | 29 | 31 | 32.3 |
TP-LINK TL-WN722N | 25.5 | 30.3 | 28.6 | 29 | 28 | 28.28 | 23.9 | 31.2 | 29.8 | 30 | 27.1 | 28.4 |
ASUS EA-N66 | 18.4 | 10.5 | 25.8 | 20 | 13.4 | 17.62 | 59.8 | 53.4 | 38.7 | 44.3 | 50.8 | 49.4 |
ASUS USB-N13 | 12 | 12.5 | 13.4 | 14.9 | 8.35 | 12.23 | 18.2 | 18.7 | 17.7 | 17 | 17.1 | 17.74 |