Time to choose

Posted in Agent on November 4, 2017 by asteriondaedalus

Having played with Profeta, eJason and now Astor I think the time has come to settle on one.

eJason is a great idea, especially as it is built on erlang, but it is knobbled as it is a partial implementation.  It has .send so can talk between agents running in the vm but does not to distributed agents.  You don’t have sensors and actuators.  All that could be added but there isn’t enough design info and pulling apart the codes would be fun but a major project in itself.

Astor is a great evolution of AgentSpeak, especially as it tries to readily incorporate the imperative side.  That is, however, already tackled in Profeta.   Astor is build with Java so has that in its favour, if you were a Java clone.

So, Profeta seems the BDI tool for me.  But it doesn’t do distributed agents.  That is, I suspect, where SPADE comes in.  However, some work involved.  Profeta assumes one environment so the PROFETA class is a singleton.   To run in the SPADE environment that design assumption may need be broken.  Also, the PROFETA class has its own execution loop, it may want a single step to be driven by a SPADE tick event.

Not much work but now having gotten over the distraction of the options I can focus.

Advertisements

You call that a retraction, THIS is a retraction!

Posted in Intel Smemtel on November 2, 2017 by asteriondaedalus

Wow.

I do rather feel vindicated.

All my gripes about the Intel Curie seemed have been spot on.  Poor quality control, useless user support, everything about open source killed Intel “maker” IOT.

I hadn’t bothered keeping up with the Curie story but golly gosh, Curie, Edison gone.

Still they have Up2.  Well up yours Intel.

You are tainted.

That was close (retraction)

Posted in Windoze10 on August 17, 2017 by asteriondaedalus

I went to start my PC yesterday to find the dopey thing had fallen into an auto-update.

I had turned off auto-update and refused to update my Windoze 10 because three times in a row the update froze.

I spoke the Windoze help desk, you know the ones in the balloon.

They hinted I had to deinstall my virus software – or at least disable it to allow the update to work.

I was planning to do just that, I just never got around to it.

Sigh!

So I sat there watching the dopey thing tick its status over.

Then it dawned on me it had gotten past the infamous 33% where it would get stuck – literally for days at a time – previously.

Happy to say the PC finally survived a Windoze update after 6 months of hiding from the process.

Not happy the machine fell into the update against my settings.

RETRACTION

So. For whatever reason my machine updated despite my settings. Fine because it finally made it through. Except another update come through this morning. Yep. It hung my machine.

Niggly

Posted in Embedded, MQTT, NodeMCU, OpenSprinklette, Orange Pi on August 16, 2017 by asteriondaedalus

I may have some more design work for the opensprinklette node-red implementation.

The nuance is that the google calendar node will happily trigger on event edges but the triggered response seems to be a dump of the calendar event parameters but not the edge that triggered the node.

It might be as simple as another parameter on the configurator to tell it whether it is for sprinklers on or off

The other might be using the before event.

Have two outputs then to act as start and stop.  Feed the stop into a timed node.

Either lapsed or absolute is another question.

Much of this is trying to think in a dataflow rather than an imperative idiom.

I want to think also about ACK from the WeMOS sectors. That might want a watchdog timer.

The lwt from the WeMOS sector will need a response. Although any sector/zone on, while WeMOS is down, falls on deaf ears.  Stil, it needs to be logged and reported.

Ta da!

Posted in Javascript, node-red, OpenSprinklette on August 12, 2017 by asteriondaedalus

Ah ha!

I had some trouble importing my pegjs parser function into the node console until I worked out node and/or javascript treats directories as “/” whereas windows uses “\”.

So finally the import is simply:

var parser=require('./parser.js');

I also hand modified the parse function signature which is now:

function peg$parse(input,zones, options) {};

I worked out that zones needed to go ahead of options as calling “parse(input,,zones)” wasn’t a popular choice with the javascript.

The input variable “zones” will come from the configuration node.  That way the parser will take the configuration object [{sector1:chipid()}] and return the mqtt topic fragment “chipid()/zone[0..4]”.

So, the modified parser tested using node console shows it working:

final zone parser test

Now all is needed is the use the zone “grammered” string in the google event title and snip it out, when the event starts/stops.  This is achieved with msg.payload.title as the first parameter in the call made by the node reacting to the calendar event.

The array returned can either be iterated over using a for-loop OR be returned by a node-red function to be treated as a stream of messages (aka msg).

I have a sneaking suspicion that, in fact (and having read the code and how it uses “options”), I [could|should] have injected the zones via options.

Something to play with I think, as it doesn’t seem clean to hand mod the parser code.

Sizzzzle!

Posted in Javascript, node-red, OpenSprinklette on August 10, 2017 by asteriondaedalus

Pop!

A parcel turned up with RaspingbreathburryDoodlePi heatsink kits.

They are the recommended source for a heatsink for the OPiZ.

Although I can certainly find the same on Aliexpress, I bought locally to get them within a week instead of 10 weeks.

Still, gotta say brrrrrrrrrrrrrr, freezy!

At least 5degreeC cooler running with heat sink.

Still not convinced that was source of ethernet dropouts on my new board.   No problems for a couple of weeks now so I will put concerns aside.

I did notice 15mmx15mmx5mm 5V fans on Aliexpress though.  Tempting.

Still tempted at getting a small peltier cooling gadget to go the whole hog – mostly for the fun of it.

But, at the moment, I am focusing on finishing the opensprinklette configurator node for in node-red.   I have a basic configurator to map sectors to WeMOS chipid(), now I will integrate the pegjs defined parser.

Parse the salt please, or at least the sector declarations

Posted in MQTT, OpenSprinklette on August 10, 2017 by asteriondaedalus

So, I spent some time on how to parse zone commands for the sprinklers in the form “sector1=1,sector3=4,sector2=0,sector3=1”, from the google calendar event titles, into mqtt commands for the WeMOS nodes.

Regex have never been a favourite of mine, being a clunky solution from hackers for hackers.

While it is a small problem to solve I still wanted to do something smart so I looked around for a parser generator for javascript.

I came across pegjs.

Brilliant!

Though, as usual, bugger all help.

However, I started with the JSON example and parred it back to get a solution that returns an array of zones (sector/zone) to act as a fragment of an MQTT topic.