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 6334C A4 GMDSS Console Four bay console for 2xSAILOR 6301 Control Unit, (2 handsets), 3xSAILOR 6018 Message Terminal Radio Tlx/Radio Tlx/Mini-C -- units to be ordered seperately. Included is: Connection boards, 2x406197A EDS-205Moxa Switche
The next generation SAILOR 6000 GMDSS Series is the most flexible, sophisticated and rugged solution available for all sea areas with high quality pre-installed hardware.
Built for GMDSS
Over 1/3 of all commercial vessels covered by international conventions use SAILOR GMDSS thanks to the rugged, reliable build quality and sophisticated, flexible functionality.
Trust A4 SAILOR GMDSS console to fulfill all requirements for the A4 sea area and to be a reliable operational and safety communication tool wherever you are.
Communication you can trust
The A4 SAILOR GMDSS Console may be pre-installed with the two most advanced GMDSS certified marine DSC Class A radios available -SAILOR 6222 VHF and SAILOR 6300 MF/HF.
Have your GMDSS delivered complete. Reduce installation costs, rest easy that you have chosen the pinnacle of marine radio technology, and improve safety and operations.
State-of-the-art SAILOR A4 Solutions
Spec the 2nd generation SAILOR 6110 mini-C, add touchscreen operation with SAILOR 6006 Message Terminal or expand functionality with Thrane IP Handset for SAILOR FleetBroadband.
A4 SAILOR GMDSS Console is built to your specification. Benefit from touch screen multimedia style operation, the most rugged, reliable mini-C available or integration with satcoms for VoIP.
A4 SAILOR GMDSS Console is delivered with four sections, and pre-installed with the required SAILOR 6000 GMDSS products, including printers, keyboards, and three SAILOR 6006 Message Terminals for operation of single or dual mini-Cs, VHF and MF/HF.
Efficient communication
As part of the SAILOR 6000 GMDSS Series, A4 SAILOR GMDSS Console 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 the console, making installation easier.
Standard equipment
A4 SAILOR GMDSS Consoles are delivered as standard with lights, dimming control, connection boards, removable front plates and SAILOR Moxa Switches for ThraneLINK.
Save time and money with everything you need in a single package from a single supplier, with easy access for extending your system and maintenance procedures.
Dimensions of the console with topmounted printer: H - 500 mm x W - 1645 mm x D - 375 mm
FOUR SECTION VERSIONS FOR A4 INSTALLATIONS
Part Numbers
Product Description
Bays/Sections
406334A-20000
SAILOR 6334C A4 GMDSS Console , 4 sections for:
2 x SAILOR 6301 MF/HF Control Unit
3 x SAILOR 6018 Message Terminals (1 for Mini-C, 2 for RadioTelex)
.jpg)
