Analyses
Only available in: BSS and BMS
The analyses screen contains the deviations regarding the operation of the blackboxes
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-items 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 | Bit |
|---|---|---|---|---|
| 21 | 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). |
Statusbit 1 = 3 | |
| 22 | 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. | Statusbit 1 = 2 |
BB Ship state
| Event ID | Event | Meaning | Fleet dependent | Bit |
|---|---|---|---|---|
| 30-37 | Ship state X | A transition to ship state X occured | ||
| 38 | Ship state unknown | The ship state is unknown |
BB Reset
Events under the category BB Reset are related to the cause of the system reboot:
| Event ID | Event | Meaning | Fleet dependent | Bit |
|---|---|---|---|---|
| 51 | Cold reset | The system has been reset after restart or a (temporary) power loss of the vessel and battery supply | X |
Statusbit 2 = 1 |
| 53 | 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 |
Statusbit 3 = 1 |
| 55 | Watchdog reset | The system has been reset after the watchdog was triggered | X |
Statusbit 4 = 1 |
| 57 | Software reset | The system has been reset by the software, which can be triggered manually by service station or maintenance station user and triggered at blackbox software update | X |
Statusbit 5 = 1 |
| 59 | Low voltage reset | The system has been reset without powering down after a voltage dip in the controller supply | X |
Statusbit 6 = 1 |
| 61 | Deep sleep reset | The system has woken up after sleep. This happens in state "standy", when the vessel supply is absent. Also the first registration where the vessel supply is available after being absent. | X |
Statusbit 7 = 1 |
BB Memory
Events under the category BB Memory are related to the memory storage of the blackbox system:
| Event ID | Event | Meaning | Fleet dependent | Bit |
|---|---|---|---|---|
| 71 | SD card failure | The system cannot read or write to the SD card | Statusbit 17 = 1 | |
| 73 | RAM failure | The system cannot read the settings from the RAM after booting | X |
Statusbit 18 = 1 |
BB Enclosure
Events under the category BB Memory are related to the physical enclosure of the blackbox system:
| Event ID | Event | Meaning | Fleet dependent | Bit |
|---|---|---|---|---|
| 81 | Buzzer active | The buzzer is active, because of an alarm | X |
Statusbit 29 = 1 |
| 83 | Enclosure open | The enclosure of the system is open | Statusbit 20 = 1 |
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 | Bit |
|---|---|---|---|---|
| 92 | Gps data failure | The system couldn't receive gps data, because of a missing or broken gps receiver | Statusbit 10 | |
| 94 | Gps position failure | The DGPS quality is lower than 2 or higher than 5, which means the system didn't receive a valid gps position, because of a missing or broken gps receiver and/or antenna, or incorrect data. | Statusbit 11 | |
| 96 | Gps antenna failure | The gps antenna has a short or open circuit | Statusbit 12 | |
| 99 | Gps moving in standby | The gps position has changed more than 0.2 minute | X |
Statusbit 33 |
| 101 | Gps position jump in state normal | A position jump occured when the system was in state normal, i.e.: the system was on with all the functionallity enabled | X |
Statusbit 0-1 |
| 103 | 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 |
Statusbit 0-1 |
| 105 | Gps position jump in state off | A position jump occured when the system was in state off | X |
Statusbit 0-1 |
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 | Bit |
|---|---|---|---|---|
| 140 | Gsm quality bad | The gsm signal is bad or absent | Byte xx = 0 | |
| 141 | Gsm quality moderate | The gsm signal is between -103 dB and -113 dB | Byte xx = 1 | |
| 142 | Gsm quality reasonable | The gsm signal is between -72 dB and -112 dB | Byte xx = 3 | |
| 157 | Modem failure | The modem initialization failed | X |
Statusbit 22-24 = 7 |
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 | Bit |
|---|---|---|---|---|
| 173 | Sms action failure | Sending a text message failed, an error response is received | X |
Statusbit 25-26 = 4 |
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 | Bit |
|---|---|---|---|---|
| 180 | RTC failure | A RTC anomaly is detected | Statusbit 19 | |
| 183 | RTC jump forward | The datetime of a record registered by the blackbox lies after the datetime of the next record | ||
| 184 | 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 the blackbox system:
| Event ID | Event | Meaning | Fleet dependent | Bit |
|---|---|---|---|---|
| 215 | Charge supply error | The charge supply has an error value | X |
Byte 49 = 255 |
| 191 | Vessel supply failure | The vessel supply, i.e. external supply, is below 22V or has disappeared | X |
Statusbit 14 |
| 195 | Vessel supply voltage error | The vessel supply voltage, i.e. external supply, has an error value | X |
Byte 50 = 255 |
| 197 | Input voltage failure | The power cable is disconnected or broken | X |
Statusbit 13 |
| 211 | 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 |
Statusbit 16 |
| 231 | No battery | No battery has been detected | X |
Statusbit 37 |
| 235 | Battery voltage error | The battery voltage has an error value | X |
Byte 48 = 255 |
| 253 | Battery capacity error | The battery capacity has an error value | X |
Byte 51 = 255 |
| 271 | Battery supply low | The battery supply is lower than 11.2 or lower than < 11.7 during battery checking in normal state | X |
Statusbit 15 |
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 | Bit |
|---|---|---|---|---|
| 291 | Board temperature alarm | The board temperature is too high: above 60°C | X |
Statusbit 27 |
| 296 | Board temperature error | The board temperature has an error value | X |
Byte 53 = 255 |
| 311 | Battery temperature alarm | The battery temperature is too low (-15°C) or too high (+60°C) | X |
Statusbit 28 |
| 316 | Battery temperature error | The battery temperature has an error value | X |
Byte 52 = 255 |
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 | Bit |
|---|---|---|---|---|
| multiple | Analogue input X alarm low | Analogue input X has gone too low according to the set* value | X |
Byte 21 & 22 = 1 |
| multiple | Analogue input X alarm high | Analogue input X has gone too high according to the set* value | X |
Byte 21 & 22 = 2 |
| 371 | Pulse input 1 failure | Pulse input 1 has a short circuit, a wire break, is not connected or broken | X |
Statusbit 30 |
| 375 | Pulse input 1 error | Pulse input 1 value has an error value | X |
Byte 39 - 41 = 16.777.215 |
| 377 | Pulse input 2 failure | Pulse input 2 has a short circuit, a wire break, is not connected or broken | X |
Statusbit 31 |
| 381 | Pulse input 2 error | Pulse input 2 value has an error value | X |
Byte 42 - 44 = 16.777.215 |
| 391 | RPM 1 error | RPM 1 has a value of 9999.9 | X |
|
| 393 | RPM 2 error | RPM 2 has a value of 9999.9 | X |
|
| 413 | Duty cycle 1 error | Duty cycle 1 value has an error value | X |
Byte 45 = 255 |
| 417 | Duty cycle 2 error | Duty cycle 2 value has an error value | X |
Byte 46 = 255 |
*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 | Bit |
|---|---|---|---|---|
| 431 | Alarm accepted | An alarm has been manually accepted | Statusbit 21 | |
| 433 | Configurable alarm 1 | Configurable via configuration (not yet available) | X |
Statusbit 34 |
| 435 | Configurable alarm 2 | Configurable via configuration (not yet available) | X |
Statusbit 35 |
| 437 | Configurable alarm 3 | Configurable via configuration (not yet available) | X |
Statusbit 36 |
BB Configuration
Events under the category BB Configuration are related to the configuration of the blackbox system:
| Event ID | Event | Meaning | Fleet dependent | Bit |
|---|---|---|---|---|
| 453 | Default configuration loaded | The default configuration parameters are loaded into the system after a configuration or SD card failure during configuration | Statusbit 8 |
IWS Processing
The events under IWS processing are caculated by the service itself:
| Event ID | Event | Meaning | Fleet dependent | Bit |
|---|---|---|---|---|
| 11 | Registration gap | A registration is missing | ||
| 90 | Gps position invalid | Both latitude and longitude values are 0 00.0000. This occurs after rebooting the system and during a reboot when the system is in 'standby' until the gps has been found. | ||
| 194 | Vessel supply voltage out of range | The vessel supply has an out of range value: lower than 15V or higher than 40V | X |
Byte 50 = >250 && <255 |
| 214 | Charge supply voltage out of range | The charge supply has has an out of range value: lower than 0V or higher than 25V | X |
Byte 49 = >250 && < 255 |
| 234 | Battery voltage out of range | The battery supply has an out of range value: lower than 0V or higher than 25V | X |
Byte 48 = >250 && <255 |
| 252 | Battery capacity out of range | The battery capacity has an out of range value: lower than 0% or higher than 100% | X |
Byte 51 = >201 && <254 |
| 293 | Board temperature too low | The board temperature is below -15°C | X |
Byte 53 < -15 |
| 294 | Board temperature too high | The board temperature is above 60°C | X |
Byte 53 > +60 |
| 295 | Board temperature out of range | The board temperature is out of range: more than 100°C | X |
Byte 53 >240 && <255 |
| 313 | Battery temperature too low | The battery temperature is below -15°C | X |
Byte 52 < -15 |
| 314 | Battery temperature too high | The battery temperature is above 60°C | X |
Byte 52 > +60 |
| 315 | Battery temperature value is out of range | The battery temperature is out of range more than 100°C | X |
Byte 52 >240 && <255 |
| 374 | Pulse input 1 out of range | The pulse input value is out of range: more than 10.000.000 | X |
Byte 39 - 41 >10.000.000 && <16.777.215 |
| 380 | Pulse input 2 out of range | The pulse input value is out of range: more than 10.000.000 | X |
Byte 42 - 44 > 10.000.000 && <16.777.215 |
| 412 | Duty cycle 1 out of range | Duty cycle 1 is out of range: above 25% | X |
Byte 45 >250 && <255 |
| 416 | Duty cycle 2 out of range | Duty cycle 2 is out of range: above 25% | X |
Byte 46 >250 && <255 |
| 460 | Ship status unknown | The ship status couldn't be determined | X |
|
| 470 | SOG status unknown | The speed over ground status couldn't be determined | X |
|
| 500 | TP status unknown | The turbo pressure status couldn't be determined | X |
|
| 502 | All analogue inputs are inactive | None of the analogue inputs is connected or active | X |
Weekly summary
The summary is automatically sent once a week by e-mail on monday mornings. The e-mail contains the events of all ships that have taken place during the past week, except the events 'Ship state X' and Gsm events. Visually, the summary is sorted by ship code and then by start date time.
The following information is shown about the events:
| Column | Meaning |
|---|---|
| Ship code | The ship code |
| Start timestamp | The date and time the event started |
| End timestamp | The date and time the event ended. If the event is still active, the end timestamp is empty. |
| Time span | The duration of the event, noted in dd:hh:mm:sssssss |
| Event category | The category of the event. If the data is complete and no events occurred, it will say 'No registrations occured' |
| Event name | The event text |
From version 2.18.x.x, events are being cumulated and Gsm events are being shown:
| Column | Meaning |
|---|---|
| Ship code | The ship code |
| Start timestamp | The date and time the event started |
| End timestamp | The date and time the event ended. If the event is still active, the end timestamp is empty. |
| Time span | The duration of the event, noted in dd:hh:mm:ss |
| Event category | The category of the event. Some extra clarification lines are: - 'No events occured': the analyses have run between the from and start datetime, but no events occurred - 'Analyses did not run': the analyses didn't run between the from and start datetime |
| Event name | The event text |
| Number of occurences | How often the event has occured during the week |
| Registrations amount | The number of registrations in which the event occured |