Issue Temperature inputs not reading the correct values Environment Cyberstation IOUs Controller Cause Bad input Bad controller Bad sensor Resolution Replace sensor with a 10k ohm resistor.  Temperature input should read roughly 77°F or 25°C.  If it does then the problem is with the sensor.  If it does not then the problem is either with the input board or that particular input itself.

Issue Cannot communicate to third party devices using the MODBus TCP XDriver or MODBus RTU XDriver. Environment CyberStation ACX5740 XDriver MODBus TCP Cause The MODBus TCP configuration point was not created Resolution Create the MODbus TCP configuration point following the guidelines in section 5.1.3 of the MODBus TCP guide

Issue How to convert a B4-920 to a BCX4040 Environment BACnet B4-920 BCX4040 CyberStation Cause How to convert a B4-920 to a BCX4040 Resolution ASCII export the B4-920 then modify the dump file to change from the B4-920 to the BCX4040.  Delete the B4920 from both the Continuum view and the BACnet view in Continuum Explorer. Import the converted dump file into the system.   Reload the new BCX and all it's child objects.  Execute a Find New BACnet Device to pull all the devices back into the BACnet view.  Execute a Send to DB on the BACnet side to pull all the objects in. NOTE:   Another option if you are running version 1.90 CyberStation or greater is to change the model number through the controller editor in Continuum Explorer.

Issue What does error 1808 mean in a controller error log Environment Controller Continuum Cause The controller tried talking to another controller but could not because the other controller was offline. Resolution Determine why the controller is offline and the error will go away

Issue Will a Power Supply PS 120/240 AC 85 work with a Netcontroller 1? Environment CX 9900 CX 9901 CX 9940 Cause Verifying power supply compatibility Resolution The PS120/240 AC 85 model power supply will work with CX 99xx model controllers.

Issue Is IPv6 supported with Continuum Netcontrollers? Environment BCX 4040 BCX 9640 9680 ACX57xx Cause IPv6 compatibility with Continuum Netcontrollers Resolution As of today, 3/21/2013, Continuum controllers do not support IPv6. There are no plans at this time to implement IPv6 into Continuum controllers.

Issue The Network Service account doesn't show when searching by using the Find button in webclient dcom configuration. dcomcnfg is used to set permissions for the network service for components in webclient and by default the wrong context may be selected. Environment Webclient 1.8x Webclient 1.9x Windows Server 2003 Windows Server 2008 Cause When using dcomcnfg (DCOM configuration) the context of the search for the user account is not correct, so the account isn't found when using the Find button. Resolution   Start> Run>dcomcnfg Select one of the 4 components to configure Select the security tab Select the Customize radio button and select Edit In the Launch Permissions dialog select the ‘Add’ button In the Select Users, Computer or Groups dialog select LOCATION Select the PC name of the webclient PC and click OK Click on Advanced and select Network Service and add Local Launch and local activation Repeat this for the other 3 components.

Issue When executing a Find New BACnet Device a third party controller (Alerton) would not come into the system. Product Line Andover Continuum Environment CyberStation BACnet Alerton Cause The third party device did not have a name assigned to it. Duplicate device id on the network. Resolution Check with third party vendor to determine how to assign a name to the device When devices from different vendors are used it is possible to have device id duplication which will prevent one or more of the devices to be found. If device id duplication is detected, Continuum will indicate the condition in the error log. To solve the problem you must change the device id of one of the devices so that they all have unique device ids. You can determine which devices are duplicating by running acctrace and a wireshark while doing a Find New Bacnet and then looking in the database for these objects. If you cannot interpret what is found in those traces, send them to PSS for analysis.

Issue What does the error 01/30/2011 01:01:57.00 0x00004418       0x00002100       0x021046e2       0x00080003       0x00000030          DEVICE_ERR_NODATA_I2C      mean in a controller error log? Environment CyberStation Controller Expansion module Cause The error code means that the 9640 can’t communicate with the expansion I/O modules or with the RealTimeClock. Resolution Check communications to expansion modules Verify correct operation of the system time in the controller. Replace controller if needed

Issue Where to send broken/mal-function I/net hardware RMA Environment I/NET  Hardware Cause Can't find where to return a broken I/Net product Resolution Västerhaninge handles repairs, advance replacement and repurchase. Repair and advance replacements shall be added into their warranty claim system. http://warranty.tac.com   NOTE: The warranty starts from the day of purchase

Issue CX9200 keeps going online and offline.  Problem is progressively getting worse Environment CyberStation CX9200 Controller Communications Cause Corrosion buildup on the connect between the main board and power supply Resolution Remove and reseat the main board on the power supply Replace board and power supply with ones that have the Gold plated connectors In some cases the power may be slightly low 4.6V or lower so that the board isn't working correctly when the battery is low. Adding an external UPS can help.

Issue Access Events not displayed at door Access Events tab or in event viewer. Environment CyberStation AC1 AC1 Plus ACX57xx Access Server, AccessServer Cause Access Server system variable not set to a workstation ID or to the ID of the controller. Resolution Edit the controllers AccessServer System Variable. Set the value of the AccessServer System Variable to equal the ACCID of the primary access server, the primary access server is the Cyberstation that will receive the access events and will handle remote validation requests if the personnel record is not found in the controller. There may be cases where remote validation needs to be disabled (i.e. RAS sites), when this is the case set AccessServer to the ID of the controller.

Issue Removing or deleting a SNVT programmed within a Xenta Device that is no longer required in the application. By removing SNVT you increase the chance of having difficulty of getting the LonMaker Template to synchronize correctly with the modified Menta file. Understand the ramifications of deleting a SNVT and only do it when the benefits outweigh the complications. Environment TAC Vista TAC Menta NL220 or Lonmaker Cause Removing a SNVT will upset the SNVT binding order, by causing the index numbers in the XIF file to be corrupted. In this case it is not advised to delete SNVTS Changing a SNVT name or type will also cause indexing problems. The Vista object name can be changed to reflect that the SNVT is spare and not used If you have no SNVTs bound in LonMaker, the cost of deleting a SNVT is potentially having difficulty getting your LonMaker device template to synch up with the Menta file. If you have a few bindings, the downside of deleting a SNVT also includes redoing all of the bindings -- with one or two that's not a big deal. If you have 200 bindings, it can be a huge deal. Leaving a SNVT in the Menta file that isn't being used anymore just consumes one network variable input ... which can usually be dealt with easier than deleting it. So it's just weighing the pros and cons, but don't just go through without knowing what will happen. Resolution If the SNVT is no longer required in the Menta Application then carry out these steps. Disconnect the SNVT from the logic in the Menta application Allocate an area in you Menta application for unused SNVTs Move your unused SNVT into this area Label this area with the Text "UNUSED SNVTS DO NOT DELETE" Remove the public check box from the point if you do not want it visible in Vista Download the Menta application to the Xenta controller. Note: If the Xenta Application is standalone (Classic) and not in a LNS database SNVTs can be deleted without a problem

Issue A Plain English program is disabling with the error "attribute does not apply to the item". Environment CyberStation Controller Plain English Cause The controller database did not match the CyberStation SQL server database Resolution Reload the affected controllers

Issue Can audible alarms be delivered to a webclient browser? Alarms can be seen in a webclient browser, but no sound can be heard even when the event notification has the action 'beep on alarm' selected. Alarms in Cyberstation from this same alarm configuration beep normally. Environment webClient Windows XP Vista Windows Server 2003 Windows Server 2008 Internet Explorer 6 Internet Explorer 7 Internet Explorer 8 Cause Webclient browsers do not support audible alarms. Resolution Webclient browsers do not support audible alarms. An enhancement request for this feature has been made, but at this time it has been decided not to implement this feature. You can silence an alarm through a webclient browser, but no audible feedback is received.

Issue Unable to login in to the I/NET SQL database using the default password for login name  INetThirdParty. Seven ODBC Settings can not be changed using the INetThirdParty login, receive 'SQL Login Error: 18456' What is the I/NET third party password? Environment Windows XP, Windows Server 2003, Windows 7 I/NET Seven 2.40 and above Cause The I/NET Seven INetThirdParty password needed to comply with security requirements for Windows 7 and SQL 2008. Resolution The INetThirdParty password is now PassInetDb3p_SE (case sensitive). for  I/NET Seven 2.40 and above For Inet 2.31 and below its PassInetDb3p

Issue Alarms not showing up in the alarm list. Environment TAC Vista Workstation TAC Vista Server Cause The alarm could be disabled. The alarm might have priority 0 (info). There might be a filter in place in the alarm list. Resolution The alarm could be disabled, in workstation go to View > Disabled alarms to see the list and enable again. The alarm might have priority 0 (info). No Alarms with priority 0 is shown in the alarm list. There might be a filter in place in the alarm list, in the alarm view you are using right click and select filter to check this. A good practice is to set the "Date and Time" tab settings to reflect "Tripped " and "Last change" to show all alarms. This is done by checking the four checkboxes for "First alarm" and "Last alarm" allowing all alarms to be viewed.  

Issue Can Continuum software be run as a service Environment Continuum Cyberstation (all versions) Webclient (all versions) Cause Is Continuum software running as a service supported Resolution The Continuum Cyberstation  and Webclient Software cannot run as a service.

Issue The option to browse outside of bacnet controllers to select Event Enrollments and Event notifications is grayed out. Infinity Alarm Enrollments and Event Notifications can be created in folders and used with many controllers. Environment Continuum Cyberstation Continuum Bacnet BCX Controller B3 Controller Cause The Bacnet alarm protocol differs substantially from the Infinity system for alarming. The option to browse out beyond the controller has been disabled. Resolution Bacnet Event Notifications and Event Enrollments must be created in the bacnet device, so the option to browse out beyond the controller has been disabled.

Issue Received error on CX reload "Infinity controller error: Copy protection violation has occurred" Environment CX 99xx model controllers Continuum Cyberstation Cause Flashing the controller with the wrong flash file will cause the error "Infinity controller error: Copy protection violation has occurred" Resolution When selecting the firmware to flash to your controller, there is are two versions for each CX99 controller. If you are not using SNMP alarming uprev your firmware to the "SNMP Not Set" version.