rsmp_schema 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (653) hide show
  1. checksums.yaml +7 -0
  2. data/.gitignore +6 -0
  3. data/.rspec +1 -0
  4. data/Gemfile +4 -0
  5. data/Gemfile.lock +49 -0
  6. data/LICENSE +7 -0
  7. data/README.md +73 -0
  8. data/Rakefile +18 -0
  9. data/examples/validate.rb +32 -0
  10. data/exe/rsmp_schema +4 -0
  11. data/lib/rsmp_schema/cli.rb +35 -0
  12. data/lib/rsmp_schema/convert/export/json_schema.rb +223 -0
  13. data/lib/rsmp_schema/convert/import/yaml.rb +41 -0
  14. data/lib/rsmp_schema/error.rb +13 -0
  15. data/lib/rsmp_schema/schema.rb +102 -0
  16. data/lib/rsmp_schema/version.rb +5 -0
  17. data/lib/rsmp_schema.rb +7 -0
  18. data/rsmp_schema.gemspec +40 -0
  19. data/schemas/core/3.1.1/aggregated_status.json +25 -0
  20. data/schemas/core/3.1.1/alarm.json +58 -0
  21. data/schemas/core/3.1.1/alarm_issue.json +47 -0
  22. data/schemas/core/3.1.1/alarm_suspend_resume.json +3 -0
  23. data/schemas/core/3.1.1/alarm_suspended_resumed.json +47 -0
  24. data/schemas/core/3.1.1/command_request.json +24 -0
  25. data/schemas/core/3.1.1/command_response.json +34 -0
  26. data/schemas/core/3.1.1/core.json +38 -0
  27. data/schemas/core/3.1.1/definitions.json +67 -0
  28. data/schemas/core/3.1.1/message_ack.json +11 -0
  29. data/schemas/core/3.1.1/message_not_ack.json +15 -0
  30. data/schemas/core/3.1.1/rsmp.json +124 -0
  31. data/schemas/core/3.1.1/status.json +21 -0
  32. data/schemas/core/3.1.1/status_request.json +5 -0
  33. data/schemas/core/3.1.1/status_response.json +30 -0
  34. data/schemas/core/3.1.1/status_subscribe.json +27 -0
  35. data/schemas/core/3.1.1/status_unsubscribe.json +5 -0
  36. data/schemas/core/3.1.1/status_update.json +30 -0
  37. data/schemas/core/3.1.1/version.json +47 -0
  38. data/schemas/core/3.1.1/watchdog.json +9 -0
  39. data/schemas/core/3.1.2/rsmp.json +3 -0
  40. data/schemas/core/3.1.3/rsmp.json +124 -0
  41. data/schemas/core/3.1.3/status_response.json +30 -0
  42. data/schemas/core/3.1.3/status_update.json +30 -0
  43. data/schemas/core/3.1.4/rsmp.json +3 -0
  44. data/schemas/core/3.1.5/aggregated_status_request.json +9 -0
  45. data/schemas/core/3.1.5/alarm.json +68 -0
  46. data/schemas/core/3.1.5/alarm_request.json +3 -0
  47. data/schemas/core/3.1.5/core.json +39 -0
  48. data/schemas/core/3.1.5/rsmp.json +133 -0
  49. data/schemas/core/3.1.5/status.json +21 -0
  50. data/schemas/core/3.1.5/status_subscribe.json +31 -0
  51. data/schemas/core/3.2/alarm.json +62 -0
  52. data/schemas/core/3.2/core.json +39 -0
  53. data/schemas/core/3.2/rsmp.json +133 -0
  54. data/schemas/tlc/1.0.10/alarms/A0001.json +7 -0
  55. data/schemas/tlc/1.0.10/alarms/A0002.json +7 -0
  56. data/schemas/tlc/1.0.10/alarms/A0003.json +7 -0
  57. data/schemas/tlc/1.0.10/alarms/A0004.json +7 -0
  58. data/schemas/tlc/1.0.10/alarms/A0005.json +7 -0
  59. data/schemas/tlc/1.0.10/alarms/A0006.json +7 -0
  60. data/schemas/tlc/1.0.10/alarms/A0007.json +7 -0
  61. data/schemas/tlc/1.0.10/alarms/A0008.json +40 -0
  62. data/schemas/tlc/1.0.10/alarms/A0009.json +7 -0
  63. data/schemas/tlc/1.0.10/alarms/A0101.json +7 -0
  64. data/schemas/tlc/1.0.10/alarms/A0201.json +39 -0
  65. data/schemas/tlc/1.0.10/alarms/A0202.json +39 -0
  66. data/schemas/tlc/1.0.10/alarms/A0301.json +111 -0
  67. data/schemas/tlc/1.0.10/alarms/A0302.json +137 -0
  68. data/schemas/tlc/1.0.10/alarms/alarms.json +238 -0
  69. data/schemas/tlc/1.0.10/commands/M0001.json +125 -0
  70. data/schemas/tlc/1.0.10/commands/M0002.json +91 -0
  71. data/schemas/tlc/1.0.10/commands/M0003.json +91 -0
  72. data/schemas/tlc/1.0.10/commands/M0004.json +64 -0
  73. data/schemas/tlc/1.0.10/commands/M0005.json +91 -0
  74. data/schemas/tlc/1.0.10/commands/M0006.json +91 -0
  75. data/schemas/tlc/1.0.10/commands/M0007.json +64 -0
  76. data/schemas/tlc/1.0.10/commands/M0008.json +91 -0
  77. data/schemas/tlc/1.0.10/commands/M0010.json +64 -0
  78. data/schemas/tlc/1.0.10/commands/M0011.json +64 -0
  79. data/schemas/tlc/1.0.10/commands/M0012.json +58 -0
  80. data/schemas/tlc/1.0.10/commands/M0013.json +58 -0
  81. data/schemas/tlc/1.0.10/commands/M0019.json +118 -0
  82. data/schemas/tlc/1.0.10/commands/M0103.json +82 -0
  83. data/schemas/tlc/1.0.10/commands/M0104.json +199 -0
  84. data/schemas/tlc/1.0.10/commands/command_requests.json +7 -0
  85. data/schemas/tlc/1.0.10/commands/command_responses.json +7 -0
  86. data/schemas/tlc/1.0.10/commands/commands.json +254 -0
  87. data/schemas/tlc/1.0.10/statuses/S0001.json +116 -0
  88. data/schemas/tlc/1.0.10/statuses/S0002.json +34 -0
  89. data/schemas/tlc/1.0.10/statuses/S0003.json +55 -0
  90. data/schemas/tlc/1.0.10/statuses/S0004.json +55 -0
  91. data/schemas/tlc/1.0.10/statuses/S0005.json +40 -0
  92. data/schemas/tlc/1.0.10/statuses/S0006.json +67 -0
  93. data/schemas/tlc/1.0.10/statuses/S0007.json +67 -0
  94. data/schemas/tlc/1.0.10/statuses/S0008.json +67 -0
  95. data/schemas/tlc/1.0.10/statuses/S0009.json +67 -0
  96. data/schemas/tlc/1.0.10/statuses/S0010.json +67 -0
  97. data/schemas/tlc/1.0.10/statuses/S0011.json +67 -0
  98. data/schemas/tlc/1.0.10/statuses/S0012.json +67 -0
  99. data/schemas/tlc/1.0.10/statuses/S0013.json +67 -0
  100. data/schemas/tlc/1.0.10/statuses/S0014.json +40 -0
  101. data/schemas/tlc/1.0.10/statuses/S0015.json +40 -0
  102. data/schemas/tlc/1.0.10/statuses/S0016.json +40 -0
  103. data/schemas/tlc/1.0.10/statuses/S0017.json +40 -0
  104. data/schemas/tlc/1.0.10/statuses/S0018.json +40 -0
  105. data/schemas/tlc/1.0.10/statuses/S0019.json +40 -0
  106. data/schemas/tlc/1.0.10/statuses/S0020.json +67 -0
  107. data/schemas/tlc/1.0.10/statuses/S0021.json +35 -0
  108. data/schemas/tlc/1.0.10/statuses/S0091.json +58 -0
  109. data/schemas/tlc/1.0.10/statuses/S0092.json +58 -0
  110. data/schemas/tlc/1.0.10/statuses/S0095.json +34 -0
  111. data/schemas/tlc/1.0.10/statuses/S0096.json +175 -0
  112. data/schemas/tlc/1.0.10/statuses/S0201.json +67 -0
  113. data/schemas/tlc/1.0.10/statuses/S0202.json +67 -0
  114. data/schemas/tlc/1.0.10/statuses/S0203.json +67 -0
  115. data/schemas/tlc/1.0.10/statuses/S0204.json +283 -0
  116. data/schemas/tlc/1.0.10/statuses/statuses.json +482 -0
  117. data/schemas/tlc/1.0.10/sxl.json +73 -0
  118. data/schemas/tlc/1.0.10/sxl.yaml +1059 -0
  119. data/schemas/tlc/1.0.13/alarms/A0001.json +7 -0
  120. data/schemas/tlc/1.0.13/alarms/A0002.json +7 -0
  121. data/schemas/tlc/1.0.13/alarms/A0003.json +7 -0
  122. data/schemas/tlc/1.0.13/alarms/A0004.json +7 -0
  123. data/schemas/tlc/1.0.13/alarms/A0005.json +7 -0
  124. data/schemas/tlc/1.0.13/alarms/A0006.json +7 -0
  125. data/schemas/tlc/1.0.13/alarms/A0007.json +7 -0
  126. data/schemas/tlc/1.0.13/alarms/A0008.json +40 -0
  127. data/schemas/tlc/1.0.13/alarms/A0009.json +7 -0
  128. data/schemas/tlc/1.0.13/alarms/A0101.json +7 -0
  129. data/schemas/tlc/1.0.13/alarms/A0201.json +39 -0
  130. data/schemas/tlc/1.0.13/alarms/A0202.json +39 -0
  131. data/schemas/tlc/1.0.13/alarms/A0301.json +111 -0
  132. data/schemas/tlc/1.0.13/alarms/A0302.json +137 -0
  133. data/schemas/tlc/1.0.13/alarms/alarms.json +238 -0
  134. data/schemas/tlc/1.0.13/commands/M0001.json +125 -0
  135. data/schemas/tlc/1.0.13/commands/M0002.json +91 -0
  136. data/schemas/tlc/1.0.13/commands/M0003.json +91 -0
  137. data/schemas/tlc/1.0.13/commands/M0004.json +64 -0
  138. data/schemas/tlc/1.0.13/commands/M0005.json +91 -0
  139. data/schemas/tlc/1.0.13/commands/M0006.json +91 -0
  140. data/schemas/tlc/1.0.13/commands/M0007.json +64 -0
  141. data/schemas/tlc/1.0.13/commands/M0008.json +91 -0
  142. data/schemas/tlc/1.0.13/commands/M0010.json +64 -0
  143. data/schemas/tlc/1.0.13/commands/M0011.json +64 -0
  144. data/schemas/tlc/1.0.13/commands/M0012.json +58 -0
  145. data/schemas/tlc/1.0.13/commands/M0013.json +58 -0
  146. data/schemas/tlc/1.0.13/commands/M0014.json +85 -0
  147. data/schemas/tlc/1.0.13/commands/M0015.json +91 -0
  148. data/schemas/tlc/1.0.13/commands/M0016.json +58 -0
  149. data/schemas/tlc/1.0.13/commands/M0017.json +58 -0
  150. data/schemas/tlc/1.0.13/commands/M0018.json +91 -0
  151. data/schemas/tlc/1.0.13/commands/M0019.json +118 -0
  152. data/schemas/tlc/1.0.13/commands/M0103.json +82 -0
  153. data/schemas/tlc/1.0.13/commands/M0104.json +199 -0
  154. data/schemas/tlc/1.0.13/commands/command_requests.json +7 -0
  155. data/schemas/tlc/1.0.13/commands/command_responses.json +7 -0
  156. data/schemas/tlc/1.0.13/commands/commands.json +334 -0
  157. data/schemas/tlc/1.0.13/statuses/S0001.json +116 -0
  158. data/schemas/tlc/1.0.13/statuses/S0002.json +34 -0
  159. data/schemas/tlc/1.0.13/statuses/S0003.json +55 -0
  160. data/schemas/tlc/1.0.13/statuses/S0004.json +55 -0
  161. data/schemas/tlc/1.0.13/statuses/S0005.json +40 -0
  162. data/schemas/tlc/1.0.13/statuses/S0006.json +67 -0
  163. data/schemas/tlc/1.0.13/statuses/S0007.json +67 -0
  164. data/schemas/tlc/1.0.13/statuses/S0008.json +67 -0
  165. data/schemas/tlc/1.0.13/statuses/S0009.json +67 -0
  166. data/schemas/tlc/1.0.13/statuses/S0010.json +67 -0
  167. data/schemas/tlc/1.0.13/statuses/S0011.json +67 -0
  168. data/schemas/tlc/1.0.13/statuses/S0012.json +67 -0
  169. data/schemas/tlc/1.0.13/statuses/S0013.json +67 -0
  170. data/schemas/tlc/1.0.13/statuses/S0014.json +40 -0
  171. data/schemas/tlc/1.0.13/statuses/S0015.json +40 -0
  172. data/schemas/tlc/1.0.13/statuses/S0016.json +40 -0
  173. data/schemas/tlc/1.0.13/statuses/S0017.json +40 -0
  174. data/schemas/tlc/1.0.13/statuses/S0018.json +40 -0
  175. data/schemas/tlc/1.0.13/statuses/S0019.json +40 -0
  176. data/schemas/tlc/1.0.13/statuses/S0020.json +67 -0
  177. data/schemas/tlc/1.0.13/statuses/S0021.json +35 -0
  178. data/schemas/tlc/1.0.13/statuses/S0022.json +34 -0
  179. data/schemas/tlc/1.0.13/statuses/S0023.json +35 -0
  180. data/schemas/tlc/1.0.13/statuses/S0024.json +35 -0
  181. data/schemas/tlc/1.0.13/statuses/S0025.json +229 -0
  182. data/schemas/tlc/1.0.13/statuses/S0026.json +34 -0
  183. data/schemas/tlc/1.0.13/statuses/S0027.json +34 -0
  184. data/schemas/tlc/1.0.13/statuses/S0028.json +34 -0
  185. data/schemas/tlc/1.0.13/statuses/S0029.json +34 -0
  186. data/schemas/tlc/1.0.13/statuses/S0091.json +58 -0
  187. data/schemas/tlc/1.0.13/statuses/S0092.json +58 -0
  188. data/schemas/tlc/1.0.13/statuses/S0095.json +34 -0
  189. data/schemas/tlc/1.0.13/statuses/S0096.json +175 -0
  190. data/schemas/tlc/1.0.13/statuses/S0201.json +67 -0
  191. data/schemas/tlc/1.0.13/statuses/S0202.json +67 -0
  192. data/schemas/tlc/1.0.13/statuses/S0203.json +67 -0
  193. data/schemas/tlc/1.0.13/statuses/S0204.json +283 -0
  194. data/schemas/tlc/1.0.13/statuses/statuses.json +610 -0
  195. data/schemas/tlc/1.0.13/sxl.json +73 -0
  196. data/schemas/tlc/1.0.13/sxl.yaml +1376 -0
  197. data/schemas/tlc/1.0.14/alarms/A0001.json +7 -0
  198. data/schemas/tlc/1.0.14/alarms/A0002.json +7 -0
  199. data/schemas/tlc/1.0.14/alarms/A0003.json +7 -0
  200. data/schemas/tlc/1.0.14/alarms/A0004.json +7 -0
  201. data/schemas/tlc/1.0.14/alarms/A0005.json +7 -0
  202. data/schemas/tlc/1.0.14/alarms/A0006.json +7 -0
  203. data/schemas/tlc/1.0.14/alarms/A0007.json +7 -0
  204. data/schemas/tlc/1.0.14/alarms/A0008.json +40 -0
  205. data/schemas/tlc/1.0.14/alarms/A0009.json +7 -0
  206. data/schemas/tlc/1.0.14/alarms/A0101.json +7 -0
  207. data/schemas/tlc/1.0.14/alarms/A0201.json +39 -0
  208. data/schemas/tlc/1.0.14/alarms/A0202.json +39 -0
  209. data/schemas/tlc/1.0.14/alarms/A0301.json +111 -0
  210. data/schemas/tlc/1.0.14/alarms/A0302.json +137 -0
  211. data/schemas/tlc/1.0.14/alarms/alarms.json +238 -0
  212. data/schemas/tlc/1.0.14/commands/M0001.json +125 -0
  213. data/schemas/tlc/1.0.14/commands/M0002.json +91 -0
  214. data/schemas/tlc/1.0.14/commands/M0003.json +91 -0
  215. data/schemas/tlc/1.0.14/commands/M0004.json +64 -0
  216. data/schemas/tlc/1.0.14/commands/M0005.json +91 -0
  217. data/schemas/tlc/1.0.14/commands/M0006.json +91 -0
  218. data/schemas/tlc/1.0.14/commands/M0007.json +64 -0
  219. data/schemas/tlc/1.0.14/commands/M0008.json +91 -0
  220. data/schemas/tlc/1.0.14/commands/M0010.json +64 -0
  221. data/schemas/tlc/1.0.14/commands/M0011.json +64 -0
  222. data/schemas/tlc/1.0.14/commands/M0012.json +58 -0
  223. data/schemas/tlc/1.0.14/commands/M0013.json +58 -0
  224. data/schemas/tlc/1.0.14/commands/M0014.json +85 -0
  225. data/schemas/tlc/1.0.14/commands/M0015.json +91 -0
  226. data/schemas/tlc/1.0.14/commands/M0016.json +58 -0
  227. data/schemas/tlc/1.0.14/commands/M0017.json +58 -0
  228. data/schemas/tlc/1.0.14/commands/M0018.json +91 -0
  229. data/schemas/tlc/1.0.14/commands/M0019.json +118 -0
  230. data/schemas/tlc/1.0.14/commands/M0103.json +82 -0
  231. data/schemas/tlc/1.0.14/commands/M0104.json +199 -0
  232. data/schemas/tlc/1.0.14/commands/command_requests.json +7 -0
  233. data/schemas/tlc/1.0.14/commands/command_responses.json +7 -0
  234. data/schemas/tlc/1.0.14/commands/commands.json +334 -0
  235. data/schemas/tlc/1.0.14/statuses/S0001.json +116 -0
  236. data/schemas/tlc/1.0.14/statuses/S0002.json +34 -0
  237. data/schemas/tlc/1.0.14/statuses/S0003.json +55 -0
  238. data/schemas/tlc/1.0.14/statuses/S0004.json +55 -0
  239. data/schemas/tlc/1.0.14/statuses/S0005.json +40 -0
  240. data/schemas/tlc/1.0.14/statuses/S0006.json +67 -0
  241. data/schemas/tlc/1.0.14/statuses/S0007.json +67 -0
  242. data/schemas/tlc/1.0.14/statuses/S0008.json +67 -0
  243. data/schemas/tlc/1.0.14/statuses/S0009.json +67 -0
  244. data/schemas/tlc/1.0.14/statuses/S0010.json +67 -0
  245. data/schemas/tlc/1.0.14/statuses/S0011.json +67 -0
  246. data/schemas/tlc/1.0.14/statuses/S0012.json +67 -0
  247. data/schemas/tlc/1.0.14/statuses/S0013.json +67 -0
  248. data/schemas/tlc/1.0.14/statuses/S0014.json +40 -0
  249. data/schemas/tlc/1.0.14/statuses/S0015.json +40 -0
  250. data/schemas/tlc/1.0.14/statuses/S0016.json +40 -0
  251. data/schemas/tlc/1.0.14/statuses/S0017.json +40 -0
  252. data/schemas/tlc/1.0.14/statuses/S0018.json +40 -0
  253. data/schemas/tlc/1.0.14/statuses/S0019.json +40 -0
  254. data/schemas/tlc/1.0.14/statuses/S0020.json +67 -0
  255. data/schemas/tlc/1.0.14/statuses/S0021.json +35 -0
  256. data/schemas/tlc/1.0.14/statuses/S0022.json +34 -0
  257. data/schemas/tlc/1.0.14/statuses/S0023.json +35 -0
  258. data/schemas/tlc/1.0.14/statuses/S0024.json +35 -0
  259. data/schemas/tlc/1.0.14/statuses/S0025.json +229 -0
  260. data/schemas/tlc/1.0.14/statuses/S0026.json +34 -0
  261. data/schemas/tlc/1.0.14/statuses/S0027.json +34 -0
  262. data/schemas/tlc/1.0.14/statuses/S0028.json +34 -0
  263. data/schemas/tlc/1.0.14/statuses/S0029.json +34 -0
  264. data/schemas/tlc/1.0.14/statuses/S0091.json +58 -0
  265. data/schemas/tlc/1.0.14/statuses/S0092.json +58 -0
  266. data/schemas/tlc/1.0.14/statuses/S0095.json +34 -0
  267. data/schemas/tlc/1.0.14/statuses/S0096.json +175 -0
  268. data/schemas/tlc/1.0.14/statuses/S0201.json +67 -0
  269. data/schemas/tlc/1.0.14/statuses/S0202.json +67 -0
  270. data/schemas/tlc/1.0.14/statuses/S0203.json +67 -0
  271. data/schemas/tlc/1.0.14/statuses/S0204.json +283 -0
  272. data/schemas/tlc/1.0.14/statuses/S0205.json +61 -0
  273. data/schemas/tlc/1.0.14/statuses/S0206.json +61 -0
  274. data/schemas/tlc/1.0.14/statuses/S0207.json +61 -0
  275. data/schemas/tlc/1.0.14/statuses/S0208.json +229 -0
  276. data/schemas/tlc/1.0.14/statuses/statuses.json +674 -0
  277. data/schemas/tlc/1.0.14/sxl.json +73 -0
  278. data/schemas/tlc/1.0.14/sxl.yaml +1514 -0
  279. data/schemas/tlc/1.0.15/alarms/A0001.json +7 -0
  280. data/schemas/tlc/1.0.15/alarms/A0002.json +7 -0
  281. data/schemas/tlc/1.0.15/alarms/A0003.json +7 -0
  282. data/schemas/tlc/1.0.15/alarms/A0004.json +7 -0
  283. data/schemas/tlc/1.0.15/alarms/A0005.json +7 -0
  284. data/schemas/tlc/1.0.15/alarms/A0006.json +7 -0
  285. data/schemas/tlc/1.0.15/alarms/A0007.json +7 -0
  286. data/schemas/tlc/1.0.15/alarms/A0008.json +40 -0
  287. data/schemas/tlc/1.0.15/alarms/A0009.json +7 -0
  288. data/schemas/tlc/1.0.15/alarms/A0010.json +7 -0
  289. data/schemas/tlc/1.0.15/alarms/A0101.json +7 -0
  290. data/schemas/tlc/1.0.15/alarms/A0201.json +39 -0
  291. data/schemas/tlc/1.0.15/alarms/A0202.json +39 -0
  292. data/schemas/tlc/1.0.15/alarms/A0301.json +111 -0
  293. data/schemas/tlc/1.0.15/alarms/A0302.json +137 -0
  294. data/schemas/tlc/1.0.15/alarms/alarms.json +254 -0
  295. data/schemas/tlc/1.0.15/commands/M0001.json +125 -0
  296. data/schemas/tlc/1.0.15/commands/M0002.json +91 -0
  297. data/schemas/tlc/1.0.15/commands/M0003.json +91 -0
  298. data/schemas/tlc/1.0.15/commands/M0004.json +64 -0
  299. data/schemas/tlc/1.0.15/commands/M0005.json +91 -0
  300. data/schemas/tlc/1.0.15/commands/M0006.json +91 -0
  301. data/schemas/tlc/1.0.15/commands/M0007.json +64 -0
  302. data/schemas/tlc/1.0.15/commands/M0008.json +91 -0
  303. data/schemas/tlc/1.0.15/commands/M0010.json +64 -0
  304. data/schemas/tlc/1.0.15/commands/M0011.json +64 -0
  305. data/schemas/tlc/1.0.15/commands/M0012.json +58 -0
  306. data/schemas/tlc/1.0.15/commands/M0013.json +58 -0
  307. data/schemas/tlc/1.0.15/commands/M0014.json +85 -0
  308. data/schemas/tlc/1.0.15/commands/M0015.json +91 -0
  309. data/schemas/tlc/1.0.15/commands/M0016.json +58 -0
  310. data/schemas/tlc/1.0.15/commands/M0017.json +58 -0
  311. data/schemas/tlc/1.0.15/commands/M0018.json +91 -0
  312. data/schemas/tlc/1.0.15/commands/M0019.json +118 -0
  313. data/schemas/tlc/1.0.15/commands/M0020.json +118 -0
  314. data/schemas/tlc/1.0.15/commands/M0021.json +58 -0
  315. data/schemas/tlc/1.0.15/commands/M0103.json +82 -0
  316. data/schemas/tlc/1.0.15/commands/M0104.json +199 -0
  317. data/schemas/tlc/1.0.15/commands/command_requests.json +7 -0
  318. data/schemas/tlc/1.0.15/commands/command_responses.json +7 -0
  319. data/schemas/tlc/1.0.15/commands/commands.json +366 -0
  320. data/schemas/tlc/1.0.15/statuses/S0001.json +116 -0
  321. data/schemas/tlc/1.0.15/statuses/S0002.json +34 -0
  322. data/schemas/tlc/1.0.15/statuses/S0003.json +55 -0
  323. data/schemas/tlc/1.0.15/statuses/S0004.json +55 -0
  324. data/schemas/tlc/1.0.15/statuses/S0005.json +40 -0
  325. data/schemas/tlc/1.0.15/statuses/S0006.json +67 -0
  326. data/schemas/tlc/1.0.15/statuses/S0007.json +67 -0
  327. data/schemas/tlc/1.0.15/statuses/S0008.json +67 -0
  328. data/schemas/tlc/1.0.15/statuses/S0009.json +67 -0
  329. data/schemas/tlc/1.0.15/statuses/S0010.json +67 -0
  330. data/schemas/tlc/1.0.15/statuses/S0011.json +67 -0
  331. data/schemas/tlc/1.0.15/statuses/S0012.json +67 -0
  332. data/schemas/tlc/1.0.15/statuses/S0013.json +67 -0
  333. data/schemas/tlc/1.0.15/statuses/S0014.json +40 -0
  334. data/schemas/tlc/1.0.15/statuses/S0015.json +40 -0
  335. data/schemas/tlc/1.0.15/statuses/S0016.json +40 -0
  336. data/schemas/tlc/1.0.15/statuses/S0017.json +40 -0
  337. data/schemas/tlc/1.0.15/statuses/S0018.json +40 -0
  338. data/schemas/tlc/1.0.15/statuses/S0019.json +40 -0
  339. data/schemas/tlc/1.0.15/statuses/S0020.json +67 -0
  340. data/schemas/tlc/1.0.15/statuses/S0021.json +35 -0
  341. data/schemas/tlc/1.0.15/statuses/S0022.json +34 -0
  342. data/schemas/tlc/1.0.15/statuses/S0023.json +35 -0
  343. data/schemas/tlc/1.0.15/statuses/S0024.json +35 -0
  344. data/schemas/tlc/1.0.15/statuses/S0025.json +229 -0
  345. data/schemas/tlc/1.0.15/statuses/S0026.json +34 -0
  346. data/schemas/tlc/1.0.15/statuses/S0027.json +34 -0
  347. data/schemas/tlc/1.0.15/statuses/S0028.json +34 -0
  348. data/schemas/tlc/1.0.15/statuses/S0029.json +34 -0
  349. data/schemas/tlc/1.0.15/statuses/S0030.json +34 -0
  350. data/schemas/tlc/1.0.15/statuses/S0031.json +34 -0
  351. data/schemas/tlc/1.0.15/statuses/S0091.json +58 -0
  352. data/schemas/tlc/1.0.15/statuses/S0092.json +58 -0
  353. data/schemas/tlc/1.0.15/statuses/S0095.json +34 -0
  354. data/schemas/tlc/1.0.15/statuses/S0096.json +175 -0
  355. data/schemas/tlc/1.0.15/statuses/S0097.json +61 -0
  356. data/schemas/tlc/1.0.15/statuses/S0098.json +82 -0
  357. data/schemas/tlc/1.0.15/statuses/S0201.json +67 -0
  358. data/schemas/tlc/1.0.15/statuses/S0202.json +67 -0
  359. data/schemas/tlc/1.0.15/statuses/S0203.json +67 -0
  360. data/schemas/tlc/1.0.15/statuses/S0204.json +283 -0
  361. data/schemas/tlc/1.0.15/statuses/S0205.json +61 -0
  362. data/schemas/tlc/1.0.15/statuses/S0206.json +61 -0
  363. data/schemas/tlc/1.0.15/statuses/S0207.json +61 -0
  364. data/schemas/tlc/1.0.15/statuses/S0208.json +229 -0
  365. data/schemas/tlc/1.0.15/statuses/statuses.json +738 -0
  366. data/schemas/tlc/1.0.15/sxl.json +73 -0
  367. data/schemas/tlc/1.0.15/sxl.yaml +1660 -0
  368. data/schemas/tlc/1.0.7/alarms/A0001.json +7 -0
  369. data/schemas/tlc/1.0.7/alarms/A0002.json +7 -0
  370. data/schemas/tlc/1.0.7/alarms/A0003.json +7 -0
  371. data/schemas/tlc/1.0.7/alarms/A0004.json +7 -0
  372. data/schemas/tlc/1.0.7/alarms/A0005.json +7 -0
  373. data/schemas/tlc/1.0.7/alarms/A0006.json +7 -0
  374. data/schemas/tlc/1.0.7/alarms/A0007.json +7 -0
  375. data/schemas/tlc/1.0.7/alarms/A0008.json +40 -0
  376. data/schemas/tlc/1.0.7/alarms/A0009.json +7 -0
  377. data/schemas/tlc/1.0.7/alarms/A0101.json +7 -0
  378. data/schemas/tlc/1.0.7/alarms/A0201.json +39 -0
  379. data/schemas/tlc/1.0.7/alarms/A0202.json +39 -0
  380. data/schemas/tlc/1.0.7/alarms/A0301.json +111 -0
  381. data/schemas/tlc/1.0.7/alarms/A0302.json +137 -0
  382. data/schemas/tlc/1.0.7/alarms/alarms.json +238 -0
  383. data/schemas/tlc/1.0.7/commands/M0001.json +125 -0
  384. data/schemas/tlc/1.0.7/commands/M0002.json +91 -0
  385. data/schemas/tlc/1.0.7/commands/M0003.json +91 -0
  386. data/schemas/tlc/1.0.7/commands/M0004.json +64 -0
  387. data/schemas/tlc/1.0.7/commands/M0005.json +91 -0
  388. data/schemas/tlc/1.0.7/commands/M0006.json +91 -0
  389. data/schemas/tlc/1.0.7/commands/M0007.json +64 -0
  390. data/schemas/tlc/1.0.7/commands/M0008.json +91 -0
  391. data/schemas/tlc/1.0.7/commands/M0010.json +64 -0
  392. data/schemas/tlc/1.0.7/commands/M0011.json +64 -0
  393. data/schemas/tlc/1.0.7/commands/M0019.json +118 -0
  394. data/schemas/tlc/1.0.7/commands/M0103.json +82 -0
  395. data/schemas/tlc/1.0.7/commands/M0104.json +199 -0
  396. data/schemas/tlc/1.0.7/commands/command_requests.json +7 -0
  397. data/schemas/tlc/1.0.7/commands/command_responses.json +7 -0
  398. data/schemas/tlc/1.0.7/commands/commands.json +222 -0
  399. data/schemas/tlc/1.0.7/statuses/S0001.json +116 -0
  400. data/schemas/tlc/1.0.7/statuses/S0002.json +34 -0
  401. data/schemas/tlc/1.0.7/statuses/S0003.json +55 -0
  402. data/schemas/tlc/1.0.7/statuses/S0004.json +55 -0
  403. data/schemas/tlc/1.0.7/statuses/S0005.json +40 -0
  404. data/schemas/tlc/1.0.7/statuses/S0006.json +67 -0
  405. data/schemas/tlc/1.0.7/statuses/S0007.json +67 -0
  406. data/schemas/tlc/1.0.7/statuses/S0008.json +67 -0
  407. data/schemas/tlc/1.0.7/statuses/S0009.json +67 -0
  408. data/schemas/tlc/1.0.7/statuses/S0010.json +67 -0
  409. data/schemas/tlc/1.0.7/statuses/S0011.json +67 -0
  410. data/schemas/tlc/1.0.7/statuses/S0012.json +67 -0
  411. data/schemas/tlc/1.0.7/statuses/S0013.json +67 -0
  412. data/schemas/tlc/1.0.7/statuses/S0014.json +40 -0
  413. data/schemas/tlc/1.0.7/statuses/S0015.json +40 -0
  414. data/schemas/tlc/1.0.7/statuses/S0016.json +40 -0
  415. data/schemas/tlc/1.0.7/statuses/S0017.json +40 -0
  416. data/schemas/tlc/1.0.7/statuses/S0018.json +40 -0
  417. data/schemas/tlc/1.0.7/statuses/S0019.json +40 -0
  418. data/schemas/tlc/1.0.7/statuses/S0020.json +67 -0
  419. data/schemas/tlc/1.0.7/statuses/S0021.json +35 -0
  420. data/schemas/tlc/1.0.7/statuses/S0025.json +229 -0
  421. data/schemas/tlc/1.0.7/statuses/S0091.json +58 -0
  422. data/schemas/tlc/1.0.7/statuses/S0092.json +58 -0
  423. data/schemas/tlc/1.0.7/statuses/S0095.json +34 -0
  424. data/schemas/tlc/1.0.7/statuses/S0096.json +175 -0
  425. data/schemas/tlc/1.0.7/statuses/S0201.json +67 -0
  426. data/schemas/tlc/1.0.7/statuses/S0202.json +67 -0
  427. data/schemas/tlc/1.0.7/statuses/S0203.json +67 -0
  428. data/schemas/tlc/1.0.7/statuses/S0204.json +283 -0
  429. data/schemas/tlc/1.0.7/statuses/statuses.json +498 -0
  430. data/schemas/tlc/1.0.7/sxl.json +73 -0
  431. data/schemas/tlc/1.0.7/sxl.yaml +1026 -0
  432. data/schemas/tlc/1.0.8/alarms/A0001.json +7 -0
  433. data/schemas/tlc/1.0.8/alarms/A0002.json +7 -0
  434. data/schemas/tlc/1.0.8/alarms/A0003.json +7 -0
  435. data/schemas/tlc/1.0.8/alarms/A0004.json +7 -0
  436. data/schemas/tlc/1.0.8/alarms/A0005.json +7 -0
  437. data/schemas/tlc/1.0.8/alarms/A0006.json +7 -0
  438. data/schemas/tlc/1.0.8/alarms/A0007.json +7 -0
  439. data/schemas/tlc/1.0.8/alarms/A0008.json +40 -0
  440. data/schemas/tlc/1.0.8/alarms/A0009.json +7 -0
  441. data/schemas/tlc/1.0.8/alarms/A0101.json +7 -0
  442. data/schemas/tlc/1.0.8/alarms/A0201.json +39 -0
  443. data/schemas/tlc/1.0.8/alarms/A0202.json +39 -0
  444. data/schemas/tlc/1.0.8/alarms/A0301.json +111 -0
  445. data/schemas/tlc/1.0.8/alarms/A0302.json +137 -0
  446. data/schemas/tlc/1.0.8/alarms/alarms.json +238 -0
  447. data/schemas/tlc/1.0.8/commands/M0001.json +125 -0
  448. data/schemas/tlc/1.0.8/commands/M0002.json +91 -0
  449. data/schemas/tlc/1.0.8/commands/M0003.json +91 -0
  450. data/schemas/tlc/1.0.8/commands/M0004.json +64 -0
  451. data/schemas/tlc/1.0.8/commands/M0005.json +91 -0
  452. data/schemas/tlc/1.0.8/commands/M0006.json +91 -0
  453. data/schemas/tlc/1.0.8/commands/M0007.json +64 -0
  454. data/schemas/tlc/1.0.8/commands/M0008.json +91 -0
  455. data/schemas/tlc/1.0.8/commands/M0010.json +64 -0
  456. data/schemas/tlc/1.0.8/commands/M0011.json +64 -0
  457. data/schemas/tlc/1.0.8/commands/M0012.json +58 -0
  458. data/schemas/tlc/1.0.8/commands/M0013.json +58 -0
  459. data/schemas/tlc/1.0.8/commands/M0019.json +118 -0
  460. data/schemas/tlc/1.0.8/commands/M0103.json +82 -0
  461. data/schemas/tlc/1.0.8/commands/M0104.json +199 -0
  462. data/schemas/tlc/1.0.8/commands/command_requests.json +7 -0
  463. data/schemas/tlc/1.0.8/commands/command_responses.json +7 -0
  464. data/schemas/tlc/1.0.8/commands/commands.json +254 -0
  465. data/schemas/tlc/1.0.8/statuses/S0001.json +116 -0
  466. data/schemas/tlc/1.0.8/statuses/S0002.json +34 -0
  467. data/schemas/tlc/1.0.8/statuses/S0003.json +55 -0
  468. data/schemas/tlc/1.0.8/statuses/S0004.json +55 -0
  469. data/schemas/tlc/1.0.8/statuses/S0005.json +40 -0
  470. data/schemas/tlc/1.0.8/statuses/S0006.json +67 -0
  471. data/schemas/tlc/1.0.8/statuses/S0007.json +67 -0
  472. data/schemas/tlc/1.0.8/statuses/S0008.json +67 -0
  473. data/schemas/tlc/1.0.8/statuses/S0009.json +67 -0
  474. data/schemas/tlc/1.0.8/statuses/S0010.json +67 -0
  475. data/schemas/tlc/1.0.8/statuses/S0011.json +67 -0
  476. data/schemas/tlc/1.0.8/statuses/S0012.json +67 -0
  477. data/schemas/tlc/1.0.8/statuses/S0013.json +67 -0
  478. data/schemas/tlc/1.0.8/statuses/S0014.json +40 -0
  479. data/schemas/tlc/1.0.8/statuses/S0015.json +40 -0
  480. data/schemas/tlc/1.0.8/statuses/S0016.json +40 -0
  481. data/schemas/tlc/1.0.8/statuses/S0017.json +40 -0
  482. data/schemas/tlc/1.0.8/statuses/S0018.json +40 -0
  483. data/schemas/tlc/1.0.8/statuses/S0019.json +40 -0
  484. data/schemas/tlc/1.0.8/statuses/S0020.json +67 -0
  485. data/schemas/tlc/1.0.8/statuses/S0021.json +35 -0
  486. data/schemas/tlc/1.0.8/statuses/S0025.json +181 -0
  487. data/schemas/tlc/1.0.8/statuses/S0091.json +58 -0
  488. data/schemas/tlc/1.0.8/statuses/S0092.json +58 -0
  489. data/schemas/tlc/1.0.8/statuses/S0095.json +34 -0
  490. data/schemas/tlc/1.0.8/statuses/S0096.json +175 -0
  491. data/schemas/tlc/1.0.8/statuses/S0201.json +67 -0
  492. data/schemas/tlc/1.0.8/statuses/S0202.json +67 -0
  493. data/schemas/tlc/1.0.8/statuses/S0203.json +67 -0
  494. data/schemas/tlc/1.0.8/statuses/S0204.json +283 -0
  495. data/schemas/tlc/1.0.8/statuses/statuses.json +482 -0
  496. data/schemas/tlc/1.0.8/sxl.json +73 -0
  497. data/schemas/tlc/1.0.8/sxl.yaml +1059 -0
  498. data/schemas/tlc/1.0.9/alarms/A0001.json +7 -0
  499. data/schemas/tlc/1.0.9/alarms/A0002.json +7 -0
  500. data/schemas/tlc/1.0.9/alarms/A0003.json +7 -0
  501. data/schemas/tlc/1.0.9/alarms/A0004.json +7 -0
  502. data/schemas/tlc/1.0.9/alarms/A0005.json +7 -0
  503. data/schemas/tlc/1.0.9/alarms/A0006.json +7 -0
  504. data/schemas/tlc/1.0.9/alarms/A0007.json +7 -0
  505. data/schemas/tlc/1.0.9/alarms/A0008.json +40 -0
  506. data/schemas/tlc/1.0.9/alarms/A0009.json +7 -0
  507. data/schemas/tlc/1.0.9/alarms/A0101.json +7 -0
  508. data/schemas/tlc/1.0.9/alarms/A0201.json +39 -0
  509. data/schemas/tlc/1.0.9/alarms/A0202.json +39 -0
  510. data/schemas/tlc/1.0.9/alarms/A0301.json +111 -0
  511. data/schemas/tlc/1.0.9/alarms/A0302.json +137 -0
  512. data/schemas/tlc/1.0.9/alarms/alarms.json +238 -0
  513. data/schemas/tlc/1.0.9/commands/M0001.json +125 -0
  514. data/schemas/tlc/1.0.9/commands/M0002.json +91 -0
  515. data/schemas/tlc/1.0.9/commands/M0003.json +91 -0
  516. data/schemas/tlc/1.0.9/commands/M0004.json +64 -0
  517. data/schemas/tlc/1.0.9/commands/M0005.json +91 -0
  518. data/schemas/tlc/1.0.9/commands/M0006.json +91 -0
  519. data/schemas/tlc/1.0.9/commands/M0007.json +64 -0
  520. data/schemas/tlc/1.0.9/commands/M0008.json +91 -0
  521. data/schemas/tlc/1.0.9/commands/M0010.json +64 -0
  522. data/schemas/tlc/1.0.9/commands/M0011.json +64 -0
  523. data/schemas/tlc/1.0.9/commands/M0012.json +58 -0
  524. data/schemas/tlc/1.0.9/commands/M0013.json +58 -0
  525. data/schemas/tlc/1.0.9/commands/M0019.json +118 -0
  526. data/schemas/tlc/1.0.9/commands/M0103.json +82 -0
  527. data/schemas/tlc/1.0.9/commands/M0104.json +199 -0
  528. data/schemas/tlc/1.0.9/commands/command_requests.json +7 -0
  529. data/schemas/tlc/1.0.9/commands/command_responses.json +7 -0
  530. data/schemas/tlc/1.0.9/commands/commands.json +254 -0
  531. data/schemas/tlc/1.0.9/statuses/S0001.json +116 -0
  532. data/schemas/tlc/1.0.9/statuses/S0002.json +34 -0
  533. data/schemas/tlc/1.0.9/statuses/S0003.json +55 -0
  534. data/schemas/tlc/1.0.9/statuses/S0004.json +55 -0
  535. data/schemas/tlc/1.0.9/statuses/S0005.json +40 -0
  536. data/schemas/tlc/1.0.9/statuses/S0006.json +67 -0
  537. data/schemas/tlc/1.0.9/statuses/S0007.json +67 -0
  538. data/schemas/tlc/1.0.9/statuses/S0008.json +67 -0
  539. data/schemas/tlc/1.0.9/statuses/S0009.json +67 -0
  540. data/schemas/tlc/1.0.9/statuses/S0010.json +67 -0
  541. data/schemas/tlc/1.0.9/statuses/S0011.json +67 -0
  542. data/schemas/tlc/1.0.9/statuses/S0012.json +67 -0
  543. data/schemas/tlc/1.0.9/statuses/S0013.json +67 -0
  544. data/schemas/tlc/1.0.9/statuses/S0014.json +40 -0
  545. data/schemas/tlc/1.0.9/statuses/S0015.json +40 -0
  546. data/schemas/tlc/1.0.9/statuses/S0016.json +40 -0
  547. data/schemas/tlc/1.0.9/statuses/S0017.json +40 -0
  548. data/schemas/tlc/1.0.9/statuses/S0018.json +40 -0
  549. data/schemas/tlc/1.0.9/statuses/S0019.json +40 -0
  550. data/schemas/tlc/1.0.9/statuses/S0020.json +67 -0
  551. data/schemas/tlc/1.0.9/statuses/S0021.json +35 -0
  552. data/schemas/tlc/1.0.9/statuses/S0025.json +181 -0
  553. data/schemas/tlc/1.0.9/statuses/S0091.json +58 -0
  554. data/schemas/tlc/1.0.9/statuses/S0092.json +58 -0
  555. data/schemas/tlc/1.0.9/statuses/S0095.json +34 -0
  556. data/schemas/tlc/1.0.9/statuses/S0096.json +175 -0
  557. data/schemas/tlc/1.0.9/statuses/S0201.json +67 -0
  558. data/schemas/tlc/1.0.9/statuses/S0202.json +67 -0
  559. data/schemas/tlc/1.0.9/statuses/S0203.json +67 -0
  560. data/schemas/tlc/1.0.9/statuses/S0204.json +283 -0
  561. data/schemas/tlc/1.0.9/statuses/statuses.json +482 -0
  562. data/schemas/tlc/1.0.9/sxl.json +73 -0
  563. data/schemas/tlc/1.0.9/sxl.yaml +1059 -0
  564. data/schemas/tlc/1.1/alarms/A0001.json +7 -0
  565. data/schemas/tlc/1.1/alarms/A0002.json +7 -0
  566. data/schemas/tlc/1.1/alarms/A0003.json +7 -0
  567. data/schemas/tlc/1.1/alarms/A0004.json +7 -0
  568. data/schemas/tlc/1.1/alarms/A0005.json +7 -0
  569. data/schemas/tlc/1.1/alarms/A0006.json +7 -0
  570. data/schemas/tlc/1.1/alarms/A0007.json +38 -0
  571. data/schemas/tlc/1.1/alarms/A0008.json +40 -0
  572. data/schemas/tlc/1.1/alarms/A0009.json +7 -0
  573. data/schemas/tlc/1.1/alarms/A0010.json +7 -0
  574. data/schemas/tlc/1.1/alarms/A0101.json +7 -0
  575. data/schemas/tlc/1.1/alarms/A0201.json +39 -0
  576. data/schemas/tlc/1.1/alarms/A0202.json +39 -0
  577. data/schemas/tlc/1.1/alarms/A0301.json +111 -0
  578. data/schemas/tlc/1.1/alarms/A0302.json +137 -0
  579. data/schemas/tlc/1.1/alarms/alarms.json +254 -0
  580. data/schemas/tlc/1.1/commands/M0001.json +125 -0
  581. data/schemas/tlc/1.1/commands/M0002.json +91 -0
  582. data/schemas/tlc/1.1/commands/M0003.json +91 -0
  583. data/schemas/tlc/1.1/commands/M0004.json +64 -0
  584. data/schemas/tlc/1.1/commands/M0005.json +91 -0
  585. data/schemas/tlc/1.1/commands/M0006.json +91 -0
  586. data/schemas/tlc/1.1/commands/M0007.json +64 -0
  587. data/schemas/tlc/1.1/commands/M0008.json +91 -0
  588. data/schemas/tlc/1.1/commands/M0010.json +64 -0
  589. data/schemas/tlc/1.1/commands/M0011.json +64 -0
  590. data/schemas/tlc/1.1/commands/M0012.json +58 -0
  591. data/schemas/tlc/1.1/commands/M0013.json +58 -0
  592. data/schemas/tlc/1.1/commands/M0014.json +85 -0
  593. data/schemas/tlc/1.1/commands/M0015.json +91 -0
  594. data/schemas/tlc/1.1/commands/M0016.json +58 -0
  595. data/schemas/tlc/1.1/commands/M0017.json +58 -0
  596. data/schemas/tlc/1.1/commands/M0018.json +91 -0
  597. data/schemas/tlc/1.1/commands/M0019.json +118 -0
  598. data/schemas/tlc/1.1/commands/M0020.json +118 -0
  599. data/schemas/tlc/1.1/commands/M0021.json +58 -0
  600. data/schemas/tlc/1.1/commands/M0103.json +82 -0
  601. data/schemas/tlc/1.1/commands/M0104.json +199 -0
  602. data/schemas/tlc/1.1/commands/command_requests.json +7 -0
  603. data/schemas/tlc/1.1/commands/command_responses.json +7 -0
  604. data/schemas/tlc/1.1/commands/commands.json +366 -0
  605. data/schemas/tlc/1.1/statuses/S0001.json +116 -0
  606. data/schemas/tlc/1.1/statuses/S0002.json +34 -0
  607. data/schemas/tlc/1.1/statuses/S0003.json +55 -0
  608. data/schemas/tlc/1.1/statuses/S0004.json +55 -0
  609. data/schemas/tlc/1.1/statuses/S0005.json +40 -0
  610. data/schemas/tlc/1.1/statuses/S0006.json +67 -0
  611. data/schemas/tlc/1.1/statuses/S0007.json +95 -0
  612. data/schemas/tlc/1.1/statuses/S0008.json +95 -0
  613. data/schemas/tlc/1.1/statuses/S0009.json +95 -0
  614. data/schemas/tlc/1.1/statuses/S0010.json +95 -0
  615. data/schemas/tlc/1.1/statuses/S0011.json +95 -0
  616. data/schemas/tlc/1.1/statuses/S0012.json +95 -0
  617. data/schemas/tlc/1.1/statuses/S0013.json +67 -0
  618. data/schemas/tlc/1.1/statuses/S0014.json +68 -0
  619. data/schemas/tlc/1.1/statuses/S0015.json +68 -0
  620. data/schemas/tlc/1.1/statuses/S0016.json +40 -0
  621. data/schemas/tlc/1.1/statuses/S0017.json +40 -0
  622. data/schemas/tlc/1.1/statuses/S0018.json +40 -0
  623. data/schemas/tlc/1.1/statuses/S0019.json +40 -0
  624. data/schemas/tlc/1.1/statuses/S0020.json +67 -0
  625. data/schemas/tlc/1.1/statuses/S0021.json +35 -0
  626. data/schemas/tlc/1.1/statuses/S0022.json +34 -0
  627. data/schemas/tlc/1.1/statuses/S0023.json +35 -0
  628. data/schemas/tlc/1.1/statuses/S0024.json +35 -0
  629. data/schemas/tlc/1.1/statuses/S0025.json +229 -0
  630. data/schemas/tlc/1.1/statuses/S0026.json +34 -0
  631. data/schemas/tlc/1.1/statuses/S0027.json +34 -0
  632. data/schemas/tlc/1.1/statuses/S0028.json +34 -0
  633. data/schemas/tlc/1.1/statuses/S0029.json +34 -0
  634. data/schemas/tlc/1.1/statuses/S0030.json +34 -0
  635. data/schemas/tlc/1.1/statuses/S0031.json +34 -0
  636. data/schemas/tlc/1.1/statuses/S0091.json +45 -0
  637. data/schemas/tlc/1.1/statuses/S0092.json +45 -0
  638. data/schemas/tlc/1.1/statuses/S0095.json +34 -0
  639. data/schemas/tlc/1.1/statuses/S0096.json +175 -0
  640. data/schemas/tlc/1.1/statuses/S0097.json +61 -0
  641. data/schemas/tlc/1.1/statuses/S0098.json +82 -0
  642. data/schemas/tlc/1.1/statuses/S0201.json +67 -0
  643. data/schemas/tlc/1.1/statuses/S0202.json +67 -0
  644. data/schemas/tlc/1.1/statuses/S0203.json +67 -0
  645. data/schemas/tlc/1.1/statuses/S0204.json +283 -0
  646. data/schemas/tlc/1.1/statuses/S0205.json +61 -0
  647. data/schemas/tlc/1.1/statuses/S0206.json +61 -0
  648. data/schemas/tlc/1.1/statuses/S0207.json +61 -0
  649. data/schemas/tlc/1.1/statuses/S0208.json +229 -0
  650. data/schemas/tlc/1.1/statuses/statuses.json +738 -0
  651. data/schemas/tlc/1.1/sxl.json +73 -0
  652. data/schemas/tlc/1.1/sxl.yaml +1749 -0
  653. metadata +784 -0
@@ -0,0 +1,1059 @@
1
+ ---
2
+ meta:
3
+ name: tlc
4
+ description: Traffic Light Controllers
5
+ version: 1.0.10
6
+ objects:
7
+ Traffic Light Controller:
8
+ description:
9
+ aggregated_status:
10
+ 1:
11
+ title: Local mode
12
+ description: Traffic Light Controller is in local mode. NTS has no control.
13
+ 2:
14
+ title: No Communications
15
+ 3:
16
+ title: High Priority Fault
17
+ description: Traffic Light Controller is in fail safe mode; e.g. yellow flash
18
+ or dark mode
19
+ 4:
20
+ title: Medium Priority Fault
21
+ description: |-
22
+ Traffic Light Controller has a medium priority fault, but not in fail safe mode.
23
+ E.g. several lamp faults or detector fault
24
+ 5:
25
+ title: Low Priority Fault
26
+ description: Traffic Light Controller has a low priority fault. E.g. Detector
27
+ fault
28
+ 6:
29
+ title: Connected / Normal - In Use
30
+ 7:
31
+ title: Connected / Normal - Idle
32
+ description: |-
33
+ Traffic Light Controller dark according to configuration.
34
+ NOTE! When dark according to configuration the controller is considered to be in use
35
+ 8:
36
+ title: Not Connected
37
+ functional_position:
38
+ functional_state:
39
+ alarms:
40
+ A0001:
41
+ description: |-
42
+ Serious hardware error.
43
+ 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.
44
+ priority: 2
45
+ category: D
46
+ A0002:
47
+ description: |-
48
+ Less serious hardware error.
49
+ Is a "minor fault" defined according to 3.11 in EN12675.
50
+ priority: 3
51
+ category: D
52
+ A0003:
53
+ description: |-
54
+ Serious configuration error.
55
+ Is 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.
56
+ priority: 2
57
+ category: D
58
+ A0004:
59
+ description: |-
60
+ Less serious configuration error.
61
+ Is a "minor fault" defined according to 3.11 in EN12675.
62
+ priority: 3
63
+ category: D
64
+ A0005:
65
+ description: |-
66
+ Communication error between traffic light controllers / synchronisation error.
67
+ Is a "minor fault" defined according to 3.11 in EN12675.
68
+ priority: 3
69
+ category: D
70
+ A0006:
71
+ description: |-
72
+ Safety error
73
+ Is 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.
74
+ priority: 2
75
+ category: D
76
+ A0007:
77
+ description: |-
78
+ Communication error between one or multiple traffic light controllers and central control system.
79
+ Used for communication errors with the central system. Includes NTP connection loss if the TLC is configured to use NTP.
80
+ Is a "minor fault" defined according to 3.11 in EN12675.
81
+ priority: 3
82
+ category: D
83
+ A0009:
84
+ description: |-
85
+ Other error.
86
+ Used for other errors not covered by any other alarm type
87
+ Is a "minor fault" defined according to 3.11 in EN12675.
88
+ priority: 3
89
+ category: D
90
+ statuses:
91
+ S0001:
92
+ description: |-
93
+ Signal group status.
94
+ Provides the status of each signal group, including basic information such as green, yellow and red. But also detailed technical information.
95
+ Can be used to draw a live signal group diagram as well provide diagnostic information about the performance of the controller.
96
+ arguments:
97
+ signalgroupstatus:
98
+ type: string
99
+ description: Signal group status as text field
100
+ range: "[text]"
101
+ pattern: "^[a-hA-G0-9N-P]*$"
102
+ cyclecounter:
103
+ type: integer
104
+ description: Cycle counter
105
+ range: "[0-999]"
106
+ basecyclecounter:
107
+ type: integer
108
+ description: Base cycle counter
109
+ range: "[0-999]"
110
+ stage:
111
+ type: integer
112
+ description: Current stage (isolated)
113
+ range: "[0-999]"
114
+ S0002:
115
+ description: |-
116
+ Detector logic status.
117
+ Provides the status of all detector logics of the controller.
118
+ Can 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.
119
+ arguments:
120
+ detectorlogicstatus:
121
+ type: string
122
+ description: Detector logic status as text field
123
+ range: "[text]"
124
+ S0003:
125
+ description: |-
126
+ Input status.
127
+ Input (1-255) of the controllers general purpose I/O.
128
+ Input is used where the traffic light controller must react to external control. It could be external detectors, bus priority, and much more.
129
+ arguments:
130
+ inputstatus:
131
+ type: string
132
+ description: Input status as text field
133
+ range: "[text]"
134
+ extendedinputstatus:
135
+ type: string
136
+ description: Extended input status as text field
137
+ range: "[text]"
138
+ S0004:
139
+ description: |-
140
+ Output status.
141
+ Output (1-255) of the controllers general purpose I/O.
142
+ Can 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.
143
+ arguments:
144
+ outputstatus:
145
+ type: string
146
+ description: Output status as text field
147
+ range: "[text]"
148
+ extendedoutputstatus:
149
+ type: string
150
+ description: Extended output status as text field
151
+ range: "[text]"
152
+ S0005:
153
+ description: |-
154
+ Traffic Light Controller starting.
155
+ The traffic signal is starting, e.g. it is in startup mode and has not begun working normally yet.
156
+ During startup mode the traffic controller shows dark, red, yellow flash or using the predetermined start cycle (minimum times).
157
+ arguments:
158
+ status:
159
+ type: boolean
160
+ description: |-
161
+ False: Controller is not in start up mode
162
+ True: Controller is currently in start up mode
163
+ S0006:
164
+ description: |-
165
+ Emergency stage.
166
+ The status is active during emergency prioritization.
167
+ Used in situations where full priority is given in the emergency vehicle program.
168
+ arguments:
169
+ status:
170
+ type: boolean
171
+ description: |-
172
+ False: Emergency stage inactive
173
+ True: Emergency stage active
174
+ emergencystage:
175
+ type: integer
176
+ description: Number of emergency stage
177
+ range: "[1-255]"
178
+ S0007:
179
+ description: |-
180
+ Controller switched on.
181
+ The controller is active and is not in dark mode.
182
+ Used to determine if the controller is operating, e.g. it shows red, green or yellow to the vehicles.
183
+ During maintenance work the controller might be using dark mode (no output to the signal heads).
184
+ arguments:
185
+ intersection:
186
+ list: true
187
+ type: integer
188
+ description: |-
189
+ 0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
190
+ Other value: Intersection number
191
+ range: "[0-255]"
192
+ status:
193
+ list: true
194
+ type: boolean
195
+ description: |-
196
+ False: Traffic Light Controller in dark mode
197
+ True: Traffic Light Controller not in dark mode
198
+ S0008:
199
+ description: |-
200
+ Manual control.
201
+ Traffic control deactivated in controller
202
+ Signal timings is controlled manually by service personnel using the operating panel of the controller.
203
+ arguments:
204
+ intersection:
205
+ list: true
206
+ type: integer
207
+ description: |-
208
+ 0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
209
+ Other value: Intersection number
210
+ range: "[0-255]"
211
+ status:
212
+ list: true
213
+ type: boolean
214
+ description: |-
215
+ False: Manual control inactive
216
+ True: Manual control active
217
+ S0009:
218
+ description: |-
219
+ Fixed time control.
220
+ Traffic actuated control deactivated and a pre-timed control is used.
221
+ Usually only used in case normal detectors can't be used, e.g. during maintenance work.
222
+ arguments:
223
+ intersection:
224
+ list: true
225
+ type: integer
226
+ description: |-
227
+ 0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
228
+ Other value: Intersection number
229
+ range: "[0-255]"
230
+ status:
231
+ list: true
232
+ type: boolean
233
+ description: |-
234
+ False: Fixed time control inactive
235
+ True: Fixed time control active
236
+ S0010:
237
+ description: |-
238
+ Isolated control.
239
+ Isolated control mode indicates that the controller operates independently of any other traffic light controllers. This may different depending on traffic program (time plan).
240
+ Used to determine if the controller is operating independently or operating with other controllers (coordination).
241
+ arguments:
242
+ intersection:
243
+ list: true
244
+ type: integer
245
+ description: |-
246
+ 0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
247
+ Other value: Intersection number
248
+ range: "[0-255]"
249
+ status:
250
+ list: true
251
+ type: boolean
252
+ description: |-
253
+ False: Isolated control disabled
254
+ True: Isolated control enabled (Vehicle actuated control or Fixed time control)
255
+ S0011:
256
+ description: |-
257
+ Yellow flash.
258
+ The controller shows yellow flash.
259
+ Yellow flash may be used during a serious fault (depending on configuration) or maintenance work. It can also be manually set using M0001.
260
+ arguments:
261
+ intersection:
262
+ list: true
263
+ type: integer
264
+ description: |-
265
+ 0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
266
+ Other value: Intersection number
267
+ range: "[0-255]"
268
+ status:
269
+ list: true
270
+ type: boolean
271
+ description: |-
272
+ False: Yellow flash disabled
273
+ True: Yellow flash enabled
274
+ S0012:
275
+ description: |-
276
+ All red.
277
+ The controller show all red.
278
+ All red can be manually set using the controllers operating panel during maintenance work.
279
+ arguments:
280
+ intersection:
281
+ list: true
282
+ type: integer
283
+ description: |-
284
+ 0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
285
+ Other value: Intersection number
286
+ range: "[0-255]"
287
+ status:
288
+ list: true
289
+ type: boolean
290
+ description: |-
291
+ False: All red disabled
292
+ True: All red enabled
293
+ S0013:
294
+ description: |-
295
+ Police key
296
+ The controller is forced to dark mode or yellow flash.
297
+ The "police key" is a external control switch present in some controllers that manually switches the controller to either dark mode or yellow flash.
298
+ arguments:
299
+ intersection:
300
+ list: true
301
+ type: integer
302
+ description: |-
303
+ 0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
304
+ Other value: Intersection number
305
+ range: "[0-255]"
306
+ status:
307
+ list: true
308
+ type: integer
309
+ values:
310
+ 0: disabled
311
+ 1: dark mode
312
+ 2: yellow flash
313
+ S0014:
314
+ description: |-
315
+ Current time plan.
316
+ The current time plan (signal program) used in the controller. There may be 1-255 predefined time plans.
317
+ The 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.
318
+ arguments:
319
+ status:
320
+ type: integer
321
+ description: Current time plan
322
+ range: "[1-255]"
323
+ S0015:
324
+ description: |-
325
+ Current traffic situation.
326
+ The current traffic situation used in the controller.
327
+ Used 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).
328
+ Traffic 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.
329
+ arguments:
330
+ status:
331
+ type: integer
332
+ description: Current traffic situation
333
+ range: "[1-255]"
334
+ S0016:
335
+ description: |-
336
+ Number of detector logics.
337
+ Can be used by the management system to check the number of detector logics configured in the controller.
338
+ arguments:
339
+ number:
340
+ type: long
341
+ description: Number of detector logics
342
+ range: "[1-65025]"
343
+ S0017:
344
+ description: |-
345
+ Number of signal groups.
346
+ Can be used for the management system to check the number of signal groups configured in the controller.
347
+ arguments:
348
+ number:
349
+ type: long
350
+ description: Number of signal groups
351
+ range: "[1-65025]"
352
+ S0018:
353
+ description: |-
354
+ Number of time plans
355
+ Can be used for the management system to check the number of time plans configured in the controller.
356
+ arguments:
357
+ number:
358
+ type: long
359
+ description: Number of time plans (depreciated)
360
+ range: "[1-65025]"
361
+ S0019:
362
+ description: |-
363
+ Number of traffic situations.
364
+ Can be used for the management system to check the number of traffic situations configured in the controller.
365
+ arguments:
366
+ number:
367
+ type: long
368
+ description: Number of traffic situations
369
+ range: "[1-65025]"
370
+ S0020:
371
+ description: |-
372
+ Control mode.
373
+ Can be used for the management system to check the current control mode (startup, normal, standby, failure, test).
374
+ arguments:
375
+ intersection:
376
+ list: true
377
+ type: integer
378
+ description: |-
379
+ 0: Not applicable (only one intersection exists or applicable for all intersection of the traffic light controller)
380
+ Other value: Intersection number
381
+ range: "[0-255]"
382
+ controlmode:
383
+ list: true
384
+ type: string
385
+ values:
386
+ startup: Startup mode
387
+ control: Normal control
388
+ standby: Standby mode
389
+ failure: Failure mode
390
+ test: Test mode
391
+ S0021:
392
+ description: |-
393
+ Manually set detector logic.
394
+ Provides status of detector logic (1-255) regarding if they are either forced to true or false.
395
+ Can be used to connect RSMP compatible detection equipment to the traffic light controller. Can also be used for prioritization.
396
+ arguments:
397
+ detectorlogics:
398
+ type: string
399
+ description: Manually set detector logics (1/0) as text field
400
+ range: "[text]"
401
+ pattern: "^[01]*$"
402
+ S0091:
403
+ description: |-
404
+ Operator logged in/out OP-panel.
405
+ Provides information if maintenance personnel is currently working on site.
406
+ arguments:
407
+ user:
408
+ description: |-
409
+ nobody: No one logged in
410
+ <username>: User currently logged in
411
+ type: string
412
+ status:
413
+ type: string
414
+ values:
415
+ login: Somebody currently logged in
416
+ logout: Nobody currently logged in
417
+ S0092:
418
+ description: |-
419
+ Operator logged in/out web-interface.
420
+ Provides information if maintenance personnel is currently working with the controller.
421
+ arguments:
422
+ user:
423
+ description: |-
424
+ nobody: No one logged in
425
+ <username>: User currently logged in
426
+ type: string
427
+ status:
428
+ type: string
429
+ values:
430
+ login: Somebody currently logged in
431
+ logout: Nobody currently logged in
432
+ S0095:
433
+ description: |-
434
+ Version of Traffic Light Controller.
435
+ Provides diagnostic version information.
436
+ arguments:
437
+ status:
438
+ type: string
439
+ description: Manufacturer, product name and version of traffic light controller
440
+ range: "[text]"
441
+ S0096:
442
+ description: |-
443
+ Current date and time
444
+ Provides diagnostic information about the current date and time set in the controller.
445
+ arguments:
446
+ year:
447
+ type: integer
448
+ description: 'Year according to format YYYY. NOTE: UTC is used'
449
+ range: YYYY
450
+ month:
451
+ type: integer
452
+ description: 'Month (01-12) according to format MM. Note: UTC is used'
453
+ range: MM
454
+ day:
455
+ type: integer
456
+ description: 'Day of month (01-31) according to format DD. Note: UTC
457
+ is used'
458
+ range: DD
459
+ hour:
460
+ type: integer
461
+ description: 'Hour of day (00-23) according to format DD. Note: UTC is
462
+ used'
463
+ range: HH
464
+ minute:
465
+ type: integer
466
+ description: 'Minute (00-59) according to format MM. Note: UTC is used'
467
+ range: MM
468
+ second:
469
+ type: integer
470
+ description: 'Second (00-59) according to format SS. Note: UTC is used'
471
+ range: SS
472
+ commands:
473
+ M0001:
474
+ description: |-
475
+ Sets functional position.
476
+ Sets the controller to yellow flash, dark mode or normal control.
477
+ Requires security code 2.
478
+ arguments:
479
+ status:
480
+ list: true
481
+ description: Set operating mode
482
+ type: string
483
+ values:
484
+ NormalControl: Normal Control
485
+ YellowFlash: Enables yellow flash
486
+ Dark: Enables dark mode
487
+ securityCode:
488
+ list: true
489
+ description: Security code 2
490
+ type: string
491
+ timeout:
492
+ list: true
493
+ description: |-
494
+ Time in minutes until controller automatically reverts to previous functional position.
495
+ 0=no automatic return
496
+ type: integer
497
+ min: 0
498
+ max: 1440
499
+ intersection:
500
+ list: true
501
+ description: Intersection number
502
+ type: integer
503
+ min: 0
504
+ max: 255
505
+ command: setValue
506
+ M0002:
507
+ description: |-
508
+ Sets current time plan.
509
+ Change of traffic program of the traffic light controller.
510
+ Typical usages is scenario based control where change of program is used to change signal timings etc.
511
+ This command changes the signal timings for optimal traffic flow.
512
+ Requires security code 2
513
+ arguments:
514
+ status:
515
+ type: boolean
516
+ description: |-
517
+ False: Controller uses time plan according to programming
518
+ True: Controller uses time plan according to command
519
+ securityCode:
520
+ type: string
521
+ description: Security code 2
522
+ range: "[text]"
523
+ timeplan:
524
+ type: integer
525
+ description: designation of time plan
526
+ range: "[1-255]"
527
+ command: setPlan
528
+ M0003:
529
+ description: |-
530
+ Sets traffic situation the controller uses.
531
+ Used 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).
532
+ Traffic 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.
533
+ Requires security code 2
534
+ arguments:
535
+ status:
536
+ type: boolean
537
+ description: |-
538
+ False: Controller uses traffic situation according to own programming
539
+ True: Controller uses traffic situation according to command
540
+ securityCode:
541
+ type: string
542
+ description: Security code 2
543
+ range: "[text]"
544
+ traficsituation:
545
+ type: integer
546
+ description: designation of traficsituation
547
+ range: "[1-255]"
548
+ command: setTrafficSituation
549
+ M0004:
550
+ description: |-
551
+ Restarts Traffic Light Controller.
552
+ Used in the event of serious faults in the device where a restart is considered to be able to remedy a problem.
553
+ Requires security code 2
554
+ arguments:
555
+ status:
556
+ type: boolean
557
+ description: 'True: Restart controller'
558
+ securityCode:
559
+ type: string
560
+ description: Security code 2
561
+ range: "[text]"
562
+ command: setRestart
563
+ M0005:
564
+ description: |-
565
+ Activate emergency route.
566
+ The 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.
567
+ Should be used in situations where full priority is given in the emergency vehicle program.
568
+ Requires security code 2.
569
+ arguments:
570
+ status:
571
+ type: boolean
572
+ description: |-
573
+ False: Activate emergency route
574
+ True: Deactivate emergency route
575
+ securityCode:
576
+ type: string
577
+ description: Security code 2
578
+ range: "[text]"
579
+ emergencyroute:
580
+ type: integer
581
+ description: Number of emergency route
582
+ range: "[1-255]"
583
+ command: setEmergency
584
+ M0006:
585
+ description: |-
586
+ Activate input.
587
+ Set given input (1-255) of the controllers general purpose I/O to either true or false.
588
+ The function can provide an input to the traffic light controller on which a predefined action can be taken.
589
+ Can be used for all types of input where the traffic light controller must react to external control.
590
+ Typical usages are bus priority, coordination between traffic controllers, external control systems, and much more.
591
+ Requires security code 2.
592
+ arguments:
593
+ status:
594
+ type: boolean
595
+ description: |-
596
+ False: Deactivate input
597
+ True: Activate input
598
+ securityCode:
599
+ type: string
600
+ description: Security code 2
601
+ range: "[text]"
602
+ input:
603
+ type: integer
604
+ description: Number of Input
605
+ range: "[1-255]"
606
+ command: setInput
607
+ M0007:
608
+ description: |-
609
+ Activate fixed time control.
610
+ Deactivates the traffic actuated control using detectors and activates pre-timed control.
611
+ Can be used in case normal detectors can't be used, e.g. during maintenance work.
612
+ Requires security code 2.
613
+ arguments:
614
+ status:
615
+ type: boolean
616
+ description: |-
617
+ False: Deactivate fixed time control
618
+ True: Activate fixed time control
619
+ securityCode:
620
+ type: string
621
+ description: Security code 2
622
+ range: "[text]"
623
+ command: setFixedTime
624
+ M0012:
625
+ description: |-
626
+ Request start or stop of a series of signal groups.
627
+ Starts or stops several signal groups.
628
+ This 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.
629
+ Although 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.
630
+ Intended for use with coordination of signaling systems where a traffic light controller communicates with neighboring controllers.
631
+ Only used when a primary controller orders signal group of other controller to green or red (Coordination with external control bits).
632
+ May also include purposes for adaptive control where a UTC system or a local traffic light controller takes over the phase control (stage control).
633
+ Requires security code 2.
634
+ arguments:
635
+ status:
636
+ type: string
637
+ description: |-
638
+ Orders signal groups to green or red. Sets a block of 16 signal groups at a time. Can be repeated to set several blocks of 16 signal groups. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon is used in example below.
639
+
640
+ 1=Order signal group to green
641
+ 0=Order signal group to red
642
+
643
+ Format: [Offset],[Bits to set],[Bits to unset]:…
644
+
645
+ Offset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.
646
+
647
+ Example 1:
648
+ "5, 4134, 65" sets input 6,7,10,17 = on and 5,11 = off
649
+ (Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)
650
+
651
+ Example 2:
652
+ "22, 1, 4" sets input 22 = on and 24 = off
653
+ (Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)
654
+
655
+ And both these examples could be sent in the same message as:
656
+ "5,4143,65:22,1,4"
657
+
658
+ Such a message would order signal group 6,7,10,17,22 to green and signal group 5,11,24 to red
659
+ range: "[text]"
660
+ securityCode:
661
+ type: string
662
+ description: Security code 2
663
+ range: "[text]"
664
+ command: setStart
665
+ M0013:
666
+ description: |-
667
+ Activate a series of inputs.
668
+ Set given inputs (1-255) of the controllers general purpose I/O to either true or false.
669
+ 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.
670
+ 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.
671
+ Requires security code 2
672
+ arguments:
673
+ status:
674
+ type: string
675
+ description: |-
676
+ Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon, ":" is used in example below.
677
+
678
+ Format: [Offset],[Bits to set],[Bits to unset]:…
679
+
680
+ Offset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.
681
+
682
+ Example 1:
683
+ "5, 4134, 65" sets input 6,7,10,17 = on and 5,11 = off
684
+ (Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)
685
+
686
+ Example 2:
687
+ "22, 1, 4" sets input 22 = on and 24 = off
688
+ (Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)
689
+
690
+ And both thease examples could be sent in the same message as:
691
+ "5,4143:65:22,1,4"
692
+
693
+ Such a message would activate input 6,7,10,17,22 and deactivate input 5,11,24
694
+ range: "[text]"
695
+ securityCode:
696
+ type: string
697
+ description: Security code 2
698
+ range: "[text]"
699
+ command: setInput
700
+ M0019:
701
+ description: |-
702
+ Force input.
703
+ Force 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.
704
+ Can be used for bus priority, coordination between traffic controllers, external control systems, and much more.
705
+ Requires security code 2.
706
+ arguments:
707
+ status:
708
+ type: boolean
709
+ description: |-
710
+ False: Force input
711
+ True: Release input
712
+ securityCode:
713
+ type: string
714
+ description: Security code 2
715
+ range: "[text]"
716
+ input:
717
+ type: integer
718
+ description: Number of Input
719
+ range: "[1-255]"
720
+ inputValue:
721
+ type: boolean
722
+ description: |-
723
+ False: input forced to False
724
+ True: input forced to True
725
+ command: setInput
726
+ M0103:
727
+ description: |-
728
+ Set security code.
729
+ Change the security code to use when sending commands
730
+ Security 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.
731
+ arguments:
732
+ status:
733
+ type: string
734
+ values:
735
+ Level1: Change security code 1
736
+ Level2: Change security code 2
737
+ oldSecurityCode:
738
+ type: string
739
+ description: Previous security code
740
+ range: "[text]"
741
+ newSecurityCode:
742
+ type: string
743
+ description: New security code
744
+ range: "[text]"
745
+ command: setSecurityCode
746
+ M0104:
747
+ description: |-
748
+ Set clock.
749
+ Can 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.
750
+ Requires security code 1
751
+ arguments:
752
+ securityCode:
753
+ type: string
754
+ description: Security code 1
755
+ range: "[text]"
756
+ year:
757
+ type: integer
758
+ description: |-
759
+ Changes internal clock. Note: UTC is used
760
+ Year according to YYYY
761
+ range: "[YYYY]"
762
+ month:
763
+ type: integer
764
+ description: |-
765
+ Changes internal clock. Note: UTC is used
766
+ Month according to MM (01-12)
767
+ range: "[MM]"
768
+ day:
769
+ type: integer
770
+ description: |-
771
+ Changes internal clock. Note: UTC is used
772
+ Day in month according to DD (01-31)
773
+ range: "[DD]"
774
+ hour:
775
+ type: integer
776
+ description: |-
777
+ Changes internal clock. Note: UTC is used
778
+ Hour according to HH (00-23)
779
+ range: "[HH]"
780
+ minute:
781
+ type: integer
782
+ description: |-
783
+ Changes internal clock. Note: UTC is used
784
+ Minute according to MM (00-59)
785
+ range: "[MM]"
786
+ second:
787
+ type: integer
788
+ description: |-
789
+ Changes internal clock. Note: UTC is used
790
+ Second according to SS (00-59)
791
+ range: "[SS]"
792
+ command: setDate
793
+ Signal group:
794
+ description:
795
+ alarms:
796
+ A0008:
797
+ description: |-
798
+ Dead lock error.
799
+ Used for dead lock errors.
800
+ For 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.
801
+ Is 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.
802
+ priority: 2
803
+ category: D
804
+ arguments:
805
+ timeplan:
806
+ type: integer
807
+ description: Current time plan
808
+ range: "[designation]"
809
+ A0101:
810
+ description: |-
811
+ Pushbutton error.
812
+ Used for push buttons.
813
+ priority: 3
814
+ category: D
815
+ A0201:
816
+ description: |-
817
+ Serious lamp error.
818
+ Used for lamp errors.
819
+ Is 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.
820
+ priority: 2
821
+ category: D
822
+ arguments:
823
+ color:
824
+ type: string
825
+ description: Color of lamp
826
+ values:
827
+ red: red
828
+ yellow: yellow
829
+ green: green
830
+ A0202:
831
+ description: |-
832
+ Less serious lamp error.
833
+ Used for lamp errors.
834
+ Is a "minor fault" defined according to 3.11 in EN12675.
835
+ priority: 3
836
+ category: D
837
+ arguments:
838
+ color:
839
+ type: string
840
+ description: Color of lamp
841
+ values:
842
+ red: red
843
+ yellow: yellow
844
+ green: green
845
+ statuses:
846
+ commands:
847
+ M0010:
848
+ description: |-
849
+ Start of signal group. Orders a signal group to green.
850
+ Although 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.
851
+ Intended 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).
852
+ Requires security code 2
853
+ arguments:
854
+ status:
855
+ type: boolean
856
+ description: |-
857
+ False: No command (default)
858
+ True: Order a signal group to green
859
+ securityCode:
860
+ type: string
861
+ description: Security code 2
862
+ range: "[text]"
863
+ command: setStart
864
+ M0011:
865
+ description: |-
866
+ Stop of signal group. Orders a signal group to red.
867
+ Although 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.
868
+ Intended 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).
869
+ Requires security code 2
870
+ arguments:
871
+ status:
872
+ type: boolean
873
+ description: |-
874
+ False: No command (default)
875
+ True: Order a signal group to red
876
+ securityCode:
877
+ type: string
878
+ description: Security code 2
879
+ range: "[text]"
880
+ command: setStop
881
+ Detector logic:
882
+ description:
883
+ alarms:
884
+ A0301:
885
+ description: |-
886
+ Detector error (hardware).
887
+ Is a "minor fault" defined according to 3.11 in EN12675.
888
+ priority: 3
889
+ category: D
890
+ arguments:
891
+ detector:
892
+ type: string
893
+ description: Designation of the detector (hardware)
894
+ range: "[designation]"
895
+ type:
896
+ type: string
897
+ description: Type of detector
898
+ values:
899
+ loop: Inductive detector loop
900
+ input: External input
901
+ errormode:
902
+ type: string
903
+ description: Detector forced on/off while detector error
904
+ values:
905
+ 'on': ''
906
+ 'off': ''
907
+ manual:
908
+ type: boolean
909
+ description: Manually controlled detector logic (True/False)
910
+ A0302:
911
+ description: |-
912
+ Detector error (logic error).
913
+ For instance; detector continuously on or off during an extended time.
914
+ Is a "minor fault" defined according to 3.11 in EN12675.
915
+ priority: 3
916
+ category: D
917
+ arguments:
918
+ detector:
919
+ type: string
920
+ description: Designation of the detector (hardware)
921
+ range: "[designation]"
922
+ type:
923
+ type: string
924
+ description: Type of detector.
925
+ values:
926
+ loop: Inductive detector loop
927
+ input: External input
928
+ errormode:
929
+ type: string
930
+ description: Detector forced on/off while detector error
931
+ values:
932
+ 'on': ''
933
+ 'off': ''
934
+ manual:
935
+ type: boolean
936
+ description: Manually controlled detector logic (True/False)
937
+ logicerror:
938
+ type: string
939
+ description: Type of logic error
940
+ values:
941
+ always_off: no detection during predefined max time
942
+ always_on: detection constantly on during predefined max time
943
+ intermittent: intermittent logic fault (flutter)
944
+ statuses:
945
+ S0201:
946
+ description: |-
947
+ Traffic Counting: Number of vehicles.
948
+ Used for Traffic counting.
949
+ arguments:
950
+ starttime:
951
+ type: timestamp
952
+ description: Time stamp for start of measuring. Format according to W3C
953
+ XML dateTime with a resolution of 3 decimal places. All time stamps
954
+ in UTC. E.g. 2009-10-02T14:34:34.341Z
955
+ vehicles:
956
+ type: long
957
+ description: Number of vehicles on a given detector logic (since last
958
+ update)
959
+ range: "[number]"
960
+ S0202:
961
+ description: |-
962
+ Traffic Counting: Vehicle speed.
963
+ Used for Traffic counting.
964
+ arguments:
965
+ starttime:
966
+ type: timestamp
967
+ description: |-
968
+ Time stamp for start of measuring. Format according to W3C
969
+ XML dateTime with a resolution of 3 decimal places. All time stamps
970
+ in UTC. E.g. 2009-10-02T14:34:34.341Z
971
+ speed:
972
+ type: integer
973
+ description: Average speed in km/h
974
+ range: "[speed]"
975
+ S0203:
976
+ description: |-
977
+ Traffic Counting: Occupancy.
978
+ Used for Traffic counting.
979
+ arguments:
980
+ starttime:
981
+ type: timestamp
982
+ description: |-
983
+ Time stamp for start of measuring. Format according to W3C
984
+ XML dateTime with a resolution of 3 decimal places. All time stamps
985
+ in UTC. E.g. 2009-10-02T14:34:34.341Z
986
+ occupancy:
987
+ type: integer
988
+ description: Occupancy in percent (0-100%)
989
+ range: "[0-100]"
990
+ S0204:
991
+ description: |-
992
+ Traffic Counting: Number of vehicles of given classification.
993
+ Used for Traffic counting.
994
+ arguments:
995
+ starttime:
996
+ type: timestamp
997
+ description: |-
998
+ Time stamp for start of measuring. Format according to W3C
999
+ XML dateTime with a resolution of 3 decimal places. All time stamps
1000
+ in UTC. E.g. 2009-10-02T14:34:34.341Z
1001
+ P:
1002
+ type: long
1003
+ description: Number of cars
1004
+ range: "[number]"
1005
+ PS:
1006
+ type: long
1007
+ description: Number of cars with trailers
1008
+ range: "[number]"
1009
+ L:
1010
+ type: long
1011
+ description: Number of trucks
1012
+ range: "[number]"
1013
+ LS:
1014
+ type: long
1015
+ description: Number of trucks with trailers
1016
+ range: "[number]"
1017
+ B:
1018
+ type: long
1019
+ description: Number of busses
1020
+ range: "[number]"
1021
+ SP:
1022
+ type: long
1023
+ description: Number of trams
1024
+ range: "[number]"
1025
+ MC:
1026
+ type: long
1027
+ description: Number of motor cycles
1028
+ range: "[number]"
1029
+ C:
1030
+ type: long
1031
+ description: Number of bicycles
1032
+ range: "[number]"
1033
+ F:
1034
+ type: long
1035
+ description: Number of pedestrians
1036
+ range: "[number]"
1037
+ commands:
1038
+ M0008:
1039
+ description: |-
1040
+ Sets manual activation of detector logic.
1041
+ Set given detector logic (1-255) to either true or false.
1042
+ Can e.g. be used to connect RSMP compatible detection equipment to the traffic light controller. Can also be used for prioritization.
1043
+ Requires security code 2
1044
+ arguments:
1045
+ status:
1046
+ type: boolean
1047
+ description: |-
1048
+ False: Deactivate manual control of detector logic
1049
+ True: Activate manual control of detector logic
1050
+ securityCode:
1051
+ type: string
1052
+ description: Security code 2
1053
+ range: "[text]"
1054
+ mode:
1055
+ type: boolean
1056
+ description: |-
1057
+ False: Deactivate detector logic
1058
+ True: Activate detector logic
1059
+ command: setForceDetectorLogic