The JN5189DK6 I used is a Release Version: 2.6.12, and I fired the firmware to the JN5189 development board for testing. I tested according to the documentation and found that when the state moved from Occupied to the unoccupied state will not sleep, it will wake up frequently, it will consume a lot of power, which is not normal, why is that? Log as follows
hello @EduardoZamora
Thank you for your reply.
1、The version of JN-AN1246 is 2006
2、In order not to enter deep sleep, I modified bDeepSleep = FALSE in the code. When Delaying Unoccupied time to APP_OCCUPANCY_SENSOR_OCCUPIED_TO_UNOCCUPIED_DELAY (180s), it can't go to sleep and wake up frequently. See the attachment below
When I use the pre-built binary file, the phenomenon is different. When the time to delay Unoccupied reaches APP_OCCUPANCY_SENSOR_OCCUPIED_TO_UNOCCUPIED_DELAY (180s), it enters a deep sleep and does not wake up.See the attachment below
3、I used the universal expansion board SW1 to simulate occupancy sensors
The sensor project I'm going to work on doesn't require deep sleep. As for the above questions, please help me analyze which step is wrong
thank you
But still the above problem, for this phenomenon, I do not know the reason. when the wake timer 0 is trigger(occupied-> unoccupied 180s), why it often wakes up when PWR_eScheduleActivity(&sWake, u32WakeMs, vWakeCallBack) is call and enters sleep (wake timer 1).I don't want it to wake up too often.I want it to wake up after 97s according to this time
How do I change it?
hi @EduardoZamora thank you.
By default, this application should wake up by pressing SW1 once an Occupied to Unoccupied event has occurred (this delay is defined by APP_OCCUPANCY_SENSOR_UNOCCUPIED_TO_OCCUPIED_DELAY macro).
1、yes， it will wake up delay(this delay is defined by APP_OCCUPANCY_SENSOR_UNOCCUPIED_TO_OCCUPIED_DELAY macro).But then it won't sleep
2、ZLO_SYSTEM_MAX_REPORT_INTERVAL this macro I did not modify, the code in the default is not used this macro。
I just changed bDeepSleep = FALSE; Prevent occupation to Unoccupied event has occurred (this delay is defined by APP_OCCUPANCY_SENSOR_UNOCCUPIED_TO_OCCUPIED_DELAY macro) into a deep sleep. But when it goes to sleep, it wakes up frequently.
3、Do you have this problem when you run OccupancySensor on the development board？
There may be some configurations I didn't modify on that cause this problem
Hi,
I tested the pre-built binary file from the App Note folder and this was the behavior I observed after the device joined the network:
The device goes inactive after APP_OCCUPANCY_SENSOR_OCCUPIED_TO_UNOCCUPIED_DELAY, and it does not show activity until SW1 from Generic Expansion Board is pressed again.
By any chance, are you using the 'keep alive' feature of this application? Occupancy Sensor can be configured to be kept awake in 'keep-alive' mode by pressing the SW2 button on the Generic Expansion Board. For more information on this, please refer to JN-AN-1246 documentation, Section 4.3.5 Sleep Options.
Regards,
Eduardo.
hi @EduardoZamora thankyou
You tested the pre-built binary from the App Note folder and observed that the behavior was correct.It fell into a deep sleep
But I don't want it to go into a deep sleep. So i modified bDeepSleep = TRUE;
and then tested it again and it didn't go to sleep， I am not used 'keep alive' feature of this application.
I want it to go to sleep and wake up periodically
You can modify it like I did and then test it
Thank you very much.
