Post navigation

First we tested the concept, just turning on and off several colored LEDs.

Second, we connected the LEDs to the output of the MSP430 and played with the code to make some LEDs light up.

After we defined and fine tuned the code, we start soldering the LEDs to each resistor

Getting the following LED-Resistor pair.

Me print a picture of the constellation and glued to a cardboard, make holes for each star and plug and glue the LEDs on the board.

We made some more soldering on the cable to plug it on the MSP430 board, along with a battery holder (2 AA battery for a total of 3V).

And was ready to go.

When you turn on-the battery pack, the program start blinking all the LEDs (to show that all are working), then you push the button once to turn them off, and afterward, just every time you push the button the corresponding star (following the paper presentation) start to blink.

First, you can download and import de following XPZ Data and Example. Which contains all the data views required to access the portal. (Make sure to have GeneXus X Update 3 or grater), in addition, and for now (hopefuly), you’ll have to add the additional DLL to the “bin” directory under ../web/bin, if you are developing for .NET

You have to set up the “GXportal” DataSource to access the database “gxportal” using the user “gxporta” (the default password is “gxportal” 🙂 )

Then, build it and execute.

On portal:

Under “Configuration” Create a new Application

Update the “Enviroments”, host where the application is located, port and the Virtual Directory is the “relative path” to the file (program) on the URL and filanlly the extension of the file

Ad Activities (the actual program), under the Program Name just the actual name of the program ,without extension or path (we created on the step above under Environments)

Under “Name” use the real name of the application, on the example is “TestWWEmployees” all together (same name as in Genexus)

After that we’ll create 3 additional applications related to the main one, which reflect the status of the transaction, so later we can configure privileges, those are Delete, Display, Insert and Delete, the “Name” we’ll use are going to be: TestTrnEmployee_DLT, TestTrnEmployee_DSP, TestTrnEmployee_INS and TestTrnEmployee_UDP all of them with NO Program Name (we’ll check the status on the actual Genexus Application)

We create a “Menu” for the Application with one option that is going to be the Main Activity, in this case “TestWWEmployees”.

Now let’s add the “Application” in to the portal, go to the page where you want to display the application, and add a GxPortlet of “Aplication Integration” and add “Application Activity”, now configure the Portlet where the “activity” points to our Main Activity (TestWWEmployees) and give it a “Dynamik hight” (make sure that the Hight of the portlet is NUL). At this point you’ll see the application running on the portal (although there is nothing to see because you don’t have the right privileges to see it right now 🙂 )

Now, let’s create the Privileges to access the application, in order to do that, go to

First you need to copy the following directories from your GeneXus installation to the CentOS server.

From under “gxruby” copy the “linux” and “generic” directory both under the same subdirectory.

In my case I’ve created a new directory on the server called “gxruby” (original 🙂 ), and put them there.

Now before you run the installation script, in order to work properly under CentOS you have to do the following:

The installation script is based on Debian, so it expects to have certain libraries installed in places where CentOS doesn’t normally used them
specially the “libmysqlclient”. On CentOS these library is called “libmysqlclient.so.15.0.0” and it’s under “/usr/lib/mysql/”, but in the installation
script it should be under “/usr/local/lib/” so we’ll have to link it to the new location, we do this with the following command:
$ ln -s /usr/lib/mysql/libmysqlclient.so.15.0.0 /usr/local/lib/libmysqlclient.so

Under the subdirectory “gxruby/generic/gx_lucene” (this is where you copy from the GeneXus machine), you have to edit the script “build_make.sh”.
In reality, because this file is corrupted on GeneXus Evo1 U3, it’s better if you delete it an create a new one with the same name with the following contente: