Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Container\Container::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Container\Container::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Container\Container::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Container\Container::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Fluent::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Fluent::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Fluent::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Fluent::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Fluent::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Database\Eloquent\Model::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Database\Eloquent\Model::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Database\Eloquent\Model::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Database\Eloquent\Model::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Database\Eloquent\Model::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Collection::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Collection::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Collection::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Collection::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Collection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Collection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Message: Return type of Illuminate\Support\Collection::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
SAILOR 6110 GMDSS System is the first system to be the world’s most powerful, user-friendly and reliable satellite transceiver system for all ship tracking, monitoring, messaging and distress communications. SAILOR 6110 mini-C GMDSS provides GMDSS, SSAS and LRIT.
The SAILOR 6110 mini-C is a true next-generation GMDSS solution. Building on the strong foundation of previous SAILOR GMDSS products, it introduces innovative new features and functionality, including touch screen operation through the cutting-edge SAILOR 6018 Message Terminal and an all-new approach to installation and networking.
The TT-00-406110A-00551 SAILOR 6110 mini-C is more than just a way to meet mandatory GMDSS requirements because as part of the innovative SAILOR 6000 Series, it is an integral part of a vessel’s communication system. The mini-C system features true triple functionality as it safely handles all GMDSS, SSAS and LRIT operations on board.
CABLING INNOVATION
SAILOR 6110 mini-C GMDSS uses CAN-BUS (NMEA 2000) and RJ45 cabling, and it comes with all required cables (30m) out of the box.
It is ready to go straight away and expanding it is easier and less costly than with traditional cabling. This flexibility also reduces installation and maintenance costs.
TOUCHSCREEN OPERATION
Operation is performed via the new SAILOR 6018 Message Terminal, which stands out as the world's first touch screen, Wheelmarked GMDSS terminal.
The multimedia style interface is user-friendly, which in turn ensures the safe operation of the vessel's IMO safety and tracking systems.
RELIABLE AND ACCURATE
SAILOR 6110 mini-C GMDSS has a brand new transceiver design and operates using a 50 channel GPS module and a high gain omnidirectional antenna.
Ensure accurate satellite fix and position even under adverse conditions. There are no condensation issues and rugged build quality ensures reliable, accurate and continuous operation.
EFFICIENT COMMUNICATION
As part of the SAILOR 6000 GMDSS Series, SAILOR 6110 mini-C GMDSS features ThraneLINK, a unique new system that enables efficient communication within the network.
Engineers can access a vessel's network from a single point for lower maintenance and lifetime costs. The system also identifies new products in a network, making installation easier.
SAILOR 6110 FEATURES INCLUDES:
First ever approved touch screen terminal for GMDSS use
External storage via SD card or USB disk
Innovative approach to cabling for simple networking and expansion
Accurate, reliable 50 channel GPS module that is also Galileo ready
ThraneLINK
SAILOR 6110 GMDSS SYSTEM NEW ORDERING DATA:
Part number
New setup antenna cables
406110A-00521
NO NMEA2K Mini Device Cable
406100-946
10m NMEA2K Mini Device Cable
406100-947
15m NMEA2K Mini Device Cable
406100-944
30m NMEA2K Mini Device Cable
406100-945
50m NMEA2K Mini Device Cable
SAILOR 6110 GMDSS SYSTEM OLD ORDERING DATA:
Manufacturer Part Number
Description
406110A-00500
SAILOR 6110 GMDSS System 30M Cable
406110A-00501
SAILOR 6110 GMDSS System 30M Cable
406110A-00551
SAILOR 6110 GMDSS System 50M Cable
SAILOR 6110 GMDSS SYSTEM INCLUDES:
SAILOR 3027 GMDSS Terminal Antenna
SAILOR 6018 Message Terminal
SAILOR 6001 Keyboard
NMEA2K Mini Device Antenna Cable not included, order separately
