Analyses temp
Only available in: BSS and BMS
The analyses screen contains the deviations regarding the operation of the blackboxes
Analyses screen
Open analyses screen
The analyses screen can be opened for one or more ships, in the following ways from the the ship overview:
- under menu-item Info → Analyses;
- by right clicking the mouse and choose Analyses from the pop up menu.
After the desired period selection has been entered, the screen will be opened.
Analyses screen content
Depending on fleet, the following data is shown in list view:
| Column | Content |
|---|---|
| Ship | The ship code |
| Category | The category under which the event falls: - BB Ship state - BB State - BB Reset - BB Memory - BB Enclosure - BB Gps - BB Gsm - BB Sms - BB RTC - BB Power - BB Temperature - BB Channel - BB Alarm - BB Configuration - IWS Processing |
| Event ID | The event, noted in code |
| Event | The event, noted in text |
| Start event | The date and time the event started |
| End event | The date and time the event ended |
| Time span | The duration of the event in minutes |
| Last registration | The date and time of the last registration in which the event occurred |
| GPS % | The gps quality, noted in percentage |
| Registrations amount | The number of registrations in which the event occured |
Meaning event ID and text
Depending on the fleet, the following information about the events is shown, divided by category.
BB State
Events under the category BB State are related to the software states of the blackbox system:
| Event ID | Event | Meaning | Fleet dependent |
|---|---|---|---|
| 13 kwk | State fast standby or standby | - "standby fast" event triggered standby registration (without waiting on GPS position information). This can be triggered by openening/closing the blackbox and by changing Namur status (okay / failure). - "standby" interval triggered standby registration (waits maximum 60 secs for GPS position information). |
|
| 14 kwk | State off | The blackbox is completely shut down and does not have any functionality. This state is entered when no vessel supply is available and the battery voltage is too low. It can also be entered manually for transport or storage. | |
| 13 | State fast standby or standby | - standby fast is active after power-up when the reset cause is (deep) sleep wake-up and the logging time is not elapsed - standby is active after power-up when the reset cause is (deep) sleep wake-up and the logging interval time is elapsed |
|
| 14 | State off | The blackbox is completely shut down and does not have any functionality. This state is entered when no vessel supply is available and the battery voltage is too low. |
BB Ship state
| Event ID | Event | Meaning | Fleet dependent | |
|---|---|---|---|---|
| ?? | Ship state X | A transition to ship state X occured | X |
Enkel verwijderen uit mail |
| ?? | Ship state unknown | The ship state is unknown | X
|
BB Reset
Events under the category BB Reset are related to the cause of the system reboot:
| Event ID | Event | Meaning | Fleet dependent |
|---|---|---|---|
| 25 | Cold reset | The system has been reset after restart or a (temporary) power loss of the vessel and battery supply | X
|
| 27 | Warm reset | The system has been reset after the watchdog was triggered, a voltage dip, software reset has occurred or at power-up from sleep | X
|
| 29 | Watchdog reset | The system has been reset after the watchdog was triggered | X
|
| 31 | Software reset | The system has been reset by the software. Triggered manually by servicestation or maintenancestation user and triggered at blackbox software update. |
X
|
| 33 | Low voltage reset | The system has been reset without powering down after a voltage dip in the controller supply | X
|
| 35 | Deep sleep reset | The system has woken up after sleep. This happen in state STANDBY, when the ship supply is absent. Also the first registration with ship supply available after absent. | X
|
BB Memory
Events under the category BB Memory are related to the memory storage of the blackbox system:
| Event ID | Event | Meaning | Fleet dependent |
|---|---|---|---|
| 37 | SD card failure | The system cannot read or write to the SD card | |
| 39 | RAM failure | The system cannot read the settings from the RAM after booting | X
|
BB Enclosure
Events under the category BB Memory are related to the physical enclosure of the blackbox system:
| Event ID | Event | Meaning | Fleet dependent |
|---|---|---|---|
| 41 | Buzzer active | The buzzer is active, because of an alarm | X
|
| 43 | Enclosure open | The enclosure of the system is open |
BB Gps
Events under the category BB GPS are related to the functioning of the gps of the blackbox system:
| Event ID | Event | Meaning | Fleet dependent |
|---|---|---|---|
| 46 | Gps data invalid | The system couldn't receive gps data, because of a missing or broken gps receiver | |
| 48 | Gps position invalid | The system didn't receive a valid gps position, because of a missing or broken gps receiver and/or antenna, or incorrect data | |
| 50 | Gps antenna invalid | The gps antenna has a short or open circuit | |
| 53 | Gps moving in standby | The gps position has changed more then |
X
|
| 55 | Gps position jump in state normal | A position jump occured when the system was is state normal, i.e.: the system was on with all the functionallity enabled | X
|
| 57 | Gps position jump in state fast standby or standby | A position jump occured when the system was in blackbox state fast standby or standby | X
|
| 59 | Gps position jump in state off | A position jump occured when the system was in state off | X
|
BB Gsm
Events under the category BB Gsm are related to the functioning of the gsm of the blackbox system:
| Event ID | Event | Meaning | Fleet dependent | ||
|---|---|---|---|---|---|
| 68 | Gsm quality bad | There is no gsm signal available | kwk: slecht of geen signaal! | ||
| 69 | Gsm quality moderate | The gsm signal is between -103 dB and -113 dB | |||
| 70 | Gsm quality reasonable | The gsm signal is between -72 dB and -112 dB | |||
| 78 | Gsm action no receipt | The modem is initialized, which happens after a system power-up, a configuration change and when a connection cannot be established | X |
kwk: geen ontvangst is toch geen ontvangst! | |
| 79 | Gsm action failure | The modem initialization failed | X
|
BB Sms
Events under the category BB sms are related to the functioning of the text messaging of the blackbox system:
| Event ID | Event | Meaning | Fleet dependent |
|---|---|---|---|
| 83 | Sms action failure | Sending a text message failed, an error response is received | X
|
BB RTC
Events under the category BB RTC are related to the real time clock of the blackbox system:
| Event ID | Event | Meaning | Fleet dependent |
|---|---|---|---|
| 84 | RTC not oke | A RTC anomaly is detected | |
| 87 | RTC jump forward | The datetime of a record registered by the blackbox lies after the datetime of the next record | |
| 88 | RTC jump backward | The datetime of a record registered by the blackbox lies before the datetime of the previous record |
BB Power
Events under the category BB Temperature are related to the power supplies in by the blackbox system:
| Event ID | Event | Meaning | Fleet dependent | bit |
|---|---|---|---|---|
| 90 | Power input failure --> Vessel supply error | The vessel supply is below 22V or has disappeared | Vessel supply, statusbit 14 | |
| 91 | Power input voltage invalid --> Vessel supply voltage invalid | The vessel supply has an invalid value: lower than 15V or higher than 40V | X |
berekend in c#. KWK: waarde ligt buiten gedefinieerde range, dit wordt neem ik aan ook in verwerkingslog gemeld |
| 94 | Power input voltage error --> Input voltage error | The power cable is disconnected | X |
power fail input, statusbit 13 |
| 96 | Power supply failure --> Internal supply failure | VCC or other internal supply failure: - V+ charge voltage is lower than 10V - Watchdog voltage is lower than 4.5V - Namur 1/2 voltage is lower than 7.5V (if enabled) - 3v4 voltage is lower than 3.2V - 5V voltage is lower than 4.5V - V+ voltage is lower than 10V - V voltage is higher than -10V |
X |
Internal supply, statusbit 16 |
| 97 | Power supply voltage invalid --> Internal supply voltage invalid | The internal supply has an invalid value: lower than 0V or higher than 25V | X |
berekend in c# KWK: waarde ligt buiten gedefinieerde range, dit wordt neem ik aan ook in verwerkingslog gemeld |
| 100 | Power supply voltage error --> Internal supply voltage error | foutwaarde 255: <15V of >40,5V | X |
berekend in c# InternalSupplyVoltErr = VesselSupplyVoltage >= RegistrationConstant.ByteErrorVal; (vesselsupplyvoltage is byte 50, errorval = 0xFF) moet zijn: < 15V of > 40,5V |
| 102 | Power battery failure --> No battery | No battery has been detected | X |
No battery, statusbit 37 |
| 103 | Power battery voltage invalid --> Battery voltage invalid | The battery supply has an invalid value: lower than 0V or higher than 25V | X |
berekend in c# |
| 106 | Power battery voltage error --> Battery voltage error | foutwaarde 255: >25.2V | X |
BatCurErr = BatCurrent >= RegistrationConstant.ByteErrorVal; (BatCurrent is byte 47, errorval = 0xFF) |
| 107 | Power battery capacity invalid --> Battery capacity invalid | The battery capacity has an invalid value: lower than 0% or higher than 100% | X |
berekend in c#: BatCapacity is byte 47, <0 of >200 |
| 110 | Power battery capacity error --> Battery capacity error | foutwaarde 255: >100 | X |
berekend in c#: BatCapErr = BatCapacity >= RegistrationConstant.ByteErrorVal; (BatCapacity is byte 47, errorval = 0xFF) |
| ??? | Battery supply error | The battery supply is lower than 11.2 or lower than < 11.7 during battery checking in normal state | X |
toevoegen |
BB Temperature
Events under the category BB Temperature are related to the temperatures of the power supplies in by the blackbox system:
| Event ID | Event | Meaning | Fleet dependent | |
|---|---|---|---|---|
| 112 | Board temperature alarm | IntTempAlrm = RawReader.MSB.ToBoolean(binRegistration.BinaryRegistration[15], 3); --> bit 27: to high (> 60°C)? | X
| |
| 114 | Board temperature too low | The board temperature is below -15°C | X |
kwk: Mogelijkheid om temperatuur in te stellen voor analyse van vloot? |
| 115 | Board temperature too high | The board temperature is above 60°C | X |
kwk: Mogelijkheid om temperatuur in te stellen voor analyse van vloot? Anders mogelijk weinig meerwaarde tov 112 |
| 117 | Board temperature error | foutwaarde 255: >100 | X
| |
| 119 | Battery temperature alarm | BatTempAlrm = RawReader.MSB.ToBoolean(binRegistration.BinaryRegistration[15], 4); --> bit 28: to high (> 60°C or < -15°C)? | X
| |
| 121 | Battery temperature too low | The battery temperature is below -15°C | X |
kwk: Mogelijkheid om temperatuur in te stellen voor analyse van vloot? anders mogelijk weinig meerwaarde tov 119 |
| 122 | Battery temperature too high | The battery temperature is above 60°C | X |
kwk: Mogelijkheid om temperatuur in te stellen voor analyse van vloot? anders mogelijk weinig meerwaarde tov 119 |
| 124 | Battery temperature error | foutwaarde 255: >100 | X
|
BB Channel
Events under the category BB Channel are related to the input sensors of by the blackbox system:
| Event ID | Event | Meaning | Fleet dependent |
|---|---|---|---|
| multiple | Analogue input X alarm low | Analogue input X has gone too low according to the set* value | X
|
| multiple | Analogue input X alarm high | Analogue input X has gone too high according to the set* value | X
|
| 150 | Pulse input 1 error | Pulse input 1 has a short circuit, a wire break, is not connected or broken | X
|
| 151 | Pulse input 1 missing | No valid value for pulse input 1 has been registered | X
|
| 154 | Pulse input 2 error | Pulse input 2 has a short circuit, a wire break, is not connected or broken | X
|
| 155 | Pulse input 2 missing | No valid value for pulse input 2 has been registered | X
|
| 158 | RPM 1 error | The RPM 1 has a value of 9999.9 | X
|
| 160 | RPM 2 error | The RPM 2 has a value of 9999.9 | X
|
| 161 | Duty cycle 1 invalid | Duty cycle 1 has gone too high (above 25%) or too low (below 0%) | X
|
| 164 | Duty cycle 1 error | foutwaarde 255 | X
|
| 165 | Duty cycle 2 invalid | Duty cycle 2 has gone too high (above 25%) or too low (below 0%) | X
|
| 168 | Duty cycle 2 error | foutwaarde 255 | X
|
*Configurable via the configuration of the blackbox.
BB Alarm
Events under the category BB Configuration are related to the alarms that were sent by the blackbox system:
| Event ID | Event | Meaning | Fleet dependent |
|---|---|---|---|
| 170 | Alarm accepted | An alarm has been manually accepted | |
| 172 | Configurable alarm 1 | Configurable via configuration (not yet available) | X
|
| 174 | Configurable alarm 2 | Configurable via configuration (not yet available) | X
|
| 176 | Configurable alarm 3 | Configurable via configuration (not yet available) | X
|
BB Configuration
Events under the category BB Configuration are related to the configuration of the blackbox system:
| Event ID | Event | Meaning | Fleet dependent |
|---|---|---|---|
| 180 | Default configuration loaded | The default configuration parameters are loaded into the system after a configuration or SD card failure during configuration |
IWS Processing
| Event ID | Event | Meaning | Fleet dependent | |
|---|---|---|---|---|
| 11 | Registration gap | A registration is missing | stond onder BB base | |
| 181 | Ship status unknown | The ship status couldn't be determined | X
| |
| 183 | SOG status unknown | The speed over ground status couldn't be determined | X
| |
| 185 | TP status unknown | The turbo pressure status couldn't be determined | X
|
Weekly summary
under construction