TIC 4.0
(Wheel Location) Technical
OBSERVED PROPERTY
Fields | Type | Description | Purpose |
|---|---|---|---|
ID (OBSERVED PROPERTY identifier) | M | wheel.location.technical | GRAMMAR |
OBSERVED PROPERTY name | M | (Wheel Location) Technical | GRAMMAR |
OBSERVED PROPERTY type | M | Wheel | GRAMMAR |
Applicable to |
| Location https://tic40.atlassian.net/l/c/K30qhray https://tic40.atlassian.net/l/c/YVsUcrYo |
|
Also known as | O | tyre position, wheel position | TIC Description |
Definition | M | Identifies the unique position of the wheel in relation to the subject and links the following observed properties to this unique position. | TIC Description |
Further Detail | O | This definition corresponds to the observed property location.technical with qualifier = wheel. As forward is definied according to Forward 2022.003, the following applies: The first number represents the position counting from front to back on the CHE. (In binary system: The high order 4 bits (first) represent this position number). The second number represents the position counting from left to right when facing in the direction of the normal CHE travel (forward). (In binary system: The low order 4 bits (second) represent this position number). In binary system: Instead of 4 / 4 bits, the byte can be split for example 6 / 2 to accomodate STS application, so that up to 64 wheels on each side are possible. The wheel_location should be labelled on the machine for better identification by humans. | TIC Description |
Required Information | M | id, location.technical; qualifier: “wheel” | TIC Description |
SUBJECT |
| axle |
|
CONCEPT |
| location |
|
Value |
| binary: 00 00 00 00 to 11 11 11 11 decimal: 00 00 to 15 15 |
|
Related standards | O | SAE J1939 SPN 929 ETRTO TRA JATMA | TIC Description |
Related TIC 4.0 definition | O | Location https://tic40.atlassian.net/l/c/YVsUcrYo Forward 2022.003 | TIC Description |
Example | M | Decimal wheel.location.technical = 00 00 would be left front tyre for a straddle carrier. Decimal wheel.location.technical = 01 01 would be right second front tyre for a straddle carrier. Decimal wheel.location.technical = 02 03 would be right outside rear on a 3-axle tractor with dual tyres per side (3rd axle, 4th tire). | TIC Description |
Example in the context of the grammar | M | A Json message of two specific wheels of the drive system. Their position in the machine are defined by the location_technical {
"che": [
{
"id": "",
"drive": [
{
"id": "",
"axe": [
{
"id": "",
"wheel": [
{
"id": "1234123",
"name": "frontleft",
"number": 1,
"location": {
"technical": [
{
"pom": "ioutput",
"pomt": "actual",
"timestamp": "2021-04-14T07:13:55.872Z",
"qualifier": "wheel",
"value": [
"01 01"
]
}
]
}
},
{
"id": "123423145",
"name": "frontright",
"number": 2,
"location": {
"technical": [
{
"pom": "ioutput",
"pomt": "actual",
"timestamp": "2021-04-14T07:13:55.872Z",
"qualifier": "wheel",
"value": [
"01 02"
]
}
]
}
}
]
}
]
}
]
}
]
} | TIC Description |
Search tags | M | wheel_ID, rim_ID, tyre_ID, tire_ID, wheel_location, rim_location, tyre_location, tire_location, wheel_position, rim_position, tyre_position, tire_position | Technical |
Version / Date | M | Release 2022.003 / 01.11.21 | Technical |
Internal TIC Version | M | definition technical group | Technical |
Created by | Edited by | Review / Approve | Published |
@Luisa Kempf | @Francisco Blanquer Jaraiz | Drive |
|
|
|
|
|
Comments
STS crane (trolley movement): forward is moving into the direction of the ship.
The trolly momement should either be removed or also added to the wheel:subject(concept)
@Luisa Kempf @RBS EMEA
We need to include in the location the che, drive, axe and wheel location_techcnial. Now we only have the axe and wheel. In the location_techcnial array we should include also the che id, drive location. If not when you query where has been the wheel you will just have the position but not in wich machine or drive system (imagen that you have two drives!
So in my opinion the definition is ok but should include in first two position of the arrray as many technical locations as needed upstream to define where is the subject.
(mk) Just to clarify: do you mean to include che_id + drive_location_technical as mandatory attributes in wheel_location_technical (upstream within the array),
or include it in location_technical, e.g. as mandatory attributes for “wheel”?
@RBS EMEA @Luisa Kempf
the first one: include che_id + drive_location_technical as mandatory attributes in wheel_location_technical
but I’ve just realized that we have that data in the che_id so we always can cross the wheel_location_technical of each register to represent where was the wheel. Of course if we duplicate the information is easier but if all the data is in the same register is not a problem. What I try to say is if we have a register (message) without che_id and only the data from the wheel the wheel_location_technical is incomplete, in the array it should be also the CHE_id and the drive, axe, location_techncial to know in what subject was the wheel. We dont need this information if we already have it in the register but that could not always happens.
In conclusion, if we want to be sure that we always have the complete location we need to include always (duplicate) the toplevel id + all the location_technical (up to the subject we are talking about) in the array of the location_technical.
Of course the subject schema has to be fix to be able to do this.
(mk) Thanks, now I understand!
Location is used in https://tic40.atlassian.net/wiki/spaces/TIC40Definitions/pages/48070844 for the logical position related to the “Yard” or place but not to the subject. So if you said location is always a geographical location and not a subject position.
I sugest to change the name to a similar one (placement or one of the “also know as”) but not the same so you can have both meanings active:
OBSERVED PROPERTY
Fields
Type
Description
Purpose
ID (OBSERVED PROPERTY identifier)
M
placement
GRAMMAR
OBSERVED PROPERTY name
M
Placement
GRAMMAR
OBSERVED PROPERTY type
M
position
GRAMMAR
Also known as
O
position; component position; arrangement; place; disposition; disposal; emplacement; situation; installed; instalation; wheel_ID, rim_ID; tyre_ID; tire_ID; wheel_location; rim_location; tyre_location; tire_location; wheel_position; rim_position; tyre_position; tire_position
TIC Description
Definition
M
A “placement” represents a logical position of a subsubject=component (spreader, wheel, hoist, twislock etc) within a subject= component’s father (e.g. CHE, drive, spreader); therefor identifies a unique position the subsubject in relation to the subject.
Further Detail
O
Wheel_placement:
In case the subject travel direction forward is clear, the following applies:
The first number represents the position counting from front to back on the CHE. (In binary system: The high order 4 bits (first) represent this position number).
The second number represents the position counting from left to right when facing in the direction of the normal CHE travel (forward). (In binary system: The low order 4 bits (second) represent this position number).
In binary system: Instead of 4 / 4 bits, the byte can be split for example 6 / 2 to accomodate STS application, so that up to 64 wheels on each side are possible.
The wheel_location should be labelled on the machine for better identification by humans.
In case the travel direction forward is not clear (e.g. missing cabin, RTG, RMG, ASC, AGV): Forward needs to be defined by the vendor or the operator and needs to be labelled on the machine.
As a generic definition the following applies to STS cranes:
STS crane (lateral movement): looking towards the water left side is forward.
STS crane (trolley movement): forward is moving into the direction of the ship.
To be done:
Spreader_placement:
Twislock_placement:
control_placement:
cabin_placement:
TIC Description
Required Information
M
SUBJECT; SUB-SUBJECT=traction; VALUE
TIC Description
SUBJECT
#wheel;
To be done: #che; #spreader; #twislock; #control; #cabin
POINT OF MEASUREMENT
#input;#internal_in ; #internal_out ;#output
#schedule; #actual; #historic
OBSERVED PROPERTY
Value
Wheel_placement:
binary: 00 00 00 00 to 11 11 11 11
decimal: 00 00 to 15 15
To be done:
Spreader_placement:
Twislock_placement:
control_placement:
cabin_placement:
Related standards
O
Wheel_placement: SAE J1939 SPN 929; ETRTO TRA JATMA
To be done:
Spreader_placement:
Twislock_placement:
control_placement:
cabin_placement:
TIC Description
Related TIC 4.0 definition
O
#wheel; #spreader; #twislock; #control; #cabin
TIC Description
Example
M
Wheel_placement:
che_wheel_placement_decimal: 00 00 = Decimal wheel ID 00 00 would be left front tyre for a straddle carrier.
che_drive_wheel_placement_decimal: 02 03 = Decimal wheel ID 02 03 would be right outside rear on a 3-axle tractor with dual tyres per side (3rd axle, 4th tire).
To be done:
Spreader_placement:
Twislock_placement:
control_placement:
cabin_placement:
TIC Description
Example in the context of the grammar
M
A SC withe a specific tyre in a wheel placement:
che_id : CURRO_2015_230894Y20934768
che_name: SC01
che_type: SC
che_drive_wheel_placement: 01 01
che_drive_wheel_tyre_id: 0912384751hp12o3jk4h5pñl123k4jn5
che_drive_wheel_tyre_totaldistance_m: 3948576
che_drive_wheel_tyre_distance_m: 12
che_drive_wheel_tyre_temperature_c: 65
che_drive_wheel_tyre_pressure_atm: 10
JSON format example in the context of a SC driving with 2 wheels, 1 motor, 1 brake:
timestamp: 2015-06-12 00:12:32.001
duration_s: 10
id: 239084yjknliunhl234kj5n234o9785234bnljk234n5o2ui34h523l4jki5nr234lkjn
che:
{
id: CURRO_2015_230894Y20934768
name: SC01
type: SC
drive:
{
status:true
totaldistance_m: 3948576
totaldistance_forward: 3900000
totaldistance_reverse: 48676
distance_m: 12
distance_forward: 12
wheel:
[{
placement : 01 01
totaldistance_m: 3948576
distance_m: 12
tyre:
{
id:0912384751hp12o3jk4h5pñl123k4jn5
temperature_C: 65
pressure_bar: 10
}
motor:
{
id:091
timer_s: 3600
power_w: 34
}
}
{
placement : 02 02
tyre:
{
id:0912384751hp12o3jk4h5pñl123k4jn5
duration_s: 10
totaldistance_m: 3948576
distance_m: 12
temperature_C: 65
pressure_bar: 10
}
brake:
{
id:aaaaaaaaawwwwww
timer_s: 33
totaltimer: 356
distance: 120
}
}]
}
}
TIC Description
Link to one or more operational processes
M
Any related with Drive: distance, speed or maintenance.
TIC Description
Search tags
M
#wheel, #rim, #tyre, #tire
Technical
Version / Date
M
TIC_R_2020 / 15.01.21
Technical
Internal TIC Version
M
definition technical group
Technical