Issue Unable to successfully install Continuum keyless license software. Product Line Andover Continuum Environment Continuum Keyless Soft License Hasp Key Utility Sentinal HASP License Manager Cause Various causes. Resolution The following articles address issues with the Continuum Keyless license software. Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped Web based email should not be used to deliver Keyless Licensing information files (c2v) or activation files (v2c) How to determine the Continuum version, features and the Hasp license ID on a Keyless Continuum License Hasp Key Utility will not activate keyless license Version Error Getting Id. -- Key Id Not Found Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped

Issue Every so often one or two programs on the Continuum workstation stop working. Editing the program results in: A Cached Program cannot be opened while it is being written. Product Line Andover Continuum Environment CyberStation WebClient Continuum Programs Cause CyberStation was not installed properly. Too many demands are being placed on the workstation. Resolution If the problem results from a problem with the installation of Continuum Cyberstation, refer to Problems installing Continuum. Once Continuum has been properly installed, the problem may result from placing to many demands on the Continuum workstation.  Some questions that should be asked are... How many programs are being run on the Cyberstation concurrently. The default setting for Run on any workstation when a workstation program in created is false. This property should be checked for all workstation programs whether they must be run from another workstation or not. This setting can be found in the Program properties editor. An a cached program cannot be opened while it is being written error may occurring when a report program is writing to disk. Verify that the Cyberstation PC conforms to the Continuum Compatibility Matrix for the Continuum version. How many PE programs are running on this workstation, how complex are these programs and are high level commands such as: Rotate, Run, Shell, OpenFile, OpenList, GetName, GetObject being used frequently. How many report programs are running concurrently.  Is the report workstation 100% dedicated to running reports and nothing else; no alarm reporting, no schedules, no extended log downloading, no Access server functions? Is the workstation hardware and operating system sufficient for the work CyberStation is expected to do. Managing these demands may involve sharing the reporting load over several CyberStations and/or adjusting the timing of processor intensive programs so that the workstation is executing fewer tasks at any given time.  In some cases program performance may be impaired due to insufficient memory allocation. See Getting a Smart Heap error when starting Cyberstation or not all processes start and Cyber doesn't open.

Issue Invalid user name or password dialog when logging into webclient with acc that works in Continuum Product Line Andover Continuum Environment Webclient Windows XP Windows 7 Windows 2003 Windows 2008 Cause Activex control didn't download or an update to .Net requires a re-register of .Net to IIS Resolution This happens when attempting to login to webclient when there are higher security restrictions on Internet Explorer so files that need to get installed on the client machine get blocked. A. Add the webclient server as a Trusted site in Internet Explorer on each client machine as follows: Open Internet Explorer and select> Tools> Internet Options> Security> Click on Trusted Sites and Click the Sites button Deselect "Require server verification (https) for all sites in this zone Add the webclient server name Ex. http://Servername (This typically populates automatically.) B. Also, change the default security settings to medium-low as follows: Open Internet Explorer and select> Tools> Internet Options> Security>Click on Trusted Sites and Click the Custom level button In the "Reset to" drop down, select Medium-Low and then Click The Reset button Click Yes to the "Are you sure you want to change the settings for this zone?" In the Settings list, manually enable "Download unsigned ActiveX controls Click OK, Click Yes to "Are you sure you want to change the settings for this zone?" Click Ok and Ok again C. Run the aspnet_regiis.exe -i command from DOS to re-register .Net with IIS From DOS> CD\ Windows\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis.exe –i Once these steps are completed, enter the URL for webclient again, the appropriate activeX controls will install and the login will work normally. If this still doesn't work and you get a message that "Internet Explorer is currently running without add-ons" then take a look at the following Microsoft articles.   https://social.technet.microsoft.com/Forums/ie/en-US/53a3b82c-e61a-4576-8d80-91e204d4b1e9/internet-explorer-is-currently-running-with-addons-disabled?forum=itprovistaie Also see Internet Explorer gets "web.Client only supports Internet Explorer 32 Bit version 8.0 and greater" when logon to the Webclient server. This article is similar, but mentions changing the compatibility view in Internet Explorer.

Issue The network administrator requires that the SQL Andover97 password be changed every three months.  How will this affect the Continuum System? Is it necessary to do a Database Initialization each time the password is changed? Product Line Andover Continuum Environment Andover97 SQL Database Initialization Cause Once the Andover97 password has been changed, the workstations will lose their connection with their access to the database until the workstation (not the database) can be initialized with the new password. This will be indicated by a Database Fault error at the workstations.  Resolution The proper way to change to transition to the new password is to: Shut down all cyberstations. Change the Andover97 password in SQL. Launch Continuum Database Initialization. Select Workstation and enter the new password on the Database page, then select OK. Relaunch all cyberstations.  Once the password is changed, it is only necessary to do perform a workstation initialization (not a database initialization), but this must be done on each workstation.   Refer also to the following article that discusses how Continuum uses the sa password: When is the SQL System Admin (sa) password required?

Issue BACnet bCX MSTP network loses communication when a b-Link is added or removed Product Line Andover Continuum Environment MSTP b3 bCX4040  b-Link Cause The bCX MSTP circuitry is slightly different to the b-Link  MSTP circuitry , thus under some circumstances, other faults on the MSTP network can cause communication to change, when the network is connected via a b-Link Resolution If an MSTP network is installed correctly, then it will operate correctly at all speeds up to 76.8k (assuming all devices operated up to this speed) If the MSTP network is not stable up to 76.8k, or adding or removing a b-Link causing a loss of communication, then it is likely there is some fault on the network. (adding or removing the end of line termination resistors, is also a useful fault finding option) The bCX MSTP components are slightly different to the b-Link MSTP components, thus under some circumstances, other faults on the MSTP network can cause communication to be lost, when the network is connected via a b-Link Example This has been seen when third party variable speed drives (VSDs) were connected to a bCX MSTP network (these unit had switchable termination resistors that by default were in circuit) The communication was ok at a low speed (19200) connected directly to a bCX, but when the network was put on the secondary side of a b-Link, the communication failed. Once the termination resistors were switched out of circuit, the communication via the b-Link was fine. In the example above the VSDs were by ABB Related: How to change the Baud Rate of a field bus (Infinet or Bacnet MSTP) when there is an Infilink or B-link on the network

Issue Using the keypad on the stat to set the comm address may result in duplicate Device Instance IDs on a BACnet network. Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconics Cause Find New BACnet Device does not result in new Viconics stat added to the system. This is due to the default assignment ID scheme used by Viconics. It is resulting in a duplicate Device ID on the BACnet network. Resolution By default, the Device Instance ID (called the Device Node ID in Continuum) is generated using the first two digits of the model of the thermostat + the comm (MAC) address assigned to the stat. Example: For a VT7200C5000 thermostats with MAC address 115, the default Device Instance would be 72115. The problem is that when installing the same model stats on multiple MSTP networks on the same BACnet system, this scheme can easily result in duplicate Device Instance IDs. The resolution is to change the duplicates or use a scheme to assign unique IDs manually to all the stats on a system. Any number between 1 and 4194303 (between 1 and 3FFFFF in Hex) is accepted by the thermostat. One scheme would be to use the BACnet Network ID and append the MAC address to it. Since each BACnet Network ID must be unique across the entire system, and the MAC address on each BACnet Network must be unique, this assures the combination is unique across the system. For example, if you have a bCX with an MSTP bus on comm2 that has a BACnet Network ID - Comm2 of 2765 and a stat with a MAC address of 9, assign it the Device Instance ID 2765009. A BACnet Explorer that provides write access to the Device Instance ID is required to change the default Device Instance ID. See Changing the BACnet device instance of the SE7000 series room controllers for a link to the Viconics VT7000 BACnet Configurator utility. For additional support on the above utility contact Viconics Support at 1-800-563-5660.

Issue Verifying the Com Port on a PC is working properly by using "Loopback" test in Terminal Emulator. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Hyperterminal RS-232 serial port Cause The following test writes to the serial port and reads from the same port. This will verify the Full duplex operation of the RS-232 communication. Resolution Short the TX and RX pins of the cable (pins 2 and 3) following the pinouts below. Gender is determined by pin type.                Male DB9 (Left) and Female DB9 (right)   Launch Hyperterminal by selecting Start>>Programs>>Accessories>>Hyperterminal. If you do not have Hyperterminal, please read Hyperterminal on Microsoft Windows Operating Systems. If you are asked if you would like to install a modem, select No. Choose any icon and name the session, select "OK". In the next Pop-Up menu, choose direct to COMx (where x is the number of the COM Port you are testing.) Set the flow control setting to None. Leave the other settings to default settings, select "OK" Select File » Properties from the menu bar, select the Settings tab, and then push the ASCII Setup button. Check the option for Echo typed characters locally. Type something. If you see double characters the serial port is setup correctly and is functional. The display is showing characters that are sent out and what is read in. The Emulator will send and display the TX and immediately read and display  RX. If you see exactly what you are typing, you have a communication issue. which could be: Bad Com Port Bad cables Pins not shorted correctly If you are out of physical ports to try, use a USB Serial Port converter. If you are using a USB, use Reassigning a USB Serial Adaptor to a desired COM port for instructions of assigning Com to another port.

Issue Right clicking the controller and selecting "Distribute Personnel" results in NO distribution There is no error Product Line Andover Continuum Environment CyberStation Cause Corrupted Personnel Distribution table in SQL ContinuumDB Resolution Truncate table PersonnelDistribution and re-populate it, then distribute personnel once again. WARNING: Unless knowing exactly what you are doing, deleting entries from your database can cause irreversible harm to your database and can potential cause corruption. Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and if not already installed, where to get Management Studio from) Make a backup of the Continuum database as a precaution. Close ALL CyberStation workstations. In SQL Management Studio execute the following query. truncate table PersonnelDistribution Once the table is truncated it must be re-populated by one of the following methods... If the total number of personnel objects is reasonably small (in the hundreds) launch Continuum and bring a list view of all the personnel objects, select all then right click and perform a 'Send to controller' OR In SQL Management Studio Invoke the stored SQL procedure that initializes the PersonnelDistribution table using the query dt_DIST_Init_Personnel_Dist_Table IMPORTANT: Truncating the PersonnelDistribution table will remove all pending personnel distribution including personnel deletions; controllers could potentially continue to allow access to doors for the deleted personnel until reloaded. Conversely, removing a pending personnel distribution could potentially cause a person to be denied access at a door until a distribution is performed to the controller.

Issue What are the bCX and b3 COV subscription limits? Product Line Andover Continuum Environment CyberStation bCX4040 bCX4920 b3 devices Cause Confusion on the limits for COV subscription in the Continuum BACnet devices. Resolution The b3 controllers are restricted to 32 devices, which means they can simultaneously establish  COV CLIENTsubscriptions with up to 32 different devices (Andover Continuum or third-party). The bCX1 and the b4920 permit COV CLIENT relationships with up to 255 devices. These limits are device limits and NOT point limits, so if a bCX has established COV subscriptions with 500 points on device X, it can still set up multiple COV subscriptions with up to 254 other BACnet devices. IMPORTANT- See Limit of how many devices a Bacnet controller can know about (Known devices). This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to as a COV SERVER. For instance if a particular controller had a global point like OAT that 50 other controllers wanted and subscribed to this particular controller for that COV, 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 stated regarding this example however. 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.

Issue Does Port Based Network Access Control Ethernet 802.1x apply to Continuum controllers? Product Line Andover Continuum Environment Continuum Ethernet Controllers Cyberstation Cause A question that may be asked by Customers IT Departments Resolution No, the 802.1x protocol is not applicable to controllers, it is a Port based Network Access Control (PBNAC) that is used by Routers and computers. It is related to the Operating system user accounts and policies so is above and outside the scope of Continuum. Not all devices support 802.1X authentication. Examples include some network printers, Ethernet-based electronics like environmental sensors, cameras, and wireless phones. For those devices to be used in a protected network environment, alternative mechanisms must be provided to authenticate them. One option would be to disable 802.1X on that port, but that leaves that port unprotected and open for abuse. Another, slightly more reliable option is to use the MAB option. When MAB is configured on a port, that port will first try to check if the connected device is 802.1X compliant, and if no reaction is received from the connected device, it will try to authenticate with the AAA server using the connected device's MAC address as username and password. The network administrator then must make provisions on the RADIUS server to authenticate those MAC-addresses, either by adding them as regular users, or implementing additional logic to resolve them in a network inventory database. Many managed Ethernet switches offer options for this. Network Security is an available option add on for IP level controllers. Please refer to IPSEC and Network Security on Controllers for more information. Another potential option would be to secure the controllers on a separate VLAN.

Issue Webclient currently unavailable Error 80070005 Check your DCOM permissions when launching webclient or webclient is currently unavailable. Product Line Andover Continuum Environment Webclient Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause A remote reboot will not write DCOM permissions the same way a local reboot does. Other Server configurations can cause this. Resolution A webClient installation was performed using Windows Remote Desktop or some other remote access software and the reboot after the webclient install was executed using the remote software. To fix this, reboot the Webclient server directly from the server itself. There are security permissions that do not get written properly when rebooting remotely and a direct reboot corrects this problem. Start Continuum on the Webclient PC locally, not remotely. Be sure Continuum has been started on the webclient PC. Also see, Webclient unavailable error when attempting to logon which mentions making sure the Network Service is selected for the default app pool. 64-bit OS will cause this error as well. Webclient versions pre 1.94 are not supported on any 64 bit platform. If that doesn't work then a complete reinstall and reboot on the server will be required. Remote installs are typically problematic. If changes were made to .net try the following steps: Start> Run> cmd (Enter)  To get to a DOS prompt cd\Windows\microsoft.net\framework\v2.0.50727 (change directory to this folder) run the command aspnet_regiis.exe -i (It will say installing .net, this re-registers .net with IIS) Restart Windows on the webclient PC and restart Continuum

Issue Planning an upgrade and need to know which Infinity system controllers can NOT be upgraded to Continuum. Product Line Andover Continuum Environment Infinity Continuum CX9000, CX9100, CX9001, CX9101 CMX220, CMX221, CMX222, CMX230, CMX231, CMX232, CMX240, CMX241, CMX245, CMX246 Cause Some Infinity system controllers can NOT be upgraded to Continuum. Resolution CX9000, CMX220 series,CMX230 series, CMX240 series and CX9500 ranges can not be upgraded to Continuum, all other controllers can be upgraded, some via a chip change, others can be upgraded via Continuum update. The LSX280 Laptop service tool is not compatible with Continuum, a RoamIO should be used. Check out the Software and Firmware compatibility matrix for older versions of the traditional product lines for the minimum versions required for Cyberstation, but the following gives an overview of the requirements: CX9200 (CX9300,CX9201) - Requires chip replacement with Continuum firmware V1.5x CX9400 Eclipse (CX9410) - Requires flash upgrade to Continuum V1.5x firmware, but will require working SX8000 system to flash the controller, otherwise send to Repairs for upgrading. ACX780 -  Requires chip replacement with Continuum firmware V1.5x ACX781C ACX700 -  Requires chip replacement with Continuum firmware V1.5x ACX701C DCX250 - Requires Infinity V2.16 firmware chip Other i1 (generation 1 infinet controller) controllers require a minimum of V1.4 firmware chips

Issue Not all 3rd party manufacturers use the same Modbus addressing. Product Line Andover Continuum, EcoStruxure Building Operation Environment Modbus RTU X Driver bCX1, CX controllers, NC2 Building Operation Enterprise Server Building Operation Automation Server Cause Not all manufacturers use the same Modbus addressing. Resolution Many manufacturers have put their own slant on the "Modbus Standard" for addressing and number formats. The standard only defines 16 bit integer and binary data, but many manufacturers needed to use long integers (or swapped) and floating point numbers. They will transmit them as 2 integers over the protocol, then the receiving system needs to interpret them accordingly. To cope with this, special function codes were added which cover most formats. There are various interpretations by different 3rd party systems on addressing. Some number from 0 and others starting at 1. Some require a 30000 or 40000 offset including in the address, depending on I/O type. What is implemented in the X Driver is that whatever decimal address you enter in the X Driver point is what is sent down the bus. If the other system supplier is asked exactly what address they want sent down the bus, that is what is required in the X Driver point. Sometimes this is not the address that is on their datasheets. Sometimes there may be a need to add or subtract a value of 1, 30000 or 40000. This article was written for Continuum, but is still relevant to EBO Also see Helpful Modbus register Information for further information on Modbus registers.  

Issue The Save to Flash exclamation point (bang) on a Controller object, does not go away even after a valid save to flash is performed on the controller. Product Line Andover Continuum Environment Continuum Controllers Cause An InfinityNumeric with its Setpoint attribute set is changing value frequently. With this Setpoint attribute set, every time the object changes value, the controller sees that the change needs to be applied to the flash as well. This changes the ObjectStatus of the Controller Device object to indicate a Save To Flash is required by  showing the exclamation point (bang) on the controller. Resolution Check if you have any InfinityNumeric points with the "Setpoint" flag set that update frequently. In ContinuumExplorer, under the controller object, right-click the InfinityNumeric default class folder and select "View". This will launch the object class listview for this controller. Add the Setpoint attribute by selecting View -> List View Configuration. Select columns tab, click "Add Column". Select the Attribute field in your new column and from the drop down select "Setpoint". Apply your Changes and refresh the ListView. The InfinityNumerics that have the Setpoint value of True are the ones you want to look at closely to determine which ones are changing value frequently and if they really need to be configured as a Setpoint.  Also, refer to Save to Flash exclamation point indicates that the controller 'requires flash backup'.

Issue Continuum reports an Unknown Model Number error. Product Line Andover Continuum Environment Controller Model number Bootloader Learn Cause Possible reasons why Continuum may report an Unknown Model Number error. Controller is in bootloader mode. Controller is not responding fast enough due to a comm issue. The controller type saved in the Continuum database is different from the controller type physically installed. The total number of controllers exceeds the maximum number of nodes allowed on the Master. The baud rate of the bLink is not correctly set for the MSTP bus. The comm bus is not stable. Problems introduced to the bus due to a bad controller or electrical interference. Resolution Communication issue must be troubleshot by using a combination of Controller error logs and LAN capture analysis. A controller can be brought out of bootloader mode by flashing the firmware.  Create the device manually. Attempt to learn the controller onto the bus with no other controllers attached Correct misaligned baud rate settings. Run an ACCTrace at the Workstation during a learn to detect duplicate IDs. Other articles that address this issue: Unknown model number error when learning I2/b3 device Learn Process stopped and get an error "Can not learn this controller, it contains an unknown model number"

Issue What badging or card creation software solutions do we support with Continuum? Product Line Andover Continuum Environment Continuum Access Control Cause Want to use a third-party badging or card creation system to create badges for a Continuum Access Control system. Resolution The only badging software that we support is EpiBuilder through the -B badging package we offer for Continuum Cyberstations. See the "Badge Manager" help topic in the Continuum on-line help for more information on EpiBuilder. See Devices that have been tested and approved by ImageWare for supported badge printers.

Issue Unexplained network and communication errors IT department may have set up IP blocking or set up IP switches incorrectly or there may be an issue with the Continuum setup Product Line Andover Continuum Environment IP network Cause Problems in the IP network, port blocking or incorrectly setup in IP switches IT departments may say their system is set up correctly, but this may need to be tested. Resolution See Router required open port numbers to run a Continuum system for IP port requirements See Continuum Controllers and IP Managed switches for other IP switch settings Get all the problematic equipment connect to a simple non managed IP switch (this will probably involve temporarily moving PCs and/or controllers) Disconnect from the site IP switches if possible (this may not be possible, depending on the site setup, eg. SQL server may be in a server room) PC and Controller settings (IP address, subnet mask, default router) may also need to be temporarily modified depending on the original site set up. Test the system with this temporary setup, if all is ok then the problem lies with the site IP network, if the problem persist then  look at the Continuum setup (Cyberstation install, database, operating systems, hardware issues)

Issue Display options now the DCX250 is no longer available Product Line Andover Continuum Environment Continuum DCX250 Touch Screen Display part number 01-0008-300 Cause The DCX250 is not available from January 2012: Discontinuation of Infinity 01-0008-300 (DCX 250) - PA-00184 Resolution There is no direct replacement for the DCX250 and there is no other display that works directly on Infinet.   The Continuum display options are- Netcontroller IO Bus - Infistat or LD-1 Direct connection to some controllers - Smart sensor or xP-Display A Continuum Cyberstation could be used if more information and input is required. Another option would be a Bacnet or Lon display. Or, the L-VIS from Loytec using bacnet MSTP may be such an option (LonWorks and BACnet Touch Panels Release - PA-00106). http://www.loytec.com/products/lvis (LON via NC2-F- port16 would also be an option, see Can LONMark Devices be used with Continuum?) NOTE - All support for this product is via Loytec. The EMX170 was a small display and keyboard available for some older Infinity Controllers (i1) This unit is obsolete, although it may be possible to repair one. There is no replacement for this unit. If the i1 controller is being replaced with an i2 unit then either a smart sensor or an xP Display plus room sensor could be used

Issue Original company sold to new company Site License needs to be updated for install/upgrade.  Computer failure and no software/license information is available. Downloaded software and during install it requests a CD Key Product Line Andover Continuum, TAC INET Environment Site Licensing for install/upgrade Cause Changes in company or computer replacement/upgrade or downloaded software and it is requesting a CD Key Resolution I/NET: 1. Original company sold to new company and Site License needs to be updated for install/upgrade: for company naming changes, contact your sales representative who in turn will contact Product Support and request a transfer of information or upgrade/purchase. Once the information has been cross referenced for validity, either a new or replacement CD Key can be generated. Please include the following when requesting transfer: User Name Site Name Site Address Serial Number Version number Build number CD Key 2. Computer failure and no software/license information is available: Send email to Product Support with the following information: User Name Site Name Site Address Serial Number version number Build number CD Key 3. CD Key for licenses on purchase of software can be ordered by contacting Contact Customer Care. Link is available on the Contact tab of this web page. Customer Care offers pricing, order placement, changes, expedites, and order status. Check Licensing of I/NET with SITE and SEAT License with License Key for issues with CD Key and Licensing information. Continuum: since Continuum only has physical security key licensing, the license is owned by the holder of the key. If you hold the key, you own the license. There is no need to contact PSS for moves, changes, restructuring. If the security key's are lost or stolen, you will need to purchase new keys to replace them. Continuum Software Licensing is available with Release 2.0. 

Issue What is the limit of the number of Controllers that can be in a Continuum System? Product Line Andover Continuum Environment Continuum Cause Want to know the theoretical and practical limits to how many controllers can be on one system. Resolution There are certainly some logical limits to how your Netcontrollers are addressed and identified in the system but for all intents and purposes you are only restricted by the IP Address. Netcontrollers Logically, you can have Netcontrollers addressed from 1 - 190 - so the maximum you can have in a "logical" Network is 190 Netcontrollers. However, the number of Networks you can have in a Continuum Database is only restricted by the Database itself - effectively infinite. See the article below on logical Networks. How many logical networks can be created on a Continuum system? This restriction is only for Netcontrollers defined within the Infinity side of the Continuum Database and does not apply to third-party BACnet controllers. Field Controllers (b3 / i2) There is a definite limit to the number of subnet (Infinet or MSTP) controllers that can be strung off of a given bCX or Netcontroller. As a general rule, each comm port can support up to a maximum of 127 subnet devices. Of course this does depend on the device being used, the amount of nodes it is enabled for, and the physical installation. The number of nodes purchased does correspond to the total number of i2 or MSTP controllers that can be on that bus. Example: If you have a bCX1 with 32 MSTP nodes this means that a total of 32 MSTP devices can be on this MSTP network and the following architecture is valid. bCX1 with bLink; (segment1) node1 to node16. (segment2) node17 to node32. If we look at a Netcontroller or Netcontroller II, these controllers have two RS-485 comm ports that can be used to support Infinet subnet controllers, up to 127 on each port and a maximum of 254 off the one controller. Now the controller would need to have both ports enabled for 127 nodes and considerations made for the amount of traffic this number of controllers would require. Similarly, the bCX1 (BACnet) will support up to 127 nodes. One thing to note is that this also includes repeaters if they are used to extend your network or star the MSTP. The general rule for the number of devices on an MSTP segment is a maximum of 32 nodes, this dependent on the network complying with MSTP installation guidelines for termination, distance, cable type, and that each node is a full load RS-485 transceiver. In the case of our BACnet controllers, they use a 1/4 load transceiver so given perfect network conditions it is possible to have 127 b3 devices on the same MSTP network segment. Even though this is possible, it is always good practice to use a b-Link repeater and a max of 32 devices per network segment - this also helps to segregate the devices for troubleshooting as well. Total Point Limits Other than with a Cyberstation with an I/O limited Security Key, I'm not aware of any limits to the number of points that can be created in a Continuum Database; this would be limited to the size and resources of the Continuum SQL Database. Consult the following article that has a spreadsheet to help estimate the size of your Continuum Database. It could also help to estimate your SQL requirements: Continuum Database Sizing and SQL Server selection