This is a post to explore the possibility of a "cascading detach".  This is when a Service is released from Mrl and is currently attached to other services.  The goal will be to release the service as cleanly as possible, and in the process notify other Services it has been released.  Potentially, this notification will "cascade" into mutliple detach calls to successfully remove the target Service.

Setup - Here is setup of the problem - ***Mats can you add to the script? to get the initial setup?***

[[/home/GroG/detach.py]]

Mats has this cool I2C temprature sensor - just needs a tiny MRL driver.

What thingies do you have which might be Borg'd ?!

Ahoy !

We recently were excited to add Java 8 default methods to interfaces for our services ... 
Sadly, this borked Jython :(

But my last checkin should have fixed all that.  There are now no more "default" methods in any Java org.myrobotlab.service interface.

In the process I tried to do some refactoring.  I created a new interface ... "Attachable" !  And moved interfaces which were common to ALL services to org.myrobotlab.framework.interfaces

I was hoping to wrap up working with the interfaces.  Mats and I made a lot of progress defining how future "attach" will work, and starting to get into the details of implementation.   I have been testing with START_INMOOV.bat script, but now realize there is a rather large issue.

The issue is the new improvement from Java 8 of "default" interface methods are not reachable from Jython !

We want to build services which can easily be attached.  With simple and consistent rules we can make a platform which supports much more complicated systems.

I'm trying to get Sabertooth service working again .. 
In the process I noticed MotorContoller is missing this method .. 

public void attach(MotorController controller) throws Exception;  

to go along with the other Controller interfaces and to follow the Attach Pattern !

Ahoy !

Recently one morning my wife turned on the furnace and we were quickly inindated with a cloud of smoke.  After the smoke cleared, I looked into the details and found the motor completely burnt.  We purchased a new motor, but in the back of my head I'm always wondering, "How did that happen?"

Sorry,
I created this one :P

As Calamity pointed out there is some missing runtime type identification of the board, which I recently  commented out. (I owe a unit test ! :P)

Now some history on it :

MRL can now "potentially" compile and upload the board, its necessary to send the correct command line parameters to avrdude.  This is "sort of" done in the ArduinoUtils - but it does not have all the needed types for all the boards.

Very cool stuff from Festo ..  First time I heard them say ROS (what?) :)

Simple compressions joints ... very cool

Manticore is becoming organized here 

Manticore Release

Thanks Shaun for pointing the github project out ..

(Image from talented artist  kikicianjur-d384nro @ deviant Art ! )

Compadres,

So we all are on the same page, we are headed for release.  This is the "short list" of worky one-click requirements.