Archive for the Erlang Category

It’s all a matter of timing

Posted in FORTH is it dead or isn't it?, Erlang, Chapel, Parallella, Elixir on June 24, 2017 by asteriondaedalus

So, phew!

I re-bombed parabuntu onto the SD card.

What the problem was earlier was the security key had changed but I was forgetting to say YES to option for saving the new key (I had quite a lot of red wine last night so don’t be so hard on me ūüėČ )

When I powered up the Parallella again, I wasted no time and jumped in with:

sudo nano /etc/network/interfaces.d/eth0

---- inside of nano ---

auto eth0
iface eth0 inet static
address // your parallella IP here
netmask // your netmask here
gateway // your gateway address here
dns-nameservers x.x.x.x //your dns server list here

--- exit and save ---

sudo reboot

Happily now running on the static IP set … phew!

Now to work.

Target environments will be erlang/elixir and chapel.  Yet, ePython for poking around.

I am reading back into my threaded interpretive days to look at a minimal FORTH runtime to run on the Epiphany. ¬†There has been chatter on the parallella groups about J1, but that is a HDL (read FPGA) FORTH. ¬†I think many people chattering haven’t worked in FORTH so much of the chatter is unproductive. ¬†I am thinking a GForth running on the ARM side that assembles, rather than cross compiles, to a hand built threaded interpreter on the matrix. ¬†I am not sure how feasible that all is but it will be ¬†a good instrument for learning the nuts’n’bolts of Epiphany.

Many lessons can come from the struggle, yes?

This, idea is no more or less I worked on during a project, in Canada, where I noted the DSP software the team was using was already using a threaded processing chain.  The idea then of control loops and conditional inside of that was a soft sell.

So, in FORTHeze no outer interpreter running on the Epiphany.


New way to stuff erlang/elixir onto embedded arm

Posted in Open Source can be professional, Erlang, RaspingBreathburryDOodlePi, Orange Pi, Elixir on June 13, 2017 by asteriondaedalus

YES, it is “designed” for RaspingBreathberryDoodlePi BUT worked a treat for OPiZ.

See the following link.

Hmmmm …

Posted in Erlang, MQTT, Orange Pi on June 1, 2017 by asteriondaedalus

… so the sage seems to be continuing.

I was able to get erlang going on the OPiZ. ¬†I tossed up whether I was going to put RabbitMQ or emqttd onto the gadget – going for emqttd since it didn’t need to carry all the protocols you can play with using RabbitMQ.

I am hoping that was a good choice – go figure emqttd appears to have grown up and so is getting bloated it seems.

The other side though is during the make the OPiZ kept losing connection with github.  Not really sure how to debug this, it is either flaky networking on OPiZ part Рgiven the problems with ssh.  The other side is that it is day time in northern hemisphere and github is not friendly to the southern hemisphere about this time at night (19:00 hours central standard time Australia) as the servers choke.   I have previously, on my PC, not been able to connect to github Рputting it down to skewing of services.


It has just occured to me …

Posted in Parallel Talk, Erlang, ConCurrency, ODROID-C1, Chapel, Parallella on May 19, 2017 by asteriondaedalus

… what a coincidence.

The Parallella and the Odroid-C1 PCB are same size (almost).  Is that Feng Shui, synchronicity or serendipity?

Pity the post holes don’t line up.

It occurred …

Posted in Erlang, Embedded, ODROID is wonderful, OpenSprinklette on December 5, 2016 by asteriondaedalus

… that after all the fluffing around with TTB on the inherited RaspingBreathBurryDOodlePi, I did rather prefer my mix I built originally on one of my ODROID-W.

Still, now I have got the additional ODROID-C1 it makes more sense for use as the house automation server.

The reason is that there is a UPS module that I can get from HardKernel that will help with survival requirements (given the blackouts we occasionally get in sleepy little Adelaide).

I do rather like the 7″ touch display you can get for the C1 as well. ¬†Although, that isn’t strictly necessary since we will browse into the node-red running on it.


Erlang on C.H.I.P.

Posted in Embedded, Erlang on July 30, 2016 by asteriondaedalus

Well, with github and down (for some dangblasted reason) I tried building Erlang on one of my C.H.I.P. from instructions here (for RaspbreathyPiklette).


Sorta stuck after that as … github is down. ¬†Git can’t find it, ping can’t browser can’t. ¬†The site reports up and running but still can’t connect.



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‘.