Details
Description
when using Read Request service with high data volume (more than 2 DPM fragments) the handling of packet header field "ulId" is not implemented as defined in DPM Manual.
firmware expects ulId to be increased when application requests second fragment but if application increases ulId for third packet this is not accepted by firmware
Attachments
Issue Links
- relates to
-
PSPNM-478 sometimes no Read confirmation received in application
- Closed