AVR Freaks

If you mean "endpoint" in data request parameters, then it is a logical address of the application inside the device. Device might run multiple logical applications running in parallel. One might handle main traffic, another one might handle network discovery and commissioning, yet another one might be handling over the air updates.

Yes, it is. Most applications are so simple that they only need one endpoint. For more complex applications you will need more.

Note that EP=0 is reserved for stack commands and should not be used in the application.

Well, if you like RFCs, endpoints are like ports in TCP or UDP.

Alex, if I develop my own application using the LwMesh SDK, let's say my application is for example, when I press a button on one of my nodes, a led blinks on my coordinator. If a write the code to do this task, Will I still be able to see the nodes on WSNMonitor ? Or WSNmonitor only works for WSNDemo application ? Thanks

Hum, Ok... I have to simulate a security system with the nodes, I mean, I have soldered a button on the nodes and my idea is when a press the button, let's say, on sensor 0x003 then led blue blinks on my coordinador ( I will solder pins and use a protoboard), when button is pressed on node 0x002, led orange blinks.. and goes on. But I would like to still be able to see the network topology on WsnMonitor, but for now is just an idea, I don't even know if it's possible to do this system. Thanks :D

Yes, I was think exactly this, doing a simple modification.. Although for my graduation project I just have to show that is possible to monitor an enviroment using wireless sensors, I would like to know how to do more complex application because I'm really enjoying this. Thanks

No, both algorithms remember discovered routes. Run-time optimizations in the native algorithm will lead to longer routes. Even with AODV it is not unusual to see 2-3 hops for devices located in one room. With native algorithm it gets even worse.

Over a long time AODV will stabilize on shorter routes and ideally no route discoveries will be done. Native on the other hand will always tend to "optimize" towards longer routes.

Hi Alex, I'm trying to develop that code that I told yo, but for now is just a sketch. I am trying to understand how to receive and process data. Let me tell you I have done and if you can, please tell me if I'm on the correct way.

on appInit(), I added this line:
#if APP_COORDINATOR
NWK_OpenEndpoint(APP_ENDPOINT_COORD, appDataIndCoord);
#endif //where APP_ENDPOINT_COORD defined as 2

and under the appDataInd, I created appDataIndCoord function, as follows:

static bool appDataIndCoord(NWK_DataInd_t *ind)
{
NWK_DataInd_t *msg = ind;

DDRC |= (1<<0)|(1<<1)|(1<<2)|(1<<3)|(1<<4)|(1<<5);

if(msg->srcAddr == 0x0001){
PORTC |= (1<<5);
_delay_ms(1000);
PORTC |= ~(1<<5);
}

return true;
}

This is the correct idea? or I understand wrong? Thanks a lot

'ind' already has type NWK_DataInd_t, there is no need for 'msg', just use ind->srcAddr.

Delaying for a second like this will work for a test, but should not be done in a real application.

I don't understand how you can break the hardware with reprogramming. Guaranteed Flash endurance is 10000 erase/write cycles. And it is much higher at a room temperature. I can not imagine anyone exceeding this limit. Even if you will reprogram your board every second, it will take about a week to reach that limit.

But the main idea is correct right? To open an endpoint with number 2 and write a new corresponding appDataInd for that EndPoint ?

Yes I think so, I have plans to do that, after finishing this project, but for now I have a deadline, so I have to hurry, and import this kind of hardware to my country is quite expensive, besides, I don't have time to wait them to arrive :( Thanks.. I will keep trying here

I did not understand any of this.

Please, Let me just say what I've done and if possible give your opinion. I have created another appSendData() function called appSendDataButton() and the only change was the Endpoint, I have setted as 2 (because on appDataIndCoord I am using another end point.. 2)

nwkDataReq.dstEndpoint = APP_ENDPOINT_COORD;
nwkDataReq.srcEndpoint = APP_ENDPOINT_COORD;

and then on the switch case that controls the state machine, I have added:

case APP_STATE_SEND:
appSendData();

#if APP_ROUTER
DDRA |= (0<<3); //set PortA Pin 3 as input
PORTA |= (1<<3); //set pull up resistor
if((PINA & (1<<3))==0) //where button is connected
appSendDataButton();
#endif

} break;

I think it's not the best way to implement this, since this way I have to press the button exactly when the code is on the if clause.. but even though is not working, but I don't know if it's problem on the code that sends or the code on de coordinator that receives... Thanks

Huum, yeah, I didn't understand very well about APP_STATE_WAIT_CONF, I mean, I didn't find yet exactly where it changes appState to a new state...
I will use macros from halGpio.h it's really better, and I will also take a look at the application that you suggested.
Can I send 2 differents NWK_DataReq_t structures inside appSendData?

I'm really trying to understand the state machine.. I know without understand it I will not be able to do what I want. But some parts I couldn't understand very well yet... like when appDataConf is called, and then the state is changed to APP_STATE_SENDING_DONE in the end. So, ok.. and then? the program should go back to appSendData where appState is changed to APP_STATE_WAIT_CONF later.. and then I can't see where appState is changed again to another state.. But it's not fait to ask explanation about this.. I shall study and find out... Thanks Alex

That's why I was not understanding.. I didn't know what time callback handler was for (SYS_TimerStart(&appDataSendingTimer);)..
it like when appState = APP_STATE_SENDING_DONE, then after a time appDataSendingTimer is called and the state is changed to APP_STATE_SEND again.. that's it ? Thanks

Yes, I could find it, but I couldn't guess what was it for, I'm not very advanced in microprogramming, I'm a beginner.. Thanks Alex.. I will study more and try to do the modifications

Please use code tags around your code, otherwise it is unreadable.

This is a very strange code. It will only sample button on the timer boundary. Usually button presses should be handled at the moment of pressing, not on some relatively long timer edge.

You also need to put braces properly in the conditions. Right now logic is not correct for what it supposed to do,

Alex, just for understand a bit more.. this function

it's kind of keep running in parelallel with the code checking every time if appState = APP_STATE_WAIT_SEND_TIMER ?

Ah.. I understand now :D.. now is working.. the 4 leds on coordinator are Toggling when I press the button on each node :D Thanks very much Alex...
IT's working, although I might find a better place to read the buttonState.. because sometimes I have to hold the button for it to send the frame.. or maybe is just because I haven't done any process of debounce on the button...