background preloader

Smarter control in robotics & automation!

Smarter control in robotics & automation!
Related:  Robotic

Orca Robotics ROS.org | Powering the world's robots arduino « Juan Antonio Breña Moral Juan Antonio Breña Moral My personal opinions about this world. Posts Tagged ‘arduino’ Neato XV-11 was hacked Sunday, November 28th, 2010 Neato XV-11 is a Robotic Vacuum System which includes a a low cost LIDAR. Inspired in Kinect contest, Robotbox organized a contest to hack the product to discover how to manage LIDAR included in the product. It is possible to see the results here: Further information: How to test it: How to buy a unit:

OpenRTM-aist official website | OpenRTM-aist Lidar I make a adapter using Arduino mega 1280 to output PWM to control XV-11 LDS motor.LDS motor power directly from USB 5V with a IPS041L low side switch control with PWM.The XV-11 LDS data is connect to Arduino mega RX3 then relay senf out from TX ( USB-serial ).So the user can use Xevel's program to see the lidar plot. [update] Currently it is has simple close loop control. Arduino mega code you can get from here( github). SmartSoft Module de reconnaissance vidéo "CMUcam5" Les caméras vidéos à sortie numérique disponibles sur le marché offrent des possibilités étonnantes. Ainsi associés à un microcontrôleur doté d'un algorithme approprié, ces dernières pourront être utilisées pour détecter pratiquement n'importe quoi dans leur champ de vision. Toutefois leur utilisation pose généralement des problèmes récurrents. En premier lieu, celui de devoir disposer d'un microcontrôleur assez puissant et rapide pour pouvoir gérer le très grand nombre de données que ces dernières founissent (pouvant aller jusqu'à plusieurs dizaines de méga-octets par seconde). Quand bien même vous disposeriez de ce type de microcontrôleur, ce dernier serait alors monopolisé en grande partie pour la gestion de l'algorithme de reconnaissance vidéo, vous laissant alors peu de ressource pour les autres tâches de votre application. De ce fait la plupart des microcontrôleurs pourront être facilement interfacés avec la CMUcam5 Pixy. Caractéristiques: - RAM: 264 K bytes - Type de lentille: M12

Introduction à Makefile Les Makefiles sont des fichiers, généralement appelés makefile ou Makefile, utilisés par le programme make pour exécuter un ensemble d'actions, comme la compilation d'un projet, l'archivage de document, la mise à jour de site, etc. Cet article présentera le fonctionnement de makefile au travers de la compilation d'un petit projet en C. Il existe une multitude d'utilitaires de Makefile fonctionnant sur différents systèmes (gmake, nmake, tmake, etc.). Les Makefiles n'étant malheureusement pas normalisés, certaines syntaxes ou fonctionnalités peuvent ne pas fonctionner sur certains utilitaires. Le présent article se base sur l'utilitaire GNU make. Toutefois les notions abordées devraient être utilisables avec la majorité des utilitaires. Le projet utilisé ici sera un classique "hello world" découpé en trois fichiers: #include <stdio.h>#include <stdlib.h> void Hello(void) { printf("Hello World\n"); } #ifndef H_GL_HELLO#define H_GL_HELLO void Hello(void); #endif cible: dependance commandes 2.1.

InMoov » open-source 3D printed life-size robot Arduino - Control 2 DC Motors Via Bluetooth UPDATE 23-12-2013: changed their whole website… So the source file that previously you could use to edit on their website, only works with AppInventor version 1.0 or also called classic that you can see here Click the button: “Invent your own Apps now” . This project still works just fine with my app and with my Arduino code. But you can only edit the source code on Appinventor classic version. In this tutorial I’ll show you how you can control 2 DC motors via bluetooth with my brand new Android app. It’s called “BlueArd” and It’s the 1.0 version. This app was created with MIT App Inventor. If you remember my previous tutorial (Click here to see that project) where I was controlling 1 DC motor, I was using an app called “BlueTerm“. It’s my very first app and It’s working for me but I’m not sure if this will work for everyone. If you want to make some improvements to my app, feel free to do that. Parts Required

App Inventor Classic What's Happening with the original version of App Inventor?! The orange "Create" button at the top right of every page of this site links to App Inventor 2.To get to App Inventor Classic, click the Invent button to the right. (Only available on this page!) As of December 3, 2013, visitors to appinventor.mit.edu will find that page of links to App Inventor 1 have been replaced by an introduction to App Inventor 2. But App Inventor 1 is still here, and your App Inventor 1 projects are still here. You can find them at the same site as always-- beta.appinventor.mit.edu. App Inventor (now called "App Inventor Classic") and App Inventor 2 are very similar, but they are not the same system, and projects downloaded from App Inventor 1 cannot be loaded in App Inventor 2. We invite you to try App Inventor 2, but feel free to remain with App Inventor Classic and continue work on your App Inventor Classic projects. MIT plans to keep supporting App Inventor Classic through the spring of 2014.

Triple Axis Magnetometer Breakout - MAG3110 - SEN-10619 I’m also having this problem, though I’m reading it out on a Raspberry Pi. I’m getting 0xFF (-1 C) most of the time, and occasionally 0x00 (0C), in ambient conditions around 25C. I never get any other values. Everything else works perfectly, except temp. I’ve tried reading it both before and after the magnetic values (since the device seems to do some magic when you read the X MSB), and with and without delays in between them (just to see what’s up). I’ve even tried reading all the registers at once, and I am getting correct values in every register, including those immediately before (Z user offset LSB) and immediately after (CTRL 1) the DIE_TEMP register. I know that -1C and 0C are both theoretically “valid” temperatures, but 0xFF and 0x00 sure look a lot like either hardware problems (letting SDA float high, or holding it low) or else programming problems (-1 and 0 are both often used as “error conditions”). Does anyone have one with a sane DIE_TEMP?

Related: