Using Third-Party Remote Communications Software

Transcription

1 Metasys Network Technical Manual 636 App. Notes: Third-Party Software Section Application Note Issue Date 0595 APPLICATION NOTE Using Third-Party Remote Communications Software Application Details Page 3 Introduction 3 Tested Remote Communications Software 5 Tested Equipment 6 Performance Issues 6 - Critical Alarm Box--Display Speed 6 - OWS Going Online/Offline 7 - Unreliable Data Display 7 Technical Tips 8 Configuration Tables Johnson Controls, Inc. 1 Code No. LIT

2 2 App. Notes: Third-Party Software Using Third-Party Remote Communications Software

3 Application Details Introduction Note: This application is intended to provide a branch service tool to help system representatives access customer networks without traveling to the sites. It is not meant to replace the Metasys Dial-up feature. Third-party remote communications packages include many features-- remote control, file transfer, terminal emulation, and chat. This application note focuses on the remote control software programs which allow you, at a remote PC, to view and operate a PC running Metasys and any other DOS/Windows applications. The keyboard and mouse input from the remote PC are sent to the local PC running Metasys, and the local PC s video and system sound output are sent to the remote PC. In essence, the remote communications program lets you access another PC (e.g., an OWS) as if it is on your own desktop. This allows you to perform customer support, teleconferencing, and troubleshooting for Metasys systems that are miles away, without returning software diskettes or other equipment, and without traveling to the site. Note: In this document, local site refers to the site running Metasys, and remote site refers to the site with a PC communicating to the Metasys Network via remote communications software. Local Metasys Network N1LAN Modem Remote PC with Remote Communications Software Standard NCU O perator Workstation with Remote Communications Software Modem rem 1 Controller N2 Bus Figure 1: Remote Communications Application App. Notes: Third-Party Software Using Third-Party Remote Communications Software 3

4 Many third-party remote communications packages claim that the connected PCs do not need to use the same type of display, keyboard, or mouse. However, in this Metasys application, we strongly recommend that you use the same or better display mode at the remote PC--for example, use VGA mode at the local site running Metasys, and use VGA or SVGA mode at the remote PC running the remote communications program. IMPORTANT: This application may not work with Metasys Release 2.01 or earlier due to the Windows 3.1 requirement for many remote communications programs. For this application, we recommend using Metasys Release 5.0 or later. The latest versions tested for the recommended remote communications programs are: PCAnywhere V2.0 Carbon Copy for Windows V2.5 Close-Up V6.0 Reachout V4.04 Most remote communications programs offer many ways to connect to remote locations, including pointto-point dial, across LAN networks, and gateway connections. However, this application note concerns only the dial connections tested and recommended by Technical Support. Table 1 is a summary of software and hardware configuration requirements. However, consult your remote communications program and Metasys technical manuals for more details on remote and local PCs. 4 App. Notes: Third-Party Software Using Third-Party Remote Communications Software

5 Table 1: Hardware and Software Requirements Local / Metasys PC CPU Type 486-based or higher Metasys supported PC is recommended. Remote PC 386-based or higher Microsoft Windows MS Windows 3.1, WFW 3.11 or later MS Windows 3.1, WFW 3.11 or later DOS Version MS-DOS 5.0 or later (prior to Metasys 7) MS-DOS 6.0 or later (Metasys 7 or later) MS-DOS 5.0 or later RAM Memory 6 Mb or more 6 Mb or more Disk Space Approximately 4.5 Mb (in addition to the disk space required for Metasys) Display VGA or higher VGA or higher Approximately 4.5 Mb required Local and remote PCs do not have to run in the same video mode. However, if the local monitor has a higher resolution than the remote monitor, you cannot see the entire screen at the remote monitor. Some packages provide an additional feature (e.g., Virtual Desktop from Carbon Copy for Windows V2.5) to see any part of the local screen easily. For this application, the recommended video mode for the remote PC is the same or higher resolution than the local PC. Mouse Microsoft compatible mouse driver supported by Windows Modem Hayes OPTIMA 9600 with 19.2K throughput on higher baud rate (or compatible) Microsoft compatible mouse driver supported by Windows Hayes OPTIMA 9600 with 19.2K throughput on higher baud rate (or compatible) Tested Remote Communications Software The following remote communications programs have been tested and recommended by Technical Support, with the highest recommendation going to PC Anywhere for Windows. (See Table 2 for the configuration used during testing.) At the higher baud rates (at least 38.4K throughput), there were not significant speed or performance differences between the packages. Keep in mind that this may change due to the frequency of product updates and improvements from the vendors. PCAnywhere for Windows V2.0--This is the package we recommend if you are purchasing remote communications software for use with Metasys. It may be the best package as far as overall performance is concerned, including remote control and file transfer features. Carbon Copy for Windows (CCW) V2.5--Many modems/graphic modes were supported, including SVGA, XGA, and 8514a. Close-Up V6.0--Test results were similar to PCAnywhere for Windows regarding performance while running with Metasys. However, file transfer speed is 20% slower than the other packages. Reachout V4.04--As far as the file transfer feature is concerned, this is the best package among those tested. However, regarding performance while running Metasys, this package is very similar to Carbon Copy for Windows, but slower than the other two packages. App. Notes: Third-Party Software Using Third-Party Remote Communications Software 5

6 Tested Equipment Performance Issues The following equipment has been tested and recommended by Technical Support. (See Table 2 for the configuration used during testing.) Hayes OPTIMA 288 modem Hayes OPTIMA 9600 modem MultiTech Modem II V K modem Hayes PCMCIA 288 modem Compaq MHz CompuAdd MHz Dell MHz This section describes currently known performance issues. Critical Alarm Box--Display Speed At 19.2K baud throughput with Hayes OPTIMA 9600 modems (see Table 2 for details), delay between two PCs ( MHz) is minimal. However, overall operation at the local PC running Metasys is slowed down--it takes up to 20 seconds to display a Critical Alarm Box while a remote PC is connected with Carbon Copy for Windows V2.5. Note: This problem only happens while displaying a standard system summary in Text mode. If another type of window is displayed, the Critical Alarm Box appears more quickly. This could be a Metasys problem. To minimize delay, use a faster modem (38.4K baud throughput). Without the remote communications program running, it takes up to 10 seconds to display the Critical Alarm Box while displaying the Network Map, Object Focus window, Trend graph, or System Summary (with the Technical Support test equipment). See Figure 2 for details. 6 App. Notes: Third-Party Software Using Third-Party Remote Communications Software

7 Key: NetMap: The Network Map was displayed while testing. GMode: A System Summary in Graphics mode was displayed while testing. TMode: A System Summary in Text mode was displayed while testing. 25 TMode: Carbon Copy for Windows V2.5 Reachout V TMode: PCAnywhere V2.0 TMode: Close-Up V6.0 (Seconds) GMode: All four packages 5 NetMap: All four packages (Baud Rate - Throughput) rem graf Figure 2: Critical Alarm Box Display Times OWS Going Online/Offline Unreliable Data Display Depending on the type of PC, the Metasys release, and the remote communications program, you may see problems with the local PC going online/offline while running this application. See Tip 1 (regarding the MaxAttrServerTasks= parameter) for a solution. If you see????? (unreliable) data on standard system summaries instead of values, you may need a more powerful PC (e.g., 486 with 33 MHz or faster) and/or the solution from Tip 2 (regarding the N1RtxTimeout= parameter). App. Notes: Third-Party Software Using Third-Party Remote Communications Software 7

8 Technical Tips 1. MaxAttrServerTasks=number (This tip applies to Metasys Release 6 or later only.) This parameter is in the [Metasys] section of the METASYS.INI file, and has a default of 4. (The default value for Release 5 and earlier versions of Metasys is 1.) If you see any of the following problems, you may modify this attribute to 1, 2, or 3 depending on system activities and PC type: the OWS going online/offline since you started this application errors in the PC ERRORLOG.TXT file, such as problems with the ATTPOLL.EXE file errors in the POLLOBJ module See the Initialization Parameters Technical Bulletin for information. 2. N1RtxTimeout=number This parameter is in the [Metasys] section of the METASYS.INI file, and has a default of 3. You may change this parameter if you see symptoms like the following: displayed values in the standard system summary change to????? (unreliable) for one refresh and then return to normal values at the next refresh. A JC_SEND failure may result when the N1DLTSK windows application is not given a chance to run at least every 3 seconds (using the default timeout). An easy test can be done to verify if the N1DLTSK is running often enough. Run the CLOCK.EXE application with seconds shown. Note the longest duration of time that is skipped over in seconds. If it is 3 seconds or more, JC_SEND errors may occur. Low performance PCs and/or task intensive thirdparty applications (including remote communications) are more likely to have this type of problem. If the duration is 3 seconds or longer, make the following changes to all OWSs and NCMs on the network: For OWSs, add the parameter N1RtxTimeout=x (where x is the longest duration plus 1). For NCMs, use NCSETUP Option 2 to change the N1 re-transmit timeout in seconds to the longest duration plus 1. This parameter is only displayed when a 1$ is entered with subnet address when starting NCSETUP. The timeout parameter must be the same throughout a network--if you make the adjustment at any node, you must make it at all nodes. See the Initialization Parameters Technical Bulletin for information. 8 App. Notes: Third-Party Software Using Third-Party Remote Communications Software

9 3. MaxBPs=number This parameter is in the [386enh] section of the SYSTEM.INI file, and has a default of 200. It specifies the Maximum Number of Break Points that can be used by the VMM (Virtual Memory Management). (A breakpoint, used by the virtual memory manager, is consumed and never restored whenever you start a DOS session in Windows.) If you see error messages like Application Error... and/or Out of Memory, we recommend that you change the value to 786 (even if you think you have enough RAM memory). This may solve your problems. This command consumes 4 Kb of RAM. See the Microsoft Windows Resource Kit for additional information. 4. Load=filename(s) This parameter is in the [Windows] section of WIN.INI file, and specifies the application to be automatically started and iconed when Windows is started. However, many remote communications packages do not work well if loading in this way when Metasys is running; in this case, the error message Unable to Load Graphics Windows may appear. In order to run the remote communications package automatically, you should load the program prior to loading Windows by using a batch file. For example, load from the AUTOEXEC.BAT file as follows: c:\ccw\doshost.exe -i=c:\windows :Carbon Copy for Windows V2.5 c:\closeup6\chost :Close-Up V6.0 c:\winaw\aw_host.exe -m=a :PCAnywhere V The remote communications password capability should be used whenever available. It provides security by letting you protect your computer from unauthorized access. Keep in mind that this is an additional password layer to the Metasys Password feature. 6. The following is a list of tips from the Carbon Copy for Windows V2.5 manual (Tips on Using Remote Control, page 59): Both local and remote sites should have high-speed modems. The baud rate (port speed) should be high (at least 9600). Transfer less information over the communication line. Turn the quick mouse option on. Move windows to make them completely visible. Make more memory available on the remote PC (2 Mb or more). App. Notes: Third-Party Software Using Third-Party Remote Communications Software 9

10 7. Dialing through Switchboard - To go through switchboards or some long distance carriers, you may need to put pauses in your dialing sequence. You can use the modem pause command, which for most packages is a comma (, ). This will create a two second pause. 8. Whenever possible, both the local site running Metasys and the remote site should use the same modems with identical baud rate, data flow control, and parity settings. 9. If the local site running Metasys and the remote site modems are not at the same baud rate, use the higher speed modem at the local site to minimize any performance problems. Do not use a modem slower than 9600 (throughput) baud at the local site. 10. Moble/Laptop PC with PCMCIA modem: Some PCMCIA modem configurations use COM3 port as the default port, and some use 8250 UART or compatible. Make sure you use UART or compatible in order to get higher throughput (e.g., up to 38.4K or even higher). Microsoft s MSD.EXE program (included with Windows) can be used to find out what type of UART your PC is using. 11. UART (Universal Asynchronous Receiver Transmitter) controls the transfer of data through a serial port. The most common UART types found in PCs are 8250, 16450, and The 8250 UART was the standard UART in the original IBM XT, but some IBM AT compatible PCs also use 8250 UART. The UART is standard on most 285, 386, and 486 PCs. Both 8250 and UART generate an interrupt for each character that is sent or received. At the data rates above 19,200 BPS (19.2K), this can slow down the PC as it handles the high volume of serial port interrupts. At high data rates in a multitasking environment such as Windows, the PC does not have time to get the character before the next character overwrites it. The UART can handle the two problems mentioned above. It has a 16-character data buffer and it generates an interrupt when the buffer is nearly full. This reduces the number of interrupts and allows more time for the PC to get the characters. The recent manufacturer trend for V.32bis, V.34bis, and V.42bis modems is that they are equipped with 1000-character data buffer size or more to minimize problems in the Windows multitasking environment. 10 App. Notes: Third-Party Software Using Third-Party Remote Communications Software

11 12. Newer 14.4K/28.8K modems, which support V.42bis data compression, can use much higher throughput. For example, the Hayes OPTIMA 288 modem can handle up to 230.4K maximum throughput, according to their data sheet. 13. It is important that the leased-line configuration be used with modems that are leased-line compatible. Some modems on the market are not leased-line compatible. The MultiTech Multimodem II, model MT1432BL, is an example of a modem that has both leased-line and dial backup capabilities. 14. Two ports sharing one IRQ line cannot be active at the same time. If both ports send an interrupt request to the CPU at the same time, the resulting confusion can force a reboot of the computer. For example, if your mouse is on COM1 and your modem is on COM3, moving your mouse can interfere with your modem. In this case, you should use COM2 as a modem port to eliminate problems. App. Notes: Third-Party Software Using Third-Party Remote Communications Software 11

12 Configuration Tables Table 2 shows the configuration used by Technical Support during testing. Table 3 is a configuration worksheet. Table 2: Technical Support Test Configuration Local (Metasys OWS) Site Metasys SW Revision 6.01 N/A Remote Site Comm. Software Carbon Copy for Windows V2.5 Carbon Copy for Windows V2.5 Computer Dell 433/L 33 MHz Compaq 486/33 33 MHz DOS Version MS DOS 6.01 Compaq DOS 6.01 Video Board (HW) Standard VGA Standard VGA Video Mode (SW) VGA VGA Modem Type (HW) Hayes OPTIMA 9600 MultiTech II 1432L Setup Type (SW) Hayes OPTIMA series Multimodem (V.32) Throughput BPS K 38.4K K 38.4K Many high-speed modems will allow a higher baud rate setting than their actual baud rate throughput, since they use larger buffers and some type of data compression. Typically, a 9600 baud modem may let you set the remote communications program to 38.4K baud. (This may depend on modems; older versions of the remote communications program may not support higher throughput baud rates.) Mouse MS Serial Mouse 8.20 MS Serial Mouse 8.26 Load (WIN.INI) =N1HOOK =(none) Run (WIN.INI) =(none) =(none) Startup Group =(none) =(none) MaxAttrServerTasks =1 =2 =3 =4 n/a MaxBPs (SYSTEM.INI) =200 =768 = =200 =768 = N1RtxTimeout =3 =4 =5 =6 =8 (seconds) N1RtxTimeout=8 was used for the test configuration above (the default value is 3). You may need a different number, if you see????? displayed instead of values in standard system summaries. See Technical Tip 2 for details. ProtocolTime =20 = ( ) n/a GraphicsUpdate =20 = (seconds) n/a Additional Notes n/a 12 App. Notes: Third-Party Software Using Third-Party Remote Communications Software

13 Table 3: Remote Communications Configuration Worksheet Local (Metasys OWS) Site Remote Site Metasys SW Revision Comm. Software Computer DOS Version Video Board (HW) Video Mode (SW) Modem Type (HW) Setup Type (SW) Throughput BPS K 38.4K K 38.4K Mouse Load (WIN.INI) = = Run (WIN.INI) = = Startup Group = = MaxAttrServerTasks =1 =2 =3 =4 n/a =200 =768 = =200 =768 = MaxBPs (SYSTEM.INI) N1RtxTimeout =3 =4 =5 =6 = (seconds) ProtocolTime =20 = ( ) n/a GraphicsUpdate =20 = (seconds) n/a Additional Notes n/a App. Notes: Third-Party Software Using Third-Party Remote Communications Software 13

14 Notes 14 App. Notes: Third-Party Software Using Third-Party Remote Communications Software

15 Notes App. Notes: Third-Party Software Using Third-Party Remote Communications Software 15

16 Notes Controls Group FAN E. Michigan Street Metasys Network Technical Manual P.O. Box 423 Release 7.0 Milwaukee, WI Printed in U.S.A. 16 App. Notes: Third-Party Software Using Third-Party Remote Communications Software