rsmp_schema 0.1.0 → 0.2.1

data/schemas/tlc/1.1/sxl.yaml

@@ -34,8 +34,8 @@ objects:
           NOTE! When dark according to configuration the controller is considered to be in use
       8:
         title: Not Connected
-    functional_position:
-    functional_state:
+    functional_position: not used (set to null)
+    functional_state: not used (set to null)
     alarms:
       A0001:
         description: |-
@@ -109,21 +109,44 @@ objects:
         arguments:
           signalgroupstatus:
             type: string
-            description: Signal group status as text field
-            range: "[text]"
+            description: |-
+              Signal group status as text field.
+              Each character represent the state of the signal group in consecutive order.
+              Signal group status is described in detail in the corresponding section.
+              - = Signal group is undefined/does not exist
             pattern: "^[a-hA-G0-9N-P]*$"
           cyclecounter:
             type: integer
-            description: Cycle counter
-            range: "[0-999]"
+            description: |-
+              Cycle counter.
+              Used for handling of coordination between TLC’s.
+              Is counted from 0 until it reaches the cycle time (See S0028).
+              
+              c = (b + o) mod t
+               
+              where c = cycle counter,
+              b = base cycle counter,
+              o = offset,
+              t = cycle time,
+              mod = modulo
+
+              See the coordination section for more information.
+            min: 0
+            max: 999
           basecyclecounter:
             type: integer
-            description: Base cycle counter
-            range: "[0-999]"
+            description: |-
+              Base cycle counter.
+              Used for handling of coordination between TLC’s.
+              Synchronized between all TLC’s in an active coordination.
+              See the coordination section for more information.
+            min: 0
+            max: 999
           stage:
             type: integer
             description: Current stage (isolated)
-            range: "[0-999]"
+            min: 0
+            max: 999
       S0002:
         description: |-
           Detector logic status.
@@ -132,8 +155,12 @@ objects:
         arguments:
           detectorlogicstatus:
             type: string
-            description: Detector logic status as text field
-            range: "[text]"
+            description: |-
+              Detector logic status as text field
+              Each character represent the state of the detector logic in consecutive order.
+              0 : Detector logic is not active
+              1 : Detector logic is active
+              - : Detector logic is undefined/does not exist
       S0003:
         description: |-
           Input status.
@@ -143,11 +170,14 @@ objects:
           inputstatus:
             type: string
             description: Input status as text field
-            range: "[text]"
           extendedinputstatus:
             type: string
-            description: Extended input status as text field
-            range: "[text]"
+            description: |-
+              Extended input status as text field
+              Each character represent the state of the detector logic in consecutive order.
+              0 : Detector logic is not active
+              1 : Detector logic is active
+              - : Detector logic is undefined/does not exist
       S0004:
         description: |-
           Output status.
@@ -157,11 +187,14 @@ objects:
           outputstatus:
             type: string
             description: Output status as text field
-            range: "[text]"
           extendedoutputstatus:
             type: string
-            description: Extended output status as text field
-            range: "[text]"
+            description: |-
+              Extended output status as text field
+              Each character represent the state of the detector logic in consecutive order.
+              0 : Detector logic is not active
+              1 : Detector logic is active
+              - : Detector logic is undefined/does not exist
       S0005:
         description: |-
           Traffic Light Controller starting.
@@ -187,7 +220,8 @@ objects:
           emergencystage:
             type: integer
             description: Number of emergency stage
-            range: "[1-255]"
+            min: 1
+            max: 255
       S0007:
         description: |-
           Controller switched on.
@@ -196,22 +230,20 @@ objects:
           During maintenance work the controller might be using dark mode (no output to the signal heads).
         arguments:
           intersection:
-            list: true
-            type: integer
+            type: integer_list
             description: |-
-              0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
-              Other value: Intersection number
-            range: "[0-255]"
+              Comma separated list of intersections which the status relates to, e.g. “1,2”.
+              Use “0” for all intersections of the TLC.
+            min: 0
+            max: 255
           status:
-            list: true
-            type: boolean
+            type: boolean_list
             description: |-
               False: Traffic Light Controller in dark mode
               True: Traffic Light Controller not in dark mode
           source:
             description: Source of the status change
-            list: true
-            type: string
+            type: string_list
             values:
               operator_panel: Operator panel 
               calendar_clock: Calendar/clock 
@@ -226,21 +258,19 @@ objects:
           Signal timings is controlled manually by service personnel using the operating panel of the controller.
         arguments:
           intersection:
-            list: true
-            type: integer
+            type: integer_list
             description: |-
-              0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
-              Other value: Intersection number
-            range: "[0-255]"
+              Comma separated list of intersections which the status relates to, e.g. “1,2”.
+              Use “0” for all intersections of the TLC.
+            min: 0
+            max: 255
           status:
-            list: true
-            type: boolean
+            type: boolean_list
             description: |-
               False: Manual control inactive
               True: Manual control active
           source:
-            list: true
-            type: string
+            type: string_list
             description: Source of the status change
             values:
               operator_panel: Operator panel 
@@ -256,21 +286,19 @@ objects:
           Usually only used in case normal detectors can't be used, e.g. during maintenance work.
         arguments:
           intersection:
-            list: true
-            type: integer
+            type: integer_list
             description: |-
-              0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
-              Other value: Intersection number
-            range: "[0-255]"
+              Comma separated list of intersections which the status relates to, e.g. “1,2”.
+              Use “0” for all intersections of the TLC.
+            min: 0
+            max: 255
           status:
-            list: true
-            type: boolean
+            type: boolean_list
             description: |-
               False: Fixed time control inactive
               True: Fixed time control active
           source:
-            list: true
-            type: string
+            type: string_list
             description: Source of the status change
             values:
               operator_panel: Operator panel 
@@ -286,21 +314,19 @@ objects:
           Used to determine if the controller is operating independently or operating with other controllers (coordination).
         arguments:
           intersection:
-            list: true
-            type: integer
+            type: integer_list
             description: |-
-              0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
-              Other value: Intersection number
-            range: "[0-255]"
+              Comma separated list of intersections which the status relates to, e.g. “1,2”.
+              Use “0” for all intersections of the TLC.
+            min: 0
+            max: 255
           status:
-            list: true
-            type: boolean
+            type: boolean_list
             description: |-
               False: Isolated control disabled
               True: Isolated control enabled (Vehicle actuated control or Fixed time control)
           source:
-            list: true
-            type: string
+            type: string_list
             description: Source of the status change
             values:
               operator_panel: Operator panel 
@@ -316,21 +342,19 @@ objects:
           Yellow flash may be used during a serious fault (depending on configuration) or maintenance work. It can also be manually set using M0001.
         arguments:
           intersection:
-            list: true
-            type: integer
+            type: integer_list
             description: |-
-              0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
-              Other value: Intersection number
-            range: "[0-255]"
+              Comma separated list of intersections which the status relates to, e.g. “1,2”.
+              Use “0” for all intersections of the TLC.
+            min: 0
+            max: 255
           status:
-            list: true
-            type: boolean
+            type: boolean_list
             description: |-
               False: Yellow flash disabled
               True: Yellow flash enabled
           source:
-            list: true
-            type: string
+            type: string_list
             description: Source of the status change
             values:
               operator_panel: Operator panel 
@@ -346,21 +370,19 @@ objects:
           All red can be manually set using the controllers operating panel during maintenance work.
         arguments:
           intersection:
-            list: true
-            type: integer
+            type: integer_list
             description: |-
-              0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
-              Other value: Intersection number
-            range: "[0-255]"
+              Comma separated list of intersections which the status relates to, e.g. “1,2”.
+              Use “0” for all intersections of the TLC.
+            min: 0
+            max: 255
           status:
-            list: true
-            type: boolean
+            type: boolean_list
             description: |-
               False: All red disabled
               True: All red enabled
           source:
-            list: true
-            type: string
+            type: string_list
             description: Source of the status change
             values:
               operator_panel: Operator panel 
@@ -376,19 +398,19 @@ objects:
           The "police key" is a external control switch present in some controllers that manually switches the controller to either dark mode or yellow flash.
         arguments:
           intersection:
-            list: true
-            type: integer
+            type: integer_list
             description: |-
-              0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
-              Other value: Intersection number
-            range: "[0-255]"
+              Comma separated list of intersections which the status relates to, e.g. “1,2”.
+              Use “0” for all intersections of the TLC.
+            min: 0
+            max: 255
           status:
-            list: true
-            type: integer
+            type: integer_list
             values:
               0: disabled
               1: dark mode
               2: yellow flash
+              3: all red
       S0014:
         description: |-
           Current time plan.
@@ -398,10 +420,10 @@ objects:
           status:
             type: integer
             description: Current time plan
-            range: "[1-255]"
+            min: 1
+            max: 255
           source:
-            list: true
-            type: string
+            type: string_list
             description: Source of the status change
             values:
               operator_panel: Operator panel 
@@ -420,10 +442,10 @@ objects:
           status:
             type: integer
             description: Current traffic situation
-            range: "[1-255]"
+            min: 1
+            max: 255
           source:
-            list: true
-            type: string
+            type: string_list
             description: Source of the status change
             values:
               operator_panel: Operator panel 
@@ -438,51 +460,54 @@ objects:
           Can be used by the management system to check the number of detector logics configured in the controller.
         arguments:
           number:
-            type: long
+            type: integer
             description: Number of detector logics
-            range: "[1-65025]"
+            min: 1
+            max: 65025
       S0017:
         description: |-
           Number of signal groups.
           Can be used for the management system to check the number of signal groups configured in the controller.
         arguments:
           number:
-            type: long
+            type: integer
             description: Number of signal groups
-            range: "[1-65025]"
+            min: 1
+            max: 65025
       S0018:
         description: |-
           Number of time plans
           Can be used for the management system to check the number of time plans configured in the controller.
         arguments:
           number:
-            type: long
+            type: integer
             description: Number of time plans (depreciated)
-            range: "[1-65025]"
+            min: 1
+            max: 65025
       S0019:
         description: |-
           Number of traffic situations.
           Can be used for the management system to check the number of traffic situations configured in the controller.
         arguments:
           number:
-            type: long
+            type: integer
             description: Number of traffic situations
-            range: "[1-65025]"
+            min: 1
+            max: 65025
       S0020:
         description: |-
           Control mode.
           Can be used for the management system to check the current control mode (startup, normal, standby, failure, test).
         arguments:
           intersection:
-            list: true
-            type: integer
+            type: integer_list
             description: |-
-              0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
-              Other value: Intersection number
-            range: "[0-255]"
+              Comma separated list of intersections which the status relates to, e.g. “1,2”.
+              Use “0” for all intersections of the TLC.
+            min: 0
+            max: 255
           controlmode:
-            list: true
-            type: string
+            type: string_list
             values:
               startup: Startup mode
               control: Normal control
@@ -498,7 +523,6 @@ objects:
           detectorlogics:
             type: string
             description: Manually set detector logics (1/0) as text field
-            range: "[text]"
             pattern: "^[01]*$"
       S0022:
         description: |-
@@ -509,7 +533,6 @@ objects:
           status:
             type: string
             description: Comma separated list of configured time plans. E.g. "1,2,3,5"
-            range: "[text]"
       S0023:
         description: |-
           Dynamic bands.
@@ -529,7 +552,6 @@ objects:
               
               E.g.
               pp-dd-ee,pp-dd-ee
-            range: "[text]"
             pattern: "(^$)|(^(?<item>(\\d{1,2})\\-\\d{1,2}-\\d{1,2})(,\\g<item>)*$)"
       S0024:
         description: |-
@@ -549,7 +571,6 @@ objects:
               
               E.g.
               pp-tt,pp-tt
-            range: "[text]"
             pattern: "^(\\d{1,2}\\-\\d{1,2})(?:,(\\d{1,2}\\-\\d{1,2}))*$"
       S0026:
         description: |-
@@ -577,7 +598,6 @@ objects:
               Each segment is separated with a comma
               E.g.
               d-t,d-t
-            range: "[text]"
       S0027:
         description: |-
           Time tables.
@@ -606,7 +626,6 @@ objects:
               
               E.g.
               t-o-h-m,t-o-h-m
-            range: "[text]"
       S0028:
         description: |-
           Cycle time.
@@ -625,7 +644,6 @@ objects:
               
               E.g.
               pp-tt,pp-tt
-            range: "[text]"
       S0029:
         description: |-
           Forced input status.
@@ -635,7 +653,6 @@ objects:
           status:
             type: string
             description: Forced input status as text field
-            range: "[text]"
       S0030:
         description: |-
           Forced output status.
@@ -645,7 +662,6 @@ objects:
           status:
             type: string
             description: Forced output status as text field
-            range: "[text]"
       S0031:
         description: |-
           Trigger level sensitivity for loop detector.
@@ -659,7 +675,105 @@ objects:
               dd=loop detector number
               ss=sensitivity value
               Each loop detector is separated with a comma. E.g.dd-ss,dd-ss.
-            range: "[text]"
+      S0032:
+        description: |-
+          Coordinated control
+          This status is used when coordination between traffic light controllers is active. Coordination is described in detail in the corresponding section
+          Please note that all values in this status uses comma-separated lists - one value for each intersection, e.g. “1,2” and “centralized,off”
+        arguments:
+          intersection:
+            type: integer_list
+            description: |-
+              Comma separated list of intersections which the status relates to, e.g. “1,2”.
+              Use “0” for all intersections of the TLC.
+            min: 0
+            max: 255
+          status:
+            type: string_list
+            description: |-
+              local: Local coordination
+              centralized: Coordination with synchronized clock
+              off: Coordination not active
+            values:
+              local:
+              centralized:
+              'off':
+          source:
+            description: Source of the status change
+            type: string_list
+            values:
+              operator_panel: Operator panel
+              calendar_clock: Calendar/clock
+              control_block: Control block
+              forced: Forced due to external command e.g. supervisor
+              startup: Set after startup mode
+              other: Other reason
+      S0033:
+        description: |-
+          Signal Priority Status
+          This status can be used to get updates about priority requests. For example, you can use it to know when priority requests are activated or cancelled.
+          A list of priorities is returned, referred to by their request ids. The same request id can appear only once.
+          All priorities are included in the list (not only the ones that have changed state since the last update). This is done regardless of whether the status is send in respond to a status request, or due to a status subscription, and also regardless of whether a status subscription uses an update interval, or send-on-change, or both.
+          If you subscribe using an update interval, you’re not guaranteed to get all intermediate states. To guarantee that, send-on-change must be used when subscribing.
+          To understand how this status relates to ETSI/J2735, please see the wiki.
+          All priorities are send on every status update, regardless of whether an interval, or sendOnChange (or both) is used.
+          When a priority reaches an end states (completed, timeout, rejected, cooldown or stale), it must be sent once on the next status update, then removed from the list.
+          A request always starts in the ‘received’ state. The following table shows the possible state transitions:
+        arguments:
+          status:
+            description: JSON array of priority status items
+            type: array
+            items:
+              r:
+                type: string
+                description: ID of the priority request
+              t:
+                type: timestamp
+                description: |-
+                  Timestamp, indicating when the priority last changed state.
+                  Format according to W3C XML dateTime with a resolution of 3 decimal places.
+                  All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z
+              s:
+                type: string
+                description: |-
+                  Current status of the priority request
+                values:
+                  received: A new priority request was received but has not yet been processed
+                  queued: The priority request has been queued for later activation
+                  activated: The priority was activated
+                  completed: The priority was cancelled as expected
+                  timeout: The priority has been queued for too long
+                  rejected: The priority request cannot be granted
+                  cooldown: A similar priority request means the priority request cannot be activated now
+                  stale: The priority has been active too long without cancellation, and was therefore removed
+              e:
+                type: integer
+                description: |-
+                  (Optional) Estimated green extension provided by the priority, in seconds
+                  Only used when state is ‘completed’.
+                optional: true
+                min: 0
+                max: 255
+              d:
+                type: integer
+                description: |-
+                  (Optional) Estimated red reduction provided by the priority, in seconds
+                  Only used when state is ‘completed’.
+                optional: true
+                min: 0
+                max: 255
+      S0034:
+        description: |-
+          Timeout for dynamic bands.
+          Time until a designated time plan is entered due to lost connection with the supervisor.
+          Disabled if set to '0'.
+          Used in conjunction with dynamic bands, M0014
+        arguments:
+          status:
+            type: integer
+            description: Timeout, in minutes
+            min: 0
+            max: 65535
       S0091:
         description: |-
           Operator logged in/out OP-panel.
@@ -692,7 +806,6 @@ objects:
           status:
             type: string
             description: Manufacturer, product name and version of traffic light controller
-            range: "[text]"
       S0096:
         description: |-
           Current date and time
@@ -701,29 +814,35 @@ objects:
           year:
             type: integer
             description: 'Year according to format YYYY. NOTE: UTC is used'
-            range: YYYY
+            min: 0
+            max: 9999
           month:
             type: integer
             description: 'Month (01-12) according to format MM. Note: UTC is used'
-            range: MM
+            min: 1
+            max: 12
           day:
             type: integer
             description: 'Day of month (01-31) according to format DD.  Note: UTC
               is used'
-            range: DD
+            min: 1
+            max: 31
           hour:
             type: integer
             description: 'Hour of day (00-23) according to format DD. Note: UTC is
               used'
-            range: HH
+            min: 0
+            max: 23
           minute:
             type: integer
             description: 'Minute (00-59) according to format MM. Note: UTC is used'
-            range: MM
+            min: 0
+            max: 59
           second:
             type: integer
             description: 'Second (00-59) according to format SS. Note: UTC is used'
-            range: SS
+            min: 0
+            max: 59
       S0097:
         description: |-
           Checksum of traffic parameters.
@@ -751,7 +870,6 @@ objects:
               
               Note:
               - The checksum should be calculated using the same data as used in S0098
-            range: "[text]"
           timestamp:
             type: timestamp
             description: Time stamp of the checksum. Format according to W3C XML dateTime
@@ -784,7 +902,6 @@ objects:
               Note:
               - There is no way to upload this binary file to the TLC using RSMP
               - The format of the binary file is not specified and is not expected to be compatible between suppliers
-            range: "[binary]"
           timestamp:
             type: timestamp
             description: |-
@@ -794,7 +911,6 @@ objects:
             description: |-
               Version information of the configuration. Contains basic information such as controller id, changes to config and other information.
               The format is not specified in detail.
-            range: "[text]"
       S0205:
         description: |-
           Traffic Counting: Number of vehicles.
@@ -805,13 +921,14 @@ objects:
             description: |-
               Time stamp for start of measuring. Format according to W3C XML dateTime with a resolution of 3 decimal places. All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z
           vehicles:
-            type: string
+            type: integer_list
             description: |-
               Number of vehicles.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-65535,...]"
+            min: 0
+            max: 65535
       S0206:
         description: |-
           Traffic Counting: Vehicle speed
@@ -824,13 +941,14 @@ objects:
               XML dateTime with a resolution of 3 decimal places. All time stamps
               in UTC. E.g. 2009-10-02T14:34:34.341Z
           speed:
-            type: string
+            type: integer_list
             description: |-
               Average speed in km/h (integer).
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-65535,...]"
+            min: 0
+            max: 65535
       S0207:
         description: |-
           Traffic Counting: Occupancy.
@@ -843,13 +961,14 @@ objects:
               XML dateTime with a resolution of 3 decimal places. All time stamps
               in UTC. E.g. 2009-10-02T14:34:34.341Z
           occupancy:
-            type: string
+            type: integer_list
             description: |-
               Occupancy in percent (%) (0-100)
               - Value expressed as an integer with a range of 0-100.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-100,...]"
+            min: 0
+            max: 100
       S0208:
         description: |-
           Traffic Counting: Number of vehicles of given classification.
@@ -862,77 +981,86 @@ objects:
               XML dateTime with a resolution of 3 decimal places. All time stamps
               in UTC. E.g. 2009-10-02T14:34:34.341Z
           P:
-            type: string
+            type: integer_list
             description: |-
               Number of cars.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-65535,...]"
+            min: 0
+            max: 65535
           PS:
-            type: string
+            type: integer_list
             description: |-
               Number of cars with trailers.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-65535,...]"
+            min: 0
+            max: 65535
           L:
-            type: string
+            type: integer_list
             description: |-
               Number of trucks.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-65535,...]"
+            min: 0
+            max: 65535
           LS:
-            type: string
+            type: integer_list
             description: |-
               Number of trucks with trailers.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-65535,...]"
+            min: 0
+            max: 65535
           B:
-            type: string
+            type: integer_list
             description: |-
               Number of busses.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-65535,...]"
+            min: 0
+            max: 65535
           SP:
-            type: string
+            type: integer_list
             description: |-
               Number of trams.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-65535,...]"
+            min: 0
+            max: 65535
           MC:
-            type: string
+            type: integer_list
             description: |-
               Number of motor cycles.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-65535,...]"
+            min: 0
+            max: 65535
           C:
-            type: string
+            type: integer_list
             description: |-
               Number of bicycles.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-65535,...]"
+            min: 0
+            max: 65535
           F:
-            type: string
+            type: integer_list
             description: |-
               Number of pedestrians.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
               - The value is set to “-1” if no data could be measured (e.g. detector fault)
-            range: "[0-65535,...]"
+            min: 0
+            max: 65535
     commands:
       M0001:
         description: |-
@@ -941,29 +1069,27 @@ objects:
           Requires security code 2.
         arguments:
           status:
-            list: true
+            type: string_list
             description: Set operating mode
-            type: string
             values:
               NormalControl: Normal Control
               YellowFlash: Enables yellow flash
               Dark: Enables dark mode
           securityCode:
-            list: true
+            type: string_list
             description: Security code 2
-            type: string
           timeout:
-            list: true
+            type: integer
             description: |-
               Time in minutes until controller automatically reverts to previous functional position.
               0=no automatic return
-            type: integer
             min: 0
             max: 1440
           intersection:
-            list: true
-            description: Intersection number
-            type: integer
+            type: integer_list
+            description: |-
+              Comma separated list of intersections which the status relates to, e.g. “1,2”.
+              Use “0” for all intersections of the TLC.
             min: 0
             max: 255
         command: setValue
@@ -983,11 +1109,11 @@ objects:
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
           timeplan:
             type: integer
             description: designation of time plan
-            range: "[1-255]"
+            min: 1
+            max: 255
         command: setPlan
       M0003:
         description: |-
@@ -1004,11 +1130,11 @@ objects:
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
           traficsituation:
             type: integer
             description: designation of traficsituation
-            range: "[1-255]"
+            min: 1
+            max: 255
         command: setTrafficSituation
       M0004:
         description: |-
@@ -1022,7 +1148,6 @@ objects:
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setRestart
       M0005:
         description: |-
@@ -1034,16 +1159,16 @@ objects:
           status:
             type: boolean
             description: |-
-              False: Activate emergency route
-              True: Deactivate emergency route
+              False: Deactivate emergency route
+              True: Activate emergency route
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
           emergencyroute:
             type: integer
             description: Number of emergency route
-            range: "[1-255]"
+            min: 1
+            max: 255
         command: setEmergency
       M0006:
         description: |-
@@ -1062,11 +1187,11 @@ objects:
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
           input:
             type: integer
             description: Number of Input
-            range: "[1-255]"
+            min: 1
+            max: 255
         command: setInput
       M0007:
         description: |-
@@ -1083,7 +1208,6 @@ objects:
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setFixedTime
       M0012:
         description: |-
@@ -1120,19 +1244,33 @@ objects:
               "5,4143,65:22,1,4"
               
               Such a message would order signal group 6,7,10,17,22 to green and signal group 5,11,24 to red
-            range: "[text]"
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setStart
       M0013:
         description: |-
-          Activate a series of inputs.
-          Set given inputs (1-255) of the controllers general purpose I/O to either true or false.
-          This command was introduced due to coordination requirements needing to set many inputs to true/false at the same time and M0006 being to slow to send a message for each input individually. With this command many inputs can be set to true/false at the same time using a single RSMP message.
-          Can be used for all types of input where the traffic light controller must react to external control. Typical usages are bus priority, coordination between traffic controllers, external control systems, and much more.
-          Requires security code 2
+          Activate a series of inputs
+
+          Set given inputs (1-255) of the controllers general purpose I/O to either true or false. This command was introduced due to coordination requirements needing to set many inputs to true/false at the same time and M0006 being to slow to send a message for each input individually. With this command many inputs can be set to true/false at the same time using a single command message. It can be used for all types of input where the traffic light controller must react to external control. Typical usages are bus priority, coordination between traffic controllers, external control systems, and much more.
+
+          Requires security code 2.
+
+          The parameter ‘status’ sets/unsets a block of 16 inputs at a time. It can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Format: [Offset];[Bits to set];[Bits to unset];…
+
+          - ‘Offset’ defines where the 16 inputs starts from
+          - ‘Bits to set’ defines which bit(s) to set. ‘0’ if unsed
+          - ‘Bits to unset’ defines which bit(s) to unset. ‘0’ if unused
+
+          Example 1: “3,4134,65” sets input 4,5,8,15 and unsets 3,9 - Input starts from no. 5 - “4134” is 1 0000 0010 0110 in binary, but since input starts from 3, it is shifted 3 bits, e.g. 1000 0001 0011 0000 which are bits 4,5,8,15 - “65” is 100 0001 in binary, but since input starts from 3, it is shifted 3 bits, e.g. 10 0000 1000 which are bits 3,9
+
+          Example 2: “12,1,4” sets input 12 and unsets 14 - Input starts from no. 12 - “1” is 1 in binary, but since input starts at 12 it is shifted 12 bits, e.g. 1 0000 0000 0000, which is bit 12 - “4” is 100 in binary, but since input starts at 12 it is shifted 12 bits, e.g. 100 0000 0000 0000, which is bit 14
+
+          And both these examples could be sent in the same message as: “3,4143,65;12,1,4”
+
+          Such a message would set input 4,5,8,12,15 and unset input 3,9,14
+
+          Example 3: “0,1,2” sets input 0 and unsets 1 - Input starts from 0 - “1” is 1 in binary, which is bit 0 - “2” is 10 in binary, which is bit 1
         arguments:
           status:
             type: string
@@ -1155,11 +1293,9 @@ objects:
               "5,4143:65:22,1,4"
               
               Such a message would activate input 6,7,10,17,22 and deactivate input 5,11,24
-            range: "[text]"
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setInput
       M0014:
         description: |-
@@ -1171,7 +1307,8 @@ objects:
           plan:
             type: integer
             description: Plan to be changed
-            range: "[0-255]"
+            min: 0
+            max: 255
           status:
             type: string
             description: |-
@@ -1184,11 +1321,9 @@ objects:
               
               E.g.
               dd-ee,dd-ee
-            range: "[text]"
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setCommands
       M0015:
         description: |-
@@ -1200,15 +1335,16 @@ objects:
           status:
             type: integer
             description: Set offset time in seconds
-            range: "[0-255]"
+            min: 0
+            max: 255
           plan:
             type: integer
             description: Time plan nr
-            range: "[0-255]"
+            min: 0
+            max: 255
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setOffset
       M0016:
         description: |-
@@ -1238,11 +1374,9 @@ objects:
               
               E.g.
               d-t,d-t
-            range: "[text]"
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setWeekTable
       M0017:
         description: |-
@@ -1273,11 +1407,9 @@ objects:
               
               E.g.
               t-o-h-m,t-o-h-m
-            range: "[text]"
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setTimeTable
       M0018:
         description: |-
@@ -1289,15 +1421,16 @@ objects:
           status:
             type: integer
             description: Set cycle time in seconds
-            range: "[1-255]"
+            min: 1
+            max: 255
           plan:
             type: integer
             description: Time plan nr
-            range: "[0-255]"
+            min: 0
+            max: 255
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setCycleTime
       M0019:
         description: |-
@@ -1309,16 +1442,16 @@ objects:
           status:
             type: boolean
             description: |-
-              False: Force input
-              True: Release input
+              False: Release input
+              True: Force input
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
           input:
             type: integer
             description: Number of Input
-            range: "[1-255]"
+            min: 1
+            max: 255
           inputValue:
             type: boolean
             description: |-
@@ -1340,11 +1473,11 @@ objects:
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
           output:
             type: integer
             description: Number of Output
-            range: "[1-255]"
+            min: 1
+            max: 255
           outputValue:
             type: boolean
             description: |-
@@ -1364,12 +1497,176 @@ objects:
               Loop detector trigger level sensitivity is written as dd-ss where:
               dd=loop detector number
               ss=sensitivity value
-            range: "[text]"
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setLevel
+      M0022:
+        description: |-
+          Request Signal Priority
+
+          Useful for bus priority or other type of priorities like emergency vehicles or groups of cyclists.
+
+          The benefit of using this message over activating inputs or detector logics is that you can specify a priority level, vehicle type and estimated time of arrival. You can also update or cancel the request, and use the corresponding status message to track the status of the request, including how much priority was actually given.
+
+          To understand how this command relates to ETSI/J2735, please see the wiki.
+
+          Activating signal priority is expected to provide more green time for a particular movement through the intersection, but the exact mechanism must typically be configured in the controller.
+
+          The movement to prioritize can be referenced in a number of ways, depending on what is configured in the controller, and in the system that sends priority requests. Either:
+
+          - Reference a signal group by setting ‘signalGroupId’. This method is simple, but will not allow you to have different priority mechanism for the same signal group, unless they can be distinguished by the vehicle type. For example, if you need to trigger different priorities depending on whether a bus goes straight or makes a turn for the same signal group, you need to use of the other referencing methods.
+          - Reference an input by setting ‘inputId’. This can be useful if you previously used inputs to activate priority. The input will not be activated, only the priority.
+          - Reference a connection by setting ‘connectionId’. A connection is a movement from a specific ingoing lane to a specific outgoing lane.
+          - Reference an intersection approach by setting ‘approachId’.
+          - Reference an ingoing lane by setting ‘laneInId’, and optionally also reference an outgoing lane by setting ‘laneOutId’.
+
+          Referencing attributes that are not used must be left out, rather than set to null or empty strings. This includes:
+
+          - signalGroupId
+          - inputId
+          - connectionId
+          - approachId
+          - laneInId
+          - laneOutId
+
+          Referencing attributes are only used when initiating a request. When updating or cancelling the request, the request is identified by its requestId, and no referencing attributes are allowed.
+
+          You initiate a priority request with type set to ‘new’. You must provide a request id that uniquely identifies the request on the controller. It can be a randomly generated UUID (universally unique identifier), or it can be constructed by combining e.g. a vehicle id and some other identifier. When updating or cancelling a request, you must pass the same request id again.
+
+          Providing ETA (estimated time of arrival) when initiating a request is optional, but can help the controller plan ahead in cases where you’re able to send the request before the vehicle arrives at the intersection. You’re allowed to initiate the request without an ETA and provide it in a later request update. But providing the ETA when initiating the request is recommended, since it will give the controller more time to plan ahead.
+
+          Like ETA, providing a vehicle type is optional, but can help the controller decide how to best handle the request.
+
+          The priority level provides a way to indicate the relative importance of the request compared to other requests. For example, emergency vehicles or delayed buses could be given a higher priority level.
+
+          If the ETA changes before the priority is cancelled, or you want to change the priority level, you can send another request message with type set to ‘update’. The vehicle type cannot be changed.
+
+          When you send a priority request, it will be processed to decide if it’s possible to activate the requested priority.
+
+          If the request is accepted, the priority can either be activated immediately, or if another priority is currently active, it can be queued for later activation.
+
+          If the priority cannot be accepted the request is rejected. Cooldown is a specific type of rejection, which means that s similar request has just completed, and some time needs to pass before a similar request can be activated.
+
+          When a request is queued, it is expected to become activated later, but in case too long passes without activation, the controller is expected to time out the request.
+
+          Once a priority is activated, you’re excepted to cancel it as soon as there’s no need for it anymore, typically when the vehicle has passed the intersection. You cancel a request by sending a request passing the existing request id setting the type to ‘cancel’.
+
+          If a request is never cancelled, the controller is expected to remove the priority at some point, but until then the priority might block requests in other direction which is why you should always cancel a priority when it’s not needed anymore.
+        arguments:
+          requestId:
+            type: string
+            description: A string that uniquely identifies the request on the controller
+          signalGroupId:
+            type: string
+            optional: true
+            description: (Optional) ID of a signal group component.
+          inputId:
+            type: integer
+            optional: true
+            description: (Optional) ID of an input, using the same numbering scheme as M0006
+            min: 0
+            max: 255
+          connectionId:
+            type: integer
+            optional: true
+            description: (Optional) ID of a connection, connecting an ingoing and an outgoing lane
+            min: 0
+            max: 255
+          approachId:
+            type: integer
+            optional: true
+            description: (Optional) ID of an intersection approach
+            min: 0
+            max: 16
+          laneInId:
+            type: integer
+            optional: true
+            description: (Optional) ID of an ingoing lane
+            min: 0
+            max: 255
+          laneOutId:
+            type: integer
+            optional: true
+            description: (Optional) ID of an outgoing lane
+            min: 0
+            max: 255
+          priorityId:
+            type: integer
+            optional: true
+            description: (Optional) ID of a priority
+            min: 0
+            max: 255
+          type:
+            type: string
+            description: |-
+              new: New priority request
+              update: Update to existing priority request
+              cancel: Cancel an existing priority
+            values:
+              new:
+              update:
+              cancel:
+          level:
+            type: integer
+            description: |-
+              0: Lowest, 14: Highest
+            min: 0
+            max: 14
+          eta:
+            type: integer
+            optional: true
+            description: (Optional) Estimated time of arrival to the intersection, in seconds
+            min: 0
+            max: 255
+          vehicleType:
+            type: string
+            optional: true
+            description: |-
+              (Optional) Vehicle type
+
+              pedestrian: Pedestrians
+              bicycle: Bicycles
+              motorcycle: Motorcycles
+              car: Passenger vehicle
+              bus: Bus used for public transport
+              lightTruck: Light truck
+              heavyTruck: Heavy truck
+              tram: Trams used for Public transport
+              emergency: Police, fire or ambulance
+              safetyCar: For e.g. escort vehicles
+              specialTransport: For e.g. heavy load
+              other: Other type of vehicle
+            values:
+              pedestrian:
+              bicycle:
+              motorcycle:
+              car:
+              bus:
+              lightTruck:
+              heavyTruck:
+              tram:
+              emergency:
+              safetyCar:
+              specialTransport:
+              other:
+        command: requestPriority
+      M0023:
+        description: |-
+          Set timeout for dynamic bands
+          Switch to a designated time plan if this timeout is reached due to lost connection with the supervisor.
+          Disable by setting timeout to '0'.
+          Used in conjunction with dynamic bands, M0014
+        arguments:
+          status:
+            type: integer
+            min: 0
+            max: 65535
+            description: Timeout, in minutes
+          securityCode:
+            type: string
+            description: Security code 2
+        command: setTimeout
       M0103:
         description: |-
           Set security code.
@@ -1384,11 +1681,9 @@ objects:
           oldSecurityCode:
             type: string
             description: Previous security code
-            range: "[text]"
           newSecurityCode:
             type: string
             description: New security code
-            range: "[text]"
         command: setSecurityCode
       M0104:
         description: |-
@@ -1399,43 +1694,48 @@ objects:
           securityCode:
             type: string
             description: Security code 1
-            range: "[text]"
           year:
             type: integer
             description: |-
               Changes internal clock. Note: UTC is used
               Year according to YYYY
-            range: "[YYYY]"
+            min: 0
+            max: 9999
           month:
             type: integer
             description: |-
               Changes internal clock. Note: UTC is used
               Month according to MM (01-12)
-            range: "[MM]"
+            min: 1
+            max: 12
           day:
             type: integer
             description: |-
               Changes internal clock. Note: UTC is used
               Day in month according to DD (01-31)
-            range: "[DD]"
+            min: 1
+            max: 31
           hour:
             type: integer
             description: |-
               Changes internal clock. Note: UTC is used
               Hour according to HH (00-23)
-            range: "[HH]"
+            min: 0
+            max: 23
           minute:
             type: integer
             description: |-
               Changes internal clock. Note: UTC is used
               Minute according to MM (00-59)
-            range: "[MM]"
+            min: 0
+            max: 59
           second:
             type: integer
             description: |-
               Changes internal clock. Note: UTC is used
               Second according to SS (00-59)
-            range: "[SS]"
+            min: 0
+            max: 59
         command: setDate
   Signal group:
     description:
@@ -1452,7 +1752,8 @@ objects:
           timeplan:
             type: integer
             description: Current time plan
-            range: "[designation]"
+            min: 1
+            max: 255
       A0101:
         description: |-
           Pushbutton error.
@@ -1495,17 +1796,17 @@ objects:
           Time-of-Green / Time-of-Red.
           Provides predicted signal timings of green and red for each signal group. Max, min and likely time to green and red.
         arguments:
-          minToGEstimate   :
+          minToGEstimate:
             type: timestamp
             description: |-
               Time stamp for the minimum time for the signal group to go to green. If the signal group is green, it is the minimum time for the next green.
               Format according to W3C XML dateTime with a resolution of 3 decimal places. All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z
-          maxToGEstimate   :
+          maxToGEstimate:
             type: timestamp
             description: |-
               Time stamp for the maximum time for the signal group to go to green. If the signal group is green, it is the maximum time for the next green.
               Format according to W3C XML dateTime with a resolution of 3 decimal places. All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z
-          likelyToGEstimate   :
+          likelyToGEstimate:
             type: timestamp
             description: |-
               Time stamp for the most likely time for the signal group to go to green. If the signal group is green, it is the most likely time for the next green.
@@ -1513,8 +1814,9 @@ objects:
           ToGConfidence:
             type: integer
             description: Confidence of the likelyToGEstimate. 0-100%
-            range: "[0-100]"
-          minToREstimate   :
+            min: 0
+            max: 100
+          minToREstimate:
             type: timestamp
             description: |-
               Time stamp for the minimum time for the signal group to go to red. If the signal group is red, it is the minimum time for the next red.
@@ -1524,7 +1826,7 @@ objects:
             description: |-
               Time stamp for the maximum time for the signal group to go to red. If the signal group is red, it is the maximum time for the next red.
               Format according to W3C XML dateTime with a resolution of 3 decimal places. All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z
-          likelyToREstimate   :
+          likelyToREstimate:
             type: timestamp
             description: |-
               Time stamp for the most likely time for the signal group to go to red. If the signal group is red, it is the most likely time for the next red.
@@ -1532,7 +1834,8 @@ objects:
           ToRConfidence:
             type: integer
             description: Confidence of the likelyToREstimate. 0-100%
-            range: "[0-100]"
+            min: 0
+            max: 100
     commands:
       M0010:
         description: |-
@@ -1549,7 +1852,6 @@ objects:
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setStart
       M0011:
         description: |-
@@ -1566,7 +1868,6 @@ objects:
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
         command: setStop
   Detector logic:
     description:
@@ -1581,7 +1882,6 @@ objects:
           detector:
             type: string
             description: Designation of the detector (hardware)
-            range: "[designation]"
           type:
             type: string
             description: Type of detector
@@ -1592,8 +1892,8 @@ objects:
             type: string
             description: Detector forced on/off while detector error
             values:
-              'on': ''
-              'off': ''
+              'on':    # on/off must be quoted, otherwise they are converted to true/false
+              'off':
           manual:
             type: boolean
             description: Manually controlled detector logic (True/False)
@@ -1608,7 +1908,6 @@ objects:
           detector:
             type: string
             description: Designation of the detector (hardware)
-            range: "[designation]"
           type:
             type: string
             description: Type of detector.
@@ -1631,6 +1930,61 @@ objects:
               always_off: no detection during predefined max time
               always_on: detection constantly on during predefined max time
               intermittent: intermittent logic fault (flutter)
+      A0303:
+        description: |-
+          Serious detector error (hardware).
+          Is a “major fault” defined according to 3.8 i EN12675 which causes the controller to switch to a “failure mode” according to 3.6 in EN12675.
+        priority: 3
+        category: D
+        arguments:
+          detector:
+            type: string
+            description: Designation of the detector (hardware)
+          type:
+            type: string
+            description: Type of detector.
+            values:
+              loop: Inductive detector loop
+              input: External input
+          errormode:
+            type: string
+            description: Detector forced on/off while detector error
+            # note that on and off must be quoted, otherwise they are parsed as true and false
+            values: ['on','off']
+          manual:
+            type: boolean
+            description: Manually controlled detector logic (True/False)
+      A0304:
+        description: |-
+          Serious detector error (logic error).
+          For instance; detector continuously on or off during an extended time.
+          Is a “major fault” defined according to 3.8 i EN12675 which causes the controller to switch to a “failure mode” according to 3.6 in EN12675
+        priority: 3
+        category: D
+        arguments:
+          detector:
+            type: string
+            description: Designation of the detector (hardware)
+          type:
+            type: string
+            description: Type of detector.
+            values:
+              loop: Inductive detector loop
+              input: External input
+          errormode:
+            type: string
+            description: Detector forced on/off while detector error
+            values: ['on','off']
+          manual:
+            type: boolean
+            description: Manually controlled detector logic (True/False)
+          logicerror:
+            type: string
+            description: Type of logic error
+            values:
+              always_off: no detection during predefined max time
+              always_on: detection constantly on during predefined max time
+              intermittent: intermittent logic fault (flutter)
     statuses:
       S0201:
         description: |-
@@ -1643,10 +1997,11 @@ objects:
               XML dateTime with a resolution of 3 decimal places. All time stamps
               in UTC. E.g. 2009-10-02T14:34:34.341Z
           vehicles:
-            type: long
+            type: integer
             description: Number of vehicles on a given detector logic (since last
               update)
-            range: "[number]"
+            min: 0
+            max: 65535
       S0202:
         description: |-
           Traffic Counting: Vehicle speed.
@@ -1661,7 +2016,7 @@ objects:
           speed:
             type: integer
             description: Average speed in km/h
-            range: "[speed]"
+            min: 0
       S0203:
         description: |-
           Traffic Counting: Occupancy.
@@ -1676,7 +2031,8 @@ objects:
           occupancy:
             type: integer
             description: Occupancy in percent (0-100%)
-            range: "[0-100]"
+            min: 0
+            max: 100
       S0204:
         description: |-
           Traffic Counting: Number of vehicles of given classification.
@@ -1689,41 +2045,41 @@ objects:
               XML dateTime with a resolution of 3 decimal places. All time stamps
               in UTC. E.g. 2009-10-02T14:34:34.341Z
           P:
-            type: long
+            type: integer
             description: Number of cars
-            range: "[number]"
+            min: 0
           PS:
-            type: long
+            type: integer
             description: Number of cars with trailers
-            range: "[number]"
+            min: 0
           L:
-            type: long
+            type: integer
             description: Number of trucks
-            range: "[number]"
+            min: 0
           LS:
-            type: long
+            type: integer
             description: Number of trucks with trailers
-            range: "[number]"
+            min: 0
           B:
-            type: long
+            type: integer
             description: Number of busses
-            range: "[number]"
+            min: 0
           SP:
-            type: long
+            type: integer
             description: Number of trams
-            range: "[number]"
+            min: 0
           MC:
-            type: long
+            type: integer
             description: Number of motor cycles
-            range: "[number]"
+            min: 0
           C:
-            type: long
+            type: integer
             description: Number of bicycles
-            range: "[number]"
+            min: 0
           F:
-            type: long
+            type: integer
             description: Number of pedestrians
-            range: "[number]"
+            min: 0
     commands:
       M0008:
         description: |-
@@ -1740,7 +2096,6 @@ objects:
           securityCode:
             type: string
             description: Security code 2
-            range: "[text]"
           mode:
             type: boolean
             description: |-