Analyses
The analyses screen contains the deviations regarding the operation of the black boxes
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 Base, see - BB State, see - BB Reset, see - BB Memory, see - BB Enclosure, see - BB GPS, see - BB GSM, see - BB SMS, see - BB RTC, see - BB Power, see - BB Temperature, see - BB Channel, see - BB Alarm, see - BB Configuration, see - IWS processing, see |
| Event ID | The event in code |
| Event | The event 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 Base
| Event ID | Event | Meaning | Fleet dependent |
|---|---|---|---|
| 11 | Registration gap | A registration is missing |
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 | 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 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 the vessel supply and battery power has been lost | X
|
| 27 | Warm reset | The system has been reset after the watchdog was triggered, a voltage dip or software reset has occurred | 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. This is done to restart the GPS receiver at power-up, when the antenna state is not known | X
|
| 33 | Low voltage reset | The system has been reset after a voltage dip | X
|
| 35 | Deep sleep reset | 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 |
|---|---|---|---|
| 44 | Gps not oke | ||
| 46 | Gps data invalid | ||
| 48 | Gps position invalid | ||
| 50 | Gps antenna invalid | ||
| 53 | Gps moving in standby | The gps position has changed more then 0.1 minute | 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 | ||
| 69 | Gsm quality moderate | ||
| 70 | Gsm quality reasonable | ||
| 78 | Gsm action no receipt | X
| |
| 79 | Gsm action failure | 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 | 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
BB Temperature
BB Channel
BB Alarm
BB Configuration
| 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 |
|---|---|---|---|
| 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
|