iicsys / pypmu

pyPMU - Python implementation of the IEEE C37.118 synchrophasor standard
BSD 3-Clause "New" or "Revised" License
62 stars 46 forks source link

Multiple messages in one DATA FRAME #8

Open RadevicI opened 6 years ago

RadevicI commented 6 years ago

Hi again,

I am facing another problem with multiple messages in one data frame. What is the reason for that? Why each message sent with send_data method is not in separate data frame? multiple_messages

Thanks.

Best Regards,

Isidora

sstevan commented 6 years ago

Hey @RadevicI,

Please share ConfigFrame that you are using in your script with us. It will help us to debug data frame from above.

RadevicI commented 6 years ago

Hi Stefan,

This is the ConfigFrame I am using:

pmu = Pmu(ip="131.180.164.101", port=4701, pmu_id=1, data_rate=50, set_timestamp=False)

pmu = Pmu(ip="131.180.164.99", port=4701, pmu_id=1, data_rate=50, set_timestamp=False)

pmu.logger.setLevel("INFO")

cfg = ConfigFrame2(pmu_id,  # PMU_ID
                   1000000,  # TIME_BASE
                   1,  # Number of PMUs included in data frame
                   "sensorPMU",  # Station name
                   pmu_id,  # Data-stream ID(s)
                   (False, True, True, True),  # Data format - POLAR; PH - REAL; AN - REAL; FREQ - REAL;
                   3,  # Number of phasors
                   1,  # Number of analog values
                   1,  # Number of digital status words
                    ["VA", "VB", "VC", "ANALOG1", "BREAKER 1 STATUS",
                    "BREAKER 2 STATUS", "BREAKER 3 STATUS", "BREAKER 4 STATUS", "BREAKER 5 STATUS",
                    "BREAKER 6 STATUS", "BREAKER 7 STATUS", "BREAKER 8 STATUS", "BREAKER 9 STATUS",
                    "BREAKER A STATUS", "BREAKER B STATUS", "BREAKER C STATUS", "BREAKER D STATUS",
                    "BREAKER E STATUS", "BREAKER F STATUS", "BREAKER G STATUS"],  # Channel Names
                   [(1, "v"), (1, "v"), (1, "v")],  # Conversion factor for phasor channels - (float representation, not important)
                   [(1, "pow")],  # Conversion factor for analog channels
                   [(0x0000, 0xffff)],  # Mask words for digital status words
                   data_rate,  # Nominal frequency
                   1,  # Configuration change count
                   50)  # Rate of phasor data transmission)

pmu.set_configuration(cfg)
pmu.set_header("sensorPMU here!")

pmu.run()
print("pmu started")
RadevicI commented 6 years ago

Also, I would like to share what I am getting in Wireshark when I am sending the data to the local PDC computer. The length of the data frames is big and varies (I would expect 110 all the time - one message per frame, now there are multiple). Finally it increases to 1230 and communication stops (Data transmission OFF).
pdc_pypmu

I hope you know the reason for this :)

Thanks

Isidora

sstevan commented 6 years ago

@RadevicI ConfigFrame looks fine, can you please upload pcap file?

Have you tried to test with PMU Connection tester or openPDC? Does the same thing happen?

RadevicI commented 6 years ago

Hi @sstevan,

I have tried to test with PMU Connection Tester. And the same issue is happening. I am sending to you pcap file. PyPMU.zip

Best regards,

Isidora

RadevicI commented 6 years ago

Additionally,

I would like to share what I have noticed after running pyPMU module. The example is tinyPMU.py, but the same happens when I run my code with pyPMU implemented inside. Namely, after running tinuPMU.py there is a huge increase in CPU load. Additionally, each time I connect with PMU Connection Tester, new process start without terminating the previous. I am sending the screen shots showing these issues: with pmu connection tester multiple_tinypmu

Thanks :)

sstevan commented 6 years ago

@RadevicI,

Looks like the FRAMESIZE is causing troubles in this case. The frame is much bigger than the actual frame size specified.

However, I am not able to reproduce this on my setup.

Can you send us the pickled version of your data frames, or maybe the script with fixed values that you are trying to send?

Regarding performance issues, we already discussed this in #5 and it will be fixed in next version.

caldweln commented 4 years ago

@sstevan @RadevicI I know this is somewhat an old issue... but why is multiple C37 dataframes in a TCP packet considered an issue here? This looks to me like the TCP layer efficiently encapsuating several PDUs (C37 Dataframes) into one TCP segment.