Flicker Summary Measurements are incorrect

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • Priority: Major
    • wd36
    • Affects Version/s: CSD03/PR03
    • Component/s: None
    • None
    • Environment:

      Marty Burns PR03 Comments

    • Hide

      Correct the specification at line 1165 Table 16-3, Figure 16-3, and the schema to describe the type of both Flicker ST and Flicker ST (and the appropriate schema names) as float.

      The description should be "A measurement of [long term][short term] Rapid Voltage Change. The actual periods for measurement are defined in the measurement protocol documents."

      Also table 16-2 line 1159, change "A described in" to "As described in" and "61000+2003}" to "61000-2003"

      Show
      Correct the specification at line 1165 Table 16-3, Figure 16-3, and the schema to describe the type of both Flicker ST and Flicker ST (and the appropriate schema names) as float. The description should be "A measurement of [long term] [short term] Rapid Voltage Change. The actual periods for measurement are defined in the measurement protocol documents." Also table 16-2 line 1159, change "A described in" to "As described in" and "61000+2003}" to "61000-2003"

      See http://lists.oasis-open.org/archives/emix-comment/201108/msg00002.html for full original email.

      All,

      Below please find comments on the definition of flicker measurements. As indicated by Erich, there is no such thing as a flicker count as related in Table 16-3 Power Quality Indicators (line 1165). Rather, these are floating point dimensionless quantities interpreted roughly as a figure of merit with a value of 1.0 that value where 50% of people would notice it in an incandescent light bulb.

      It is suggested that the definitions be modified accordingly.

            Assignee:
            Toby Considine (Inactive)
            Reporter:
            William Cox (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: