Hello,
After configuring an OpenPDC as a concentrator, 3 PMUs. I noticed the following error on the Remote System Console.
I also noticed that my system has 63 defined measurements, but the PPA code starts from 404. I am wondering if the error shown can decrease system operation or reach maximum size when adding new PMUs.
Any help to understand the erro on screen?
Hello luis_philipe_Morais,
The PPA measurement IDs are a coincidence. The error message indicates that the RNMSD_230_PM_01 adapter is overrunning a buffer for some reason. If you can find a matching entry in the ErrorLog.txt file, the stack trace would help to narrow down the location in the code and help explain where that buffer comes from. You can find the ErrorLog.txt file in the installation folder for openPDC.
Thanks,
Stephen
Hello StephenCWills, here is a printscreen from the log file. It appears to be happening for a while.
It’s having trouble parsing the StationName of the configuration cell in the CFG3 frame sent by the device. It suggests maybe that the device is not sending a valid CFG3 frame.
You are right. I was looking at UDP packets on Wireshark, and from all 3 PMUs on the database, I am receiving a [Malformed packet] error.
Stephen, could you help me understand if this error could impact OpenPDC performance and output stream?
When I look into output packets, I see no error, and all data has been read from the TSO remote PDC.
The openPDC would not be able to decode the data frames unless it receives a configuration frame that is not malformed. Based on your screenshot, it seems that the openPDC is receiving both CFG1 and CFG2 in addition to the malformed CFG3 frame which is unusual in my experience. But that probably explains why the malformed frame doesn’t have any impact on your output stream. openPDC is able to decode the data frames coming from the PMU because it is receiving the configuration data it needs from the CFG2 frame.
In terms of impact, this means that openPDC will not be using the information provided by the CFG3 frame at all, because it cannot be decoded. I suspect that you could turn off the CFG3 frame in the PMU and everything would likely work the same as it currently does. If your process does not rely on any data from the PMU that is exclusive to the CFG3 format–such as long station names or long channel names–then this error shouldn’t have any impact at all.
