rsmp_schemer 0.3.2 → 0.4.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (218) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +23 -22
  3. data/lib/rsmp_schemer/version.rb +3 -3
  4. data/rsmp_schemer.gemspec +3 -3
  5. data/schemas/core_3.1.2/schema/core/alarm.json +8 -4
  6. data/schemas/core_3.1.2/spec/core/alarm_spec.rb +15 -0
  7. data/schemas/core_3.1.3/Gemfile.lock +20 -20
  8. data/schemas/core_3.1.3/schema/core/alarm.json +8 -4
  9. data/schemas/core_3.1.3/schema/core/core.json +0 -1
  10. data/schemas/core_3.1.3/schema/core/rsmp.json +0 -9
  11. data/schemas/core_3.1.3/spec/core/alarm_spec.rb +20 -7
  12. data/schemas/core_3.1.3/spec/core/command_request_spec.rb +3 -6
  13. data/schemas/core_3.1.3/spec/core/command_response_spec.rb +1 -43
  14. data/schemas/core_3.1.3/spec/core/status_request_spec.rb +4 -8
  15. data/schemas/core_3.1.3/spec/core/status_response_spec.rb +13 -8
  16. data/schemas/core_3.1.3/spec/core/status_subscribe_spec.rb +4 -8
  17. data/schemas/core_3.1.3/spec/core/status_unsubscribe_spec.rb +4 -8
  18. data/schemas/core_3.1.3/spec/core/status_update_spec.rb +4 -8
  19. data/schemas/core_3.1.3/spec/schemer_helper.rb +19 -17
  20. data/schemas/core_3.1.4/.gitignore +1 -0
  21. data/schemas/core_3.1.4/schema/core/alarm.json +8 -4
  22. data/schemas/core_3.1.4/spec/core/alarm_spec.rb +15 -0
  23. data/schemas/core_3.1.4/spec/core/version_spec.rb +3 -2
  24. data/schemas/core_3.1.5/.gitignore +1 -0
  25. data/schemas/core_3.1.5/schema/core/alarm.json +40 -41
  26. data/schemas/core_3.1.5/schema/core/alarm_issue.json +44 -0
  27. data/schemas/core_3.1.5/schema/core/alarm_suspend_resume.json +3 -0
  28. data/schemas/core_3.1.5/schema/core/alarm_suspended_resumed.json +47 -0
  29. data/schemas/core_3.1.5/schema/core/command_response.json +1 -1
  30. data/schemas/core_3.1.5/schema/core/status_response.json +1 -1
  31. data/schemas/core_3.1.5/schema/core/status_update.json +1 -1
  32. data/schemas/core_3.1.5/spec/core/alarm_issue_spec.rb +299 -0
  33. data/schemas/core_3.1.5/spec/core/alarm_resume_spec.rb +93 -0
  34. data/schemas/core_3.1.5/spec/core/alarm_resumed_spec.rb +277 -0
  35. data/schemas/core_3.1.5/spec/core/alarm_suspend_spec.rb +93 -0
  36. data/schemas/core_3.1.5/spec/core/alarm_suspended_spec.rb +277 -0
  37. data/schemas/core_3.1.5/spec/core/version_spec.rb +3 -2
  38. data/schemas/tlc_1.0.15/Gemfile.lock +17 -17
  39. data/schemas/tlc_1.0.15/README.md +7 -0
  40. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0001.json +1 -1
  41. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0002.json +1 -1
  42. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0003.json +1 -1
  43. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0004.json +1 -1
  44. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0005.json +1 -1
  45. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0006.json +1 -1
  46. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0007.json +1 -1
  47. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0008.json +1 -1
  48. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0009.json +1 -1
  49. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0010.json +1 -1
  50. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0101.json +1 -1
  51. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0201.json +1 -1
  52. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0202.json +1 -1
  53. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0301.json +1 -1
  54. data/schemas/tlc_1.0.15/schema/tlc/alarms/A0302.json +1 -1
  55. data/schemas/tlc_1.0.15/schema/tlc/commands/M0002.json +1 -1
  56. data/schemas/tlc_1.0.15/schema/tlc/commands/M0003.json +1 -1
  57. data/schemas/tlc_1.0.15/schema/tlc/commands/M0004.json +1 -1
  58. data/schemas/tlc_1.0.15/schema/tlc/commands/M0005.json +1 -1
  59. data/schemas/tlc_1.0.15/schema/tlc/commands/M0006.json +1 -1
  60. data/schemas/tlc_1.0.15/schema/tlc/commands/M0007.json +1 -1
  61. data/schemas/tlc_1.0.15/schema/tlc/commands/M0008.json +1 -1
  62. data/schemas/tlc_1.0.15/schema/tlc/commands/M0010.json +1 -1
  63. data/schemas/tlc_1.0.15/schema/tlc/commands/M0011.json +1 -1
  64. data/schemas/tlc_1.0.15/schema/tlc/commands/M0012.json +1 -1
  65. data/schemas/tlc_1.0.15/schema/tlc/commands/M0013.json +1 -1
  66. data/schemas/tlc_1.0.15/schema/tlc/commands/M0014.json +1 -1
  67. data/schemas/tlc_1.0.15/schema/tlc/commands/M0015.json +1 -1
  68. data/schemas/tlc_1.0.15/schema/tlc/commands/M0016.json +1 -1
  69. data/schemas/tlc_1.0.15/schema/tlc/commands/M0017.json +1 -1
  70. data/schemas/tlc_1.0.15/schema/tlc/commands/M0018.json +1 -1
  71. data/schemas/tlc_1.0.15/schema/tlc/commands/M0019.json +1 -1
  72. data/schemas/tlc_1.0.15/schema/tlc/commands/M0020.json +1 -1
  73. data/schemas/tlc_1.0.15/schema/tlc/commands/M0021.json +1 -1
  74. data/schemas/tlc_1.0.15/schema/tlc/commands/M0103.json +1 -1
  75. data/schemas/tlc_1.0.15/schema/tlc/commands/M0104.json +1 -1
  76. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0001.json +1 -1
  77. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0002.json +1 -1
  78. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0003.json +1 -1
  79. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0004.json +1 -1
  80. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0005.json +1 -1
  81. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0006.json +1 -1
  82. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0007.json +1 -1
  83. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0008.json +1 -1
  84. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0009.json +1 -1
  85. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0010.json +1 -1
  86. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0011.json +1 -1
  87. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0012.json +1 -1
  88. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0013.json +1 -1
  89. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0014.json +1 -1
  90. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0015.json +1 -1
  91. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0016.json +1 -1
  92. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0017.json +1 -1
  93. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0018.json +1 -1
  94. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0019.json +1 -1
  95. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0020.json +1 -1
  96. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0021.json +1 -1
  97. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0022.json +1 -1
  98. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0023.json +1 -1
  99. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0024.json +1 -1
  100. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0025.json +1 -1
  101. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0026.json +1 -1
  102. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0027.json +1 -1
  103. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0028.json +2 -2
  104. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0029.json +1 -1
  105. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0030.json +1 -1
  106. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0031.json +1 -1
  107. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0091.json +1 -1
  108. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0092.json +1 -1
  109. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0095.json +1 -1
  110. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0096.json +1 -1
  111. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0097.json +1 -1
  112. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0098.json +2 -2
  113. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0201.json +1 -1
  114. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0202.json +2 -2
  115. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0203.json +2 -2
  116. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0204.json +2 -2
  117. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0205.json +3 -3
  118. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0206.json +3 -3
  119. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0207.json +3 -3
  120. data/schemas/tlc_1.0.15/schema/tlc/statuses/S0208.json +11 -11
  121. data/schemas/tlc_1.0.15/schema/tlc/sxl.yaml +1655 -0
  122. metadata +20 -105
  123. data/schemas/core_3.1.2/examples/validate.rb +0 -35
  124. data/schemas/core_3.1.3/examples/validate.rb +0 -32
  125. data/schemas/core_3.1.3/schema/core/aggregated_status_request.json +0 -9
  126. data/schemas/core_3.1.3/schema/tlc/alarms/A0001.json +0 -7
  127. data/schemas/core_3.1.3/schema/tlc/alarms/A0002.json +0 -7
  128. data/schemas/core_3.1.3/schema/tlc/alarms/A0003.json +0 -7
  129. data/schemas/core_3.1.3/schema/tlc/alarms/A0004.json +0 -7
  130. data/schemas/core_3.1.3/schema/tlc/alarms/A0005.json +0 -7
  131. data/schemas/core_3.1.3/schema/tlc/alarms/A0006.json +0 -7
  132. data/schemas/core_3.1.3/schema/tlc/alarms/A0007.json +0 -7
  133. data/schemas/core_3.1.3/schema/tlc/alarms/A0008.json +0 -19
  134. data/schemas/core_3.1.3/schema/tlc/alarms/A0009.json +0 -7
  135. data/schemas/core_3.1.3/schema/tlc/alarms/A0101.json +0 -7
  136. data/schemas/core_3.1.3/schema/tlc/alarms/A0201.json +0 -20
  137. data/schemas/core_3.1.3/schema/tlc/alarms/A0202.json +0 -20
  138. data/schemas/core_3.1.3/schema/tlc/alarms/A0301.json +0 -49
  139. data/schemas/core_3.1.3/schema/tlc/alarms/A0302.json +0 -59
  140. data/schemas/core_3.1.3/schema/tlc/alarms/alarms.json +0 -68
  141. data/schemas/core_3.1.3/schema/tlc/commands/M0001.json +0 -48
  142. data/schemas/core_3.1.3/schema/tlc/commands/M0002.json +0 -39
  143. data/schemas/core_3.1.3/schema/tlc/commands/M0003.json +0 -39
  144. data/schemas/core_3.1.3/schema/tlc/commands/M0004.json +0 -30
  145. data/schemas/core_3.1.3/schema/tlc/commands/M0005.json +0 -39
  146. data/schemas/core_3.1.3/schema/tlc/commands/M0006.json +0 -39
  147. data/schemas/core_3.1.3/schema/tlc/commands/M0007.json +0 -30
  148. data/schemas/core_3.1.3/schema/tlc/commands/M0008.json +0 -40
  149. data/schemas/core_3.1.3/schema/tlc/commands/M0010.json +0 -30
  150. data/schemas/core_3.1.3/schema/tlc/commands/M0011.json +0 -30
  151. data/schemas/core_3.1.3/schema/tlc/commands/M0012.json +0 -29
  152. data/schemas/core_3.1.3/schema/tlc/commands/M0013.json +0 -1
  153. data/schemas/core_3.1.3/schema/tlc/commands/M0014.json +0 -38
  154. data/schemas/core_3.1.3/schema/tlc/commands/M0015.json +0 -38
  155. data/schemas/core_3.1.3/schema/tlc/commands/M0016.json +0 -29
  156. data/schemas/core_3.1.3/schema/tlc/commands/M0017.json +0 -29
  157. data/schemas/core_3.1.3/schema/tlc/commands/M0018.json +0 -38
  158. data/schemas/core_3.1.3/schema/tlc/commands/M0019.json +0 -49
  159. data/schemas/core_3.1.3/schema/tlc/commands/M0020.json +0 -49
  160. data/schemas/core_3.1.3/schema/tlc/commands/M0021.json +0 -1
  161. data/schemas/core_3.1.3/schema/tlc/commands/M0103.json +0 -39
  162. data/schemas/core_3.1.3/schema/tlc/commands/M0104.json +0 -1
  163. data/schemas/core_3.1.3/schema/tlc/commands/command_requests.json +0 -7
  164. data/schemas/core_3.1.3/schema/tlc/commands/command_responses.json +0 -7
  165. data/schemas/core_3.1.3/schema/tlc/commands/commands.json +0 -97
  166. data/schemas/core_3.1.3/schema/tlc/statuses/S0001.json +0 -45
  167. data/schemas/core_3.1.3/schema/tlc/statuses/S0002.json +0 -17
  168. data/schemas/core_3.1.3/schema/tlc/statuses/S0003.json +0 -26
  169. data/schemas/core_3.1.3/schema/tlc/statuses/S0004.json +0 -26
  170. data/schemas/core_3.1.3/schema/tlc/statuses/S0005.json +0 -18
  171. data/schemas/core_3.1.3/schema/tlc/statuses/S0006.json +0 -27
  172. data/schemas/core_3.1.3/schema/tlc/statuses/S0007.json +0 -26
  173. data/schemas/core_3.1.3/schema/tlc/statuses/S0008.json +0 -26
  174. data/schemas/core_3.1.3/schema/tlc/statuses/S0009.json +0 -26
  175. data/schemas/core_3.1.3/schema/tlc/statuses/S0010.json +0 -26
  176. data/schemas/core_3.1.3/schema/tlc/statuses/S0011.json +0 -26
  177. data/schemas/core_3.1.3/schema/tlc/statuses/S0012.json +0 -26
  178. data/schemas/core_3.1.3/schema/tlc/statuses/S0013.json +0 -27
  179. data/schemas/core_3.1.3/schema/tlc/statuses/S0014.json +0 -17
  180. data/schemas/core_3.1.3/schema/tlc/statuses/S0015.json +0 -17
  181. data/schemas/core_3.1.3/schema/tlc/statuses/S0016.json +0 -17
  182. data/schemas/core_3.1.3/schema/tlc/statuses/S0017.json +0 -17
  183. data/schemas/core_3.1.3/schema/tlc/statuses/S0018.json +0 -17
  184. data/schemas/core_3.1.3/schema/tlc/statuses/S0019.json +0 -17
  185. data/schemas/core_3.1.3/schema/tlc/statuses/S0020.json +0 -27
  186. data/schemas/core_3.1.3/schema/tlc/statuses/S0021.json +0 -18
  187. data/schemas/core_3.1.3/schema/tlc/statuses/S0022.json +0 -17
  188. data/schemas/core_3.1.3/schema/tlc/statuses/S0023.json +0 -18
  189. data/schemas/core_3.1.3/schema/tlc/statuses/S0024.json +0 -18
  190. data/schemas/core_3.1.3/schema/tlc/statuses/S0025.json +0 -80
  191. data/schemas/core_3.1.3/schema/tlc/statuses/S0026.json +0 -18
  192. data/schemas/core_3.1.3/schema/tlc/statuses/S0027.json +0 -18
  193. data/schemas/core_3.1.3/schema/tlc/statuses/S0028.json +0 -18
  194. data/schemas/core_3.1.3/schema/tlc/statuses/S0029.json +0 -17
  195. data/schemas/core_3.1.3/schema/tlc/statuses/S0030.json +0 -1
  196. data/schemas/core_3.1.3/schema/tlc/statuses/S0031.json +0 -1
  197. data/schemas/core_3.1.3/schema/tlc/statuses/S0091.json +0 -27
  198. data/schemas/core_3.1.3/schema/tlc/statuses/S0092.json +0 -27
  199. data/schemas/core_3.1.3/schema/tlc/statuses/S0095.json +0 -17
  200. data/schemas/core_3.1.3/schema/tlc/statuses/S0096.json +0 -68
  201. data/schemas/core_3.1.3/schema/tlc/statuses/S0097.json +0 -26
  202. data/schemas/core_3.1.3/schema/tlc/statuses/S0201.json +0 -26
  203. data/schemas/core_3.1.3/schema/tlc/statuses/S0202.json +0 -26
  204. data/schemas/core_3.1.3/schema/tlc/statuses/S0203.json +0 -26
  205. data/schemas/core_3.1.3/schema/tlc/statuses/S0204.json +0 -98
  206. data/schemas/core_3.1.3/schema/tlc/statuses/S0205.json +0 -26
  207. data/schemas/core_3.1.3/schema/tlc/statuses/S0206.json +0 -26
  208. data/schemas/core_3.1.3/schema/tlc/statuses/S0207.json +0 -26
  209. data/schemas/core_3.1.3/schema/tlc/statuses/S0208.json +0 -98
  210. data/schemas/core_3.1.3/schema/tlc/statuses/statuses.json +0 -181
  211. data/schemas/core_3.1.3/schema/tlc/sxl.json +0 -24
  212. data/schemas/core_3.1.3/spec/tlc/M0001_spec.rb +0 -67
  213. data/schemas/core_3.1.3/spec/tlc/S0007_spec.rb +0 -233
  214. data/schemas/core_3.1.4/examples/validate.rb +0 -35
  215. data/schemas/core_3.1.4/spec/core/alarm_request_spec.rb +0 -72
  216. data/schemas/core_3.1.5/examples/validate.rb +0 -35
  217. data/schemas/core_3.1.5/spec/core/alarm_request_spec.rb +0 -72
  218. data/schemas/core_3.1.5/spec/core/alarm_spec.rb +0 -298
@@ -68,3 +68,10 @@ This is useful when developing the schema, to ensure it validates correctly.
68
68
  $ bundle # install gems
69
69
  $ bundle exec rspec # run rspec tests
70
70
  ```
71
+
72
+ ## Schema generation
73
+ Note that the SLX JSON schemas are generated automatically from an authoritative YAML file, using using the 'convert' command of rsmp gem.
74
+
75
+ The JSON schema files should not be edited by hand. Instead, edit the YAML source and regenerate the schema files.
76
+
77
+ For the TLC SXL the YAML source file is schema/tlc/sxl.yaml.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Serious hardware error\n\nIs 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."
4
+ "description" : "Serious hardware error.\nIs 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."
5
5
  }
6
6
  ]
7
7
  }
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Less serious hardware error\n\nIs a \"minor fault\" defined according to 3.11 in EN12675."
4
+ "description" : "Less serious hardware error.\nIs a \"minor fault\" defined according to 3.11 in EN12675."
5
5
  }
6
6
  ]
7
7
  }
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Serious configuration error\n\nIs a \"major fault\" defined according to 3.8 in EN12675 which causes the controller to switch to a \"failure mode\" according to 3.6 in EN12675."
4
+ "description" : "Serious configuration error.\nIs a \"major fault\" defined according to 3.8 in EN12675 which causes the controller to switch to a \"failure mode\" according to 3.6 in EN12675."
5
5
  }
6
6
  ]
7
7
  }
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Less serious configuration error\n\nIs a \"minor fault\" defined according to 3.11 in EN12675."
4
+ "description" : "Less serious configuration error.\nIs a \"minor fault\" defined according to 3.11 in EN12675."
5
5
  }
6
6
  ]
7
7
  }
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Communication error between traffic light controllers / synchronisation error\n\nIs a \"minor fault\" defined according to 3.11 in EN12675."
4
+ "description" : "Communication error between traffic light controllers / synchronisation error.\nIs a \"minor fault\" defined according to 3.11 in EN12675."
5
5
  }
6
6
  ]
7
7
  }
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Safety error\n\nIs a \"major fault\" defined according to 3.8 in EN12675 which causes the controller to switch to a \"failure mode\" according to 3.6 in EN12675."
4
+ "description" : "Safety error\nIs a \"major fault\" defined according to 3.8 in EN12675 which causes the controller to switch to a \"failure mode\" according to 3.6 in EN12675."
5
5
  }
6
6
  ]
7
7
  }
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Communication error between one or multiple traffic light controllers and central control system.\n\nUsed for communication errors with the central system. Includes NTP connection loss if the TLC is configured to use NTP.\n\nIs a \"minor fault\" defined according to 3.11 in EN12675."
4
+ "description" : "Communication error between one or multiple traffic light controllers and central control system.\nUsed for communication errors with the central system. Includes NTP connection loss if the TLC is configured to use NTP.\nIs a \"minor fault\" defined according to 3.11 in EN12675."
5
5
  }
6
6
  ]
7
7
  }
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Dead lock error\n\nUsed for dead lock errors.\n\nFor instance; a signal group has requested green but is unable to switch due to a conflicting signal group for an extended period of time. At some point the request times out and the controller goes failure mode. The cause for this error is due to configuration errors or external sources.\n\nIs a \"major fault\" defined according to 3.8 in EN12675 which causes the controller to switch to a \"failure mode\" according to 3.6 in EN12675.\n",
4
+ "description" : "Dead lock error.\nUsed for dead lock errors.\nFor instance; a signal group has requested green but is unable to switch due to a conflicting signal group for an extended period of time. At some point the request times out and the controller goes failure mode. The cause for this error is due to configuration errors or external sources.\nIs a \"major fault\" defined according to 3.8 in EN12675 which causes the controller to switch to a \"failure mode\" according to 3.6 in EN12675.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Other error\n\nUsed for other errors not covered by any other alarm type\n\nIs a \"minor fault\" defined according to 3.11 in EN12675."
4
+ "description" : "Other error.\nUsed for other errors not covered by any other alarm type\nIs a \"minor fault\" defined according to 3.11 in EN12675."
5
5
  }
6
6
  ]
7
7
  }
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Door open\n\nUsed for open door (room or cabinet)."
4
+ "description" : "Door open.\nUsed for open door (room or cabinet)."
5
5
  }
6
6
  ]
7
7
  }
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Pushbutton error\n\nUsed for push buttons"
4
+ "description" : "Pushbutton error.\nUsed for push buttons."
5
5
  }
6
6
  ]
7
7
  }
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Serious lamp error\nUsed for lamp errors\nIs a \"major fault\" defined according to 3.8 in EN12675 which causes the controller to switch to a \"failure mode\" according to 3.6 in EN12675.",
4
+ "description" : "Serious lamp error.\nUsed for lamp errors.\nIs a \"major fault\" defined according to 3.8 in EN12675 which causes the controller to switch to a \"failure mode\" according to 3.6 in EN12675.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Less serious lamp error\nUsed for lamp errors\nIs a \"minor fault\" defined according to 3.11 in EN12675.",
4
+ "description" : "Less serious lamp error.\nUsed for lamp errors.\nIs a \"minor fault\" defined according to 3.11 in EN12675.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Detector error (hardware)\n\nIs a \"minor fault\" defined according to 3.11 in EN12675.",
4
+ "description" : "Detector error (hardware).\nIs a \"minor fault\" defined according to 3.11 in EN12675.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Detector error (logic error)\n\nFor instance; detector continuously on or off during an extended time.\n\nIs a \"minor fault\" defined according to 3.11 in EN12675.",
4
+ "description" : "Detector error (logic error).\nFor instance; detector continuously on or off during an extended time.\nIs a \"minor fault\" defined according to 3.11 in EN12675.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Sets current time plan\n\nChange of traffic program of the traffic light controller.\n\nTypical usages is scenario based control where change of program is used to change signal timings etc.\n\nThis command changes the signal timings for optimal traffic flow.\n\nRequires security code 2",
4
+ "description" : "Sets current time plan.\nChange of traffic program of the traffic light controller.\nTypical usages is scenario based control where change of program is used to change signal timings etc.\nThis command changes the signal timings for optimal traffic flow.\nRequires security code 2",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Sets traffic situation the controller uses.\n\nUsed for area-based control where a command can be sent to a master traffic light controller about which predefined traffic situation to use (1-255).\n\nTraffic situation is a concept used to divide multiple TLC's into areas and sub-areas. The traffic situation gives the possibility to change the TLC sub-area dynamically depending on the time of day and the traffic flow. Depending on the traffic situation each TLC selects the time plan dynamically.\n\nRequires security code 2",
4
+ "description" : "Sets traffic situation the controller uses.\nUsed for area-based control where a command can be sent to a master traffic light controller about which predefined traffic situation to use (1-255).\nTraffic situation is a concept used to divide multiple TLC's into areas and sub-areas. The traffic situation gives the possibility to change the TLC sub-area dynamically depending on the time of day and the traffic flow. Depending on the traffic situation each TLC selects the time plan dynamically.\nRequires security code 2",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Restarts Traffic Light Controller\n\nUsed in the event of serious faults in the device where a restart is considered to be able to remedy a problem.\n\nRequires security code 2",
4
+ "description" : "Restarts Traffic Light Controller.\nUsed in the event of serious faults in the device where a restart is considered to be able to remedy a problem.\nRequires security code 2",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Activate emergency route\n\nThe function is made for emergency prioritization. Works in the same way as the M0006 and M0008 where the traffic light controller responds to an input.\n\nShould be used in situations where full priority is given in the emergency vehicle program.\n\nRequires security code 2.",
4
+ "description" : "Activate emergency route.\nThe function is made for emergency prioritization. Works in the same way as the M0006 and M0008 where the traffic light controller responds to an input.\nShould be used in situations where full priority is given in the emergency vehicle program.\nRequires security code 2.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Activate input\n\nSet given input (1-255) of the controllers general purpose I/O to either true or false.\n\nThe function can provide an input to the traffic light controller on which a predefined action can be taken.\n\nCan be used for all types of input where the traffic light controller must react to external control.\n\nTypical usages are bus priority, coordination between traffic controllers, external control systems, and much more.\n\nRequires security code 2",
4
+ "description" : "Activate input.\nSet given input (1-255) of the controllers general purpose I/O to either true or false.\nThe function can provide an input to the traffic light controller on which a predefined action can be taken.\nCan be used for all types of input where the traffic light controller must react to external control.\nTypical usages are bus priority, coordination between traffic controllers, external control systems, and much more.\nRequires security code 2.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Activate fixed time control\n\nDeactivates the traffic actuated control using detectors and activates pre-timed control.\n\nCan be used in case normal detectors can't be used, e.g. during maintenance work.\n\nRequires security code 2.",
4
+ "description" : "Activate fixed time control.\nDeactivates the traffic actuated control using detectors and activates pre-timed control.\nCan be used in case normal detectors can't be used, e.g. during maintenance work.\nRequires security code 2.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Sets manual activation of detector logic\n\nSet given detector logic (1-255) to either true or false.\n\nCan e.g. be used to connect RSMP compatible detection equipment to the traffic light controller. Can also be used for prioritization.\n\nRequires security code 2",
4
+ "description" : "Sets manual activation of detector logic.\nSet given detector logic (1-255) to either true or false.\nCan e.g. be used to connect RSMP compatible detection equipment to the traffic light controller. Can also be used for prioritization.\nRequires security code 2",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Start of signal group. Orders a signal group to green.\n\nAlthough this command is intended to be used with coordination it is not actually specified to be used for this yet. It is reserved in the SXL for possible future use.\n\nIntended for use with coordination of signaling systems where a traffic light controller communicates with neighboring controllers. Only used when a primary controller orders signal group of other controller to green or red (Coordination with external control bits).\n\nRequires security code 2",
4
+ "description" : "Start of signal group. Orders a signal group to green.\nAlthough this command is intended to be used with coordination it is not actually specified to be used for this yet. It is reserved in the SXL for possible future use.\nIntended for use with coordination of signaling systems where a traffic light controller communicates with neighboring controllers. Only used when a primary controller orders signal group of other controller to green or red (Coordination with external control bits).\nRequires security code 2",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Stop of signal group. Orders a signal group to red.\n\nAlthough this command is intended to be used with coordination it is not actually specified to be used for this yet. It is reserved in the SXL for possible future use.\n\nIntended for use with coordination of signaling systems where a traffic light controller communicates with neighboring controllers. Only used when a primary controller orders signal group of other controller to green or red (Coordination with external control bits).\n\nRequires security code 2",
4
+ "description" : "Stop of signal group. Orders a signal group to red.\nAlthough this command is intended to be used with coordination it is not actually specified to be used for this yet. It is reserved in the SXL for possible future use.\nIntended for use with coordination of signaling systems where a traffic light controller communicates with neighboring controllers. Only used when a primary controller orders signal group of other controller to green or red (Coordination with external control bits).\nRequires security code 2",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Request start or stop of a series of signal groups.\n\nStarts or stops several signal groups.\n\nThis command was introduced due to coordination requirements needing to set many signal groups to green and red at the same time and M0010 and M0012 being to slow to send a message for each signal group individually.\n\nAlthough this command is intended to be used with coordination it is not actually specified to be used for this yet. It is reserved in the SXL for possible future use.\n\nIntended for use with coordination of signaling systems where a traffic light controller communicates with neighboring controllers.\n\nOnly used when a primary controller orders signal group of other controller to green or red (Coordination with external control bits).\n\nMay also include purposes for adaptive control where a UTC system or a local traffic light controller takes over the phase control (stage control).\n\nRequires security code 2.",
4
+ "description" : "Request start or stop of a series of signal groups.\nStarts or stops several signal groups.\nThis command was introduced due to coordination requirements needing to set many signal groups to green and red at the same time and M0010 and M0012 being to slow to send a message for each signal group individually.\nAlthough this command is intended to be used with coordination it is not actually specified to be used for this yet. It is reserved in the SXL for possible future use.\nIntended for use with coordination of signaling systems where a traffic light controller communicates with neighboring controllers.\nOnly used when a primary controller orders signal group of other controller to green or red (Coordination with external control bits).\nMay also include purposes for adaptive control where a UTC system or a local traffic light controller takes over the phase control (stage control).\nRequires security code 2.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Activate a series of inputs\n\nSet given inputs (1-255) of the controllers general purpose I/O to either true or false.\n\nThis 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.\n\nCan 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.\n\nRequires security code 2",
4
+ "description" : "Activate a series of inputs.\nSet given inputs (1-255) of the controllers general purpose I/O to either true or false.\nThis 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.\nCan 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.\nRequires security code 2",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Set dynamic bands\n\nCan be used to change between predefined signal timings. Moves the start of signal groups in the cycle.\n\nThis command can be used to change the split of green time during the cycle. A typical usage is scenario based control where changing of signal timings is used for optimal traffic flow.\n\nRequires security code 2",
4
+ "description" : "Set dynamic bands.\nCan be used to change between predefined signal timings. Moves the start of signal groups in the cycle.\nThis command can be used to change the split of green time during the cycle. A typical usage is scenario based control where changing of signal timings is used for optimal traffic flow.\nRequires security code 2",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Set Offset time\n\nOffset time is used to define an offset between intersections in coordinated control. It is based on the expected travel time between intersections.\n\nThis command can be used to fine tune the coordination for optimal traffic flow.\n\nRequires security code 2.",
4
+ "description" : "Set Offset time.\nOffset time is used to define an offset between intersections in coordinated control. It is based on the expected travel time between intersections.\nThis command can be used to fine tune the coordination for optimal traffic flow.\nRequires security code 2.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Set week time table\n\nSet which time table for signal programs to use for each day during a week.\n\nThis command changes the signal timings during the week for optimal traffic flow.\n\nRequires security code 2.",
4
+ "description" : "Set week time table.\nSet which time table for signal programs to use for each day during a week.\nThis command changes the signal timings during the week for optimal traffic flow.\nRequires security code 2.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Set time tables\n\nSet time of day for when to automatically switch signal program (time plan).\n\nThis command changes the signal timings according to time of day for optimal traffic flow.\n\nRequires security code 2.",
4
+ "description" : "Set time tables.\nSet time of day for when to automatically switch signal program (time plan).\nThis command changes the signal timings according to time of day for optimal traffic flow.\nRequires security code 2.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Set Cycle time\n\nCycle time (or cycle length) is the sum of all phases in a time plan (traffic program). This time is fixed when using fixed time control or coordination (except \"local coordination\"). When the cycle counter reaches this length it is reset back to zero.\n\nThis command provides the ability to change the cycle time when using coordinated or fixed time control. It changes the timings for optimal traffic flow. Can be used with scenario based control.\n\nRequires security code 2.",
4
+ "description" : "Set Cycle time.\nCycle time (or cycle length) is the sum of all phases in a time plan (traffic program). This time is fixed when using fixed time control or coordination (except \"local coordination\"). When the cycle counter reaches this length it is reset back to zero.\nThis command provides the ability to change the cycle time when using coordinated or fixed time control. It changes the timings for optimal traffic flow. Can be used with scenario based control.\nRequires security code 2.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Force input\n\nForce a given input (1-255) of the controllers general purpose I/O to either True or False. Can be used for all types of input where the traffic light controller must react to external control.\n\nCan be used for bus priority, coordination between traffic controllers, external control systems, and much more.\n\nRequires security code 2.",
4
+ "description" : "Force input.\nForce a given input (1-255) of the controllers general purpose I/O to either True or False. Can be used for all types of input where the traffic light controller must react to external control.\nCan be used for bus priority, coordination between traffic controllers, external control systems, and much more.\nRequires security code 2.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Force output\n\nForce a given output (1-255) of the controllers general purpose I/O to either True of False. Can be used for all types of output where the traffic light controller needs to control other equipment.\n\nCan be used for bus priority, coordination between traffic controllers, external control systems, and much more.\n\nRequires security code 2.",
4
+ "description" : "Force output.\nForce a given output (1-255) of the controllers general purpose I/O to either True of False. Can be used for all types of output where the traffic light controller needs to control other equipment.\nCan be used for bus priority, coordination between traffic controllers, external control systems, and much more.\nRequires security code 2.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Set trigger level sensitivity for loop detector\n\nThe trigger level sensitivity determines at what level a loop detector should trigger. If it set too low then then traffic will not be detected as intended. If it is set too high the detector might give false positives.\n\nThis command provides the ability to fine tune loop detectors to make sure they detect traffic as intended.\n\nRequires security code 2",
4
+ "description" : "Set trigger level sensitivity for loop detector.\nThe trigger level sensitivity determines at what level a loop detector should trigger. If it set too low then then traffic will not be detected as intended. If it is set too high the detector might give false positives.\nThis command provides the ability to fine tune loop detectors to make sure they detect traffic as intended.\nRequires security code 2",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Set security code\n\nChange the security code to use when sending commands\n\nSecurity codes are used as an extra layer of security in many commands. They need to match between the supervision system and the traffic light controller in order for the commands to be executed.",
4
+ "description" : "Set security code.\nChange the security code to use when sending commands\nSecurity codes are used as an extra layer of security in many commands. They need to match between the supervision system and the traffic light controller in order for the commands to be executed.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Set clock\n\nCan be used to manually set the clock of the traffic light controller if automatic time synchronization (NTP or watchdog sync) is not available. For instance, during maintenance work.\n\nRequires security code 1",
4
+ "description" : "Set clock.\nCan be used to manually set the clock of the traffic light controller if automatic time synchronization (NTP or watchdog sync) is not available. For instance, during maintenance work.\nRequires security code 1",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Signal group status\n\nProvides the status of each signal group, including basic information such as green, yellow and red. But also detailed technical information.\n\nCan be used to draw a live signal group diagram as well provide diagnostic information about the performance of the controller.",
4
+ "description" : "Signal group status.\nProvides the status of each signal group, including basic information such as green, yellow and red. But also detailed technical information.\nCan be used to draw a live signal group diagram as well provide diagnostic information about the performance of the controller.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Detector logic status\n\nProvides the status of all detector logics of the controller.\n\nCan be used to draw a live signal group diagram as well provide diagnostic information about the performance of the controller. Can also be used for bus priority, external control systems, and much more.",
4
+ "description" : "Detector logic status.\nProvides the status of all detector logics of the controller.\nCan be used to draw a live signal group diagram as well provide diagnostic information about the performance of the controller. Can also be used for bus priority, external control systems, and much more.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Input status\n\nInput (1-255) of the controllers general purpose I/O.\n\nInput is used where the traffic light controller must react to external control. It could be external detectors, bus priority, and much more.",
4
+ "description" : "Input status.\nInput (1-255) of the controllers general purpose I/O.\nInput is used where the traffic light controller must react to external control. It could be external detectors, bus priority, and much more.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Output status\n\nOutput (1-255) of the controllers general purpose I/O.\n\nCan be used for all types of output where the traffic light controller needs to control other equipment. Can be used for bus priority, coordination between traffic controllers, external control systems, and much more.",
4
+ "description" : "Output status.\nOutput (1-255) of the controllers general purpose I/O.\nCan be used for all types of output where the traffic light controller needs to control other equipment. Can be used for bus priority, coordination between traffic controllers, external control systems, and much more.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Traffic Light Controller starting\n\nThe traffic signal is starting, e.g. it is in startup mode and has not begun working normally yet.\n\nDuring startup mode the traffic controller shows dark, red, yellow flash or using the predetermined start cycle (minimum times).",
4
+ "description" : "Traffic Light Controller starting.\nThe traffic signal is starting, e.g. it is in startup mode and has not begun working normally yet.\nDuring startup mode the traffic controller shows dark, red, yellow flash or using the predetermined start cycle (minimum times).",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Emergency stage\n\nThe status is active during emergency prioritization.\n\nUsed in situations where full priority is given in the emergency vehicle program.",
4
+ "description" : "Emergency stage.\nThe status is active during emergency prioritization.\nUsed in situations where full priority is given in the emergency vehicle program.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Controller switched on\n\nThe controller is active and is not in dark mode.\n\nUsed to determine if the controller is operating, e.g. it shows red, green or yellow to the vehicles.\n\nDuring maintenance work the controller might be using dark mode (no output to the signal heads).\n",
4
+ "description" : "Controller switched on.\nThe controller is active and is not in dark mode.\nUsed to determine if the controller is operating, e.g. it shows red, green or yellow to the vehicles.\nDuring maintenance work the controller might be using dark mode (no output to the signal heads).\n",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Manual control\n\nTraffic control deactivated in controller\n\nSignal timings is controlled manually by service personnel using the operating panel of the controller.",
4
+ "description" : "Manual control.\nTraffic control deactivated in controller\nSignal timings is controlled manually by service personnel using the operating panel of the controller.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Fixed time control\n\nTraffic actuated control deactivated and a pre-timed control is used.\n\nUsually only used in case normal detectors can't be used, e.g. during maintenance work.",
4
+ "description" : "Fixed time control.\nTraffic actuated control deactivated and a pre-timed control is used.\nUsually only used in case normal detectors can't be used, e.g. during maintenance work.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Isolated control\n\nIsolated control mode indicates that the controller operates independently of any other traffic light controllers. This may different depending on traffic program (time plan).\n\nUsed to determine if the controller is operating independently or operating with other controllers (coordination).",
4
+ "description" : "Isolated control.\nIsolated control mode indicates that the controller operates independently of any other traffic light controllers. This may different depending on traffic program (time plan).\nUsed to determine if the controller is operating independently or operating with other controllers (coordination).",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Yellow flash\n\nThe controller shows yellow flash.\n\nYellow flash may be used during a serious fault (depending on configuration) or maintenance work. It can also be manually set using M0001.",
4
+ "description" : "Yellow flash.\nThe controller shows yellow flash.\nYellow flash may be used during a serious fault (depending on configuration) or maintenance work. It can also be manually set using M0001.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "All red\n\nThe controller show all red\n\nAll red can be manually set using the controllers operating panel during maintenance work.",
4
+ "description" : "All red.\nThe controller show all red.\nAll red can be manually set using the controllers operating panel during maintenance work.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Police key\n\nThe controller is forced to dark mode or yellow flash.\n\nThe \"police key\" is a external control switch present in some controllers that manually switches the controller to either dark mode or yellow flash.",
4
+ "description" : "Police key\nThe controller is forced to dark mode or yellow flash.\nThe \"police key\" is a external control switch present in some controllers that manually switches the controller to either dark mode or yellow flash.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Current time plan\n\nThe current time plan (signal program) used in the controller. There may be 1-255 predefined time plans.\n\nThe time plan (signal program) may change signal timings, cycle time, control strategy and much more. Typical usage is is scenario based control where change of program is used to change priority etc.",
4
+ "description" : "Current time plan.\nThe current time plan (signal program) used in the controller. There may be 1-255 predefined time plans.\nThe time plan (signal program) may change signal timings, cycle time, control strategy and much more. Typical usage is is scenario based control where change of program is used to change priority etc.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Current traffic situation\n\nThe current traffic situation used in the controller.\n\nUsed for area-based control where a command can be sent to a master traffic light controller about which predefined traffic situation to use (1-255).\n\nTraffic situation is a concept used to divide multiple TLC's into areas and sub-areas. The traffic situation gives the possibility to change the TLC sub-area dynamically depending on the time of day and the traffic flow. Depending on the traffic situation each TLC selects the time plan dynamically.",
4
+ "description" : "Current traffic situation.\nThe current traffic situation used in the controller.\nUsed for area-based control where a command can be sent to a master traffic light controller about which predefined traffic situation to use (1-255).\nTraffic situation is a concept used to divide multiple TLC's into areas and sub-areas. The traffic situation gives the possibility to change the TLC sub-area dynamically depending on the time of day and the traffic flow. Depending on the traffic situation each TLC selects the time plan dynamically.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Number of detector logics\n\nCan be used by the management system to check the number of detector logics configured in the controller.",
4
+ "description" : "Number of detector logics.\nCan be used by the management system to check the number of detector logics configured in the controller.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Number of signal groups\n\nCan be used for the management system to check the number of signal groups configured in the controller.",
4
+ "description" : "Number of signal groups.\nCan be used for the management system to check the number of signal groups configured in the controller.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Number of time plans\n\nCan be used for the management system to check the number of time plans configured in the controller.",
4
+ "description" : "Number of time plans\nCan be used for the management system to check the number of time plans configured in the controller.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "allOf" : [
3
3
  {
4
- "description" : "Number of traffic situations\n\nCan be used for the management system to check the number of traffic situations configured in the controller.",
4
+ "description" : "Number of traffic situations.\nCan be used for the management system to check the number of traffic situations configured in the controller.",
5
5
  "properties" : {
6
6
  "n" : {
7
7
  "enum" : [