Building Automation Knowledge Base

Issue Cannot select data points of remote nodes to be references in a graphic on the monitor MPM Environment SmartStruxure Lite Multi-Purpose Manager MPM-VA MPM-UN MPM-GW Cause Feature not built-in Resolution When building dashboards on monitor MPMs, only local points can be used in the graphics. To be able to select points of remote MPMs, The Object_Copy script must be used. The script will copy points from the remote nodes to the monitor and make them local to that monitor MPM. This method can be used in ZigBee, Canbus and UDP networks. For example, to copy a point from each of the remote MPMs to the monitor, the script would have to be modified as follows object_list[1] = {tag = "zone1", source_device = "DEV200", source_point = "AV11", destination_device = "ME", destination_point = "AV1"} object_list[2] = {tag = "zone2", source_device = "DEV300", source_point = "AV22", destination_device = "ME", destination_point = "AV2"} object_list[3] = {tag = "zone3", source_device = "DEV400", source_point = "AV33", destination_device = "ME", destination_point = "AV3"}   Important notes: This script increase the monitor's CPU % usage and increases the traffic on the network. Therefore, depending on the size of the network, it is critical not to use more than a couple of points per remote MPM

Issue How can I clear the memory of an MR? Environment MR Cause If an MR with a database is given a new address using the dip switches, the DDC, I/STAT parameters and points remain in its memory. Resolution The only way truly clear the memory is to use an I/STAT or M/STAT: Enter the service mode Re-enter the address or communication speed. Changing these parameters can work but be careful not to leave the speed at anything other than 9600. Refer to the I/STAT instructions in TCON 126 or TCON 130 for instructions on service mode operations.

Issue The automation server password policy is grayed out making it unavailable to make configuration changes. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium   Cause When an Automation Server is attached to an Enterprise Server, all of the password policy configurations are inherited from the enterprise server. Therefore the AS settings cannot be changed.  Resolution The password policies of the Automation Server must be administered from the ES when it is connected to an Enterprise Server.   In order to make changes to the password policy settings in the Automation Server directly, it must be detached from the Enterprise Server. Note: For EBO V 1.9.X and lower, the password policy settings can be located under Control Panel > Security and Communication > Security settings area. For EBO 2.0.X and higher, the password policy settings can be located under Control Panel > Security and Communication > Password policy.

Issue How to send an event based alarm to one or multiple email addresses using an MPM Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager MPM-VA MPM-UN MPM-GW Cause Emails can only be sent using a Lua script Resolution To send e-mails to alert a list of recipients when a pre-defined condition is met, you need to create a Lua Program object (PG1 for example) on your monitor MPM. Copy and paste the attached Email_Alert_AN015 script in the Loop section of the program object and activate it by pressing the green Play button. Don’t forget to save both the object and the database when you are done. You will need to modify this script to represent your own event, including the server information, the list of recipients and the content of the message sent. The monitored variable and the limit conditions can be modified directly from the Event object in Building Expert. In the above example, room temperature is 23 which means that the "Event State" is 0. An email alert will be sent out when the temperature exceeds the high limit (Event State = 3) or when the temperature goes below the low limit (Event State = 4) defined by the event.   Tip 1 Only a Manager connected via Ethernet has the ability to send emails. For a network composed of a daisy chain (CANbus) or a wireless mesh (ZigBee mesh), the Lua program that manages e-mail alerts for all the nodes on the network must reside on the monitor node. The variables in the Lua program will be obtained from any remote node on the network, and the email sent by the monitor if a condition is met. To get an object from a remote node, refer to Display values/objects from a remote MPM on dashboard of the monitor MPM Tip 2 Should you have issues sending emails with the above script, verify that the User and Password defined in the script are accurate and up to date and that all server information is accurate. Also ensure that the Ethernet configuration (ETH1 object) of your SmartStruxure™ Lite Manager is accurate and represents the current settings of your network. Pay special attention to the DNS and Gateway settings. Your monitor Manager will be able to operate on a local network even if these settings are not accurate, but will not be able to access the Internet, which is required to send emails. Tip 3 When using Google’s server mentioned below, it is important to use the following information Google* Server aspmx.l.google.com Domain google.com Port 25** Sender *** Recipient   Username (Not Required)**** Password (Not Required) *Google can only be used to send emails internally from Gmail to Gmail **When port 25 is used, emails are stored in the spam folder ***Bracket < > are not to be discarded, otherwise syntax error 5.5.2 appears ***Note that the user authentication is not required for the google server and if included, will be rejected. Tip 4 The AOL’s server mentioned below can be used to send emails from an AOL account to any other email and does not send the emails to the spam folder AOL Server Smtp.aol.com Domain Aol.com Port 25 or 587 Sender email@AOL.com Recipient Your_email@AOL.com Username (Required) email@AOL.com     (or any other email) Password (Required) Your password   Tip 5 Email server using Port 25 and not requiring authentication, sendUser and SendPassword lines needed to be deleted from Variables section

Issue Unable to read any public signals from TAC Xenta 300/400/280 in a TAC Xenta 511, but SNVTs from TAC Xenta 100 controllers are fine. Environment Xenta Programmables Xenta 511 Xenta 100 series ASCs Cause The TAC Xenta 511 is not a member of the TAC Vista group. Resolution Go to the System plug-in Choose LNS Network >Create group bindings.

Issue How much ethernet bandwidth do lonworks systems consume using Loytec L-IPs, iLons, etc.? Environment TCP/IP ethernet network LNS System Cause IT professionals will sometimes hesitate to allow the control system to use the same TCP/IP network as the internet, phones, etc. They may ask what the expected bandwidth usage will be before granting access. Resolution It is impossible to explicitly state how much bandwidth a LonWorks system will consume on the ethernet. It depends heavily on the amount of LON traffic being sent by the controllers. The routers themselves do not produce traffic, they only pass the traffic onto and off of the ethernet. The traffic is created by the LON devices, Xenta controllers, Vista and LonMaker or other HMIs. Vista can create a maximum of 15 LON telegrams/second. This is very little traffic with respect to IP bandwidth. Unless you have made bindings into the LNS NI (which we never do in a Vista-scenario, since Vista cannot read these) there is basically nothing at all going out from LonMaker/LNS unless you are commissioning devices. Starting the LonMaker Browser also generates traffic. But this is also normally just in the design phase of the network, not in "operating mode". SNVT bindings or TAC network variables from one LON network to another over the IP channel also generate traffic. A typical Xenta can produce 2 SNVTs propagation/second and/or maybe 10 TACNV. This is not much (as IP-traffic), but if there are hundreds of nodes communicating simultaneously all passing through L-IP gateways, the amount of IP traffic will grow. If you are using a Loytec L-IP, it uses a protocol feature called "packet bunching". Before it sends out a packet on the IP side, it waits for an adjustable time (Aggregation Time, default = 16ms) if some packets are following, which have to be sent to the same IP addresses. If some packets are following, it puts the packets in the same IP frame and sends it all together in a single IP packet. The receiving node unpacks it and makes multiple EIA-709 (Lonworks) packets again.

Issue I/NET Seven does not support the 7791/7792 MCI platforms. Only the 7793 MCI platform is supported. Consequently, a conversion from the 7791/7792 MCI platforms to the 7793 MCI platform is necessary. The following steps should insure a correct conversion. Environment 7791/7792 MCI platforms Cause I/NET Seven does not support the 7791/7792 MCI platforms. Only the 7793 MCI platform is supported. Resolution A Hand Held Console (HHC) is required for this process. Turn EVERY sub-LAN device “Internal” using the MCU Configuration Editor under Edit > Controller > MCU Configuration. Save the current databases in the MCIs (7791/7792). Attach the Hand Held Console (HHC) to a MCI. Use the following keystrokes to clear the MCI memory: CTRL, MEM, ENTER, “0”, ENTER. Press the red RESET button on the MCI The indication on the HHC should be seconds counting up from zero. Using the HHC, enter CODE, 90, and press the ENTER key.  The display should show the current MCI configuration (i.e., 7791 or 7792 and TAP emulation of 01, 03 or 06).  Using the increment/decrement keys advance the display to show 779301 or 779306 (use the –06 if dialing into a MCI with the RS-232 Expansion board attached--otherwise use the -01) and press the ENTER key.  The display should indicate seconds counting up from zero.  Check the COMM port speed on the MCI using the HHC.  Enter in CODE, 91, and press the ENTER key.  The display will show the COMM port speed, typically 19,200 if directly connected to a PC.  Change the port speed using the INC key to 19200 if necessary. Move the I/NET 2000 saved databases (DCUXXXX.sav) to the SAV folder in I/NET Seven. In I/NET Seven connect to the Link address where the MCI is located.  Go to Edit > Host Computer > Software Restore, and check the MCI address to download the .BIN file only (do not load the .SAV file here).  After the .BIN file downloads to the 7793, connect to the MCI.  Go to Edit > Controller > Station Restore, and download the .SAV file to the controller.

Issue I/NET Seven elevator control configuration and setup. (Traditional versus Extended elevator control) Product Line TAC INET Environment I/NET Seven Extended elevator control: DPU Firmware 3.20 or above. (DPU7920 with 48K MIP or SCU1284) Cause There are two types of elevator control that you can implement within TAC I/NET: Traditional Elevator Control – Tradition elevator control allows each elevator to support up to 62 floors. This type of control has been used for as long as elevators have been supported within TAC I/NET. Extended Elevator Control – Extended elevator control does away with floor mapping and allows you to assign floors directly to tenants. Using this type of elevator control, each elevator can support up to 79 floors. Resolution Elevators The Elevator control function will work with the access control parameters and personnel schedules to control access to banks of elevators. Activating () the elevator option in the Door Extension editor will cause the DPU to process each reader transaction as though it were an entry into an elevator cab. Note: An elevator DPU will support only one door reader. Changing a Door from elevator to non-elevator, or vice versa will cause the DPU to purge its database. In addition to supplying the above parameters at the door (DPU) level, it will also be necessary to supply the DPI/MCI with the information required to associate an elevator cab with the discrete output points that enable the floor relays, and the discrete input points that monitor the button selection. There will be an elevator extension on each door point in the DPI/MCI that is assigned as an elevator. After adding the extension to the point, you must define the Elevator parameters such as floor selection time, floor designation description, button enable point, and button selection point. Elevator Control Schemes There are two types of elevator control that you can implement within I/NET Seven: Traditional Elevator Control – Tradition elevator control allows each elevator to support up to 62 floors. This type of control has been used for as long as elevators have been supported within I/NET. Extended Elevator Control – Extended elevator control does away with floor mapping and allows you to assign floors directly to tenants. Using this type of elevator control, each elevator can support up to 79 floors. You can use either type of control, or a combination of both, to implement elevators within your system. By allowing you to mix both types of control, I/NET gives you the ability to begin using extended elevator control without reconfiguring your traditional elevator control system. The following sections describe each elevator control type. Traditional Elevator Control Traditional elevator control allows each elevator to support up to 62 floors. To implement this type of control, you assign the elevator door point to one or more tenants. You then create floor maps that associate floors with personnel schedules (see “Defining Floor Maps”, below). After performing these tasks, any individual (or group) assigned to the elevator can gain access to the floors that are associated with their personnel schedule Assigning the Elevator to Tenants Traditional elevator control requires you to assign the elevator to one or more tenants. Until you perform this task, the Floors button in the Elevator editor will not be available (i.e., it remains grey). Defining Floor Maps Floor maps are only necessary when configuring your I/NET system for traditional elevator control. Floor maps determine which floors are enabled during each schedule that a tenant defines for the elevator. For example: Tenant 1 has a personnel schedule named “24 Hour” defined for the elevator. This schedule provides 24-hour access, seven days a week. The elevator’s floor map associates the floor enable points for floors 1 and 2 with Tenant 1’s “24 Hour” schedule. This allows Tenant 1 individuals using the “24 Hour” schedule to select floor 1 or floor 2 at any time. Use the Floors button in the Elevator editor to create floor maps as follows: Choose a tenant. Select a schedule from up to 31 personnel schedules defined for the elevator. Select an entry from up to seven access intervals defined for the schedule. Assign floor enable points to the schedule’s access interval. Floor enable points cause the elevator buttons for those floors to be enabled for selection by the key/card holder. Up to 62 floor enable points can be assigned to each access interval. Any floor enable points beyond 62 are unavailable when using traditional elevator control. These higher floor enable points are only available for use with extended elevator control, as described below. Note: Extended elevator control is only available with the 7920 48k DPU. Repeat these steps as necessary to create floor maps for each of up to 31 personnel schedules assigned to the elevator by a tenant. Extended Elevator Control I/NET Seven now offers an alternative to the traditional elevator control just described. Enhancements to the I/NET system support up to 79 floors per elevator. Instead of assigning the elevator door point to the tenant, you can implement extended elevator control by assigning floors to the tenant. The DI/DO pairs that you add to an elevator from the Elevator editor are listed in the Tenant editor, much like normal door points. Select the floors that you wish to assign to the tenant. Implementing Elevator Control Note: Extended elevator control is only available with the 7920 48k DPU. Adding an elevator extension to the door point provides access to elevator-related features and editors within I/NET and allows floors to be assigned. Each floor assigned to an elevator must have an associated DO and DI point. The DO point enables the elevator button for the specific floor. The DI point provides feedback indicating whether the floor button has been selected. Preliminary Requirements Before defining an elevator, you must do the following: Define a door point as an elevator in the Door Extensions editor. Use the Resident I/O Points editor to define a floor enable point (DO) and a floor selection point (DI) for each floor that will be assigned to an elevator. Use the Personnel Schedules editor to define up to 31 schedules for the selected elevator door point. Adding an Elevator Extension Use the following procedure to add an elevator extension: Select Edit Controller Elevators from the main menu. The system displays the Resident I/O Points Editor. This screen lists the available door (elevator) points. Choose a point that does not have a Y in the EL column and select the Add button. The system displays the Elevators window. Enter a Floor selection time (sec) (1 to 255). This is the amount of time in seconds that the key/card user has to make a selection from the floor buttons in the elevator cab. The default is 5. Select Add. The system displays the Elevators - Floor Parameters window. This window allows you to define the floor index attached to this elevator extension. Enter the Floor index number (1 to 62). This is the line number in the list. Enter the Floor designation (up to two characters). This identifies the floor. For example, the first level of a basement could be represented as B1. For each elevator floor extension assigned to a point in the DPI/MCI, there must be an associated DO and DI point attached to the elevator extension. This association of DO and DI points produces closed-loop feedback allowing the controller to identify an elevator floor selection with each successful key/card reader access. In the Button enable field to choose a point from the drop-down list of all possible discrete output points in the controller  In the Button selection field, choose a point from the list of all possible discrete input points in the controller. Select OK. The system returns to the Elevators window. How you proceed from this point will depend upon the type of elevator control you are implementing. Use the appropriate steps below: Traditional Elevator Control: From the Elevators window, select Floors. The system displays the Tenant Selection window. Choose a tenant from the list and select the Select button. The system displays the Elevators - Floor Schedules window. Choose a schedule from the list and select the Select button. The system displays the Elevators - Access Intervals window. Choose an access interval from the list and select the Select button. The system displays the Elevators - Floor Map editor. Choose the DO points which enable the floor selection buttons for the appropriate floors. Points marked with "[X]" will enable their respective floor selection button in the elevator cab. When you have finished choosing the appropriate DO points, select OK. The system returns to the Elevators - Access Intervals window. You may continue assigning floors to access intervals, or you may back out of the elevator functions by selecting Close at each window. Extended Elevator Control (See also article Extended Elevator control (Step by step instructions) ) From the Tenant Editor, assign floors (i.e., door enable points) to the tenant. Assign floors to individuals and/or groups as necessary.

Issue Extended Elevator control (Step by step instructions) Product Line TAC INET Environment I/NET Seven DPU Firmware 3.20 or above. (DPU7920 with 48k MIP or SCU1284) Cause Extended elevator control allows support up to 79 floors and easier programming methodology than the traditional method.  This has been added to I/NET Seven software and DPUs as detailed in the environment.  Resolution To use any of these features requires that the DPU be a 7920 w/ MIP board or the new SCU1284. 7910 and 7920 w/o MIP board will still work with the I/Net system but they cannot use these functions. The host prevents the download of these features to any DPU revision prior to 3.10.   Extended Elevator Control Setup Example This is based impart on basic prior knowledge of InetSeven Host software setup and configuration to include but not limited to Controller Station Parameters, Resident I/O, Point Extensions, Operations of Network Configuration, and Access Configurations (Doors, Tenants, Groups, Individuals and Personnel Schedules). Hardware required: DPU 7920 48k (The following control will only apply to the 7920 48k) Please follow these steps to configure extended elevator control. Resident I/O Editor Edit / Controller / Resident I/O – Add the following Internal DO Door Reader point Internal DI point for each Floor DO External DO point for each Floor button DI Note – Save Door in the Network Configuration editor. Controller Door Editor Edit / Controller / Door Editor Select Door to add Elevator Control Modify – check Elevator Control box Select “Message type” Alarm / Transaction Note – Ensure a Schedule (s) has been assigned to the Door reader point. Controller Elevator Parameter Edit / Controller / Elevator Add Elevator Extension to reader point. Add Floor parameters. Complete the following; Floor Index Selection Floor designation Button Enable (DO) Button Selection (DI) Note – When finished “STOP” Do not select floors, Select OK and Close. Network Configuration  Edit / Host Computer / Network Configuration. Penetrate down to the DPU (Door Read Point) with Elevator Control Penetrate one more level and SAVE all your floor extensions. Tenants Access / Tenants Select Tenant Locate Door Reader point – Remove “X” (Unselect). Place an “X” next to all floors that tenant will have access to – Select Ok At this time I would suggest performing a save function followed by an SLI and DPU restore. Individual Editor You are now ready to add individuals or assign individuals access to floors.

Issue Cannot register LonMaker plugins Product Line TAC Vista Environment LNS, LonMaker, NL220 Cause If you are having difficulty registering plug ins in LonMaker then you may have corrupted LNS credits. Resolution To check your LNS credit status, run the LNS Server License Wizard which is found at C:\LonWorks\bin\LnsLic.exe If you run the wizard and it displays the Max Credits at zero and Credits Available as zero as well, then your LNS credits have become corrupted. To correct this, select Next in the Wizard so that it displays the PC Key. The wizard provides a button titled "Copy to Clipboard" which when selected will allow you to paste a form letter into an email or text editor. After filling your specific contact information you will want to check the "No Charge" box and the "Replacement Use" box. Before you send the form via fax or email, you also need to provide evidence that your LNS credits have been corrupted. Select Start > Run > and type "cmd" to reach a command prompt. This command will check the status of the LNS credits: checklic nsseng.exe The output of this command should either be printed and sent with the fax or included in the email to the address or phone number shown at the top of the form letter. You should then receive instructions or an application key to correct the problem.

Issue Transferring an I/NET Seven system from one PC to another Product Line TAC I/NET  Environment I/NET Seven Site Cause Customer needs to transfer I/NET between two computers Resolution Perform the following steps: Install I/NET Seven on the new PC. Using DBCreate.exe, create a backup of the I/NET database. Copy the backup to the new PC and restore it using DBCreate. If the database needs to be upgraded it will prompt you.  Proceed with the upgrade.  Copy the save files, graphic pages, archives, any custom reports, custom symbols, and custom BIN files (ICI bin files) to the new PC using the same directory path as the previous PC to guarantee that graphic links will still work. The following are default paths for these files assuming it was not an upgrade from I/NET 2000. If it was an upgrade from I/NET 2000 please consult TCON298 the Getting Started guide which includes I/NET 2000 paths. Default location for Archives: C:\Program Files\INET Seven\Arch\ Default location for BIN Files: C:\Program Files\INET Seven\Data\ Default location for Reports: C:\Program Files\INET Seven\Reports\ Default location for Save Files: C:\Program Files\INET Seven\Sav\ Default location for Bin Files: C:\Program Files\INET Seven\Data\ Default location for Graphics: C:\Program Files\INET Seven\ Take a screen capture or write down the active configuration profile in I/NET configuration and manually fill this information into I/NET configuration on the new PC and make it the active configuration profile. Transfer the communication medium to the new PC (serial cable or Ethernet cable) and if communicating via NPR’s set the IP address of the new PC to match that of the old PC and remove the old PC from the network to avoid IP address conflict. Start up I/NET, login, and edit the Host Computer->Network Configuration to verify that the PC is communicating with the controllers.

Issue Xenta Programmable Device is Offline in Vista, but Online in LonMaker. For LonWorks Devices refer to LonWorks Device is Offline in Vista but Online in LonMaker or NL220. Product Line TAC Vista Environment LonMaker, NL220 Vista Workstation Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In an LNS system, Xenta programmable controllers have different methods of communication to the LNS server and the Vista server.  Communication with the LNS server indicates the wiring is connected, the neuron ID is set correctly, but does not guarantee communication with the Vista server.  An online condition for Vista is dependent on Xenta Group bindings and network description files in the device and the Xenta Group Master being online. Resolution Ensure that Vista Workstation is in Operating Mode vs. Engineering Mode. Refresh the Folders View - Highlight the root directory "TAC Vista" press "F5" or click the refresh icon. Ensure the device is physically Online in LonMaker even though the drawing displays as green. Check the status by right clicking on the device, select Properties. Commission Status should say "Current", and State should say "Online". Alternatively, right click on the device and select Manage / Test.  The state should read "configured online" if the device is online in LonMaker. Make sure that your Master Device in the corresponding Xenta Group in the System Plug-in is online. If the Master Device is online and displaying values, it is always necessary to download the application and parameters to the Xenta group after adding a new device. The entire Xenta Group must know there is a new device for proper communication to occur.  Download the applications and parameters to the entire group in the TAC System Plug-In. If all the above is true and there is still no data then use Verifying Xenta Group Bindings in an LNS system to verify that the Xenta Group Bindings are correct. If not, in the Vista system plug-in, click on the LNS Network tab choose Create Group Bindings and click Yes on the Resynchronize drawing to database (Fix-up Drawing). Ensure the Xenta Group name is less than 20 characters without any spaces. Note: Channel names can contain spaces (NL220) but still must stay under the 20 character limit. 

Issue In a TAC Xenta group, there must be one TAC Xenta which is the master, which TAC Xenta device in the group is most suitable to be the master in the group? Product Line TAC Vista Environment TAC Xenta 401 TAC Xenta 301/302 TAC Xenta 281/282 Cause TAC Xenta group master devices have additional communication responsibilities to the Vista Server -- reporting online/offline status of their group members. Resolution During network planning, choose the master device to be the group member with the: least amount of SNVTs least TACNV least amount of I/O modules least memory used least communication least processing load If adding controllers in an ad-hoc manner, the first controller commissioned must be the group Master to enable communication with any other controllers. If the group master is offline, the whole group will be offline. Remember that when a controller is added to a group all controllers in that group need to have the application and parameters downloaded. If the Master Device is changed after the group is set up you will also need to download every controller, Download the new Master first so that as you download the rest of the controllers they will come online after the download.

Issue Reset Instructions for 1200 Series SCU Product Line TAC INET Environment SCU 1200 series controllers I/NET Cause Need to restart SCU, perhaps after a reload of firmware or dip switch settings Resolution Follow the written instruction carefully.   Reset Instructions: Locate the 3-pin connector labeled P610 and the reset push button switch. Refer to the above diagram. Momentarily short P610 pins 1 and 2 while simultaneously pressing the reset push button switch. (Note: P610 pins 1 and 2 are the pins located nearest the dip switch.) Re-download the proper BIN file to the SCU.

Issue If you are using OPC Server for I/NET on a computer with Windows XP with SP2 you may have some difficulty connecting to the OPC Server from another computer. Environment OPC Server for I/NET Windows XP SP2 Cause Incorrect DCOM settings will prevent a connection from another PC. Resolution Start > Run > dcomcnfg Right click My Computer found under Component Services, Computers. Click on the COM Security tab. Click the Edit Limits on the Launch and Activation permissions. Add ANONYMOUS LOGON with remote launch and remote activation permissions.  

Issue Direct Connect Xenta 527-NPR or 527 Web Server through I/NET Environment I/NET site Cause Direct Connect a Xenta 527-NPR or 527 Web Server through I/NET Resolution Are you using a Xenta 527-NPR or 527 Web Server and want to direct connect to it through I/NET and not having any luck? There are a couple of things that you need to set up in the unit for serial communication to I/NET through Port A (RS 232). The Xenta 527 NPR is set at factory default (RS232 Port A). The following steps should get you through this: Start I/Net and create a profile for the NPR (Net Plus Router) in I/O Server, then make this active. Verify that you have the correct cable to hook up from the serial port of the PC to Port A (RS 232) on the unit. (L1: RJ45 to RJ45 part # 0-073-0817). Connect them together. At this time you will need to start X Builder, if you don’t have it already, then you need to download it from the Exchange Extranet. The path is TAC Vista > Engineering Tools > TAC XBuilder > TAC XBuilder 1.5 (or latest revision). Download this to the PC. Start XBuilder through Programs > TAC > TAC Tool > XBuilder. Once started, select File\ New Project\(Project Name)\Location (default)\Project Template (select 527 Project), call it 527 NPR or whatever makes sense to you. At the settings Editor, just hit the OK button. Once the Editor comes up, in the Network frame, expand the TAC_Xenta_527. Right Click on the RS232-485A selection, click on Add then select I/NET. If you click on the TAC_Xenta_527, you will see all the settings that you have originally set up through Hyper Terminal or you can put those in at this time. Now select the Generate Icon or press F10 to generate the file. In the bottom of your project you would see a message that says Xbuilder – 0 error(s), 0 warning (s). This indicates that your project is now complete without errors. Now select the Rocket Ship Icon or press F11 to transfer the file to the unit. Once completed, restart or cycle power on the 527. Go to I/Net\Edit\Host Computer\Network Configuration and your 527 will show up in the Link Summary. At this time you can save the link, penetrate it and save the controllers etc. the old fashioned way. At this time you should be able to work on your system through a direct connect on a Xenta 527 NPR/Webserver unit.

Issue What should I set the Access Server System variable to on Continuum access controllers? Environment CX9200, CX99xx, ACX57xx or CX9702 controller with an ACX780 or ACX700 controller. Access Server, AccessServer Cause Below are the different configurations and what their different AccessServer system variable settings mean. Unlike Infinity when changing the setting in the controllers the controller does not reset. It is best if you set the AccessServer setting to the ACC Net ID of the Primary Access server workstation. This will keep the Access Control system operational should there be any distribution problems. Resolution CX9200, CX99xx,  or CX9702 controller with an ACX780 or ACX700 controller. The CX can stay at the default of it’s own ACC Net ID. In the above configuration the AccessServer variable in the CX is ignored. The AccessServer variable in the ACX controller can be one of the following: AccessServer value set to 0 in the ACX (Default setting).This means that access validation of personnel records will only be done locally in the ACX. If the person is not found in the ACX or the person is denied access locally in the ACX the person will not get in. AccessServer in the ACX controller set to the ACC Net ID of the Primary Access Server workstation (valid values are 191-253). This means that access validation of personnel records will be done locally in the ACX first. If the person is not found in the ACX or if the person is denied access the controller will double check at the workstation to verify whether or not the person is supposed to have access. If the person is also denied access at the workstation then the person will not get in. If the AccessServer value in the ACX controller is set to the ACC Net ID of the parent CX controller it has no effect and is ignored. CX99xxor CX9680 controller with AC1 modules  or ACX57xx. The CX can stay at the default of it’s own ACC Net ID.  AccessServer value set to the CX’s own ACC Net ID (Default). This means that access validation of personnel records will only be done locally in the CX. If the person is not found in the CX or the person is denied access locally in the CX the person will not get in. AccessServer value set to the ACC Net ID of the Primary Access Server workstation (valid values are 191-253). This means that access validation of personnel records will be done locally in the CX first. If the person is not found in the CX or if the person is denied access the controller will double check at the workstation to verify whether or not the person is supposed to have access. If the person is also denied access at the workstation then the person will not get in. AccessServer value set to 0. This is not a valid setting for a CX controller.

Issue How does a controller get an alarm into the database when using the Enhanced Alarm Logging feature of CyberStation? Product Line Andover Continuum Environment Cyberstation Cause Continuum Alarms are configured in the Netcontrollers and Infinet-controllers at each site. Only the CX Controller sends alarms to the Cyberstations once a point in the Controller surpasses its threshold and goes into an alarm state. The CX Controller then uses an internal algorithm to determine which CyberStation will log the alarm. Resolution The alarm is sent to the first (Non "0" Network ID) Cyberstation on its list of known devices. If the controller does not get a response from this workstation that the alarm was logged, it will try again three more times. If the workstation still does not respond to the controller, the controller will flag this workstation as offline in its internal controller database. It will then move to the next workstation in its list until it finds a workstation that is online and has logged the alarm successfully. If no workstations respond to the controller, the controller will buffer the alarm internally until it can find a workstation that is online. If the workstation is online, the alarm will be logged to the Continuum Database and then the database will notify the Workstation that the alarm was logged successfully. When the workstation gets this notification from the database that the alarm was logged, it will in turn send a notification to the CX controller that the alarm was logged successfully. Next, the controller will send the alarm to all recipient workstations for this alarm. When the controller is sending the alarm to the other recipient workstations it will follow the same logic and try to send it three times to each. If for any given recipient workstations the controller does not get a response that the alarm was received the controller will flag that workstation as offline internally and not try to send the alarm to that workstation again.

Issue WebClient most common installation problems Product Line Andover Continuum Environment Continuum webClient Server Microsoft IIS Microsoft .NET Framework Cause WebClient is not functioning properly. Troubleshooting steps are required. Resolution Below are some of the more common problems that Technical Support runs into when troubleshooting a WebClient installation. Microsoft DCOM settings (Manually setting up DCOM was needed prior to version 2.0) This is the most common problem that PSS runs into. There are two areas that these settings need to be set in are, “Access Permissions” and “Launch and Activation permissions”. Incorrect DCom settings in WebClient will cause many different problems. It could cause problems with logging into the system, opening graphics, seeing the Active Alarm view, etc… The users that should be in there are below for Windows 2000 IIS and Windows XP IIS servers: INTERACTIVE SYSTEM ComputerName\IUSR_ComputerName (Internet guest account) ComputerName\IWAM_ComputerName (Launch IIS process account) ComputerName\ASPNET (ASP.NET) Additionally for Windows 2003 IIS servers this additional user is needed: ComputerName\NETWORK_SERVICE To help pinpoint the DCOM permission that is not set properly, consult the steps at Identify which DCOM permission are causing DCOM errors when trying to use WebClient. Microsoft .Net Frame work Zone Permissions This is another one of the more common problems in WebClient installs. Not setting the .Net Zone permissions correctly will cause problems with opening schedules in the WebClient browser machines. The .Net zone permissions has to be set on each client browser. See the section in the WebClient install guide on setting the .Net Zone permissions. Microsoft .Net Framework is installed before the IIS is installed If .Net is installed prior to IIS you will see problems with logging into the system, editors may not work, schedules will not be able to be opened. If there is any doubt to whether or not .Net was install before the IIS then open a Windows command prompt and run the below commands. For Windows 2000 Professional it is: c:\WinNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i For Windows XP Professional, Windows Server 2003 it is: c:\windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i For Windows10/Windows7/Server2003 it is: c:\Windows\Microsoft.NET\Framework\v2.05.50727\aspnet_regiis.exe -i Also, Windows10/Windows7/Server2003 using 1.94 SP1 and greater, .net 4.x is used  c:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i Run both 2 and 4 commands  Microsoft .Net 2.0 This is not supported until V1.74 and will cause problems with WebClient. You will see problems with reports, schedules on earlier versions. SQL Authentication methods with WebClient The only authentication method for SQL server that WebClient supports is SQL Server and Windows. Due to the methods we use to access data in the SQL database with WebClient the authentication must be set this way. Internet Information Server Secure Sockets Layer (IIS SSL) Currently using SSL with WebClient is not supported in versions prior to V1.74. Remote installs of WebClient due to underlying Microsoft Security a WebClient cannot be installed through any kind of remote terminal services, or RDP. If the system is installed through remote services there will be security problems with accessing WebClient. The correction to these problems is to be directly on the WebClient / IIS machine and uninstall all the WebClient apps, Microsoft .Net, and Microsoft IIS then re-install the applications per our instructions while directly on the WebClient machine. Remote reboots of a WebClient IIS server If you use a remote terminal service and reboot and log on to an IIS server running WebClient you will run into problems with logging into WebClient. (webclient is unavailable error) If using VMWare with 2.0 and above, use the VMWare Open console feature Multiple Network cards in the IIS server Using multiple network interface cards in an IIS server is not supported. Doing this will cause problems with opening graphics through WebClient. Installation of files on the Client browsing machines The first time WebClient is accessed through a browser, either in new installs or upgrades, files need to be installed on that client browser machine. You will need to be logged in with a Windows user that has the permissions to install software. Install of WebClient on the IIS computer while virus scan software is running. Make sure that when installing WebClient, either new installs or upgrades, that any virus scan software is disabled. In some instances virus scan software has caused problems with WebClient installs or upgrades. "&" characters in names of objects Ampersands are special characters in web browsing and should not be used in anything in Continuum that the WebClient browser will have access to. Some of the problems that have been seen are alarms not showing up in the Active Alarm view and not being able to add areas to personnel objects. Setting up WebClient graphics Once WebClient is installed on the IIS server you need to make sure you open CyberStation Pinpoint and set the “Web Locations” for your graphics sharing. If you do not set this you will not be able to access graphics through WebClient. When these are set incorrectly you will see a red “X” next to the path. Ports used in WebClient Until V1.74 we only support the use of Port 80 in WebClient. CyberStation on the IIS WebClient server. In order for WebClient to function properly the CyberStation that is installed as part of the WebClient install on the IIS server must be running. You do not need to be logged on to the CyberStation it just needs to be running. WebClient graphics and firewalls Prior to 1.73 there were some special installation considerations when dealing with customers that had browsing machines both inside and outside a firewall. In the 1.73 WebClient there is no special installation/configuration that needs to be done. The system can be set up as if all the browsers are on the local network. Renaming or changing the Domain of the IIS Server after IIS is installed Renaming or changing the Domain that the IIS server was initially installed with will cause problems with IIS which in turn will cause problems with WebClient. If this has to be done then you will need to uninstall webclient before name change and then re-install webclient. Directory Browsing setting for WebClient graphics In some instances where the Windows security on the IIS server is restrictive you will need to add “Directory Browsing” to the NewGraphicsFiles share in the web site configuration on the IIS Server. In webclient 2.0 and greater, directory browsing is configured during the installation. Using underscores or hyphens in the name of the IIS Server This will cause problems with the operation of WebClient because those characters are special characters in the application.

Issue No Communications when directly connecting to a MicroNet Controller. Product Line Satchwell MicroNet Environment MicroNet controller (MN300, MN440, MN500, MN620 or MN350, MN450, MN550, MN650) using VisiSat Cause Controller subnet setting incorrect. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Go to the VisiSat server on the taskbar by the clock.      Drop down the Network menu Then select restart. This will reset the controller subnet setting to 1 Now the Visisat server should be able to connect to the controller.