GroG's blog

New Years Resolution - (Better Resolution !)

GroG's picture

Before the year is out, I vote we update the motor, servo, & position interfaces from int to double.

Double allows us better resolution for the future, and ints can change into doubles, but not the other way around.

And if there are questions to use a Double the object vs double the primitive :


Servo Speed Control

GroG's picture

Future Of Servo Speed Control

This will be the future !  Please be part of it .. thumbs up or thumbs down - if thumbs down state why.. WHOOHOO ! - this is what I have so far....


WebGui like MrlComm

GroG's picture

Ahoy Mates !

It's good to be back on the "develop" branch.... :)


Build a Raspberry Pi-Powered Amazon Echo

GroG's picture

Here's a nice Instructable I thought was worth posting.

The big software companies (Amazon, Google, Microsoft) are all working hard and providing Cloud  Robotic Services for the new world.  In this tutorial he does a complete build out with a very interesting omni-microphone & raspi.

For Backend services Amazon has free developer use cloud services. I like Moz4r's idea of a distributed MRL cloud services.


Control Controller Manifesto

GroG's picture

Control & Controller (aka DeviceControl & DeviceController) are a recurring patterns in MRL.
Control represents an interface for other consumers (e.g. ServoControl).  
Controller manages a resource (e.g. Arduino).

"Attach" is the ubiquitous concept of joining the two together.  The Lego Snap ! (e.g. ear.attach(mouth)).


ArduinoMsgGenerator

GroG's picture

arduino3 branch (along with ArduinoMsgGenerator) and MRLCOMM version 46 has been merged into develop branch ... WHOOHOO !

publishPinArray and enablePin appear to be working with new ArduinoMsgGenerator framework now...
(on arduino3 branch)

I've pushed all the stuff I have been working on into a new branch called arduino3.

All the important stuff is in src/resource/Arduino/generate


MrlComm library - customMsg publishCustomMsg what do we need ?

GroG's picture

Hi,

This is a question to the community about what is needed regarding custom messaging to and from MrlComm.   Any references of this being used, or requirements, or suggestions would be appreciated.

Part of this is describing what kind of interface or methods are needed (if any more) and also the msg size - potentially if we have a byte msg structure we (almost) can have msg size == 255 vs 64

Thanks.

Greg.