MultiMap. Name. Operating Manual

Transcription

1 MultiMap Name Operating Manual

2

3 Contents Note General description of functions MultiMap as the user interface and for display Using MultiMap with MultiScope Using MultiMap with GeViSoft Using with GeViScope Using MultiMap with MultiScope and GeViSoft System examples Licence to run MULTIMAP Getting started quickly with a demo project Demo system Step 1: Save new layout plan project and layout plans it contains Step 2: Creating the necessary connections Step 3: Inserting navigation icons in the site plans Step 4: Inserting icons for the control and display of MultiScope Step 5: Inserting icons for the control and display of GeViSoft Step 6: Insert icons for the control and display of GeViScope Step 7: Adding responses to MultiMap events Step 8: Site plan project settings MultiMap Editor Working with site plan projects Editing a site plan project Changing site plan project settings Layout graphic size Settings when using a double graphic map Working with connections Changing connection settings Double function for connection with MultiScope Working with site plans Changing site plan settings Working with icons Icon types Changing icon settings Camera GeVi monitor MSC monitor MultiView GeVi output contacts GeVi input contacts Events GeVi alarm Site plan change Text Graphics Macros MultiMap command

4 9. Working with responses to internal MultiMap events Store action instructions Working with Media Viewers MultiMap Editor settings MultiMap viewer Starting MultiMap Structure of the MultiMap window Login dialogue Command operations Statistics Display action instructions Alarm management Media Viewers User Interaction

5 Note This documentation may not be copied, translated or converted to a machine-readable form, whether in whole or in part, without prior permission. GEUTEBRÜCK GmbH cannot guarantee the correctness of any information provided in this documentation, nor for the software or the information it contains. Any suggested guarantee, assurance of marketable quality or suitability for a specific purpose of the documentation, the software or other information is hereby explicitly rejected. Under no circumstances is GEUTEBRÜCK GmbH liable for direct or indirect subsequent damage or for special subsequent damage resulting from or in association with this documentation, regardless of whether this arises as a result of illegitimate action, of a contract, or for other reasons in association with this documentation, the software or of the information contained or used within it. GEUTEBRÜCK GmbH retains the right to change this documentation or the information contained within it at any time without warning. The software described in it is subject to the conditions of a special licence contract. Please note that the illustrations in this documentation will not necessarily match those of your software version. The documentation consists of manuals that can be read on the device. The Windows help for the licensed software is installed on the device. This help can (in whole or in part) be updated over the internet or, by agreement, in other ways. The Windows help is, moreover, included on CD or DVD. 1. General description of functions MultiMap is the common user interface and display tool for GeViScope, GeViSoft and MultiScope II/III. It can be used both for each individual system type and for mixed versions of the two systems. TCP/IP is the communications protocol between MultiMap and the system for control or display, facilitating the user-determined distribution of MultiMap and other systems throughout the network. MultiMap consists of two core components, MultiMap Editor and MultiMap Viewer (abbreviated to MultiMap in this document). MultiMap-Editor MultiMap Editor is used to create and maintain site plan projects, providing the design environment for these projects. 3

6 MultiMap MultiMap is the run-time environment for site plan projects and together with the respective site plan project, provides the visual user interface in the form of site plans (user-definable graphics) and icons (user-definable control components). 4

7 2. MultiMap as the user interface and for display 2.1 Using MultiMap with MultiScope When MultiMap is used as the user interface for MultiScope, digital picture data is displayed via MultiView. When interfaced with MultiMap, MultiViewruns in special mode and functions as a virtual monitor screen only, controlled remotely via MultiMap. Data for display in MultiViewis received via a separate connection to MultiScope, established automatically during start-up. MultiMap allows the user to access most of the functionality of MultiView. As well as the connection of cameras to MultiViewdisplays and MultiScope monitors, it is also possible to control playback, filter and search picture data, and control cameras with telemetry capability from within MultiMap via the well-known MultiViewdialogue box. Events triggered by MultiScope, processed in MultiView, can also trigger special functions within MultiMap. It is thus also possible to display special site plans as a result of MultiScope events. Any number of MultiScope and MultiViewterminals may be operated or displayed using MultiMap and a site plan project. All systems used may be freely distributed throughout the network, or combined on one computer. Fig. 1: MultiMap with several MultiViews and MultiScopes 2.2 Using MultiMap with GeViSoft MultiMap with MultiScope may also be used as a user interface or display tool for GeViSoft, facilitating the operation and presentation of all GeViSoft components, including cameras, monitors, digital inputs and outputs, events and alarms. Using a site plan project, any number of GeViSofts can also be operated from MultiMap. User-defined distribution throughout the network, or integration on one computer is also possible, as for MultiScope. Fig. 2: MultiMap with several GeViSofts 5

8 2.3 Using with GeViScope When MULTIMAP is applied as the user-interface for GEVISCOPE, the digital image data is displayed through the media viewer that is directly integrated into MULTIMAP. MULTIMAP can manage up to 36 media viewers. Data for display in MULTIMAP is received via a separate connection to GEVISCOPE, established automatically during start-up. In addition to switching cameras through to media viewers, the display of the image data can be controlled. Any number of GEVISCOPEs may be operated or displayed using MULTIMAP and a site plan project. All the systems involved can be distributed in any way across the network, or can be collected on a single computer. Figure 3: MULTIMAP with a number of GEVISCOPEs 2.4 Using MultiMap with MultiScope and GeViSoft As MultiMap may be used for any system type individually, it is of course also possible to operate and display several different system types. MultiMap recognises the various system types (GeViScope, MultiScope, GeViSoft) and can connect to any user-defined number of such systems. MultiMap also maintains the necessary connections to the MultiViews for the display of picture data. Fig. 4: MultiMap with several GeViScope, MultiView, MultiScope und GeViSofts 2.5 System examples The following are short examples of systems with an explanation of their structures: Figure 5: GeViScope computer with MultiMap 6

9 This configuration describes a stand-alone system for controlling a GeViScope. The GeViScope software and MultiMap run together on one computer. Media viewers integrated into the site plan allow the image data provided by GeViScope to be displayed. Fig. 6: MultiScope with two monitors for MultiMap and MultiView This configuration is a stand-alone system for the control of one MultiScope. This example shows the server, recorder, MultiViewand MultiMap running together on a MultiScope system. A double graphics card facilitates the display of the site plan project on one MultiMap monitor and the picture data on the MultiViewmonitor. Using MultiMap, display of MultiScope and remote control of MultiVieware possible. Fig. 6: GeViSoft computer with MultiMap This configuration is a stand-alone system for the control of one GeViSoft. The server, IO client(s) and MultiMap are running together on one computer. MultiMap is displayed on the screen with the site plan project. Using MultiMap, GeViSoft can be displayed and its components controlled remotely. Fig. 7: MultiScope and GeViSoft on one computer with two monitors for MultiMap and MultiView This stand-alone system shows the two systems shown above integrated on one computer. MultiScope and its components, and GeViSoft and its components, are displayed and controlled remotely in one MultiMap with the site plan project. 7

10 Fig. 8: Any user-defined number of MultiScopeIis with several MultiViews, any user-defined number of GeViSofts and MultiMaps distributed throughout a network. This example shows a distributed computer system with GeViSoft, MultiViewand MultiScope. All the systems involved are displayed or controlled remotely by one, or several, central MultiMaps. 2.6 Licence to run MULTIMAP MULTIMAP requires a licence to run correctly. The licence is located on a hardware dongle. MULTIMAP Editor is not affected by this. It can be run on unlimited systems without a licence. If MULTIMAP does not find the necessary licence on start-up, then the user will see a relevant message. MULTIMAP will then only function in Demo mode for a limited time. After the time expires, MULTIMAP will be forced to end. The time remaining in Demo mode can be seen in the Info dialogue (select from menu). 8

11 3. Getting started quickly with a demo project The demo project included should make it easy to get started with MultiMap. It provides basic information on using the MultiMap-Editor, and demonstrates some possible operations in MultiMap based on the components used within the project. If you wish to design the demo project using this description, we would advise you to move the installed demo project 'mm.map' from the 'Maps' sub-directory in the installation directory to a safe location, alternatively rename the project. 3.1 Demo system A description of the demo system is provided here, followed by a step-by-step breakdown of the project creation. The demo project is based on a system consisting of a MultiScope, a GeViSoft, a MultiViewand a MultiMap. The MultiMap is integrated on a stand-alone computer. A double graphics card with two screens for MultiMap and MultiViewmay be used, or MultiView may be displayed as a window in the foreground overlaying MultiMap. Fig. 10: Configuration of MultiScope in the demo project MultiScope will search for a camera with the global number (MSC) 2 and a monitor with the global number (MSC) 1. An event (MSC) with the name 'AD event' should also exist. Where possible, the event source should be Activity Detection (a MultiScope digital input will also suffice). The basic configuration of the MultiScope is carried out accordingly using MultiSet. 9

12 Fig. 11: GeViSoft configuration in the demo project MultiScope will also search for a modular crossbar system and a digital input/output group from GeViSoft. The crossbar system manages two cameras with the global numbers (GeVi) 1 and 2 and a monitor with the global number (GeVi) 1. The input/output group manages three output contacts with the global numbers (GeVi) 1 to 3 and two input contacts with the global numbers (GeVi) 1 and 2. An event with the global number (GeVi) 1 should also exist. The event source may be another input contact. The basic configuration of the GeViSoft is selected using GeViSet. MultiView is used to display MultiScope picture data. To do this, MultiViewmust be in a special mode (MRI mode) and connect automatically to the local MultiScope server following start-up. The necessary settings are implemented in the MultiViewConnections and Options dialogue boxes. Camera signals are transmitted to the crossbar system and to the Multi-Scope. 10

13 Figure 12: GeViScope configuration in the example project A camera with global number (GSC) 1, and another camera with global number (GSC) 2, are expected on the GeViScope that is connected over the network. The basic configuration of the GeViScope is prepared using GSCSetup. The resulting hardware configuration for the demo project is shown in the following diagram: Fig. 13: Demo project hardware configuration This hardware configuration is displayed in the demo project and the user has the opportunity, using MultiMap and the demo project, to control all components (cameras, monitors, input contacts, output contacts and MultiView). Once the user-defined systems have been configured and started (MultiScope, GeViSoft, and MultiView), the site plan project can be created using the MultiMap Editor. While the project is being created, MultiMap and the 11

14 created site plan project can be started at any time in parallel to the Editor, allowing for immediate testing of the project Step 1: Save new layout plan project and layout plans it contains. After starting the MultiMap Editor (via the Start menu), a new layout plan project is created. With three layout plans are included in the project. These plans are based on the three graphic files 'overview.bmp', 'floor1.bmp' and 'floor2.bmp' from the 'DemoProjectGraphics' directory. The individual site plans should be given meaningful names such as 'Overview', 'First floor' und 'Second floor'. The names of the site plans are shown to the user for selection from the site plan list in MultiMap later on. At this stage, no icons are added to the new site plans. The layout plan project should be saved regularly during creation. If the name 'mm.map' has been given to the project and saved to the installation directory in 'Maps', then this file will be loaded automatically whenever MultiMap is started. Where another file name has been used, this file name should be entered using the command line when MultiMap is started, or selected from the file selection dialogue box after start up is complete. 12

15 3.1.2 Step 2: Creating the necessary connections The new connections to the local MultiScope server, to the local GeViSoft server and to the local MultiViewshould now be created in the list of connections Connections should also be given meaningful names, as they will be used several times during the site plan project creation process. The address "localhost" is given for the local connections, while the GeViScope server is addressed using the computer name or the IP address of the GeViScope PC. User name and password should be specified according to the configurations of the individual systems, to ensure the connections can be established automatically without further input when MultiMap is started. 13

16 3.1.3 Step 3: Inserting navigation icons in the site plans Once the site plans and the necessary connections have been created, the required icons may be placed within the site plans. To do this, first select the 'Overview' site plan from the list at the left side of the window. The graphic on which the site plan is based should now be displayed in the right section of the window. This is the working surface for positioning the icons. In order to be able to navigate between layout plans later in MultiMap using navigation symbols, two switch layout plan symbols are added. After selecting icon type, simply click on the site plan to place the icon in the desired location. In Icon Properties, a meaningful name is given to the icon and a corresponding site plan chosen. This site plan will appear when a MultiMap user selects the icon at a later date. A bit map previously created with a graphics tool may be used instead of the default Change Site Plan icons. Thus, from the registration page "Layout" to the symbol settings, the "ChangeMapFirstFloor.bmp" or 14

17 "ChangeMapSecondFloor.bmp" from the "DemoProjectGraphics" directory can be selected. The exact position of the icon on the site plan can be adjusted by dragging and dropping using the mouse, or using the cursor keys for the selected icon. At this stage it is possible to save the site plan project and test the project using MultiMap. 15

18 Once MultiMap has been started, the first site plan created within the site plan project will be displayed onscreen. At this stage it should be possible to navigate through the site plans using the site plan list or the change site plan icons created on the 'Overview' site plan. During start-up, in the background, MultiMap will also attempt to establish the connections that are already created. Connection status can be displayed with this After successful testing, you may close MultiMap and continue to work in the Editor Step 4: Inserting icons for the control and display of MultiScope In the 'Second floor' site plan, the options for using MultiMap with MultiScope and MultiVieware demonstrated. For this purpose, four icons are added to the site plan. The icon types and icon names are shown in the following table: Icon type MultiView MSC Monitor Event Camera Icon name MV Monitor 1 on MSC AD event Cam 2 on MV The MultiView icon facilitates the control of the connected MultiViewin MultiMap. 16

19 The MSC Monitor icon is configured in such a way that it can be used to control the local MultiScope monitor with the global number 1. 17

20 The Event icon displays the MultiScope event for the local MultiScope using the name 'Cam 2 AD'. While the event is running, a bitmap, created using any type of graphics tool, is displayed in flashing mode within the site plan. To achieve this, deactivate the 'Visible' option for the icon and replace the basic graphic with the 'adevent.bmp' graphic ('Layout' tab). To make the icon visible and flashing while the event is active, two settings should be adjusted for the 'Event started' ('Status' tab) icon status. The existing settings preset after the creation of the icon must be cleared first. 18

21 The camera icon controls the local MultiScope camera with the global number 2. Camera icon information and icon text can be inserted in the 'Layout' tab. 19

22 Once the site plan project has been saved, it may be tested again using MultiMap for correct functioning with the local MultiScope and the local MultiView. 20

23 Cameras may be displayed on the MSC monitor by firstly clicking on the monitor icon and then the camera icon. Cameras can be displayed in a MultiViewviewer in the same way. First select the viewer by clicking on the MultiViewicon (or alternatively in the MultiViewviewer) and then click on the camera icon. The camera images should appear in the viewer after a short time. Once the MultiScope event has been started (e.g. triggered by 'Activity Detection' or by a MultiScope digital input), the created event icon will begin to flash. After successful testing, MultiMap may be closed and you can continue to work in the Editor Step 5: Inserting icons for the control and display of GeViSoft. The "First floor" site plan shows the options for using MultiMap with GeViSoftII. For this purpose, nine icons should first be added to the site plan. The icon types and icon names are shown in the following table: Icon type Icon name GeVi output contact Arm / Disarm 1 GeVi output contact Arm / Disarm 2 GeVi input contact Armed 1 GeVi input contact Armed 2 Camera Cam 1 Camera Cam 2 Event GeVi Event 1 GeVi Monitor Monitor 1 GeVi output contact Open / Close door The GeVi monitor icon in MultiMap facilitates the control of the local GeViSoft monitor with the global number 1. The two camera icons represent the two cameras with the global numbers 1 and 2 (reference GeViSoft). The event icon represents the GeVi event with the global number 1. The output contacts are given the global numbers 1 to 3. Output contact 3 functions as a push button. 21

24 The two input contact icons represent the GeVi input contacts with the global numbers 1 and 2. They are initially declared invisible and their display will change when the contact is closed. A flashing user-defined graphic is then displayed. Icon settings should be selected accordingly. 22

25 Once the site plan project has been saved, it may be tested again using MultiMap for correct functioning with the local GeViSoft. 23

26 To display a camera on the GeVi Monitor requires a similar procedure to displaying MultiScope cameras. Output contacts may be opened and closed by simply clicking with the mouse, and output contact 3 has a push button function in this instance. The icon display will change when the GeVi event is started and the basic graphic (a green lamp) will be replaced by a different graphic (a red lamp). The basic graphics may also be replaced by user-defined graphics. If one of the two input contacts is closed, the configured user-defined graphic will appear on each occasion, and one of the two will also be displayed in flashing mode. After successful testing, MultiMap may be closed and you can continue to work in the Editor Step 6: Insert icons for the control and display of GeViScope. The options for using MultiMap in relation to GeViScope are illustrated on the "Third floor" site plan. For this purpose, 2 icons are first added to the site plan. The types and names of the icons may be found in the following table: Icon type Camera Camera Icon name Cam 1 (GSC) Cam 2 (GSC) The two camera icons represent the two cameras with global names 1 and 2 (with reference to GeViScope). So that it is possible to display the two cameras on a media viewer integrated into the site plan project in MultiMap, a new media viewer is added to the list of media viewers. Its settings are made in such a way that the media viewer is shown in MultiMap without a window title. The user is not to be allowed to close the media viewer. 24

27 The size of the media viewer for normal and maximized display is chosen in such a way that it usually only covers a small part of the site plan, but that it covers almost the entire site plan when maximized. The user can switch between the two displays in MultiMap by double-kicking. 25

28 Special settings must be made for the media viewer with reference to each site plan so that the media viewer is automatically only visible on the two site plans for the "Second floor" and "Third floor". To do this, the visibility of the media viewer is forced on for these two site plans, while the other two site plans are defined such that the media viewer is not visible when they are displayed. 26

29 Once the site plan project has been saved, the correct interaction of the GeViScope with MultiMap can be tested again. 27

30 GeViScope cameras and MultiScope II/III cameras can be switched through to the media viewer by a simple mouse click, assuming this has first been selected with the mouse (which causes the media viewer to obtain the focus). 28

31 3.1.7 Step 7: Adding responses to MultiMap events By defining responses to internal MultiMap events, numerous options are available to alert a user that a particular event has occurred. The following reactions are added : Event MSC event 'Cam 2 AD' starting MSC event 'Cam 2 AD' stopping GeVi Input contact 1 closing GeVi Input contact 2 closing GeVi input contact 2 opening Responses Display 'Change to second floor' flashing Change Site Plan icon Display 'Change to second floor' Change Site Plan icon, no longer flashing Display 'First floor' site plan Play 'ringin.wav' sound file repeatedly and display 'Change to first floor' flashing Change Site Plan icon Stop playing 'ringin.wav' sound file and display 'Change to first floor' Change site plan icon, no longer flashing When entering the individual responses, the first thing that should be defined is the event that requires a response, then the required responses. 29

32 A response type can be specified for each response. It is also possible to test the responses entered using MultiMap, once the site plan project has been saved. When events from the table are triggered, the set responses can be observed accordingly. After successful testing, MultiMap may be closed and you can continue work in the Editor Step 8: Site plan project settings Within Project settings it is possible to define general settings for the display of the site plan project in MultiMap. Default settings are used in the demo project. The set up of the demo project is now complete. The project may be tested using MultiMap once it has been saved. In the following sections, all MultiMap Editor and MultiMap functions are described in the form of a reference. 30

33 4. MultiMap Editor MultiMap Editor is used to create and maintain site plan projects. When the program is started, the main window will appear: The menu bar is located at the top of the window, and gives access to all Editor functions. The main and most frequently used functions can also be accessed via the toolbar (underneath the menu bar) or via individual context menus (e.g. the context menu for an icon). The list of site plans for the site plan project is displayed in the left section of the window. Clicking on one of the site plans will display the plan to the right of the site plan list. The plan may then be edited using the mouse and the functions in either the menu bar or the toolbar. Site plan icons can be selected by clicking with the mouse over the desired icon. The information for the selected icon is then displayed in the status bar at the bottom of the window. 4.1 Working with site plan projects Via the File menu, a new site plan project can be created, an existing project can be opened, and changes in a project currently open can be saved. The 'Reopen Site Plan Project' button allows rapid access to the last edited projects. Care should be taken when a project is saved to save all file paths of an icon and site plan graphics or sound files relative to the file path of the site plan project. This also includes the file paths for the icon basic graphics. For this reason, you should select the 'Save Site Plan Project As' option in the MultiMap Editor if you wish to move site plan projects. 4.2 Editing a site plan project The Project menu allows site plans to be added to a site plan project, facilitates access to the list of site plans, the list of connections, the list of responses to MultiMap internal events, and allows you to change the site plan project settings. 4.3 Changing site plan project settings The project settings are structured in multiple areas: General, Display MultiMap-Viewer, Configure Commands, Message LOG, Statistics, Action Instructions and Alarm Management. 31

34 Setting Site plan displayed after startup Display site plan for connected camera Icon drag and drop Minimize MultiMap viewer with MultiView Restore MultiMap viewer with MultiView Display connections between cameras and viewers Symbol Graphic Path Display login dialogue after start. Second user required in login dialog Auto. Logout after n minutes Display last layout plan again after end of alarm Function Determines the site plan for the site plan project that will be displayed when MultiMap is started Each time a camera is displayed in MultiView(manually or event-triggered), the system checks if the camera is present on the currently displayed site plan. If the camera is not present, the first site plan from the list that includes the camera will be displayed It is not possible to display a camera by simply clicking on it; the camera must be dragged to the monitor or the MultiViewviewer using the mouse MultiMap will be minimized whenever MultiViewis minimized MultiMap is restored whenever MultiViewis restored Connections between the MultiViewviewers and connected cameras are displayed Specifies file path for layout plan project, in which the symbol graphics are expected. After MultiMap starts, a login dialog is displayed, before the server connection is made. Specifies whether the control element for login with a second user should be displayed in the login dialogue. Specifies whether all connections should be automatically disconnected after n minutes, where the user carries out no action instructions. After the end of an alarm from a GeVi-Server, the active layout plan prior to the alarm is displayed again. The icon graphics path determines the file path for the location of the icon graphics for the site plan. The graphics used by the icons are stored by default in the 'DefaultSymbolGraphics' directory within the 'Maps' directory of the MultiMap installation directory (usually 'C:\MultiMap'). This setting facilitates the use of 32

35 personalised icon graphics sets in the site plan project. However, the graphics file names and tree structure must correspond to the 'DefaultSymbolGraphics' directory. To easily create a personalised icon graphic sets, copy and rename the entire directory. Personalised graphics files may then be created as required. When activating "Display last layout plan again after end of alarm", MultiMap notes the layout plan prior to an alarm and displays it again automatically after the alarm has ended. Thus, an alarm could ensure display of the relevant layout plan for an alarm with the help of a configured reaction (see section "Working with reactions to MultiMap-internal events) and then display the previously visible layout plan again, once the alarm has been acknowledged. If MultiMap should automatically disconnect all connections, where users have not operated MultiMap for n minutes, the "Auto. Logout after n minutes" setting must be activated. After all connections have been logged out, the login display is shown again, so the user can log in once more. Note: Activation of the setting "Display layout plan for switched camera" in conjunction with configured reactions (especially "Display layout plan") can lead to undesired effects! Note: The entries in the login dialogue currently only affect connections to GeVi-Servers. All other connections are made irrespective of the entries made here. For further information, see "Login Dialogue" section! 33

36 Setting Display window title Display site plan list Variable size Always in the foreground Window display Define size and position Display telemetry dialogue box automatically Display telemetry dialogue box after start-up Define position of telemetry dialogue box Function This setting deactivates the display of the MultiMap window title The list of site plans belonging to the site plan project is displayed in the left section of the MultiMap window Allows the user to change the size of the MultiMap window MultiMap is always displayed in the foreground and cannot be hidden by other windows Determines whether the MultiMap window is displayed in normal, maximized, or minimized mode following start-up Allows the user to define the size and position of the MultiMap window The telemetry dialogue box is displayed automatically when a user selects a telemetry-capable camera The telemetry dialogue box is always displayed after MultiMap start-up. Allows the user to define the position of the telemetry dialogue box Only allow special users to Saving fixed positions in the telemetry dialogue is only possible for a user save fixed positions registered in MultiMap (Settings "User name" and "Password"). Note: Some settings determine the maximum display size of layout plan graphics in MultiMap, without scroll bars being displayed. For further information, see "Size of Layout Plan Graphics" section! These settings allow the user to define the shortcut keys and the appearance of the tool bar and the context menus. MultiMap provides the option for the user to configure four toolbars (top, left, right and bottom left/right). Context menus are provided for the different icon types, as well as a general context menu. Any number of shortcut keys for fast command access may be defined. Each command can be assigned by dragging the command from the list in the lower right part of the dialogue 34

37 box over to the toolbar and the list of context menu entries or shortcut keys. The available commands are divided into categories. By selecting a particular category, the user can change the associated list of commands. Command functions are explained in "Operating Actions" section. When the 'Large Icons Toolbar' option is selected, the MultiMap toolbars are displayed in enlarged format. Note: The "Large symbol bar buttons" setting affects the maximum display size of layout plan graphics in MultiMap, without scroll bars being displayed. For further information, see "Size of Layout Plan Graphics" section! Setting Meaning Display after start The "Message LOG" dialogue is always displayed after MultiMap starts. Display window title Display of a window title can be suppressed with this setting. Adjust size The dialogue size can be adjusted by the user. Moveable The dialogue can be moved by the user. Only display message time Only the time and not the date is displayed for the messages displayed in the dialogue. Max. No. Messages Specifies maximum number of messages, which can be displayed in the message LOG. If this is exceeded, the oldest message is deleted. Allow LOG save Allows the user to save the contents of the message LOG as a file (text format or CSV format) in MultiMap. Allow connection exclusion Allows user to change connection exclusion list in MultiMap. list to be changed Connection exclusion list In the connection exclusion list, all messages from specific connections can be suppressed from being displayed in the message LOG (see below). Specify position and size Offers the option to specify the position and size of the dialogue. The "Connection exclusion list" button enables a list of connections to be made, whose messages are not to be displayed in the message LOG. 35

38 The messages from the selected connections are not displayed in the connection LOG - they are excluded from the display. Note: Only relevant messages from GeViSoft and MultiScope are displayed in the "Message LOG" dialogue. The functionality of the "Message LOG" dialogue is explained in the "Operating Actions" section! 36

39 Setting Display after start. Display window title Adjust size Moveable Only display n results Permit results save Permit changes to filter criteria Permit activation or deactivation of cyclic refreshing of the statistics Cyclic refresh of statistics after start Interval for cyclic refresh Specify position and size Permit closing Meaning The "Statistics" dialogue is always displayed after MultiMap starts. Display of a window title can be suppressed with this setting. The dialogue size can be adjusted by the user. The dialogue can be moved by the user. If this setting is activated, then only maximum n results will be displayed in the dialogue. The maximum number of results to be displayed can no longer be adjusted by the user within the dialogue. Allows the user to save the results of the statistics as a file (text format or CSV format) in MultiMap. Allows the user in MultiMap to change the filter criteria used for the statistics. Allows the user in MultiMap to activate or deactivate cyclic refreshing of the statistics. The statistics are updated once MultiMap has started. Defines the time interval, in seconds, between automatic updates of the statistics in MultiMap. Offers the option to specify the position and size of the dialogue. The user can close the "Statistics" dialogue in MultiMap. Note: The functionality of the "Statistics" dialogue is explained in the "Statistics" section! 37

40 Setting Display after start. Display window title Adjust size Moveable Display automatically Display window in foreground Specify position and size Meaning The " Action Instructions " dialogue is always displayed after MultiMap starts. Display of a window title can be suppressed with this setting. The dialogue size can be adjusted by the user. The dialogue can be moved by the user. The dialogue is automatically visible, as soon as an action instruction has to be displayed, due to a MultiMap-internal event. The dialogue appears in the foreground and covers all other windows, as soon as an action instruction has to be displayed. The dialogue is closed when the "Read" button is clicked. Offers the option to specify the position and size of the dialogue. Note: The functionality of the "Action Instructions" dialogue in MultiMap is explained in the "Display Action Instructions" section; the "Saving Action Instructions" section describes how to save action instructions and how to use previously saved action instructions is described in the section "Working with reactions to MultiMapinternal events! 38

41 Setting Display after start. Display window title Moveable User must comment on information of alarm User must comment on confirmation of alarm Allow to write in user comments Display layout plans, when alarms are displayed Information of alarms automatically twice Comments Specify position and size Meaning The " Alarm Management " dialogue is always displayed after MultiMap starts. Display of a window title can be suppressed with this setting. The dialogue can be moved by the user. The user must enter a comment in MultiMap when informed of an alarm The user must enter a comment in MultiMap when confirming an alarm User is allowed to write own comments in MultiMap on information or Confirmation of alarms. Carry out relevant layout plan switch automatically, if various alarms are presented Information of alarms is automatically carried out twice (similar to MBeg functionality) Enables a list of comments to be preset Offers the option to specify the position and size of the dialogue. The "Comments" button enables a list of comments to be preset, from which the user can select when informed of or confirming an alarm in the "Alarm Management" dialogue. Note: The functionality of the "Alarm Management" dialogue is explained in the "Alarm Management" section! Note: The "Display layout plans, when alarms are displayed" setting only ensures automatic layout plan switching, if relevant reactions to MultiMap-internal events are configured. If the reaction "Display layout plan" exists for the alarm to be presented, due to the MultiMap-internal event "GeVI Alarm has been started", then the layout plan set in the reaction is displayed automatically, if the user has the alarm displayed in the "Alarm management" 39

42 dialogue, with the function "Display" or "Display next alarm". Setting reactions to MultiMap-internal events is described in the section "Working with reactions to MultiMap-internal events"! Setting Output format Meaning Specifies the output format for all media viewers. Note: If the graphic output for the media viewer does not work because the CPU does not support SSE2, the problem can be rectified by changing the output format! 4.4 Layout graphic size In principle, the layout plans can be any size, based on the graphics available. However, in particular application instances, it is desirable to select the size of the layout plan graphics exactly, so that MultiMap uses the maximum space available for display and shows no scroll bars. To achieve this, the size of the layout plan graphics can calculated, based on screen resolution. With the following layout plan project settings, the maximum width of the layout plan graphics is calculated for "Screen resolution in horiz. direction" Pixels and "Screen resolution in vert. direction" Pixels: The MultiMap window title is displayed The layout plan list is displayed The size of the MultiMap window can be adjusted by the user. The tool bars are not maximised The Windows task bar is visible No double graphics card is used If the window title is not displayed, the maximum height increases by 19 pixels. If the layout plan list is not displayed, the maximum width increases by 180 pixels. If the user cannot adjust the window size, then the maximum width and height both increase by 2 pixels. If the 40

43 Windows task bar is configured, so that it automatically disappears to the background, when it is not used, then the maximum height can be increased by another 28 pixels. On the other hand, if the tool bars are maximised, then the maximum must be reduced by 46 pixels. If a double graphics card is used, then the maximum width and height both decrease by 8 pixels. With the following settings, a maximum layout plan size of 1019 x 716 pixels is achieved with a screen resolution of 1024 x 768 pixels. The MultiMap window title is not displayed The layout plan list is not displayed The size of the MultiMap window cannot be adjusted by the user. The tool bars are not maximised The Windows task bar automatically disappears in the background No double graphics card is used 4.5 Settings when using a double graphic map Use of a double graphics card makes sense for some system configurations. The double graphic card is operated in a special mode, known by some card manufacturers as "multiple display mode". This enables the Windows Desktop to be split horizontally into two screens. Thus, the horizontal screen resolution usually doubles. By using some settings in the double graphic card driver, some settings in the layout plan project and some settings in MultiView, configurations, such as those described in the "System Examples" section can be realised. Mostly, MultiMap covers one of the screens controlled by the double graphics card completely and MultiView the other. Thus, MultiView is operated in Full Screen view: Only the view window is displayed to show image data. The sizes and position of the MultiView window can be set in the MultiView settings, so that the window covers one of the two screens completely. The MultiView settings required for this are located in the MultiView documentation. The layout plan project setting "Specify position and size" enables the positioning of the MultiMap window on the second screen. Alternatively, the "Window Display" setting can be used with the value "Maximum". It is then necessary to activate a setting in the double graphics card driver, which prevents application windows from covering both screens, if they are maximised. In particular for double graphic cards from Matrox, the relevant setting is called "MaxVIEW" and is located in the driver's "Maximum Display Control". Otherwise, MultiView must be configured, so that the MultiView window stretches across the available second screen. Note: Activation of a possible setting "Save/replay window position" for the double graphics card, in conjunction with the configuration of window positions and window size for MultiMap or MultiView can lead to undesired effects! This characteristic should therefore not be activated. 41

44 The diagram shows a possible configuration. The left half (MultiMap) of the "virtual" Windows desktop is on the one screen and the right half (MultiView) is on the other screen. In order to start the two applications together, for example, a batch file can be set up, or links can be made in the Start-up directory. The "MRI" settings should be selected in MultiView, so that MultiView starts in full screen view automatically and makes all necessary connections to the participating MultiScope automatically on start up. The settings required for this are located in the MultiView documentation. Due to the missing window titles, the applications can only be ended by pressing ALT+F4 twice. 42

45 5. Working with connections The definition of connections allows MultiMap to recognise which systems it must communicate with during start-up and which systems can be remotely controlled by the user. New connections may be added and existing connections can be changed, removed and cloned. Connections can also be copied to the clipboard and pasted using the list context menu. These functions are available in almost every list and allow settings to be copied from one site plan to another. 5.1 Changing connection settings 43

46 Setting Type of connection Name Connect Address User name Password Time between connection attempts Set viewer matrix after start-up Viewer matrix Influence extended viewer display Extended viewer display Function Specifies whether the connection is to a MultiView, a MultiScope II, a GeViScope or a GeViSoft Meaningful name for further use in the site plan project Determines whether the connection should be established by MultiMap (connections can be temporarily deactivated for test purposes) IP address or name of the computer to which a connection is to be established. If a local computer is used, enter 'localhost'. User name used by MultiMap to log on to the GeVi server (for connection to GeViSoft only) Password required to establish a connection (for connection to MultiScope II currently always 'masterkey', not required for connection to MultiView) The elapsed time between an unsuccessful connection attempt and the new attempt Determines whether viewer matrix in MultiViewshould be set automatically following a connection to MultiView(for connections to MultiViewonly) The viewer matrix set automatically following a connection to MultiView(for connections to MultiViewonly) After a connection to MultiView, this option determines if the viewer representation in MultiViewwill be affected (for connections to MultiViewonly) The viewer display that is set automatically after a connection to MultiViewhas been established (for connections to MultiViewonly) Note: When using the login dialogue, the entries made currently only affect connections to GeVi-Servers. All other connections are made irrespective of the entries made here. If the login dialogue is displayed after MultiMap is started, the username and password in the settings are meaningless for a connection to a GeViSoft. For further information, see "Login Dialogue" section! Note: If you want to use a MultiScope's cameras for switching to MultiView, then the "Address" setting for the necessary connection to the MultiScope must agree with the computer name entered in "MultiScope Server Connections" (within MultiView). The connection to MultiScope must not be made obligatory for this ("Connect" setting not set). However, the correct settings are required by MultiView, so that it can request the required image data from the MultiScope. Further information is contained in section "Double function for connection with MultiScope"! Note: The "Set viewer matrix after start-up" setting should be activated if the site plan that appears after MULTIMAP has been started has a MultiView symbol that represents the MULTIVIEW for this connection; this is because the "Set special viewer matrix" of the MultiView symbol is not effective under these conditions. Further information is contained in the "Modify the Settings of a Symbol" section. 44

47 5.2 Double function for connection with MultiScope The connections with MultiScope stored in MultiMap have a double function. On the one hand, they are required to receive messages regarding start and stop for events via a direct connection to the MultiScope Server. The "Connect" setting must be activated for this. On the other hand, the connections are used for unique identification of MultiScope cameras for switching on MultiView windows. If a direct connection to the MultiScope Server is not required, then the "Connect" setting can be deactivated. The second function is necessary, because MultiMap also has to transmit an identification to MultiView for the MultiScope Server, to which the camera belongs, in addition to the global camera number, when switching to MultiView view windows. MultiView expects the information, which was entered in the MultiView connection dialogue for the "Computer Name" setting. If the connection is defined as a "local connection" in MultiView, then MultiView expects the name of the computer on which it is running. For the settings of a connection to a MultiScope Server in MultiMap, this means that the "Address/Computer Name" setting must be identical to the "Computer Name" setting in the MultiView connection dialogue, or that the setting has to be identical to the MultiView computer name (with a "local connection" in the MultiView connection catalogue). Example 1: MultiMap, MultiView and MultiScope are all running on computer "MSC2". In the MultiView connection catalogue, the connection to MultiScope is defined as a "local connection". Thus, the "Address/Computer name" characteristic in the respective connection to MultiScope in MultiMap must be "MSC2" (i.e. the computer name). Example 2: MultiMap runs alone on computer "VIEW", MultiView and MultiScope are run together on computer "MSC2". In the MultiView connection catalogue, the connection to MultiScope is also defined as a "local connection". Thus, the "Address/Computer name" characteristic in the respective connection to MultiScope in MultiMap must also be "MSC2". Example 3: MultiMap and MultiView are running together on computer "VIEW", MultiScope is running alone on computer "MSC2". In the MultiView connection catalogue, the connection to MultiScope is no longer a "local connection", but rather the "Computer Name" characteristic contains the IP address for the computer "MSC2". The characteristic "Address/Computer Name" must now also contain the IP address of the computer "MSC2". If the computer name "MSC2" is used in MultiMap instead, all connections will be made correctly, but error messages will occur when switching cameras to MultiView windows from MultiMap. If the computer name "MSC2" is used for both settings ("Computer name" characteristic in MultiView connection dialogue and "Address/Computer name in MultiMap), then there should not be any problems. 45

48 6. Working with site plans The site plans in the site plan project can be accessed via the 'List of Site Plans' menu item and the list in the left section of the MultiMap window. The site plan graphic is the basic visual work surface. Within this graphic, icons may be arranged as desired. Bitmap and JPEG graphic formats are supported for the site plan graphics. Here, as in almost every other list, site plans can be added, changed, removed, cloned, and copied to the clipboard and pasted. 46

49 6.1 Changing site plan settings The site plan must be assigned a meaningful name for use within the site plan project. The graphics file name (and therefore the associated file path) is set in the Windows standard dialogue box. The list of icons used in this site plan is displayed in the lower section of the 'Site Plan Settings' window. The icon settings can be accessed directly through this list rather than double-clicking on the site plan graphic. It is also possible to add, change, remove and clone icons, and to copy and paste icons. Please note that when icons are added, they are placed in the top left-hand corner of the site plan. The icons may then be moved into the required position using the mouse directly in the site plan. 47

50 7. Working with icons The icon list for the current site plan can also be accessed directly via the 'Icon List' menu item from the 'Site Plan' menu. By selecting an icon type, it is possible to restrict those icons displayed in the list to icons of the selected type. Otherwise those icon options already described for the 'Site Plan Settings' dialogue box are also available here. The majority of icon tasks are performed directly in MultiMap Editor using the displayed site plan. The icons can be roughly positioned using the mouse. For more accurate positioning, the cursor keys can be used. To assist with icon alignment, a grid may be activated and displayed using the MultiMap Editor settings. 48

51 Icon settings may be edited and icons can be removed, cloned or copied to the clipboard via the icon context menu. The icons may also be moved to the foreground or background and the sequence of superimposed/overlapping icons can be changed. Some information regarding the selected icon (position, size, type and name) is displayed in the status bar. The icon size may be changed using the mouse on the markings at the edge of the icon. The user can add icons quickly using the icon type buttons on the MultiMap Editor toolbar. After selection of icon type, the icon can be inserted by clicking on the desired location in the site plan. The '...Icon Settings' dialogue box will appear automatically, allowing selection of the desired icon settings. Click on 'OK' to add the icon. Simply click on an icon for instant access to its settings. 7.1 Icon types The following icon types are currently supported: Icon type Camera GeVi Monitor MSC Monitor MultiView GeVi output contact GeVi input contact Event GeVi Alarm Change site plan Text Graphics Macro MultiMap command Function Enables the control or display of a GeViSoft and/or a MultiScope II camera Enables the control or display of a GeViSoft monitor Enables the control or display of a Multi-Scope II monitor Enables the control or display of a Multi-View Enables the control or display of a GeViSoft output contact Enables the display of a GeViSoft input contact Enables the control or display of a GeViSoft or MultiScope II event Enables the display of a GeViSoft alarm Enables changing over to a different site plan within the current project Enables the display of free text as an icon Enables the display of a free graphic as icon Enables the processing of a macro consisting of a sequence of MultiMap, MultiViewor GeVi commands Enables the processing of a single MultiMap command 49

52 8. Changing icon settings Some settings are available for all icon types: Setting Name Visible Function Meaningful name for further use in the site plan project Determines if an icon is visible Sensitive Determines if the icon will respond to a mouse click The 'Sensitive' setting is not available for input contact icons, alarm icons, change site plan icons or text icons. Some of the icon types offer functions in the MultiMap toolbar. For some icon types an electronic focus is available so that these functions can be executed for a particular icon. The electronic focus will change when the user selects the icon in MultiMap using the mouse. The focus display can be deactivated by selecting the 'Display Focus' option. An electronic focus is provided for each display destination in MultiMap (MultiView icons, MSC monitor icons and GeVi monitor icons), for all camera icons and for all GeVi output contact icons. 50

53 The appearance of the icons can be specified in the 'Layout' tab for the icon settings. For each icon type (except for text icons) a basic graphic and transparent colour must be specified. The transparent colour defines the areas of the graphic through which the background (usually the site plan graphic) will be visible. A fixed background colour can also be specified for the icon. The size of the icons can be changed via the icon settings, in addition to using the mouse directly within the site plan. The 'Aspect Ratio' option allows the user to specify whether the height:width ratio should be maintained when the icon size is altered. Using the icon text settings, fixed text can be displayed next to the icon in the site plan graphic. The user can specify the text itself, its position relative to the icon, its transparency and the background colour. Note: If a freely-positionable symbol text is required, this can be achieved via an additional text symbol! In the 'Status' tab, the user can specify settings to change the icon display for different icon statuses. For 51

54 example, the GeVi input contact icon can be displayed as flashing when the associated input contact status is 'closed'. Possible statuses are dependent on the icon type. The options available are shown in the following list: Option Display additional graphic Replace basic graphic Display icon Hide icon Make icon sensitive Make icon insensitive Effect Overlays the basic graphic of the icon with an additional graphic Replaces the basic graphic of an icon with a different graphic. Makes an icon visible that was formerly configured as invisible Hides an icon that was formerly configured as visible Makes an icon sensitive that was formerly configured as insensitive Makes an icon insensitive that was formerly configured a sensitive Change icon background colour Changes the background colour of an icon Display icon flashing Displays the icon flashing as per the specified flashing period and duration By definition, there are no statuses for site plan change and text icons. The list of options may be as long as the user requires. However, each status can only be combined once for each option. All the well-known functions already given for previous lists are also available here (adding, removing, cloning, copying to the clipboard). The settings for icon manipulation will differ according to the option selected. Where the user wishes to display an additional graphic, or needs to replace the basic graphic, he/she will need to specify the graphics file name and the transparent colour of the graphic. To change the background colour of an icon, the colour must be specified. To display a flashing icon, the flashing period and duration must be specified in ms (the smallest increment being 300 ms). In addition to those settings that are available for almost all icons, specific settings for the individual icon types are available, and these are shown below. 52

55 8.1 Camera For a camera icon, the camera represented by the icon must be specified. The camera can be connected to either a MultiScope, a GeViScope or a GeViSoft individually, or even to both systems simultaneously. However, the connection must be selected and the global number specified on each occasion. The connections available for selection must first be configured using the connection list in the site plan project. 53

56 Basic graphics are already defined in various orientations especially for camera icons. The user selects the orientation using the switches. These switches have no effect on user-defined graphics. Basic graphics settings for cameras capable of telemetry are also defined. They can be selected by the button. The possible statuses of a camera icon will depend on which camera is represented by the icon. The following statuses are possible for a MultiScope camera: Status Camera does not exist on any MSC II server Camera is displayed in a MultiView viewer Function None of the connected MultiVieware connected to a MultiScope on which the camera exists. Camera images are displayed in one or several MultiViewviewers. 54

57 The following statuses are possible for a GeViSoft camera: Status No connection to remote GeVi server Camera does not exist on the GeVi server Camera is not available on the GeVi server Contrast error detected Synchronisation error detected Camera is displaying alarm pictures VS40 of the camera is active VS40 of the camera is not active VS40 of the camera is not available VS40 reports alarm PTZ camera head is not available Camera is displayed on a GeVi monitor Function No connection exists to the specified GeViSoft server. The camera does not exist on the specified GeViSoft server. The camera exists on the GeViSoft server but is not available. The camera is either deactivated or the user does not have permission to use it. The camera has insufficient contrast. There is a fault in the synchronisation signal of the camera. The camera is currently displaying alarm pictures. The camera is monitored by the associated VS40 The camera is not currently monitored by the associated VS40 VS40 monitoring of this camera is currently not available. The associated VS40 is either deactivated or not operative. VS40 monitoring of the camera reports an alarm. Telemetry control of the camera is currently not available. It is either deactivated or not operative. Camera images are displayed on one or more GeVi monitors. The following statuses are possible for a GeViScope camera: Status Meaning No connection to the remote No connection exists to the specified GeViScope server. GSC server Camera does not exist on The camera does not exist on the specified GeViScope server. the GSC server Note: The "Camera is displayed on a GeVi monitor" status can currently only be used for GeVi cameras, if the special client "GeViCam" is also used. This is a special client for GeViSoft. It evaluates all camera switching within a GeViSoft and sends relevant messages to a participating MULTIMAP. In order for MULTIMAP to evaluate the messages sent by the special client, it must be run with the command line switch "USEGEVICAMCLIENT". The functionality of the special client will be integrated in a later version of GeViSoft. It will then no longer be necessary to enter the command line switch. 55

58 8.2 GeVi monitor For a GeVi monitor icon, the user must specify which monitor for which GeViSoft server is represented by the icon. Here, the user should specify the connection to GeViSoft and the global number of the monitor. 56

59 The number of the connected camera can be shown in the GeVi monitor icon where required. For this purpose, the user will need to specify the output area relative to the left upper corner of the icon. Typeface and text colour can be selected and the display may be either transparent for the basic icon graphic, or have an opaque background in a specified colour. The following statuses are possible for a GeViSoft monitor: Status Function No connection to the remote No connection exists to the specified GeViSoft server. GeVi server GeVi monitor does not exist. The monitor does not exist on the specified GeViSoft server. Monitor not available on the GeVi server Monitor is currently displaying a cycle Monitor is currently displaying a camera Monitor is currently displaying alarm pictures The monitor does exist on the GeViSoft server, but is not available. The monitor is either deactivated, or the user does not have permission to use it. The monitor is currently displaying a camera cycle. A camera is currently displayed on the monitor. The monitor is currently displaying alarm pictures. 57

60 8.3 MSC monitor For a MultiScope monitor icon, the user must specify which monitor for which MultiScope server is represented by the icon. Here, the user must specify the connection to the MultiScope server and the global number of the monitor. The global number of a currently displayed camera cannot be displayed in an MSC monitor icon. This number is not recognised by either MultiMap or the connected MultiView. The following statuses are possible for a MultiScope monitor: Status MSC II monitor does not exist Function None of the connected MultiViewhave a connection to a MultiScope server on which the monitor exists. 58

61 8.4 MultiView Only the relevant MultiView connection should be specified for a MultiView icon. 59

62 Certain colours may be configured for the layout of the MultiView icon. The colour of the viewer matrix can be specified, and the user may also select the colour of selected viewers, or the colour of the active viewer and the master viewer. The user should specify the area in the icon in which the viewer matrix is displayed in relation to the left upper corner of the icon. The setting 'Set Special Viewer Matrix' allows the user to specify that a particular viewer matrix is always selected in the associated MultiView, whenever the site plan associated with the icon is displayed. Note: The "Set Special Viewer Matrix" setting is not effective if the site plan associated with the symbol is displayed after MULTIMAP started. The "Set viewer matrix after start-up" setting for the MULTIVIEW connection can be used for this. Further information is contained in the "Modify the Settings of a Connection" section. The following statuses are possible for a MultiView Status Function No connection to remote MultiView No connection exists to the specified MultiView. A magnified viewer is displayed One of the MultiViewviewers is displayed in full screen mode. 60

63 8.5 GeVi output contacts For a GeVi output contact icon, the user must specify which contact for which GeViSoft is represented by the icon. Here, the user must enter the connection to the GeViSoft server and the global number of the output contact. 'Functional Mode" allows the user to specify the behaviour of the icon in MultiMap (and therefore also the behaviour of the output) when selected with the mouse. The following settings are possible: Functional Mode Switch Button Function With every mouse click, the output contact switches between the statuses 'open' and 'closed'. When the mouse button is pressed, the output contact either opens or closes and when the mouse button is released, it closes and opens respectively. Close contact only The output contact is closed with a mouse click. Open contact only The output contact is opened with a mouse click. The following statuses are possible for a GeViSoft output contact: Status No connection to remote GeVi server GeVi output contact does not exist Function No connection exists to the specified GeViSoft server. The output contact does not exist on the specified GeViSoft server. GeVi output contact not available on The output contact does exist on the GeViSoft, but is not available. The the GeVi server output contact is either deactivated, or the user does not have permission to use it. GeVi output contact is open GeVi output contact is closed GeVi output contact alternating The output contact is currently open. The output contact is currently closed The output contact is currently alternating. 61

64 8.6 GeVi input contacts For a GeVi input contact icon, the user must specify the connection to the GeViSoft server and the global number of the input contact. The following statuses are possible: Status Function No connection to remote No connection exists to the specified GeViSoft server. GeVi server GeVi input contact does not The input contact does not exist on the specified GeViSoft server. exist. GeVi input contact not The input contact does exist on the GeViSoft, but is not available. The input available on the GeVi server contact is either deactivated, or the user does not have permission to use it. GeVi input contact is open The input contact is currently open. GeVi input contact is closed The input contact is currently closed. Status of GeVi input contact The state of the input contact is currently not known in GeViSoft. is unknown 62

65 8.7 Events An event icon can represent a MultiScope event or a GeViSoft event. The connection must be selected on each occasion and the global number or event name specified. Where the event icon needs to be sensitive, the user can specify in the "Functional Mode"' settings how the icon should respond to mouse clicks in MultiMap (and therefore also the behaviour of the event), in a similar way as for the GeVi output contacts. The following settings are possible: Functional Mode Switch Button Start event only Stop event only Function With each mouse click, the event is started or stopped depending on the current status. When the mouse button is depressed, the event either starts or stops, and when released, it stops and starts respectively. The event is started with a mouse click. The event is stopped with a mouse click. The following statuses are possible for an Event: Status No connection to the remote server Event does not exist Event was started Function No connection exists to the specified GeViSoft or MultiScope server. The event does not exist on the specified GeViSoft or MultiScope server. The event is currently running. 63

66 8.8 GeVi alarm The GeVi alarm icon represents a GeViSoft alarm. The connection must be selected and the global number or the alarm name specified. The following statuses are possible: Status No connection to remote GeVi server GeVi alarm does not exist. GeVi alarm was started GeVi alarm was confirmed Function No connection exists to the specified GeViSoft server. The alarm does not exist on the specified GeViSoft server. The alarm is active but not confirmed or acknowledged. The alarm is already confirmed but not yet acknowledged. 64

67 8.9 Site plan change The site plan that MultiMap should display when the respective icon is selected by a mouse click, should be chosen from the list of available site plans in the site plan project Text Here, the user can specify settings for the text to be displayed, the typeface and display. Via the 'Transparent Background' setting, the user can specify that the text will be displayed on an opaque background in a preselected colour Graphics Apart from general options, the graphics icon contains only those settings that are relevant for the graphic to be displayed. These settings are identical to the settings for the basic graphics of other icons. 65

68 8.12 Macros Using the macro icon, a sequence of commands can be defined that will be executed in sequence when the user clicks on the icon in MultiMap. The standard features are available for the command list (add, change, remove, clone, copy via clipboard). Three types of command are supported: MultiMap commands, MultiViewcommands and GeVi commands. A MultiMap command macro-command offers all the options that can also be assigned to the toolbar, context 66

69 menus and shortcut keys via the site plan settings. The command functions are explained in the 'Command Operations' section. Note: The MultiViewand GeVi commands are used to configure special functions, a feature not yet available via other icons. These commands should be performed by 'experts' only, using the relevant documentation as reference. The MultiViewmacro command allows an MRI command in plain text to be sent directly to a MultiView. For the exact syntax of the MRI commands, please see the MRI (MultiViewRemote Interface) documentation. Two of the most important MRI commands are explained in brief below: viewermatrix(matrix=...); The command 'viewermatrix' displays the MultiViewviewers. The following values may be entered for the parameter 'matrix' parameter: Value Function vmnone No viewer vm1x1 1 viewer vm2x2 4 viewers vm3x3 9 viewers vm4x4 16 viewers vm5x5 25 viewers vm6x6 36 viewers Example: The command 'viewermatrix(matrix=vm5x5);' instructs MultiViewto display 25 viewers. viewerconnect(viewer=point(x=...,y=...),server=...,camera=...,playmode=...); The command 'viewerconnect' connects a camera to a viewer and activates the requested playback mode. Parameters 'X' and 'Y' determine the viewer. Counting begins with the top left viewer with 'X' and 'Y' each at zero. The 'server' parameter determines the MultiScope server with a camera for connection. Here, the user must enter the computer name that was configured in the dialogue box 'MultiScope Server Connections' (in MultiView). The global number of the camera is specified in the 'camera' parameter. The 'play mode' parameter determines the desired playback mode. The 'live' value facilitates quasi-live playback mode in this case. Example: The command line "viewerconnect(viewer=point(x=0,y=0),server=localhost,camera=1,playmode=live);" 67

70 enables the display of the camera with the global number 1 of the local MultiScope server in the top-left section of the viewer in quasi-live mode. The GeVi macro command makes it possible to send a GeVi action in plain text directly to a GeVi server or a GeVi client. Please see the documentation on GeVi actions for the exact syntax. The macro icon has only one status for the definition of settings: 'Icon was clicked'. This status is intended mainly for the display of the mouse click on the macro icon (e.g. by replacing the basic graphic 'Button Not Pressed' with a graphic 'Button Pressed') 8.13 MultiMap command This icon facilitates the processing of a single MultiMap command. All those commands that can also be assigned to the toolbar, context menus and shortcut keys via the site plan project settings, may also be individually assigned to an icon. The command is executed when the icon is clicked by a user in MultiMap. The functions of those commands are explained in 'Command Operations' 68

71 9. Working with responses to internal MultiMap events The list of responses to MultiMap internal events can be maintained via the menu item 'Responses to Events' in the 'Project' menu. As with all other lists, entries may be added to this list, changed, deleted, cloned and inserted by copying to the clipboard. 69

72 A number of different MultiMap internal events can be distinguished, and a list of different responses for each triggered within MultiMap. The following types of MultiMap events exist: Type of MultiMap event MSC II event starts MSC II event stops GeVi alarm was started GeVi alarm was confirmed GeVi alarm was acknowledged GeVi input contact closes GeVi input contact opens GeVi event starts GeVi event stops Function The start of an MSC II event triggers the response. The end of a MSC II event triggers the response. The start of a GeVi alarm triggers the response. The confirmation of an alarm triggers the response. The acknowledgement of a GeVi alarm triggers the response. The closing of a GeVi input contact triggers the response. The opening of a GeVi input contact triggers the response. The start of a GeVi event triggers the response. The end of a GeVi event triggers the response. 70

73 The following responses are possible within MultiMap: Type of Response Display site plan Display Action Instructions Display icon flashing Display icon no longer flashing Display icon Hide icon Make icon sensitive Make icon insensitive Play sound file once Play sound file in loop Stop playing sound file Update statistics Function Displays the specified site plan Displays action instructions set. The icon is displayed flashing The specified flashing period and duration is used A previously flashing icon is displayed no longer flashing Displays a previously hidden icon Hides the specified icon Makes a previously insensitive icon sensitive again Makes the specified icon insensitive Plays the specified sound file once Continuously repeats the specified sound file Stops a sound file playing in loop Updates the data in the "Statistics" dialogue Response settings will differ according to the selected type. If the user wishes to display a certain site plan or change the display of a particular icon, he/she must specify the site plan and/or the icon. Same applies for displaying one action instruction. In order to display an icon in flashing mode, the flashing time period and the duration must be set in ms (the smallest increment being 300 ms). To play a sound file, the file path must be selected. The user may select any number of responses for an event. The defined responses must not be mutually exclusive (e.g. displaying and hiding of the same icon). Note: If a site plan project, contrary to expectations, does not automatically display site plans due to the responses configured, this may be due to the activated setting 'Display Site Plan for Connected Camera' in the site plan project. Further information can be found in the section 'Changing Site Plan Project Settings'. 71

74 10. Store action instructions The list of action instructions can be managed via the command "List Action Instructions", in the "Project" menu. In this list as all other lists, it is possible to insert, change, remove clone, as well as copy and paste entries via the clipboard. The entry made in "Instructions" is displayed in the MULTIMAP Viewer in the "Action Instructions" dialogue, as soon as the action instructions are presented, due to a MULTIMAP-internal event. Note: Use of the action instructions stored here is explained in the sections "Working with reactions to MULTIMAP internal events" and "Display Action Instructions"! 72

75 11. Working with Media Viewers By adding media viewers to the site plan project, the user can display digital image data in configurable display regions in the MULTIMAP viewer. A MULTIVIEW is not needed for this. MULTIMAP obtains the image data that is to be displayed directly through a connection, defined in the site plan project, to MULTISCOPE II/III or GeViScope. A number of media viewers may be created, and can be configured freely. Both the behaviour and layout of the viewers are specified through their configuration in the site plan project. The list of viewers can be managed via the "List of Viewers" command in the "Project" menu. In this list, as in all other lists, entries can be inserted, changed, removed, cloned, or copied and pasted via the clipboard. Note: The maximum number of media viewers within one site plan project is limited to 36. The media viewer settings are divided into a number of areas: general, display, automatic linking and special settings for site plans. 73

76 Settings Display after start Display window title Adjustable size Moveable Display additional data Maximisation permitted Closing permitted Zoom permitted Standard display mode Meaning The viewer is displayed after MULTIMAP has started. Display of a viewer's window title can be suppressed with this setting. The viewer then looks less like a window, and more like a display area integrated into the site plan. The size of the viewer can be adjusted by the user. The viewer can be moved by the user. As well as the image data itself, the viewer shows further information relating to the image currently being displayed at its bottom edge. The user can switch display of the MULTIMAP viewer between normal and maximised modes. The user can close viewers in the MULTIMAP viewer. The user can drag with the mouse to digitally zoom the viewer image data in the MULTIMAP viewer. Specifies the display mode that will automatically be used to show images whenever a camera is manually switched through to the viewer. 74

77 A distinction is made in the MULTIMAP viewer between the normal and the maximised display of a media viewer. The user can switch between the two modes, provided this is permitted by the viewer settings in the site plan project. The size and position of the viewer can be adjusted with reference to the entire desktop area. 75

78 A defined camera can be switched through to a media viewer automatically after the MULTIMAP viewer has started up. The specified camera will be switched through, with the selected display mode, immediately a connection to the associated MULTISCOPE II/III or GeViScope has successfully been established. 76

79 In addition to the media viewer settings that have already been explained, it is possible to define further individual settings for the viewer of each site plan in the site plan project. They have their effect when the specified site plan is displayed in the MULTIMAP viewer. 77

80 Settings Visibility Normal or maximised display Switch camera Meaning The viewer is or is not shown as soon as the specified site plan is displayed. The viewer is shown in normal or maximised mode as soon as the specified site plan is displayed. The defined camera is switched through to the viewer in the configured display mode, as soon as the specified site plan is displayed. 78

81 The size and position of the normal and maximised displays change in accordance with the settings that have been made as soon as the specified site plan is displayed. Note: Use of the media viewer that is configured here is described in the "Media Viewers" section. Note: Not too many media viewers should be integrated into a site plan project, as the display of live image data in the MULTIMAP viewer will affect the overall performance of the system. 79

82 12. MultiMap Editor settings Via the 'Settings' menu item in the 'File' menu, the user can activate a grid to facilitate alignment of the icons within the site plan. The setting 'Use Grid' activates the grid. 'Display Grid' makes the grid visible. The width and height of a grid cell can also be configured. 13. MultiMap viewer MultiMap viewer provides the user with the site plan projects created using the MultiMap editor in the form of a user interface and display Starting MultiMap When the application is started, the site plan project 'mm.map' is always loaded from the sub directory 'Maps' of the installation directory by default. If the project cannot be loaded, the user has the option to select a site plan project via a standard Windows dialogue box. Any site plan project may be used via the command line switch 'MAPPROJECTFILENAME', without display of the Windows standard dialogue box, e.g.: MultiMap.exe /MAPPROJECTFILENAME="c:\multimap\maps\MyMapProjectFile.map" 80

83 13.2 Structure of the MultiMap window The MultiMap window display is affected by the settings in the site plan project selected in MultiMap Editor. If toolbars have been configured, these will be displayed at the upper and bottom edges of the window, at the right and the left. The list of site plans is displayed at the left side, if this option was already activated in the site plan project. Once MultiMap has started up, the desired site plan with its allocated icons will appear in the remaining area of the window. Depending on the configuration, a telemetry dialogue box for control of the pan/tilt or dome cameras will also appear. The icons and the site plan contain context menus. The structure of these menus is defined in the site plan project. Some of the icons provide functionality to the user via the toolbar in MultiMap. So that these functions can be executed for a particular icon, an electronic focus is available for some icon types (the display of a focus is specified for each icon individually within the site plan project). 81

84 The focus will change when a user selects an icon with the mouse. A focus is available for each display destination (MultiViewicons, MSC II monitor icons and GeVi monitor icons), for all camera icons and for all GeVi output contact icons Login dialogue The login dialogue display can be forced after starting MULTIMAP using the layout plan settings. Connections are only then made after login information is entered. Logout and login again is enabled by the MULTIMAP command ("Logout / Login"). Further information on the command is contained in the section "Operating Actions"! When logging out, all connections are first terminated. After login information is entered, an attempt is made to make all connections again. Note: The entries in the login dialogue currently only affect connections to GeVi- / GSC-Servers. All other connections are always made irrespective of the entries made here! 82

85 By using the GeViSoft configurable User and Privileges profile, it is possible to make specific resources (including Cameras, monitors, input and output contacts) available only to particular users. Whether resources are available to the user currently logged in or not can be visualised using the respective symbols (e. g. State "Monitor is not available on the GeViSoft Server" of a GeVi Monitor). The resources identified with the red question mark symbols may exist on the connected server, but are not available to the user currently logged in and may not be used by them. Note: If MULTIMAP should automatically disconnect all connections, where users have not operated MULTIMAP for n minutes, the "Auto. Logout after n minutes" setting must be activated. After all connections have been logged out, the login dialog is displayed again. Further information on the command is contained in the section "Edit Layout Plan Settings"! 83

86 13.4 Command operations The available commands that may be accessed by a user via the context menus, toolbar buttons or shortcut keys (depending on the site plan project settings, 'Command Configuration' tab in the MultiMap Editor) are shown below: General commands: Command Function Displays connection lines between the MultiViewviewers and the cameras displayed in the viewers. Displays or hides the list of site plans Displays or hides the telemetry dialogue box. Associates the telemetry dialogue box with the currently controlled camera, or cancels the association. Displays the dialogue box with information on the status of the individual connections to the displayed systems. Terminates all connections and displays the login dialogue box to re-establish the connections. Displays the "Message LOG" dialogue or not. Displays the "Statistics" dialogue or not. Displays the "Action Instructions" dialogue or not. Displays the "Alarm Management" dialogue or not. Displays (or hides) the "List of Media Viewers" dialog Note: The entries in the login dialogue currently only affect connections to GeVi-/GSCServers. All other connections are made irrespective of the entries made here. For further information, see "Login Dialogue" section! Note: The functionality of the "Statistics" dialogue is explained in the "Statistics" section! All messages sent between MULTIMAP and GeViSift or MULTISCOPE are displayed in the "Message LOG" dialogue. 84

87 The appearance and functionality of the dialogue are affected by the Layout Project settings. Button Function Enables the connection exclusion list to be changed (see section "Edit Layout Plan Settings"). Enables the current entries in the "Message LOG" dialogue to be saved in a file. Two formats are supported: Text format and CSV format. "Freezes" the current entries in the "Message LOG" dialogue and adds no further entries. This state can be reversed by pressing the button again. The messages accumulated in the interim period are not stored. Note: The message text of the individual messages is generated by possible messages from the GeViSift and MULTISCOPE II systems. It is not subject to translation and so is always displayed in English! Commands relating to the focused MultiViewicon (i.e. commands controlling or affecting the associated MULTIVIEW): Command Function Does not display a viewer Displays 1 viewer Displays 2 x 2 viewers Displays 3 x 3 viewers Displays 4 x 4 viewers Displays 5 x 5 viewers Displays 6 x 6 viewers Switches the extended viewer display on or off Displays the MultiViewwindow in full screen view Displays the MultiViewwindow in thumbnail view Minimizes or restores the MultiViewwindow Connects all cameras on the current site plan in sequence for display in the MultiViewviewers Clears all MultiViewviewers 85

88 Commands relating to the focused MultiViewicon (i.e. commands that control or affect the associated MULTIVIEW). Command Function Clears the active viewer Displays the first picture of the previous event from the connected camera Displays the first picture of the next event from the connected camera Displays the first picture available in the database for the connected camera Displays the last picture available in the database for the connected camera Displays pictures from the connected camera backward in fast sequence in reverse chronological order Displays pictures from the connected camera in fast sequence in normal chronological order Displays pictures in normal sequence in reverse chronological order Displays pictures in normal sequence in normal chronological order Displays the previous picture Displays the next picture Displays the pictures in quasi-live mode (precondition: the pictures must be recorded by the MultiScope II at a suitable frequency) Stops replay of pictures and shows the last picture displayed in the viewer Displays the pictures in the viewer in black/white or in colour (Precondition: the pictures must have been recorded in colour) Activates or deactivates fast decoding of pictures. Fast decoding increases the replay rate of pictures, but impairs the reproduction quality. Displays the pictures rotated by 180º Displays a mirror image of the pictures Activates or deactivates full screen display of the viewer in the MultiViewwindow Prints the picture currently displayed in the viewer to the default printer of the computer running the MultiViewsystem (this does not need to be the MultiMap computer). Facilitates the restriction of the data quantity for the connected camera for a specific time period (filter). Enables searching of picture data for pictures within a specific timeframe. 86

89 The user may specify the date and time for picture data searches or to restrict picture data quantity (filter). Picture data restriction settings will remain active until the 'Clear' function is selected. Commands relating to the focused monitor icon (i.e. commands that control of affect the associated monitor): Command Function Clears the monitor display Starts a camera cycle on the monitor Stops the camera cycle currently displayed on the monitor Starts the standard camera cycle on the monitor 87

90 The global number of the camera must be specified to start the cycle. Commands relating to the focused camera icon (i.e. commands that control or affect the associated camera): Command Function Starts a tour of fixed camera positions (only supported for GeViSoft telemetry cameras) Stops the currently running tour of fixed camera positions (only supported for GeViSoft telemetry cameras) Starts the standard tour of fixed camera positions (only supported for GeViSoft telemetry cameras) The global number must be specified to start the tour. Commands relating to the focused GeVi output contact icon (i.e. commands that control or affect the associated output contact): Command Function Causes the output contact to alternate 88

91 To alternate the output contact, the user must specify the period duration and the pulse duration. Closing or opening the output contact (e.g. by the user with the mouse) will terminate alternation. The user can perform further operations with the aid of the mouse and the icons directly within the site plan. A camera can be displayed in a monitor or a MultiViewviewer, depending on the settings in the site plan project, either by clicking with the mouse, or by dragging the camera icon over to the monitor or viewer (drag and drop). If drag and drop mode is not activated (setting in the site plan project), the monitor or the MultiViewviewer should be selected with the mouse. The icon will then acquire the focus where the focus display is activated for this icon (setting in the site plan project). The user will then need to select the camera for connection by simply clicking with the mouse, thereby concluding the connection process. If the focused camera, or the camera displayed in the active viewer of the focused MultiViewis a pan/tilt or dome camera, it can be controlled via the telemetry dialogue box. The dialogue box offers the same range of functions as in MULTIVIEW. For a detailed description of these functions, please refer to the MultiViewdocumentation. Note: In order to permit fixed positions to be saved only by one specific user, can be activated in the layout plan settings in the option "Only permit fixed positions to be saved by specific user." It is then only possible for fixed positions to be saved by the user entered in the layout project settings. The user must login in MULTIMAP with their user name and password to do this. Further information is contained in the sections "Edit Layout Plan Settings" and "Login Dialogue"! 13.5 Statistics The "Statistics" dialogue gives the user the option to evaluate the databases connected to the GeVi Server with MULTIMAP. The appearance and functionality of the dialogue are affected by the Layout Project settings. Note: Display of the Statistics dialogue either takes place automatically after MULTIMAP starts (setting "Display after start" in the layout project settings) or the user controls the display via the respective command. Further information is contained in the sections "Edit Layout Plan Settings" and "Operating Actions"! 89

92 Button Function Enables specific data to query specific data from the database connected to the GeVi Server with MULTIMAP by specifying filter criteria. Allows the user to update the statistics, manually or cyclically, in accordance with the previously defined filter criteria. Permits graphic evaluation of the results displayed in the alarm or action list. Enables the current query results displayed in the "Statistics" dialogue to be saved in a file. Two formats are supported: Text format and CSV format. Note: In addition to manual and cyclic triggering of statistical updates, this can also be done through a reaction to an event internal to MultiMap. MultiMap's internal events include, for instance, "GeVi event started" and "GeVi event stopped". Further information can be found in the section entitled "Working with reactions to MultiMapinternal events". The user must first specify filter criteria, in order to export data from a GeVi-Server database. The GeVi Server, whose database is to be queried, is selected via the "Connection" setting. Only connected GeVi Servers appear in the list of possible connections. The "Alarms with the following criteria" and "Actions with following criteria" decide whether the results from the query concern alarms or actions. A GeVi Server database contains alarms, which can be completed or still active. In addition, it contains actions, which represent all messages occurring in the GeViSoft belonging to the GeVi Server. Because the database cannot reach an unlimited size, it only contains a limited number of past alarms and actions. The number is determined by the size of database specified in GeViSoft. Further information is contained in the GeViSoft documentation! The further settings specify the criteria, which limit the number of results from the query. Various criteria can be defined, dependent on result type selected (alarms or actions). Multiple activated criteria are applied with an AND link. 90

93 Example: The user wants to query all alarms dated between 9.00 am and 4.00 pm from the database of the GeVi server named "GeVi on local machine". However, only the alarms displayed on monitor group 1 are to be displayed. The following filter criteria must be entered: After confirming the required criteria, the query is carried out with "OK". Dependent on the appearance of the query and the size of the database, this may take some time. The results investigated by the query are then displayed in the "Statistics" dialogue. If more information is required on one of the alarms in the list of results, this is available by double clicking on the respective entry in the list. Note: If the characteristic "Use wild chars" is activated for a criteria, then the "*" place holder can be used. For example, should you want to query all alarms, whose name begins with the string "New", activate the "Wildchars characteristic for the criteria "Only alarms with name" and enter "New*" as the name! 91

94 The "Alarm Details" dialogue shows general information on the alarm and a list of actions, which are related to the alarm. Dependent on the size of the database, the construction of this list can take some time. The list contains actions, which were involved at the start, the confirmation or at the stop of the alarm. It can be saved in a file via The text format and CSV formats are supported here as well. In addition to displaying the results in the form of a list, the button permits a graphic evaluation of the displayed results. Two types of graphic evaluation are supported: absolute frequency distribution and time-based frequency distribution. Either can be applied both to alarms and to actions. 92

95 The absolute frequency distribution displays the absolute frequency with which alarms or actions occur as a column chart, in ascending order. Time-based frequency distribution displays the frequency of alarms or actions with reference to a particular period of time. The time period (hours, days, weeks,...) can be selected by the user. 93

96 Note: The names of the actions and their respective data are generated by the possible messages in the GeViSoft system. They are not subject to translation and so are always displayed in English! 13.6 Display action instructions In the "Action Instructions" dialogue, users can display action instructions dependent on the occurrence of MULTIMAP-internal events. The appearance and functionality of the dialogue are affected by the Layout Project settings. Should an additional action instruction be displayed (due to an internal MULTIMAP event), whilst the user is reading an action instruction, this will be stored temporarily and displayed as soon as the user has pressed the "Read" button. Note: Display of the Action Instructions dialogue either takes place automatically after MULTIMAP starts (setting "Display after start" in the layout project settings) or the user controls the display via the respective command. Otherwise, the dialogue appears automatically, when a MULTIMAP internal event occurs, which should react by displaying an action instruction. Further information is contained in the sections "Edit Layout Plan Settings" and "Login Dialogue", "Saving Action Instructions" and "Working with reactions to MULTIMAP internal events"! 94

97 13.7 Alarm management The "Alarm Management" dialogue gives the user the option to evaluate the databases connected to the GeVi Server with MULTIMAP. The appearance and functionality of the dialogue are affected by the Layout Project settings. In the top section of the dialogue, a maximum of two monitor groups with their respective active alarms for the GeVi Server selected are displayed. Using the buttons, all existing monitor groups can be navigated. The selected alarm, with which some of the dialogue functions are connected, is displayed with a blue background. The respective monitor group automatically becomes the selected monitor group. Use the mouse to select an alarm. The dialogue is initially displayed minimised. Use the buttons to expand the display. The buttons visible in the lower section of the dialog are then expanded with additional functions. Note: In order to process alarms from various GeViSoft servers, the connection to the GeVi Server must be changed in the expanded dialogue display! Note: Display of the Alarm Management dialogue either takes place automatically after MULTIMAP starts (setting "Display after start" in the layout project settings) or the user controls the display via the respective command. Further information is contained in the sections "Edit Layout Plan Settings" and "Operating Actions"! Button Comments Information End Function The user can select comments from a list previously defined in the Layout Plan Project settings, or enter a new comment, which is then transmitted with the alarm information or Alarm confirmation to the GeVi Server database. The alarm selected has been informed. The alarm selected is identified as being "Processed" (alarm confirmation). 95

98 Display Show next alarm Description The alarm selected is shown on the relevant monitors. The next alarm of the selected monitor group is shown. The description of the selected alarm, as well as the description of the respective monitor group is displayed for information. Instructions Provided that action instructions for the selected alarm have been defined in the Layout Project Settings, these will be displayed again. Note: Further information on predefining comments is contained in the section "Edit Layout Plan Settings". Working with action instructions stored here is explained in the sections "Saving Action Instructions" and "Working with reactions to MULTIMAP internal events"! 96

99 13.8 Media Viewers The "List of Media Viewers" dialog gives the user the option of making media viewers that are configured in the site plan project visible or of hiding them. Any visible media viewer can obtain the focus, which means that a simple click on a camera symbol can be used to switch it through. The commands available for controlling the media viewer that has the focus largely correspond to the commands that can be applied to the active window of a MULTIVIEW symbol. Note: The section covering "Operating Actions" contains more information on the commands that are available to affect the media viewer. 97