Getting acknowledgement only from single node which is 1st connected
Getting acknowledgement only from single node which is 1st connected
Okey, then you need to check what's the modification you have made.
Could send the project so that we can test here ? Please make sure that we can compile on a DK and can run it here. We prefer minimal code that can reproduce the issue.
Okay.
I am sending our project with modifications. Please find the attached zip file.
Note: Its name is OnOff Controller with 5 elements. Please configure Generic On Off Server model in 3rd
or 4th element.
We have used nRF52 development kit.
LED1 and LED2 are shows element3 and 4 status respectively
LED4 is for indication purpose only and blinks continuously
Please check at your side and suggest the possible solution.
Hi Anaya,
I did a test here and it seems that when connecting to one of the node as proxy node and then control another node, it worked most of the time, but some times it didn't send the set/get command to the remote node. It seems that the proxy node didn't managed to forward the data to the other node. Could you confirm that what you saw on your side ? It worked most of the time, and only occasionally you can't control the other node and got a timeout ?
I added another node running the stock light switch server example. And it worked just fine to control the other 2 nodes running your firmware.
There must be a modification or something that caused the issue. Do you have any activity on the node rather than just adding 3 server and 1 client ? Is there any background activity ? I saw that you have a timer with 500us interval, what is that for ? How long the processing for that last ? Wouldn't having a interrupt every 0.5ms quite short ?
Hi Hung,
Greetings!
I am colleague of Mrs. Anaya and I am working on it's nRF52832 development.
Please note below points.
1. We also have observed timeout
2. There is no activity apart from 3 servers and 1 client
3. However at every 3.3 seconds or 10 seconds client requests status from it's respective server and also while requesting it finds that client is busy with previous transmission then it cancels it and sends new request on next timeout.
Please confirm whether it will affect other models (OnOff Server) behavior?
4. Regarding 500uSec timer
4a. It is used for handling background activities like LED, Buzzer and flash persistence storage (status of device)
4b. Please note that in flash persistence storage activity, every time when there is change in device status, we tried to save it into flash.
4c. If needed we can increase it's time to couple milliseconds.
5. Can you please help us to understand how we can debug proxy functionalities? I mean how can we find out that proxy node has missed to forward data to other nodes?
Also please mention if there is anything we can do additional to resolve this issue.
Waiting for your positive reply.
Thanks to you and Nordic team for your quick, timely and great support.
Regards,
Dinesh
