| Author |
Message |
|
|
 Posted: Jun 27, 2012 - 10:29 AM |
|
Joined: Jun 25, 2012
Posts: 11
|
|
Hi!
In an example of WSNDemo ED falls asleep with *CS_END_DEVICE_SLEEP_PERIOD* period. In my program it should work always. Whether it is possible to off the sleep mode at ED? |
|
|
| |
|
|
|
|
|
|
Posted: Jun 27, 2012 - 05:57 PM |
|
Joined: Apr 15, 2009
Posts: 4861
Location: San Jose, CA
|
|
| CS_END_DEVICE_SLEEP_PERIOD defines for how long ED will be asleep. If you need ED to be constantly on, just don't call ZDO_SleepReq(). |
_________________
The opinions and views expressed by me on this forum are my own and do not represent my employer or anyone else that I’m affiliated with.
|
| |
|
|
|
|
|
|
Posted: Jun 28, 2012 - 04:48 AM |
|
Joined: Jun 25, 2012
Posts: 11
|
|
Thanks for answer.
When I change WsnDemo by comment call ZDO_SleepReq() ED really to be constantly on, but after 10-20 seconds ED is disappear from WSNmonitor.
Code:
case SLEEPPING_DEVICE_STATE:
{
//visualizeSleep();
appDeviceState = WAITING_DEVICE_STATE;
//ZDO_SleepReq(&sleepReq);
}
I think it is happen because ED stopped send data request to coordinator. |
|
|
| |
|
|
|
|
|
|
Posted: Jun 28, 2012 - 04:55 AM |
|
Joined: Apr 15, 2009
Posts: 4861
Location: San Jose, CA
|
|
| You need to replace sleep timer by a regular timer. Right now device gets stuck in a WAITING_DEVICE_STATE and as name suggests it waits. You need to replicate what happens when device wake up. |
_________________
The opinions and views expressed by me on this forum are my own and do not represent my employer or anyone else that I’m affiliated with.
|
| |
|
|
|
|
|
|
Posted: Jun 28, 2012 - 05:53 AM |
|
Joined: Jun 25, 2012
Posts: 11
|
|
Ok, i'll try to do this.
Another question. If I want to send data from coordinator to many ED in broadcast mode without data request from ED have I got information about ED in WSNmonitor? Or I need to send data req from ED to coordinator to see info in WSNmonitor? |
|
|
| |
|
|
|
|
|
|
Posted: Jun 28, 2012 - 05:55 AM |
|
Joined: Apr 15, 2009
Posts: 4861
Location: San Jose, CA
|
|
| Currently application is designed in a way that each device reports its own information, but you are free to change the application at any time. |
_________________
The opinions and views expressed by me on this forum are my own and do not represent my employer or anyone else that I’m affiliated with.
|
| |
|
|
|
|
|
|
Posted: Jun 29, 2012 - 01:50 AM |
|
Joined: Jun 25, 2012
Posts: 11
|
|
I found this strings in pwm.h file:
Code:
typedef enum
00097 {
00098 /* Base address of T/C1 PWM related registers */
00099 PWM_UNIT_1 = 0x80,
00100 /* Base address of T/C3 PWM related registers */
00101 PWM_UNIT_3 = 0x90
00102 } HAL_PwmUnit_t;
This mean that i can use Bitcloud's function to control pwm only T/C1 and T/C3? What about another timers? |
|
|
| |
|
|
|
|
|
|
Posted: Jun 29, 2012 - 01:53 AM |
|
Joined: Apr 15, 2009
Posts: 4861
Location: San Jose, CA
|
|
Write your own code, or extend existing one.
Also, create new topic for unrelated questions. |
_________________
The opinions and views expressed by me on this forum are my own and do not represent my employer or anyone else that I’m affiliated with.
|
| |
|
|
|
|
|
FAQ
Search
Register
Log in to check your private messages
Log in
Maximize
RSS
