Menu

DSTCP protocol problem

2020-05-30
2020-06-01
  • Alejandro Escallon

    Greetings,
    I am working with the IEEE 8500 nodes and when I require the voltage in some specific nodes, however when using the DSTCP protocol the result is not the same is shown in OpenDSSG report.
    For example I am using this codes to get the position in the list:

    data = sendTCP('42;')
    c=data.index('m1069169')
    

    The result is 2, then by usign the next code I require the voltage in that node.

    data = sendTCP('04;')
    c = data[2]
    

    The result is "-34857,56" and by checking the DSS report, we see that:
    "Bus ---Magnitude, kV (pu) --- Angle

    ELEMENT = "Line.LN5806919-1"
    E182724 -- - 7.2301 ( 1.004) / -40.3
    E182724 --- 7.3511 ( 1.021) /
    -160.8
    E182724 --- 7.3981 ( 1.028) / 80.5
    /
    M1069169 --- ** 7.2177** ( 1.003) /
    -40.3
    M1069169 --- 7.3409 ( 1.02) / -160.9
    M1069169 --- 7.3972 ( 1.027) /
    80.5
    This value is very different by the one obtained with DSTCP. I found that this problem is not only with the function "04;", but also with "20;" and other functions. Is it correct to assume that the bus name list is in the same order as the bus voltage list and can ask for the voltage in that node by this command?
    Thank you for your attention

     

    Last edit: Alejandro Escallon 2020-05-30
  • Alejandro Escallon

    I tried this, however; there was no effect. I requested some buses through the function 42 and now tried checking with the function 43 in order to get the position of specific nodes. The nodes that i require does not appear with function 43 but they appear with function 42. Any explanation for this?
    Thank you for your attention

     
    • Davis Montenegro

      Hi,

      I saw you are using Python, so just made an example for you. In this example I'm comparing the voltages at the nodes obtained using DSTCP and the report released by DSS-G. Everything seems to be OK.

      Best regards

      Davis

       

      Last edit: Davis Montenegro 2020-06-03

Log in to post a comment.