marcas | 1 Jun 2012 07:11
Picon

Re: Contiki Debug System

Hello,

I also had something like this in mind.

I found a more complex method for debugging

http://stackoverflow.com/questions/2429333/c-debugging-macro-with-different-debug-sources

but I think this would be to complex to handle, so i expanded the 
current contiki implementation.

I wrote a test in the meantime based on your  idea with some 
modifications, and it seems to work.

in debug.h:
----------------------------------------

#ifndef DEBUG_H_
#define DEBUG_H_

#define DEBUG /*add this to the compiler invocation in future*/

#ifdef DEBUG

#include <stdio.h>

// Debugging output function (printf or any other var args function)
#ifdef DEBUG
#define DBG(...) printf(__VA_ARGS__)
#else
(Continue reading)

Valentin Rouxel | 1 Jun 2012 09:39
Picon
Picon
Favicon

Re: avr/io.h missing in avr-ravenlcd

Ok. Thank you for these information. I will look for AVR studio.

----- Mail original -----
> De: "David Kopf" <dak664@...>
> À: "Contiki developer mailing list" <contiki-developers@...ge.net>
> Envoyé: Jeudi 31 Mai 2012 17:38:52
> Objet: Re: [Contiki-developers] avr/io.h missing in avr-ravenlcd
> 
> That is an AVR studio project (the .aps file) although it builds with
> make on cygwin. Since Studio is windows only there might be a
> compatibility problem.
> On my cygwin:
> $ locate avr/io.h
> /cygdrive/c/avr-gcc47/avr/include/avr/io.h
> /cygdrive/c/Program Files (x86)/Atmel/AVR Studio 5.0/AVR
> Toolchain/avr/include/avr/io.h
> /cygdrive/c/WinAVR-20100110/avr/include/avr/io.h
> /home/dak/avr-libc-1.8.0/include/avr/io.h
> 
> $ which avr-gcc
> /cygdrive/c/WinAVR-20100110/bin/avr-gcc
> 
> 
> 
> -----Original Message-----
> From: Valentin Rouxel
> Sent: Thursday, May 31, 2012 11:19 AM
> To: Contiki developer mailing list
> Subject: [Contiki-developers] avr/io.h missing in avr-ravenlcd
> 
(Continue reading)

Siva Subramani | 1 Jun 2012 11:20

TDMA MAC error

Hello all,

I would like to use TDMA MAC. I got an error

Error: 'const struct radio_driver' has no member named 'set
receiver_function'

I searched through the mailing list and I found many people have had the
same error. I couldn't find any fix or solution for this problem. I wonder if anyone have managed to run TDMA
or CTDMA MAC in contiki.

Please provide if you have any solution to this problem.

Thanks
Siva

For your information:

(i) tdma_mac.c and ctdma_mac are included in Conf.h
(ii) Following suggestions from the mailing list
#define NETSTACK_CONF_MAC nullmac_driver
#define NETSTACK_CONF_RDC tdma_mac_driver

________________________________

NOTE: The information in this email and any attachments may be confidential and/or legally privileged.
This message may be read, copied and used only by the intended recipient. If you are not the intended
recipient, please destroy this message, delete any copies held on your system and notify the sender immediately.

Toshiba Research Europe Limited, registered in England and Wales (2519556). Registered Office 208
(Continue reading)

Alan Ferrari | 1 Jun 2012 12:14
Picon

Extra trafic over RPL

Hello All,

I'm using Contiki 2.5 with RPL enabled, I would like to send a broadcast message only
to nearest nodes and without passing through RPL, any advise?

Thanks a lot in advance.

Alan

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
António Oliveira Gonga | 1 Jun 2012 12:25
Picon
Picon
Favicon

Re: TDMA MAC error

that RDC layer is no longer supported for long time. 
Skip it, and it's better to update it yourself

---
Best Regards,
António Gonga
-------------------------
KTH-ACL
________________________________________
From: Siva Subramani [Siva.Subramani@...]
Sent: Friday, June 01, 2012 11:20
To: Contiki developer mailing list
Subject: [Contiki-developers] TDMA MAC error

Hello all,

I would like to use TDMA MAC. I got an error

Error: 'const struct radio_driver' has no member named 'set
receiver_function'

I searched through the mailing list and I found many people have had the
same error. I couldn't find any fix or solution for this problem. I wonder if anyone have managed to run TDMA
or CTDMA MAC in contiki.

Please provide if you have any solution to this problem.

Thanks
Siva

(Continue reading)

David Kopf | 1 Jun 2012 12:32
Gravatar

Re: Extra trafic over RPL


Where do these broadcasts originate, and what would RPL normally do with 
them? Nodes will send all received multicasts to the uip stack where they 
are filtered through RPL but the stack will originate only unicasts to the 
parent.

However nothing stops you from calling the mac, rdc, or  radio input routine 
to send your own packets.

-----Original Message----- 
From: Alan Ferrari
Sent: Friday, June 01, 2012 6:14 AM
To: Contiki developer mailing list
Subject: [Contiki-developers] Extra trafic over RPL

Hello All,

I'm using Contiki 2.5 with RPL enabled, I would like to send a broadcast 
message only
to nearest nodes and without passing through RPL, any advise?

Thanks a lot in advance.

Alan

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
(Continue reading)

Alan Ferrari | 1 Jun 2012 14:09
Picon

Fwd: Extra trafic over RPL

My final goal is to have a traffic which is not influenced by the RPL,
I'm right now working on the radio routine in doing that but if there
is something at higher level (i.e. in ICMP) will be better especially
for the portability of the code.

Thanks a lot!

Alan



Begin forwarded message:

Subject: Re: [Contiki-developers] Extra trafic over RPL
Date: June 1, 2012 12:32:25 PM GMT+02:00
To: Contiki developer mailing list <contiki-developers <at> lists.sourceforge.net>
Reply-To: Contiki developer mailing list <contiki-developers <at> lists.sourceforge.net>


Where do these broadcasts originate, and what would RPL normally do with
them? Nodes will send all received multicasts to the uip stack where they
are filtered through RPL but the stack will originate only unicasts to the
parent.

However nothing stops you from calling the mac, rdc, or  radio input routine
to send your own packets.

-----Original Message-----
From: Alan Ferrari
Sent: Friday, June 01, 2012 6:14 AM
To: Contiki developer mailing list
Subject: [Contiki-developers] Extra trafic over RPL

Hello All,

I'm using Contiki 2.5 with RPL enabled, I would like to send a broadcast
message only
to nearest nodes and without passing through RPL, any advise?

Thanks a lot in advance.

Alan



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Contiki-developers mailing list
Contiki-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/contiki-developers


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Contiki-developers mailing list
Contiki-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/contiki-developers

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Contiki-developers mailing list
Contiki-developers@...
https://lists.sourceforge.net/lists/listinfo/contiki-developers
Adam Dunkels | 1 Jun 2012 14:34
Gravatar

Re: Fwd: Extra trafic over RPL

Check out examples/ipv6/simple-udp-rpl/broadcast-example.c - despite the name of the directory, I'm pretty sure those broadcasts would bypass RPL.


/adam

On Fri, Jun 1, 2012 at 2:09 PM, Alan Ferrari <alan.ferrari-gy3b+zu4XSAfv37vnLkPlQ@public.gmane.org> wrote:
My final goal is to have a traffic which is not influenced by the RPL,
I'm right now working on the radio routine in doing that but if there
is something at higher level (i.e. in ICMP) will be better especially
for the portability of the code.

Thanks a lot!

Alan



Begin forwarded message:

Subject: Re: [Contiki-developers] Extra trafic over RPL
Date: June 1, 2012 12:32:25 PM GMT+02:00
To: Contiki developer mailing list <contiki-developers <at> lists.sourceforge.net>


Where do these broadcasts originate, and what would RPL normally do with
them? Nodes will send all received multicasts to the uip stack where they
are filtered through RPL but the stack will originate only unicasts to the
parent.

However nothing stops you from calling the mac, rdc, or  radio input routine
to send your own packets.

-----Original Message-----
From: Alan Ferrari
Sent: Friday, June 01, 2012 6:14 AM
To: Contiki developer mailing list
Subject: [Contiki-developers] Extra trafic over RPL

Hello All,

I'm using Contiki 2.5 with RPL enabled, I would like to send a broadcast
message only
to nearest nodes and without passing through RPL, any advise?

Thanks a lot in advance.

Alan



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Contiki-developers mailing list
Contiki-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/contiki-developers


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Contiki-developers mailing list
Contiki-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/contiki-developers


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Contiki-developers mailing list
Contiki-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/contiki-developers


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Contiki-developers mailing list
Contiki-developers@...
https://lists.sourceforge.net/lists/listinfo/contiki-developers
Adam Dunkels | 1 Jun 2012 14:42
Gravatar

Re: Contiki Debug System

I'd also like a nicer handling of debugging statements - the current "design" is just a hack. Having a central debug.h is the way to go. This could also include contiki-conf.h, which could potentially include a bunch of different DEBUG_CONF_CONTIKIMAC/DEBUG_CONF_UIP6/DEBUG_CONF_RPL_DAG, etc.

Using the preprocessor to selectively compile debugging statements in selected modules in the only way to go in memory-constrained systems like ours, so that leaves out some of the nice *printf()-based systems people are using elsewhere. 

The downside is of course the complete recompilation of the system (which was always the reason for the current per-file #defines, by the way), but at least that is less of a problem in Instant Contiki.

/adam

On Fri, Jun 1, 2012 at 7:11 AM, marcas <marcas-fW+7u5HpypJeoWH0uzbU5w@public.gmane.org> wrote:
Hello,

I also had something like this in mind.

I found a more complex method for debugging

http://stackoverflow.com/questions/2429333/c-debugging-macro-with-different-debug-sources

but I think this would be to complex to handle, so i expanded the
current contiki implementation.

I wrote a test in the meantime based on your  idea with some
modifications, and it seems to work.

in debug.h:
----------------------------------------

#ifndef DEBUG_H_
#define DEBUG_H_

#define DEBUG /*add this to the compiler invocation in future*/

#ifdef DEBUG

#include <stdio.h>

// Debugging output function (printf or any other var args function)
#ifdef DEBUG
#define DBG(...) printf(__VA_ARGS__)
#else
#define DBG(...)
#endif //DEBUG


// Debug switches for each module, remove x to activate

// application modules
#define DEBUG_MAIN

//    net/mac modules
#define DEBUG_XMACx
#define DEBUG_CONTIKIMACx
// ...

// core/sys modules
//......


#endif //DEBUG

#endif //DEBUG_H_

In the Module:
----------------------------------------

#include "debug.h"

#ifdef DEBUG_MAIN
#define MAIN_DBG(...) DBG(__VA_ARGS__)
#else
#define MAIN_DBG(...)
#endif

#include <stdlib.h>

int main(void) {
    MAIN_DBG("This is a debug message!\n");
    return EXIT_SUCCESS;
}

The drawback that all modules have to be recompiled is acceptable for
me, as  I anyway will sit a long time in front of the code and the debug
messages  to find the bug.
Once I know where the bug could be, i enable the debug messages for the
involved modules, recompile once and start searching for the bug.

Kind regards
marcas

On 2012-05-31 21:59, David Kopf wrote:
> I don't know if the preprocessor would choke on so many names, but if each
> module used something like DEBUG_CONTIKIMAC("foo is %u\n",foo) with at the
> top
> #ifndef DEBUG_CONTIKIMAC
> #define DEBUG_CONTIKIMAC(...)
> #endif
>
> then you could have a debug.h included in the contiki-conf.h on each
> platform which I guess could be overridden by a debug.h in the project, that
> defined them. For AVR the printf_p saves RAM, so
> #define DEBUG_CONTIKIMAC(FORMAT,args...) printf_P(PSTR(FORMAT),##args)
>
> The downside would be changing debug.h would force a complete rebuild. But
> in that file you could have
> #define DEBUG_PRINTF(FORMAT,args...) printf_P(PSTR(FORMAT),##args)
> and then in any individual module switch the debug on with
>
> #define DEBUG_CONTIKIMAC  DEBUG_PRINTF
>
> have not tried that though.
>
> -----Original Message-----
> From: Fabio Giovagnini
> Sent: Thursday, May 31, 2012 2:22 PM
> To: Contiki developer mailing list
> Subject: Re: [Contiki-developers] Contiki Debug System
>
> Hi
> I'm interested in fixing the debug system.
> I also had the problem of my own printf, so I think it could be a very
> good improvement if easily could be possible in config to choose stdio
> printf or your own one.
> I think we can open a discussion
>
> Best regards
>
> Fabio Giovagnini
>
>
> Il giorno gio, 31/05/2012 alle 19.15 +0200, marcas ha scritto:
>> Hello,
>>
>> the current debug system of contiki is not flexible enough for my
>> purposes.
>> I saw a lot of other debug implementations in other C based projects
>> with following advantages :
>>
>> - centralized enabling and disabling of debug massages (per module!) in
>> one structured debug.h file
>> - printf function is replaceable by any other var arg output function
>> (also only within the debug.h  file).
>> - DEBUG is defined during compiler invocation, not within code (=main
>> DEBUG switch)
>>
>>
>> Maybe I do not really understand the current debug system, so please
>> correct me if I am wrong. All modules have following definitions:
>>
>> #define DEBUG 0
>> #if DEBUG
>> #include<stdio.h>
>> #define PRINTF(...) printf(__VA_ARGS__)
>> #else
>> #define PRINTF(...)
>> #endif
>>
>> The only way to enable DEBUG for the module is to set DEBUG to 1 or
>> something other than 0 within the code of the module.
>> printf is fixed in all modules as standard output function. I tried to
>> globally replace it with following definition:
>>
>> #define printf MyPrintf
>>
>> This leads to a conflict with the existing printf of stdio.h with the
>> IAR compiler (warnings that do not need to be thrown and can be avoided).
>>
>> There are also some modules within contiki where DEBUG is set to 1
>> (looks like someone forgot to set it back to 0 again)
>>
>> Did some of you had a talk about the debug system yet? I would be
>> appreciated to receive some more information about it or to start a
>> discussion on how to improve the current debug system.
>>
>> Kind regards
>> marcas
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Contiki-developers mailing list
>> Contiki-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>> https://lists.sourceforge.net/lists/listinfo/contiki-developers
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Contiki-developers mailing list
> Contiki-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/contiki-developers
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Contiki-developers mailing list
> Contiki-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/contiki-developers
>


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Contiki-developers mailing list
Contiki-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/contiki-developers

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Contiki-developers mailing list
Contiki-developers@...
https://lists.sourceforge.net/lists/listinfo/contiki-developers
Ivan Lapitski | 1 Jun 2012 14:44
Picon

Re: Contiki Shell extension for Home Automation?

Hello Paulo

Yes, I'm using the erbium engine for contiki.

Yes, I agree it's great.

I do not know what has happened with IPSO-Profile, maybe someone with
more insight can answer this.

Basically what it said was that you have a number of standard coap resources.

for example:
/dev/mdl (model)
/dev/n (name)
/dev/ser (serial)

and some other resources for sensors/controllers.

It would be great with an open source based standard.

SEP 2.0 is based on HTTP/XML and is imho not very well suited for
resource-constrained devices.

Best regards

Ivan

On Mon, May 28, 2012 at 9:44 PM, paulo louro <paulo_louro <at> msn.com> wrote:
> Hello Ivan,
>
> Thank you for the information, that was exactly what i was looking for.
>
> I have fun this Erbium REST engine and CoAP for Contiki, is that what you
> using?
>
> From what i can see this is all very recent stuff, its great to see people
> working on such protocol.
>
> I didn't manage to find much about IPSO profile, found this
> link http://www.ipso-alliance.org/wp-content/uploads/IPSO-Profile.pdf but
> the file doesn't exist.
> If you have any documentation on this and if it is not asking for much
> please forward it to me.
>
>
> Best Regards,
> Paulo Louro
>
>> Date: Mon, 28 May 2012 20:42:37 +0200
>> From: ivan.lapitski <at> gmail.com
>> To: contiki-developers <at> lists.sourceforge.net
>
>> Subject: Re: [Contiki-developers] Contiki Shell extension for Home
>> Automation?
>>
>> Hello Paulo
>>
>> Read on about coap and ipso-profile, it's more or less what you want.
>>
>> I would (actually already have) combine coap with a http-coap proxy,
>> and then use ajax to read/represent/control properties/nodes
>>
>> Best regards
>>
>> Ivan
>>
>> On Mon, May 28, 2012 at 8:14 PM, paulo louro <paulo_louro <at> msn.com> wrote:
>> > Hi Fabio and others
>> >
>> > Is there any protocol already implemented on Contiki?
>> >
>> > I'm thinking on implementing a simple SHELL protocol via UDP with the
>> > function of READ/WRITE properties. From there i will implement more
>> > commands
>> > and expand the protocol.
>> > But before i begin i'm looking for someáadviceáfor the Contiki experts.
>> > á :D
>
>> >
>> > This is more or less what i have in mind.
>> >
>> > Example of commands:
>> >
>> > list - shows a list of all properties on the root of the device
>> > tree - prints a tree layout of all groups and thereáproperties
>> > read [path.propertieName] - read a specificápropertyáof a group
>
>> > write [path.propertieName] - write to a specific property of a group
>> >
>> > Example of tree command:
>> >
>> >> tree
>> >
>> > NodeName [TestNode1]
>> > á á á|
>> > á á á|----> NodeInformation ------> [Name] ->áá[TestNode1]
>> > á á á| á á á á á á á á á á á á á á á á á|----> [Version] ->áá[Ver1.0]
>> > á á á| á á á á á á á á á á á á á á á á á|----> [LocalTime] ->
>> > [2012/05/28 -
>> > 20:14:45]
>> > áá á | á á á á á á á á á á á á á á á á á|----> Etc..........
>> > á á á|
>> > á á á|----> Sensors -----------> Digital
>> > á á á| á á á á á á á á á á á| á á á á á á á á |------> [Push Button 1]
>> > ---->
>> > [Status]
>> > á á á| á á á á á á á á á á á| á á á á á á á á |------> [Push Button 2]
>> > ---->
>> > [Status]
>> > á á á| á á á á á á á á á á á| á á á á á á á á |------> [Push Button 3]
>> > ---->
>> > [Status]
>> > á á á| á á á á á á á á á á á|
>> > á á á| á á á á á á á á á á á|---------> Analog
>> > á á á| á á á á á á á á á á á á á á á á á á á á |------> [Temperature]
>> > á á á| á á á á á á á á á á á á á á á á á á á á |------> [Battery Level]
>> > á á á| á á á á á á á á á á á á á á á á á á á á |------> [Light]
>> > á á á|
>> > á á á|----> Actuators ---------> Digital
>> > á á á| á á á á á á á á á á á| á á á á á á á á |------> [Relay á1] ---->
>> > [Status]
>> > á á á| á á á á á á á á á á á| á á á á á á á á | á á á á á á á á
>> > |---------->
>> > [Output]
>> > á á á| á á á á á á á á á á á| á á á á á á á á |
>> > á á á| á á á á á á á á á á á| á á á á á á á á |------> [Relayáá2] ---->
>> > [Status]
>> > á á á| á á á á á á á á á á á| á á á á á á á á | á á á á á á á á
>> > |---------->
>> > [Output]
>> > á á á| á á á á á á á á á á á| á á á á á á á á |
>> > á á á| á á á á á á á á á á á| á á á á á á á á |------> [Relayáá3] ---->
>> > [Status]
>> > á á á| á á á á á á á á á á á| á á á á á á á á | á á á á á á á á
>> > |---------->
>> > [Output]
>> > á á á| á á á á á á á á á á á| á á á á á á á á |------> [PWM 1] ----->
>> > [Status]
>> > á á á| á á á á á á á á á á á| á á á á á á á á á á á á á á á á
>> > á|----------->
>> > [Output]
>> > á á á| á á á á á á á á á á á|
>> > á á á| á á á á á á á á á á á|---------> Analog
>> > á á á| á á á á á á á á á á á á á á á á á á á á|------> [DAC 1] ------>
>> > [Status]
>> > á á á| á á á á á á á á á á á á á á á á á á á á á á á á á á á
>> > á|---------->
>> > [Output]
>> > á á á|
>> > á á á|----> Regulators --> PIDs ---> [PID 1] á--> [Input PV]
>> > (This.Sensors.Analog.Temperature)
>> > á á á| á á á á á á á á á á á á á á á á á á á á á á á á |-------> [P
>> > value]
>> > (0.10)
>> > á á á| á á á á á á á á á á á á á á á á á á á á á á á á |-------> [I
>> > value]
>> > (1.0)
>> > á á á| á á á á á á á á á á á á á á á á á á á á á á á á |-------> [D
>> > value]
>> > (0.0)
>> > á á á| á á á á á á á á á á á á á á á á á á á á á á á á |------->
>> > [Setpoint]
>> > (40.0)
>> > á á á| á á á á á á á á á á á á á á á á á á á á á á á á |------->
>> > [Output]
>> > (This.Actuators.Digital.PWM1)
>> > á á á| á á á á á á á á á á á á á á á á á á á á á á á á |------->
>
>> > [Description] "This PID control the heat element XPTO"
>> > á á á|
>> > á á á|
>> > á á á|----> Tasks----> DataChange/WhileTrue/OnTrue/OnFalse/etc etc
>> > etc....
>
>> >
>> >
>> >
>> > So if i want to read a temperature i can do:
>> >
>> >> readá TestNode1.Sensors.Analog.Temperature
>
>> >
>> > Or even read form TestNode2 via TestNode2
>> >
>> >> read TestNode2.Sensors.Analog.Temperature
>> >
>> >
>> >
>> > Best Regards,
>> > Paulo Louro
>> >
>> >
>> >
>> >> From: fabio.giovagnini <at> aurion-tech.com
>> >> To: contiki-developers <at> lists.sourceforge.net
>> >> Date: Mon, 28 May 2012 17:50:13 +0200
>> >> Subject: Re: [Contiki-developers] Contiki Shell extension for Home
>> >> Automation?
>> >
>> >>
>> >> Hi Paulo.
>> >> I think it is a good idea to open a discussion about which protocol
>> >> could be more useful.
>> >> We will keep in touch, ok?
>> >>
>> >> Best Regards
>> >>
>> >> Fabio Giovagnini
>> >>
>> >>
>> >>
>> >> Il giorno lun, 28/05/2012 alle 15.04 +0000, paulo louro ha scritto:
>> >> > Hello guys,
>> >> >
>> >> >
>> >> > I┤m wondering if someone has implemented an open source protocol on
>> >> > contiki for Home Automation.
>> >> >
>> >> >
>> >> > If NOT:
>> >> >
>> >> >
>> >> > I┤m thinking on making something very simple, similar to the contiki
>> >> > shell.
>> >> >
>> >> >
>> >> > What you guys think about?
>> >> >
>> >> >
>> >> > Regards,
>> >> > Paulo Louro
>> >> >
>> >> >
>> >> >
>> >> > ------------------------------------------------------------------------------
>> >> > Live Security Virtual Conference
>> >> > Exclusive live event will cover all the ways today's security and
>> >> > threat landscape has changed and how IT managers can respond.
>> >> > Discussions
>> >> > will include endpoint security, mobile security and the latest in
>> >> > malware
>> >> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> >> > _______________________________________________ Contiki-developers
>> >> > mailing list Contiki-developers <at> lists.sourceforge.net
>> >> > https://lists.sourceforge.net/lists/listinfo/contiki-developers
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Live Security Virtual Conference
>> >> Exclusive live event will cover all the ways today's security and
>> >> threat landscape has changed and how IT managers can respond.
>> >> Discussions
>> >> will include endpoint security, mobile security and the latest in
>> >> malware
>> >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> >> _______________________________________________
>> >> Contiki-developers mailing list
>> >> Contiki-developers <at> lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/contiki-developers
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Live Security Virtual Conference
>> > Exclusive live event will cover all the ways today's security and
>> > threat landscape has changed and how IT managers can respond.
>> > Discussions
>> > will include endpoint security, mobile security and the latest in
>> > malware
>> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> > _______________________________________________
>> > Contiki-developers mailing list
>> > Contiki-developers <at> lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/contiki-developers
>> >
>>
>>
>>
>> --
>> Ivan Lapitski
>> Crafoords võg 14
>
>> 11324 Stockholm
>> org-nr: 8412050539
>> +4673 988 25 15
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Contiki-developers mailing list
>> Contiki-developers <at> lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/contiki-developers
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Contiki-developers mailing list
> Contiki-developers <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/contiki-developers
>

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Contiki-developers mailing list
Contiki-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/contiki-developers

Gmane