Go Down

Topic: Enlightened Domotics Alarm Monitoring System(EDAMS) (Read 3 times) previous topic - next topic

alex72

Hi all!

Wiki for EDAMS is available! you'll found documentation about:


  • Introduction

  • Installation procedure

  • Example of use case

  • Screenshots of developpement version



Wiki is here: http://code.google.com/p/edams/

alex72

Hi all!

EDAMS  0.7.0 is here, and comes with:


  • Add xPL support(via xPLLib, integrated in edams!)

  • Add cosm data handling(ex pachube) via feeds and datasteams creation.

  • Add a new general map to see all sensors in one way.

  • Can add same sensor many times on same or different location.

  • Add geolocalization support(+cosm).

  • Many many fixes.



As you cans see, big adds(cosm, xPL) comes with 0.7 version! EDAMS follows references standards(xPL,cosm). General map is a new tool to auto-group your sensors and lets you the ability to move them together(background can be configured to draw your house map image).

To enhance your EDAMS experience, you'll need to configure an xPL hubl(like perl-hub or xPL_Hub).

Screenshots:




Seasons Greetings

alex72

#7
Dec 11, 2012, 02:42 pm Last Edit: Feb 19, 2013, 05:55 pm by alex72 Reason: 1
You can use USB to talk to Arduino but to be more precise it's serial communication. In my house sensors are connected to Arduino along an long sort of ethernet cable:

1 line for +5v
1 line for GND
1 line for OneWire(DS18B20)
others depends(DHT11 need 1 cable per sensors)

In fact, sensor's connection aren't not a problem you can use whatever you want(wifi,bluetooth,I2C...).

The only needs is that you use same terminology as EDAMS speak, for now I've (poorly)designed the following  data trame:

DEVICE;DEVICE_ID;DEVICE_TYPE;DEVICE_DATA;OK

All trame fields must be seperated by ';'.

DEVICE is use to declare a new device(sensor now, but in next version I'll define more device types).
DEVICE_ID is an integer to identify your device connected to Arduino. It must be unique and should be the same at anytime.
DEVICE_TYPE is a string to identify what's your device, EDAMS use database(you can add your's own device) to compare with this received string. Example "DS18B20"  database file is shipped with EDAMS so you can use with it.
DEVICE_DATA is a string to update device data, in case of DS18B20 you should get a T° in float format. EDAMS have generic widget to display this value(counter, thermometer...) so 2 cases: if your sensor is recognized by EDAMS in database, it will set for you in correct format(°F with thermometer widget) in other case, you sensor isn't recognized and EDAMS will show your data in generic way(only a numerical formatted with counter widget).
OK:is just used by EDAMS to verifify correct trame lenght(to avoid serial parasite).

Example:
With arduino, with just a:

serial.println("DEVICE;0;DS18B20;17.296;OK")

you say to EDAMS that you've a device with ID 0(it's your job to generate id number here, you can use another unique ID per sensor) and it's a DS18B20 and 17,296 correspond to it's data.

With EDAMS you'll be able to affect this DS18B20 to a room and select this room to see it's values in a nice way.

I've attached with this message, a sample talk to EDAMS.


EDIT:Since, EDAMS use xPL all description here is obsolete...

Graynomad

Quote
you speak about software developpement or sensor data?

Software development.

I'm just trying to get a handle on the topology here. If I've got this right you are talking USB to an Arduino, how is that Arduino talking to the sensors? Presumably they can be all over the house.

______
Rob
Rob Gray aka the GRAYnomad www.robgray.com

alex72

#5
Dec 11, 2012, 12:06 pm Last Edit: Feb 19, 2013, 05:54 pm by alex72 Reason: 1
Hi Graynomad!

What's do you mean by "looks like it's coming along slowly", you speak about software developpement or sensor data?

For now I'm using serial CP2102(USART=>TTL) connected to Atmega(in C) or Arduino.  But for testing purpose, I'm using serial buffer emulation(in fact, only printf in forked child with some random data values and sensors). And some times, I'm using CP2102 in loopback mode(TX<=>RX) and use some serial write func to see if all is good in reading serial buffer.

Later and to avoid string serial buffer and to save some bandwith, I think I'll pass data in binary form to arduino/atmega=>PC....

Thanks a for your interest.

EDIT:Since, EDAMS don't use serial anymore. All data are passed to xPL network, so we can say that EDAMS  talk 'xPL language'...

Go Up