Forth

Forth on RPi

Start the Forth interpreter with ./atlast and exit with Ctrl-d

atlast.html and atlast.pdf is included and is an extensive atlast-forth manual. Read it online and read about Forth itself here  and here  (Beware that the Forth dialect in the book Starting Forth is a bit outdated compared to Atlast Forth). Leo Brodie wrote another book, Thinking Forth, read it here

Adding new words
Most of the power of Atlast Forth derives from the ease with which C coded primitives can be added to the language. In my case I will add some words for controlling my Gertboard. There is a detailed description on how to do this in the atlast-forth manual. And you can copy much of the word implementations from the gertboard_sw directory if you have downloaded the gertboard demo files. It is easy to add your own words, just add a "define GERTBOARD" to atlast.c around line 56.

Include the gb_common.h right after include 

Then add your own word definitions at the end of the section with word definitions, around line 2704, right after #endif /* COMPILERW */ in atlast.c

And finally, add the actual words to the Table of primitive words, right after #endif /* EVALUATE */ at line 2960 or so.

As we are using code from the Gertboard demos, copy the files gb_common.o and gb_common.h from the gertboard_sw directory to atlast-1.2 directory (it's there if you have run make in this directory as well).

Add gb_common.o to the file Makefile in atlast-1.2. Now, save and run "make" again to recompile atlast.c.

Test the new words
Wire up the Gertboard according to the information you get when you run the command sudo ./leds in the Gertboard demo directory.

Run sudo ./atlast in the atlast-1.2 directory.

Type 1 gertboard

Type 22 1 setio and press enter, the corresponding LED will go on.

Type 22 0 setio and the LED will go off.

Type 0 gertboard

Play with it
Define your own LED demo, start the interpreter with sudo ./atlast. Define these words:

Now type:

A real Use Case
I have a kWh meter that I would like to read with the RPi. On the meter there is a small light that blinks once per 3.6 sec at 1 kW. So I need a way to detect time between pulses. I mounted a simple LDR (2k - 20k) for around €2 over the blinking light and connected it to Gertboard Buf1 and ground. Set B1 as an input with a jumper on the board and connect GP25 to B1.

Now that you know how to add a primitive word to atlast I just list the code for the word: Start the interpreter with sudo ./atlast. Test the commands Result: Jolly good, or as they say in USA, Awesome! Tests shows an accuracy down to a single watt.

However, having the kW load on the command line in a terminal is not good enough, I want it online on the web or as a mobile app. If you are interested, follow me over to the Erlang page where I vill use this Atlast Forth application as an Erlang Port to access Gertboard from a web page.

More Fun
To play a little more with the demo I need another primary word: SLEEP that takes one item on the stack, sleep time in microseconds. This very simple word should have been the word to start with, it actually shows three fundamental things for a primary word in three lines of code. Sl(1) to make sure there is at least one item on the stack. usleep(S0) is using the top stack item S0. Pop; pops the S0 stack item off the stack when it has been used.

Add this primary word to atlast.c. Put it right after the function prim P_quit Remember to wire up the Gertboard according to the information you get when you run the command sudo ./leds in the Gertboard demo directory. Now we can do:

Now define the word leddemo:

Reflective Sensor
The edge trigger word can be used for other sensors as well, I tried it with this Reflective Sensor and it works right out of the box. Connect VCC to a digital output and the "Out" to a digital input. Gnd to Gnd. I found it more convenient to look for positive edges so here is the word for that:

Define a word COUNT to test the setup (Out on the sensor is connected to Buf2 on Gertboard and VCC is connected to Buf3)

Tellstick
In order to have a safe way to handle mains switching, a Tellstick is an excellent choice. It can control many consumer brands of wireless controlled sockets and dimmers. Implementing some words in Forth for switching mains on and off leaves the safe voltages for sensing thru the Gertboard interface.

Download and install the dev kit from Telldus:

When that installation is done you can copy two files over to the Atlast Forth directory:

Then add the lib libtelldus-core.so to the Makefile, at the top, right after -lm:

In atlast.c, add define TELLDUS right before #define MATH;

In atlast.c, include the telldus_core.h file:

In atlast.c, right after #endif /* COMPILERW */ add the following tellstick primitives:

And finally, add the new words to the list of primitives:

Save atlast.c and re-run make to compile and you can try your new words. Remember to configure /etc/tellstick.conf according to the brands of hardware you are using, read the tellstick documentation. First, start telldusd and then atlast. In the atlast console, type your new forth words

Tellstick duo
If you are fortunate enough to have a Tellstick Duo, you probably want to listen for incoming 433 Mhz signals so here we go. But first follow the Tellstick instructions above, and test that they work as expected.

Add this primitive word to atlast.c. We will use it to register a callback. (A callback is an ordinary function, nothing strange, but it will be called not by you but by the Tellstick Duo when there is data coming in). Then add the callback function, this is the function that will be called. Add it around line 295, just above the line /* TOKEN  --  Scan a token and return its type. */ Finally, add the new primitive word to the list of primitives

Now, to try it out, save and re-compile with make and then start telldusd and ./atlast. Type the following in the atlast console: The word rawevent is executed by the callback function, you can re-define it and it will use the latest definition. With this definition it will just type the incoming data in the console. If you take a Nexa remote controll and press a few buttons, the incoming data should print as a string, eg "class:command;protocol:waveman;model:codeswitch;house:A;unit:1;method:turnoff;"