My modules pass time in sleep and wake up period constantly. On a applicative event, one of my modules wake up and transmit a time related information. The problem happen when one of the receiving module wake up, he process a old frame with an old information of time.
As I see, the SNAP kernel process is stop when passing in sleep with a reception message queue filled. At wake up the process is completed and i have to deal with a old message. At this time i can't know if the message is correct or just a old.
There is some mechanisms to use for the reception process like the use of RPC_SENT hook with getInfo(9) for the transmission? I'm try to ensure that there's no frame saved in queue before going to sleep. It's possible to have acces at the information of the reception queue to avoid this problem?
I'm running on the firmware : RF200_AES128_debug_SnapV2.4.22.sfi
As I see, the SNAP kernel process is stop when passing in sleep with a reception message queue filled. At wake up the process is completed and i have to deal with a old message. At this time i can't know if the message is correct or just a old.
There is some mechanisms to use for the reception process like the use of RPC_SENT hook with getInfo(9) for the transmission? I'm try to ensure that there's no frame saved in queue before going to sleep. It's possible to have acces at the information of the reception queue to avoid this problem?
I'm running on the firmware : RF200_AES128_debug_SnapV2.4.22.sfi
Comment