On element startup, if it does not get any response from the device, say the device is powered off, is there a way to ensure that once communications is achieved that the protocol starts polling from scratch with all timers reset to ensure all groups are polled. For example, if there is parameter that is only polled every 6 hours and upon element startup the device was offline, then when the element initially attempted to poll this parameter it timed out but then a few minutes later the device came online. In this case I would want the protocol to reset all the timers to ensure all parameters are polled at least once. Another way to look at is that the element does not start any polling timers or buffering up polling commands until communications to the device has been achieved. I hope this is clear.
Thanks
Hi Jeff, I believe the particular feature of interest is Slowpoll for you. A similar question has been asked (How does slow poll work? - DataMiner Dojo). Perhaps the answer is what you're searching for?
An extract from the DataMiner Help:
When an element is in a timeout state, the DMA can force it to go into so-called slow poll mode. While the element is in that special poll mode, the DMA will not send any commands to the element. Instead, it will just send a protocol-dependent ping command at regular intervals. As soon as the element responds to that ping command, the DMA will start polling the element the normal way again.
When making the implementation yourself, it is important to configure the ping group correctly as explained on Protocol thread run-time errors: use cases - DataMiner Dojo