Hi,

I encountered that the request-id of some protocols/elements goes into negative (I assume a integer overflow).
The related device answers with a "normal" positive request-id.
I assume, that the dataminer cannot match this response to the request it send, so the element goes into timeout.

In the past a restart of the element in the dataminer was a possible workaround to reset the ID.
Not sure if it is now not longer possible with the dataminer version (10.1.0.0-10049-CU1) we are using or if it is driver related.

So the question is, how can i prevent the usage of "unnormal" negative request-id's, to get rid of the root problem without a workaround? As I don't write protocols, is the request-id handling specified in the protocol or in the dataminer core software? Where do i need to look for this?

-> get-request

-> get-respond

Best Regards
Thomas