Get in touch with your Things

Any object that can be attached to an Arduino microcontroller is a potential Things: get interaction in wireless or wired, acts automatically and is even remotely controllable from you smartphone or tablet.

Starts in three steps : get your building blocks, load Souliss and get your Things on the smartphone.

Do it simple!

Do it simple!
A network of Things in minutes for your Android and Arduino

Building Blocks

Building Blocks
Easily compose hardware

Souliss on AVRs

Souliss on AVRs
Load Souliss on your Things

Android App

Android App
Get your Things on your Smartphone

Wednesday, January 30, 2013

First step of Olimex integration near to complete

Olimex's AVR-T32U4 board with MOD-WIFI and MOD-IO2
After a while  the Atmel AVR on board of Olimex AVR-T32U4 (using Arduino Leonardo bootloader) is now running Souliss with both support for MOD-IO and MOD-WIFI giving access to I/O via Android (using MaCaco protocol) and/or Modbus.

We get time to work on Olimex's MOD-IO2 board and fully include that board into Souliss, the first step started from Wayne's I2C library that after some work became lighter and basic enough to be part of Souliss. The I2C library is the core for the MODIO one, that provide similar methods to access standard I/O pins, so now the Olimex's MOD-IO2 (and MOD-IO) can be controlled like standard pins.

In the top of the picture shows the IDC10 cable breaked out on a bread board, this because we need from the UEXT the SPI for the MRF24WB0MA WiFi module and the I2C for the PIC on board of the I/O board. Unfortunately the MOD-IO2 doesn't extend the whole UEXT bus and so this workaround was needed. There is one more clean solution, that use an IDC10 cable with one female and two male headers, that can easily be build using a crimping tool for IDC cables.

The code will be released under revision A4.1 just after completion of ready to use examples for Olimex boards, this revision will support also MOD-ENC28J60 and MOD-IO. For these two boards we cannot perform any test, but Microchip ENC28J60 is yet working under Souliss and MOD-IO is pretty similar to the smaller MOD-IO2. If you would like to get the code before the public release, just email us.

There are other Olimex's boards that we would like to support, like the RF ones but this will depend on hardware availability.

At the end one important note, the Microchip MRF24WB0MA is distributed with different firmwares and the latest 0x120C is not yet supported in our drivers. We will work to include latest modules, but for now ensure that you are getting boards  with module manufactured before August 2012.


Monday, January 14, 2013

Pointers are so dangerous

MaCaco / vNet log screen and Modbus in Wireshark over the MRF24WB0MA
The screenshot on the top is the logging of a session with the WiFi MRF24WB0MA running Souliss with both MaCaco protocol over vNet and Modbus TCP, it was a long day looking around for a strange crash.

The Microchip MRF24WB0MA doesn't offer the IP stack in hardware, so I'm running that chip over the uIP stack, Souliss is running uIP from release A3 due to ENC28J60 support. This stack was for us a big headache but is now running really fine. So same should be for the WiFi module.

It was, but not at 100%. Souliss was running fine over WiFi, but some time the communication hang without reason, not so strange when including a new module, the driver may stopped to work.
But it doesn't, is still working and looks fine because the board is still alive and reply to pings without any problem, but MaCaco and Modbus stops after some minutes.

That's strange, MaCaco and Modbus are the same that runs over vNet and all its drivers, more the same stack is used for ENC28J60 where the problem doesn't occur, the morning goes testing but only with WiFi these protocols stops.

At first look the WiFi driver seems to work, otherwise ping wasn't available, so what happen? Just deeper in the stack MaCaco and Modbus stops because their listeners became crazy, the listened ports are changing randomly. So, some one is writing out of its boundaries.

Back to the drivers, they were working but didn't handle properly the uIP buffer, some more if() and now the WiFi is behaving correctly from almost one our.

Tomorrow I will let it run for more time, if it will not stop means that Souliss A4.1 is ready, there are just some minor bugfix on the logics and examples that shall be solved than it will be released.

Stay tuned,

Sunday, January 13, 2013

Souliss goes WiFi / 2

Olimex AVR-T32U4 and MOD-WIFI running Souliss / 1
Once included the Microchip MRF24WB0MA core of the Olimex MOD-WIFI most of the job was done, the step after was the Olimex AVR-T32U4 shown in the picture.

The T32U4 is a small microcontroller board with UEXT socket powered by the ATmega32U4 that power also the Arduino Leonardo board. Just a bit of tuning on the SPI configuration and Souliss was running over it using the MRF24WB0MA radio to bring communication in it.

This Microchip WiFi controller offer a wireless IEEE 802.11 (WiFi) offering up to the MAC layer of the ISO/OSI, is Souliss runs over the uIP software stack offering same functionality of ENC28J60 but without cables.

Saturday, January 12, 2013

Souliss goes WiFi

Souliss communicate over WiFi with MRF24WB0MA
After a long run in design the Alpha 4 release of Souliss, we are back on the drivers, working on the cheap and spread used Microchip MRF24WB0MA.

Starting from AsynchLabs / Open Electronics porting of ZeroG Wireless G2100 drivers we have now included in the working-on release of vNet the code for pairing the Microchip radio in both standard or AdHoc connections.

In the actual picture we are using a MOD-WIFI from Olimex connected to an ever-green Arduino Duemilanove, then we will move Souliss to the ATmega32U4 microcontroller and the Olimex AVR-T32U4 board before release the code as Souliss A4.1.

Stay tuned,

Monday, January 7, 2013

Souliss Example Documentation

Is now released a new documentation format for the examples provided with the Souliss code, these are build using Pencil and are distributed as HTML pages.

In each example there is a drawing with a sketch of the data flow and involved boards, this give an easy understanding of the example goal and features.


Friday, January 4, 2013

KMTronic DINo Back in Stock

Data flow diagram for example ssDINo_ex01_Lights
The KMTronic DINo is probably the unique single board that include opto-insulated inputs, relay and an Ethernet communication interface. From it first release we get the KMTronic support for including this board into the Souliss framework.

Now the board is back in stock from KMTronic online shop, that makes Souliss ready to install if the feature of this board fit the installation requirements.