We currently make a call to get the CPU info, and then CPU state. On S7-300, the PDUR is limited to 240, so CPU info is fragmented into a few frames. If we make a call to get CPU state immediately after getting CPU info, then controller throws error since we haven't completely retrieving CPU info yet. v1.0.1.1 bypasses the error, and allows operations to continue, but it's merely a patch. Ultimately, we should intelligently stitch up these fragmented responses.
We currently make a call to get the CPU info, and then CPU state. On S7-300, the PDUR is limited to 240, so CPU info is fragmented into a few frames. If we make a call to get CPU state immediately after getting CPU info, then controller throws error since we haven't completely retrieving CPU info yet. v1.0.1.1 bypasses the error, and allows operations to continue, but it's merely a patch. Ultimately, we should intelligently stitch up these fragmented responses.