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 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 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 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 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 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.  

Issue Search for all inputs and outputs in a system that are forced by operator Find IOs that are set in manual override Product Line TAC Vista Environment TAC Vista Workstation Cause Need to find all Inputs/outputs that are set to Forced by operator (manual override). Resolution In Workstation, right click on the Lonworks object and select search. In type of devices or objects select Analog/Digital input and/or Analog/Digital outputs.     Select property value 'Forced by operator' and Select equal to 1.     (To be able to set the property value 'Forced by operator' specify Analog/Digital input and/or Analog/Digital outputs, not just Points in 'type of devices or objects'.)

Issue Error when Starting CyberStation: "Continuum Server - OMSInit failed" Product Line Andover Continuum Environment Cyberstation Cause The most common reasons for this are listed below: After installing a new database the workstation was not initialized The IP address is not configured in the workstation. The Upgrade procedure was not followed and the database was never updated The Folder specified for the CyberStation already exists in the DB Resolution To resolve based on the cause above: Initialize the workstation by clicking on the Workstation button during the installation process. Configure the IP address in the workstation (load a network card) Go back and update the database Delete the folder from a second WS (if possible) or specify a different folder name.

Issue When trying to save a program in the Plain English editor, you receive the message "Infinity controller error: File took too long to open" Environment Plain English editor Cause This is typically caused because the program in the controller is busy executing a command that cannot be interrupted. Resolution A workaround for this issue is: Right-click within the PE panel of the editor Clicking "Configuration..." Set the program state to Disabled, click OK Save your program Repeat the steps above but select Enabled and then click OK

Issue 3rd party Modbus RTU devices go offline or have unstable value transfer after upgrading to version 1.7.1 or above Product Line EcoStruxure Building Operation Environment Detected in version 1.7.1 or above. Automation Server Modbus RTU (RS485) interface Cause The performance of the Modbus RTU interface was improved in version 1.6 and further in version 1.7. This improved performance can make the Modbus Master in SmartStruxure too fast for some third party Modbus RTU devices, and they may be unable to handle the faster polling rates the newer software can provide. Resolution In the Modbus Master Network there are various settings that can be changed to allow it to compensate for slower devices. The settings in this screen shot shows example settings that may be suitable for slower devices or problem networks.   Increasing the Transmit Guard bits from the default of 2 allows more time after one packet before the next packet will start transmitting on the bus. This is useful both for slow responding devices, devices that take longer to turn off their Transmit driver as well as networks that have a high capacitance due to poor cable selection. The Receive timeout (ms) is the length of time the master will wait to receive a response. Decreasing this from the default of 2000 mS (2 Seconds) can often improve network communications, by not waiting too long for a device that may not be responding or offline will improve the overall network operation. By default there is 0 delay between polling the points, by introducing a delay in the Point Poll Delay (ms)  it allows slower devices to handle the data polls from the interface. This is a key setting for slower devices that cannot keep up with the faster polling from the latest Automation Servers and most 3rd party devices will require a value greater than 0. The Silence Characters do not usually need changing in an upgrade, but they can be used to help with poor installations where there is high capacitance in the cabling or poor grounding, this can often be used with lower baud rates on problem sites. The default Poll Duty Cycle is usually appropriate for most installations and is not affected by the upgrades, but can be adjusted if required to match 3rd party devices. In V3.x the same settings apply and the screenshot now looks like this:

Issue What is the BACnet attribute COV Increment and how to use it Product Line Andover Continuum Environment BACnet Cause The COV Increment attribute on a BACnet point is equivalent to the Threshold attribute of standard Continuum Infinity inputs. When a Continuum BACnet point is subscribed to by other BACnet devices using COV (Change of Value), its value must change by at least that COV Increment value before a new Value Notification will be sent out. Using this attribute will decrease network traffic especially on the MSTP network when subscribing to frequently changing values.  Resolution This CovIncrement attribute can be set in the BACnet point's Editor on the Basic Alarms Tab.   If you have a CyberStation prior to Version 1.8, setting this value from the point editor will not stay persistent in the controller after the controller is reloaded, it will default to 0. In order to keep the value after a reload, you will need to write a PE program to set the desired value after a reload. The program should be Autostart and Fallthru. A sample of the program is below: Line SetCov Writeproperty("Full Bacnet Path to Point", CovIncrement, "Desired Value") Stop If you have several points that need the CovIncrement set, you would just add the additional lines into this program.   In 1.8 or greater, this program is not needed as these attributes get sent to controller on a reload. Suitable initial CovIncrements still need to be added to each BACnet point however as they default to 0.

Issue What is the limit of how many devices a BACnet controller can know about (Known devices) and what does that mean. Product Line Andover Continuum Environment BACnet bCX bCX4040 Cause More details required about Known devices Resolution The known device limit of a Continuum Ethernet level BACnet controller is 255 and for a B3 level MSTP controller it is 32. This limit means is if a controller needs to either subscribe to a COV from another controller or deliver alarms (Event notifications) to a workstation, that each one of these target devices is a known device. So, for example, if a b3 controller is subscribing to COV's from 30 other controllers and needs to deliver alarms to 3 WorkStations, it would require 33 known devices and the last request for a target device would fail. If a Controller is making 30 COV Subscriptions from one a single controller that would only count as 1 known device. This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to. For example, if a controller had a global point (OAT) that 50 other controllers needed to subscribe to, this is allowed because each COV subscription has within it the target controller's address information and does not use the known device limit. There are two cautions that must be considered. Refer to What are the differences between Standard Continuum Import/Export and Continuum BACnet COV?. Each COV subscription in an exporting controller takes away user memory. Each subscription uses approximately 56 Bytes of user memory. So the limit of how many other devices can subscribe COV's in an individual controller is limited by free memory in the exporting controller. NOTE: To reset  the known devices following a change in the Controllers that will effect the number of known devices, the controller needs to be reloaded.