Once you have everthing setup, you can start vmplayer and open aircable.vmx or just double click on it's icon to get it opened. Don't plug in your Bluetooth dongles yet, wait until the virtual computer booted.

It will start loading

The first time you run it, it will ask you about vmware guest tools, you can tell it do not download and ask it to remember your settings as it is useless for this system.

From this page you will be able to tell what is the ip the vm got from your dhcp server, which will allow you later to connect with your browser, from this window you can also make some basic management of the Linux installation.

Now it's the time to connect your Bluetooth dongle, on both MS Windows and Linux VMplayer will try to attach the dongle to the virtual machine automatically. On MacOS you have to ask it to do it at least the first time.

If you ever need to do any maintaince and need to login into Linux then the username is aircable and the password is aircable as well.

As you may know SensorSDK runs inside a Bluetooth Linux framework called OpenProximity. Which you can access by just pointing your browser to the ip address you got on the previous step.
The window you will see looks like this picture. Pay attention that you see your Bluetooth dongle listed there. As soon as you see them listed you're ready to continue.

Once you got into OpenProximity you can access SensorSDK by selecting plugins.sensorsdk from the drop down list that you find on the top right.

After you selected SensorSDK you will be presented this screen. From here you will be able to monitor SensorSDK and your nodes. Now let's setup SensorSDK so it does something useful.

To access SensorSDK setup you have to click on the SensorSDK Admin button on the navbar. You need privileged access in order to continue from here, if you haven't log in yet you will be asked to do it. User name is admin password is aircable

This how the administration interface main page looks like. You will have to interact with this page many times. As you can see there's a box on the right that will allow you to easily follow the missing steps for a good setup.

A campaign describes the rules that let SensorSDK decide which of the devices that OpenProximity discovered needs to be handled by SensorSDK. We have all ready created a campaign with the default values for a SensorSDK Dev Kit installation for you on the cdrom.

Dongle setup is the part of the process where you let OpenProximity know which of all the available system dongles will be used by SensorSDK.
In case you have more than 1 dongle make sure you create a Sensor dongle for each one of them, because as of SensorSDK 0.3.6 there's a bug in the code that will make the system fail randomly.

This little menu on the right will allow you to see all the dongles that are available right now. Each time you modify a campaign or a dongle OpenProximity and SensorSDK gets restarted, so it may happen that when you get the webpage the list is empty (as in the example) in those cases hit refresh until the list gets something. If your dongle still doesn't appear then make sure it's connected to the VM.

This is how it looks like when it knows of a dongle. Copy and then Paste the address, as there's no scripting yet that does this for you.

Each dongle can have a name, in this example Generic Dongle.
A Bluetooth compatible radio can handle up to 7 connections at the time, so theoretically you could make the Connections number equal to 7, but as there is some stuff that neither OpenProximity or SensorSDK have control so it's not recommended to use more than 6 or 5 as safe values.

SensorSDK has a built-in alarm system, in order to get alarms delivered it uses email. So you have to setup your smtp server settings.
Take into account that passwords are stored as plain text, so make sure you don't let anyone access your server or they will know your email username and password.

Once you press save SensorSDK will try to reach your email server and tell you if configuration is ok or not.

SensorSDK uses some templates to generate the emails when alerts gets triggered.
The system also includes some basic factory templates, on this page you can ask to fill up the templates for you. Don't forget to select Save changes or it will not do anything.

First you have to select a username and a password.

Then after pressing save you can set it's name, last name and email.

Each alarm mode needs different settings, and have different meaning for the same internal variable, on screen interactive help will help you get through.
On this example we choose no data so we only need to tell the system after how many seconds with no reporting we start considering there could be a problem.

We also need to select the devices we want this Alert Definition to cover and the users we want to notify in case it's needed.

The last important part on this page is the reset time if no data got into the system (meaning the alarm situation never got resolved) then the alarm will get reset after reset time seconds with no data, and will eventually send a new email.