Archive for June, 2015

Why?

Posted in Embedded on June 26, 2015 by asteriondaedalus

Death to Electric IMP~!

Why? Aus$60 versus AUS$3.16 for ESP8266 or AUS$9.42 for NodeMCU.

The development tools for IMP are cute but once you are past NEWBEE who cares … really.

 

Small steps

Posted in Uncategorized on June 22, 2015 by asteriondaedalus

So, finished an online 8 week course I was interested in doing.  MOOC no less.  Not sure about them as my feeling was you don’t get much connectivity with teaching end and it would appear that MOOC are not hitting their target audiences.

I am going to do one on first order logic, for my stuff I play with at work (I am moving into formal languages).  Another will be on AI planning (for fun at home).  In any event, some time to kill so I wired up a breakout to mount an ESP8266 on a breadboard to try out nodemcu, and voila!

Hello world from nodemcu

Hello world from nodemcu

Now my wife wants a few things around the house, like burglar detection down the alleyway etc.  So I have a batch of IR detectors and the nodemcu can email detections no less.  The alternative is to SMS via a cheap GPRS module:

Tini!

Tini!

Now this was under $10 and the module is the size of a phone MicroSIM card.  TBD

Finally!

Posted in Agent, Erlang, Python RULES!, RabbitMQ, XMPP on June 8, 2015 by asteriondaedalus

So, sorted the BlackWidow and likely the YellowJacket connectivity. The socket approach seems to be the better option, and that is TCP based, so porting of mqtt code might still be possible – although the application is simple enough so a Python adaptor on the host between the boards and the mqtt server would do just as well.

Now, the other side is that I opted for moving from emqttd to RabbitMQ as the mqtt broker.  This is due to the fact that there is likely a way to get RabbitMQ talking to Spade agents via XMPP (with some work).  This might be a way of integrating Profeta agents into the picture without deep integration into Spade that I have been currently investigating.

Not to mention likely being able to use the same inter-agent communication for eJason base experiments.

Essentially using mqtt as a ‘blackboard‘.