rsmp_schema 0.4.0 → 0.4.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/Gemfile.lock +10 -4
- data/lib/rsmp_schema/version.rb +1 -1
- data/schemas/tlc/1.0.10/commands/M0001.json +6 -8
- data/schemas/tlc/1.0.10/sxl.yaml +1 -1
- data/schemas/tlc/1.0.13/commands/M0001.json +6 -8
- data/schemas/tlc/1.0.13/sxl.yaml +1 -1
- data/schemas/tlc/1.0.14/commands/M0001.json +6 -8
- data/schemas/tlc/1.0.14/sxl.yaml +1 -1
- data/schemas/tlc/1.0.15/commands/M0001.json +6 -8
- data/schemas/tlc/1.0.15/sxl.yaml +1 -1
- data/schemas/tlc/1.0.7/commands/M0001.json +6 -8
- data/schemas/tlc/1.0.7/sxl.yaml +1 -1
- data/schemas/tlc/1.0.8/commands/M0001.json +6 -8
- data/schemas/tlc/1.0.8/sxl.yaml +1 -1
- data/schemas/tlc/1.0.9/commands/M0001.json +6 -8
- data/schemas/tlc/1.0.9/sxl.yaml +1 -1
- data/schemas/tlc/1.1/alarms/A0009.json +1 -1
- data/schemas/tlc/1.1/commands/M0001.json +10 -18
- data/schemas/tlc/1.1/commands/M0013.json +2 -2
- data/schemas/tlc/1.1/commands/M0022.json +10 -11
- data/schemas/tlc/1.1/commands/M0023.json +1 -1
- data/schemas/tlc/1.1/commands/M0104.json +7 -7
- data/schemas/tlc/1.1/statuses/S0001.json +1 -1
- data/schemas/tlc/1.1/statuses/S0003.json +2 -2
- data/schemas/tlc/1.1/statuses/S0004.json +2 -2
- data/schemas/tlc/1.1/statuses/S0006.json +2 -2
- data/schemas/tlc/1.1/statuses/S0007.json +1 -1
- data/schemas/tlc/1.1/statuses/S0008.json +1 -1
- data/schemas/tlc/1.1/statuses/S0009.json +1 -1
- data/schemas/tlc/1.1/statuses/S0010.json +1 -1
- data/schemas/tlc/1.1/statuses/S0011.json +1 -1
- data/schemas/tlc/1.1/statuses/S0012.json +1 -1
- data/schemas/tlc/1.1/statuses/S0013.json +1 -1
- data/schemas/tlc/1.1/statuses/S0014.json +9 -8
- data/schemas/tlc/1.1/statuses/S0015.json +9 -8
- data/schemas/tlc/1.1/statuses/S0020.json +1 -1
- data/schemas/tlc/1.1/statuses/S0024.json +2 -2
- data/schemas/tlc/1.1/statuses/S0032.json +0 -1
- data/schemas/tlc/1.1/statuses/S0033.json +3 -3
- data/schemas/tlc/1.1/statuses/S0096.json +7 -7
- data/schemas/tlc/1.1/statuses/S0097.json +1 -1
- data/schemas/tlc/1.1/statuses/S0204.json +1 -1
- data/schemas/tlc/1.1/statuses/S0208.json +1 -1
- data/schemas/tlc/1.1/sxl.yaml +188 -180
- metadata +3 -3
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"allOf" : [
|
|
3
3
|
{
|
|
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).",
|
|
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).\nPlease note that all values in this status uses comma-separated lists - one value for each intersection, e.g. \"0\" and \"True\" (one intersection) or \"1,2\" and \"True,False\" (two intersections).",
|
|
5
5
|
"properties" : {
|
|
6
6
|
"n" : {
|
|
7
7
|
"enum" : [
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"allOf" : [
|
|
3
3
|
{
|
|
4
|
-
"description" : "Manual control.\nTraffic control deactivated in 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.\nPlease note that all values in this status uses comma-separated lists - one value for each intersection, e.g. \"0\" and \"True\" (one intersection) or \"1,2\" and \"True,False\" (two intersections).",
|
|
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.\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.",
|
|
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.\nPlease note that all values in this status uses comma-separated lists - one value for each intersection, e.g. \"0\" and \"True\" (one intersection) or \"1,2\" and \"True,False\" (two intersections).",
|
|
5
5
|
"properties" : {
|
|
6
6
|
"n" : {
|
|
7
7
|
"enum" : [
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"allOf" : [
|
|
3
3
|
{
|
|
4
|
-
"description" : "Isolated control.\nIsolated control mode indicates that the controller operates independently of any other traffic light
|
|
4
|
+
"description" : "Isolated control.\nIsolated control mode indicates that the controller operates independently of any other traffic light controller. This may be different depending on traffic program (time plan).\nUsed to determine if the controller is operating independently or operating with other controllers (coordination).\nPlease note that all values in this status uses comma-separated lists - one value for each intersection, e.g. \"0\" and \"True\" (one intersection) or \"1,2\" and \"True,False\" (two intersections).",
|
|
5
5
|
"properties" : {
|
|
6
6
|
"n" : {
|
|
7
7
|
"enum" : [
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"allOf" : [
|
|
3
3
|
{
|
|
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.",
|
|
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.\nSome countries may use yellow flash as an normal operating mode, and not necessarily during fault.\nPlease note that all values in this status uses comma-separated lists - one value for each intersection, e.g. \"1,2\" and \"True,False\"",
|
|
5
5
|
"properties" : {
|
|
6
6
|
"n" : {
|
|
7
7
|
"enum" : [
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"allOf" : [
|
|
3
3
|
{
|
|
4
|
-
"description" : "All red.\nThe controller show all red.\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.\nPlease note that all values in this status uses comma-separated lists - one value for each intersection, e.g. \"1,2\" and \"True,False\"",
|
|
5
5
|
"properties" : {
|
|
6
6
|
"n" : {
|
|
7
7
|
"enum" : [
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"allOf" : [
|
|
3
3
|
{
|
|
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.",
|
|
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.\nPlease note that all values in this status uses comma-separated lists - one value for each intersection, e.g. \"1,2\" and \"0,1\"",
|
|
5
5
|
"properties" : {
|
|
6
6
|
"n" : {
|
|
7
7
|
"enum" : [
|
|
@@ -51,14 +51,15 @@
|
|
|
51
51
|
"then" : {
|
|
52
52
|
"properties" : {
|
|
53
53
|
"s" : {
|
|
54
|
-
"
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
54
|
+
"description" : "Source of the status change",
|
|
55
|
+
"type" : "string",
|
|
56
|
+
"enum" : [
|
|
57
|
+
"calendar_clock",
|
|
58
|
+
"control_block",
|
|
59
|
+
"forced",
|
|
60
|
+
"operator_panel",
|
|
61
|
+
"other",
|
|
62
|
+
"startup"
|
|
62
63
|
]
|
|
63
64
|
}
|
|
64
65
|
}
|
|
@@ -51,14 +51,15 @@
|
|
|
51
51
|
"then" : {
|
|
52
52
|
"properties" : {
|
|
53
53
|
"s" : {
|
|
54
|
-
"
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
54
|
+
"description" : "Source of the status change",
|
|
55
|
+
"type" : "string",
|
|
56
|
+
"enum" : [
|
|
57
|
+
"calendar_clock",
|
|
58
|
+
"control_block",
|
|
59
|
+
"forced",
|
|
60
|
+
"operator_panel",
|
|
61
|
+
"other",
|
|
62
|
+
"startup"
|
|
62
63
|
]
|
|
63
64
|
}
|
|
64
65
|
}
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"allOf" : [
|
|
3
3
|
{
|
|
4
|
-
"description" : "Control mode.\nCan be used for the management system to check the current control mode (startup, normal, standby, failure, test).",
|
|
4
|
+
"description" : "Control mode.\nCan be used for the management system to check the current control mode (startup, normal, standby, failure, test).\nPlease note that all values in this status uses comma-separated lists - one value for each intersection, e.g. \"1,2\" and \"startup,control\"",
|
|
5
5
|
"properties" : {
|
|
6
6
|
"n" : {
|
|
7
7
|
"enum" : [
|
|
@@ -24,9 +24,9 @@
|
|
|
24
24
|
"then" : {
|
|
25
25
|
"properties" : {
|
|
26
26
|
"s" : {
|
|
27
|
-
"description" : "Offset table\nEach offset time is written as
|
|
27
|
+
"description" : "Offset table\nEach offset time is written as p-t where:\np=time plan number (from 1 to 255)\nt=offset time in seconds (from 0 to 255)\n\nEach offset time is separated with a comma\n\nE.g.\n1-0,2-13-3-7",
|
|
28
28
|
"type" : "string",
|
|
29
|
-
"pattern" : "^(\\d{1,
|
|
29
|
+
"pattern" : "^(\\d{1,3}\\-\\d{1,3})(?:,(\\d{1,3}\\-\\d{1,3}))*$"
|
|
30
30
|
}
|
|
31
31
|
}
|
|
32
32
|
}
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"allOf" : [
|
|
3
3
|
{
|
|
4
|
-
"description" : "Signal Priority Status\nThis status can be used to get updates about priority requests. For example, you can use it to know when priority requests are activated or cancelled.\nA list of priorities is returned, referred to by their request ids. The same request id can appear only once.\nAll priorities are included in the list (not only the ones that have changed state since the last update). This is done regardless of whether the status is send in respond to a status request, or due to a status subscription, and also regardless of whether a status subscription uses an update interval, or send-on-change, or both.\nIf you subscribe using an update interval, you’re not guaranteed to get all intermediate states. To guarantee that, send-on-change must be used when subscribing.\nTo understand how this status relates to ETSI/J2735, please see the wiki.\nAll priorities are send on every status update, regardless of whether an interval, or sendOnChange (or both) is used.\nWhen a priority reaches an end states (completed, timeout, rejected, cooldown or stale), it must be sent once on the next status update, then removed from the list.\nA request always starts in the ‘received’ state. The following table shows the possible state transitions
|
|
4
|
+
"description" : "Signal Priority Status\nThis status can be used to get updates about priority requests. For example, you can use it to know when priority requests are activated or cancelled.\nA list of priorities is returned, referred to by their request ids. The same request id can appear only once.\nAll priorities are included in the list (not only the ones that have changed state since the last update). This is done regardless of whether the status is send in respond to a status request, or due to a status subscription, and also regardless of whether a status subscription uses an update interval, or send-on-change, or both.\nIf you subscribe using an update interval, you’re not guaranteed to get all intermediate states. To guarantee that, send-on-change must be used when subscribing.\nTo understand how this status relates to ETSI/J2735, please see the [wiki](https://github.com/rsmp-nordic/rsmp_sxl_traffic_lights/wiki/Signal-priority-and-ETSI-J2735).\nAll priorities are send on every status update, regardless of whether an interval, or sendOnChange (or both) is used.\nWhen a priority reaches an end states (completed, timeout, rejected, cooldown or stale), it must be sent once on the next status update, then removed from the list.\nA request always starts in the ‘received’ state. The following table shows the possible state transitions:\n\nState | Possible next states\n---------- | -------------------------------------\nreceived | queued, activated, rejected, cooldown\nqueued | activated, timeout\nactivated | completed, stale\ncompleted |\ntimeout |\nrejected |\ncooldown |\nstale |",
|
|
5
5
|
"properties" : {
|
|
6
6
|
"n" : {
|
|
7
7
|
"enum" : [
|
|
@@ -66,7 +66,7 @@
|
|
|
66
66
|
"e" : {
|
|
67
67
|
"allOf" : [
|
|
68
68
|
{
|
|
69
|
-
"description" : "
|
|
69
|
+
"description" : "Estimated green extension provided by the priority, in seconds\nOnly used when state is ‘completed’."
|
|
70
70
|
},
|
|
71
71
|
{
|
|
72
72
|
"$ref" : "../../../core/3.1.2/definitions.json#/integer"
|
|
@@ -76,7 +76,7 @@
|
|
|
76
76
|
"d" : {
|
|
77
77
|
"allOf" : [
|
|
78
78
|
{
|
|
79
|
-
"description" : "
|
|
79
|
+
"description" : "Estimated red reduction provided by the priority, in seconds\nOnly used when state is ‘completed’."
|
|
80
80
|
},
|
|
81
81
|
{
|
|
82
82
|
"$ref" : "../../../core/3.1.2/definitions.json#/integer"
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"allOf" : [
|
|
3
3
|
{
|
|
4
|
-
"description" : "Current date and time
|
|
4
|
+
"description" : "Current date and time.\nNote: UTC is used.\nProvides diagnostic information about the current date and time set in the controller.",
|
|
5
5
|
"properties" : {
|
|
6
6
|
"n" : {
|
|
7
7
|
"enum" : [
|
|
@@ -31,7 +31,7 @@
|
|
|
31
31
|
"s" : {
|
|
32
32
|
"allOf" : [
|
|
33
33
|
{
|
|
34
|
-
"description" : "Year
|
|
34
|
+
"description" : "Year"
|
|
35
35
|
},
|
|
36
36
|
{
|
|
37
37
|
"$ref" : "../../../core/3.1.2/definitions.json#/integer"
|
|
@@ -57,7 +57,7 @@
|
|
|
57
57
|
"s" : {
|
|
58
58
|
"allOf" : [
|
|
59
59
|
{
|
|
60
|
-
"description" : "Month
|
|
60
|
+
"description" : "Month"
|
|
61
61
|
},
|
|
62
62
|
{
|
|
63
63
|
"$ref" : "../../../core/3.1.2/definitions.json#/integer"
|
|
@@ -83,7 +83,7 @@
|
|
|
83
83
|
"s" : {
|
|
84
84
|
"allOf" : [
|
|
85
85
|
{
|
|
86
|
-
"description" : "Day of month
|
|
86
|
+
"description" : "Day of month"
|
|
87
87
|
},
|
|
88
88
|
{
|
|
89
89
|
"$ref" : "../../../core/3.1.2/definitions.json#/integer"
|
|
@@ -109,7 +109,7 @@
|
|
|
109
109
|
"s" : {
|
|
110
110
|
"allOf" : [
|
|
111
111
|
{
|
|
112
|
-
"description" : "Hour
|
|
112
|
+
"description" : "Hour"
|
|
113
113
|
},
|
|
114
114
|
{
|
|
115
115
|
"$ref" : "../../../core/3.1.2/definitions.json#/integer"
|
|
@@ -135,7 +135,7 @@
|
|
|
135
135
|
"s" : {
|
|
136
136
|
"allOf" : [
|
|
137
137
|
{
|
|
138
|
-
"description" : "Minute
|
|
138
|
+
"description" : "Minute"
|
|
139
139
|
},
|
|
140
140
|
{
|
|
141
141
|
"$ref" : "../../../core/3.1.2/definitions.json#/integer"
|
|
@@ -161,7 +161,7 @@
|
|
|
161
161
|
"s" : {
|
|
162
162
|
"allOf" : [
|
|
163
163
|
{
|
|
164
|
-
"description" : "Second
|
|
164
|
+
"description" : "Second"
|
|
165
165
|
},
|
|
166
166
|
{
|
|
167
167
|
"$ref" : "../../../core/3.1.2/definitions.json#/integer"
|
|
@@ -25,7 +25,7 @@
|
|
|
25
25
|
"then" : {
|
|
26
26
|
"properties" : {
|
|
27
27
|
"s" : {
|
|
28
|
-
"description" : "Checksum of the traffic parameters\nUses SHA-2 as hashing algorithm\nIncludes\n- all signal programs, including program versions\n- signal group settings\n- time plans\n- safety matrix\n- intergreen times\n- detector settings\n\nIt should NOT include:\n- network settings\n- log files\n- software\n- other device settings that are not part of the signal program\n\nNote:\n- The checksum should be calculated using the same data as used in S0098",
|
|
28
|
+
"description" : "Checksum of the traffic parameters\nUses SHA-2 as hashing algorithm\nIncludes\n- all signal programs, including program versions\n- signal group settings\n- time plans\n- safety matrix\n- intergreen times\n- detector settings\n\nIt should NOT include:\n- network settings\n- log files\n- software\n- other device settings that are not part of the signal program\n\nNote:\n- The checksum should be calculated using the same data as used in S0098\n- Data Downloaded with S0098 and hashed with SHA-2 should match this value.",
|
|
29
29
|
"type" : "string"
|
|
30
30
|
}
|
|
31
31
|
}
|
|
@@ -165,7 +165,7 @@
|
|
|
165
165
|
"s" : {
|
|
166
166
|
"allOf" : [
|
|
167
167
|
{
|
|
168
|
-
"description" : "Number of
|
|
168
|
+
"description" : "Number of buses.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)"
|
|
169
169
|
},
|
|
170
170
|
{
|
|
171
171
|
"$ref" : "../../../core/3.1.2/definitions.json#/integer_list"
|