6 thoughts on “TLM command processing in NE50-868 LP End Point”
I want to operate a small network with low power end points, which shall wake up every 10 minutes and then occasionally send digital telemetry or set digital outputs.
For the time settings I have chosen a network period of 5 sec und a periodic wake up of S341=120. Although the protocol user guide states that it is not possible to send information to an end point in such case, I found that the tlm commands are processed if sent shortly before the scheduled end point wake up.
What exactly is the timing requirement for sending data to a low power end point to ensure that these are properly received and processed? Could I perhaps synchronize the tlm commands with the network period?
Hi,
when
you send a message meanwhile module is in sleep mode, data is buffered
and sent after module wake up, so you may send data in each moment.
It depends also by wake up setting (at every n network period set).
Thank you Cosmin for your reply.
I found that if I set S341=n network periods, I can sent data to the end point at period n-1 and period n. Data sent at n-1 are processed in the subsequent wake-up period (e.g. response to a telemetry command). Data sent in period n are recieved but processed in the next wake-up period. Data or commands sent at any other period apparently do not arrive at the end point.
What would be a paractical approach for reliable bidirectional communication with end points in low power mode? (e.g. to synchronize with wake up times and or if wake up time is not known to send repeatedly same data / command to an end point at every net work period until response is received)
I found that if I set S341=n network periods, I can sent data to the
end point at period n-1 and period n. Data sent at n-1 are processed in
the subsequent wake-up period (e.g. response to a telemetry command).
Data sent in period n are recieved but processed in the next wake-up
period. Data or commands sent at any other period apparently do not
arrive at the end point.
What would be a paractical approach for
reliable bidirectional communication with end points in low power mode?
(e.g. to synchronize with wake up times and or if wake up time is not
known to send repeatedly same data / command to an end point at every
net work period until response is received)
Hi
could you tell me FW version?
Thanks
Dear Cosmin,
sorry for the late reply, but I was unavailable during last weeks. To come back to this post: the firmware version is.
I want to operate a small network with low power end points, which shall wake up every 10 minutes and then occasionally send digital telemetry or set digital outputs.
For the time settings I have chosen a network period of 5 sec und a periodic wake up of S341=120. Although the protocol user guide states that it is not possible to send information to an end point in such case, I found that the tlm commands are processed if sent shortly before the scheduled end point wake up.
What exactly is the timing requirement for sending data to a low power end point to ensure that these are properly received and processed? Could I perhaps synchronize the tlm commands with the network period?
Thank you Cosmin for your reply.
I found that if I set S341=n network periods, I can sent data to the end point at period n-1 and period n. Data sent at n-1 are processed in the subsequent wake-up period (e.g. response to a telemetry command). Data sent in period n are recieved but processed in the next wake-up period. Data or commands sent at any other period apparently do not arrive at the end point.
What would be a paractical approach for reliable bidirectional communication with end points in low power mode? (e.g. to synchronize with wake up times and or if wake up time is not known to send repeatedly same data / command to an end point at every net work period until response is received)
Dear Cosmin,
sorry for the late reply, but I was unavailable during last weeks. To come back to this post: the firmware version is.
GC.M0A.03.16
Regards
Reinhard