Blogs

I want at least 7 more !

Setting the arduino board type needs to come from the user's UI or helper functions like arduino.setBoardUno().

Currently the board can set the type, by data coming back from the board.  Although I would prefer this method, if Arduino & its firmware was capable of providing all the necessary information.  But its not.  Sad, too, because I like "plug and play"

I think interfaces should NOT be using primitive types.  We should always use the Object form of the primitive.

For example :
In 
instead of this :

enablePin(int address);

do this :

enablePin(Integer address);

In the past I thought int was somehow more effecient or cleaner than using the Object form, but in MRL-Land that is not the case.  In fact it can cause problems.

this is the script use for the demo, run after my inMoov script.

[[home/Calamity/imdemo.py]]

Ok, I feel the need to get on the SoapBox again, because I'm currently working with Swing UI and pin control. 

I have made tonnes of mistakes, the stuff I'm refactoring now could be a shiney example of what "not to do". With that said, I think Arduio's following functions were a mistake :

Last weekend I, Markus and Robyn visited the Indian Institute of Technology, Rorkee in India.

http://www.iitr.ac.in/

It was a very interesting and inspiring visit. The people we met were very nice and asked a lot of good questions. Markus had his Robyn InMoov robot and I was bringing the head of my robot. We were showing the robots from Friday to Sunday and met a lot of interesting people. 

Hello guys!

i know leapMotion is not a new service, but i recently had the necessity to use it for some work, and ofcourse MRL was the platform i used!

With alot of help from Kevin i did reach a final script that uses leap to mimic my index finger and moves a servo accordingly.

The script prints all info from all fingers and palm, however i am only using the index from right hand to control the servos (ofc u can control multiple servos).

moz4r having fun with virtual inmoov :)

Sometimes we need to figure out unecessary complexities, so that we can make things more accessable.

I'm talking about Arduino Board Type.  Something you'd think is very straight forward, yet .. its not.  Not because it can't be, but I think because few have taken the time to make sense of it.

"Board Type" is a general term, but there are potentially 2 things which depend on it.