Building Automation Knowledge Base

Issue What is the purpose of the Max Info Frames attribute in a Continuum BACnet controller? Product Line Andover Continuum Environment BACnet MS/TP, MaxInfoFrames Optimizing MSTP Cause Information on the Max Info Frames function. Resolution The Max Info Frames setting on the BACnet controller object editor specifies how many messages that the controller can send out to other controllers when it has the token on the network. For instance, a B3 controller has a default of 2 for this setting. If it receives the token on the MSTP network and it has 5 COV or Event notifications to send to other controllers or workstations, it will send the first 2, and wait until it gets the token the next time around and send 2 more, etc. The BCX controller has a default of 8 for Max Info Frames. This setting is changeable through the BACnet controller editor, however care should be taken not to increase it to too large a number. The larger the setting, the more time that particular controller can hold the onto the token, which in turn denies other controllers on the network the capability of sending out their data in a timely manner. It should only be adjusted if there is a definite need for increased messaging, but on the MSTP network it is not recommended to go above 10, although we do not limit the value. In a Cyberstation Version 1.8 or above the setting can be made on the details page of the BACnet controller device editor. If adjustment of this parameter is done using any Cyberstation prior to version 1.8, the setting will not stay at the new value after a controller reload from the Infinity side, it will revert to it's default. You will need to create a PE program in the controller to set this parameter to the desired value if it is reloaded. The program should be autostart and fallthru, and use the "Writeproperty" keyword to set the parameter. The syntax should be as follows: Line SetMaxInfo WriteProperty ("Full Bacnet path name of controller", MaxInfoFrames, "New Value") Stop

Issue How do I change out a failed B4920 or BACnet BCX controller? Product Line Andover Continuum Environment B4920 BACnet BCX controller Cause Failed device Resolution Place Cyberstation Offline. Edit existing B4920 or BCX Controller object on the Infinity side and note the following: ACC Net ID BACnet Device ID Network ID - UPD Network ID - Comm2 (MS/TP network ID) IP Address, Subnet Mask, Default Router (Gateway) Address Name of the controller Physically disconnect power and MS/TP data cables from existing B4 or BCX Controller. Remove existing B4 or BCX Controller. Install replacement B4 or BCX Controller. Connect MS/TP data cable to the replacement B4 or BCX Controller. Connect power to the replacement B4 or BCX Controller. Use a web browser to connect to the login page of the B4 or BCX at IP Address 169.254.1.1. Use the controller configuration web page to configure the following values: ACC Net ID (enter the value from Step 2 a) BACnet Device ID (enter the value from Step 2 b). This is very important - do not use the new controller's serial number or you will likely have trouble communicating with the new controller on the BACnet side.  BACnet Network ID - UDP (enter the value from Step 2 c) BACnet Network ID - Comm2 (enter the value from Step 2 d) IP Address, Subnet Mask, Gateway Address (enter the values from Step 2 e) Name (enter the value from Step 2 f) If this device is a BCX, the user will want to reset the BACnet MAC ID - Comm2 value, if that value was non-zero in the device being replaced (there is no record of this value in Cyberstation). Click the Submit to Controller button then Commit Changes button and then CommitChanges/Restart Controller button. Allow sufficient time for the controller to restart. In CyberStation, on the Infinity side, edit the controller object and change the serial number to that of the new controller. Save the object.   Go back to Online mode in CyberStation. The new B4 or BCX should now be online in the Infinity view. Reload the B4 or BCX Controller. Verify existing Points and Programs are running correctly. Perform a “Backup to Flash” operation on the B4 or BCX Controller. Check that the controller is online in the BACnet side. Note that the Device Node ID on the BACnet side is the serial number of the old (replaced) controller. This is as it should be since we do not want to create a new BACnet device; we just want to replace the controller hardware. Edit objects on the BACnet side to verify that there are no errors.   Test alarms, graphics, communication to b3's/3rd party devices, etc. 

Issue Getting "Failed CreateDNWACServer. Cause: Object reference not set to an instance of an object. URL: “http:///DNWACServerFactory/WACServerFactory.soap" when trying to open a graphic through WebPinpoint with Continuum version Product Line Andover Continuum Environment Windows XP Windows Vista Webclient Windows Server 2003 Windows Server 2008 Cause Configuration of mime types and correct path to the file must be made Resolution Make sure Microsoft .Net 2.0 is not installed as this will cause the above error message. We did not support Microsoft .Net 2.0 until the 1.74 release. Check to make sure that on the machine that the browser is being run from has the NetBIOS over TCP/IP enabled. This can be found in the advanced properties of the TCP/IP settings on that machine. Make sure that “Directory Browsing” is enabled for the NewGraphicsFiles in the IIS configuration. This can be found by running the IIS Service manager and expanding the explorer until you see the NewGraphicsFiles virtual directory. Right-click on the virtual directory and select properties. There will be a checkbox for “Directory Browsing” in the middle of the page, make sure this is selected. On XP add the aspnet to the DNWACServerFactory folder security tab on the folder.

Issue Quick Knowledgebase access to Continuum 2.0X information Product Line Andover Continuum Environment Continuum Cause A Knowledgebase article for Continuum 2.0X information in case a product announcement wasn't received. Resolution The initial release of Continuum v2.0 software was announced by Schneider Electric in PA-00353 CyberStation & web.Client v2.0. Version 2.0 includes a Software licensing option, SMTP email, support for Internet Explorer 10 & 11, and access control enhancements. Version 2.0 is a paid upgrade for all prior Andover Continuum versions (i.e. v1.9x and below). Release Documents: Feature Blast Compatibility Matrix Cyberstation Installation Guide Webclient Installation Guide Download Links: Continuum Cyberstation 2.0 Download Webclient 2.0 Download Software license and Ordering and activation process  

Issue DCX 250, backlight is working but no text or splash screen is being displayed. Product Line Andover Continuum Environment DCX250 Cause Failure of controller hardware. Resolution Replace DCX250.

Issue Question on what to set the virtual memory to on a Continuum Workstation PC Product Line Andover Continuum Environment Windows XP Cause Question on what to set the virtual memory to on a Continuum Workstation PC Resolution Virtual Memory Requirements The virtual memory "Initial size (MB)" setting on your workstation PC should be set to a minimum of 1 GB. To make this change: Go to Start, Settings, Control Panel. In the Control Panel, double click System. The System Properties menu, shown on the next page, appears. Click the Advanced tab and click Settings in the Performance box. The Performance Options menu appears. Click the Advanced tab. In the Virtual Memory box, click on Change. When the Virtual Memory dialog appears, fill in the desired paging file memory size (initial and Maximum). Click OK as you back out of the dialogs.

Issue A license is needed for using the Roam IO2 with ethernet Product Line Andover Continuum Environment Roam IO2 Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause A license is required to use the ethernet feature with the Roam IO2 Resolution Follow the instructions for Generating a License request in the BACnet Service Tool Generating a License manual, (PDF attached). Include your contact information, PO (purchase order) and RA numbers for the RoamIO2. Send that information to Upgrades.Continuum@schneider-electric.com to process the request.

Issue After upgrading to Continuum 1.94, Cyberstation throws the following error: Failed to call pILiveData -> GetLiveData().  ACDataServices has an error. Product Line Andover Continuum Environment Continuum 1.94 Schedule Error Cause This behaviour is due to a bug that was described in TPA-BOST-12-0002 00 Schedule Exception Errors. Resolution Install the CyberStation v1.94 SP1 - Software which can be found on the Exchange Extranet.

Issue What file types or graphical components does Pinpoint support? Cannot import a GIF file in to a Pinpoint graphic. Product Line Andover Continuum Environment Continuum Cyberstation 1.XXX MS Windows XP Server 2003 Cause GIF files are not supported. Resolution Pinpoint graphical components supported: Lines Rectangles Polygons Curves Ellipses Text Bitmaps Enhanced Metafiles (EMF) Icons DIBS (Device Independent Bitmaps) Jpeg

Issue Alert - New Worm: W32.Slammer UPDATED: January 27, 2003 SEVERITY: CRITICAL Go to the following Microsoft https://docs.microsoft.com/en-us/security-updates/securitybulletins/2002/ms02-039 web site for more information. Customers who have followed previously issued instructions and already installed Microsoft Security Bulletin MSO2-061 and the patch associated with Q317748 do not need to install the new patch in order to prevent the W32.Slammer worm from infecting their machines. Customers who have not yet taken those preventative measures should follow the directions provided in this alert to patch their machines against the vulnerability exploited by the W32.Slammer worm. Environment PRODUCTS AFFECTED: SQL Server 2000 RTM, SQL Server 2000 SP1, SQL Server 2000 SP2, and Microsoft SQL Desktop Engine Version (MSDE) 2000 Cause WHAT IS IT? The PSS Security Response Team (Microsoft) is issuing this alert to inform customers about the W32.Slammer worm, which is currently spreading in the wild. You are not at risk unless you are running one of the above listed products. Customers are advised to review this information and take the appropriate action for their environments. This alert is primarily focused at business customers. IMPACT OF ATTACK: Denial of Service TECHNICAL DETAILS: W32.Slammer is a memory resident worm that propagates via UDP Port 1434 and exploits a vulnerability in SQL Server systems that have not applied the patch released by Microsoft Security Bulletin MSO2-039. This bulletin was first available on July 24, 2002. This worm is designed to propagate, but does not appear to contain any additional payload. Customers can detect if they have Microsoft SQL Desktop Engine (MSDE) 2000 installed by using the following instructions: Right-click on the My Computer icon Select Manage Double-Click on Services and Applications Double-Click Services If MSSQLSERVER is in the list of services, the default instance of MSDE is installed on their machines. Other Instances may exist, if they do they will be listed as MSSQL$**** (where stars indicate the name of the instance). Resolution RECOVERY: Instructions for Removal of W32.Slammer from infected Microsoft SQL Server 2000 Servers or Microsoft SQL Desktop Edition (MSDE 2000) Set the SQL Server Service to Manual. Reboot the infected machine. If you are running Windows NT 4.0 Server Service Pack 6a install the patch referenced in Microsoft Knowledgebase Q258437. The Microsoft Knowledge Base can be found at http://support.microsoft.com. Install the security patch associated with Microsoft Security Bulletin MS02-061. Please note that the Microsoft Security Bulletin MS02-061 patch has been re-released to include the functionality previously only available through Q317748. Users who install this updated patch do not need to install Q317748. Users can verify installation of this patch by verifying the following files are at version 8.00.568: ssmslpcn.dll dbmslpcn.dll Set the SQL Server Service to Automatic.

Issue HID Proxpro with keypad Environment Applies to both I/NET and Continuum door controllers. Cause Information pertaining to the HID ProxPro   Resolution When ordering a keypad reader from HID, you need to make sure the Configuration Setting option is "09 - Buffer one key, add compliment, 8 bit message (Dorado)". Example: 5355 AGK 09 - ProxPro w/ Keypad If you are using the 5535 model reader on an Infinity ACX781 or ACX780 model controller you will need to order with Configuration Setting option 00.

Issue How do I time sync my controllers to my workstations? Product Line Andover Continuum Environment Continuum site Cause The workstation will only synchronize its time to the controllers automatically when the controller is reloaded. It is common practice though to have the controller synchronize its time with the workstation on a periodic basis, commonly once a day. Resolution The only way to synchronize time between the Controller and the Workstation is through a Plain English program running the Workstation. This Program only needs to be created in one Workstation. Below is an example of the program as well as how to trigger the program to run. If Minute = 3 then Goto SetTime Else Stop SETTIME: Set NetworkName\LowestNodeCXName\Date to Date Stop E: Stop Note: This program needs to be triggered off the minute system variable. The program is a Fallthru program which resides in the CyberStation. You only need to do the lowest ACCNet Id controller in each Continuum network. Also ensure that the UTC offset has been correctly entered in every Workstation and BACnet device, and that each Network has the correct Time Zone setting.

Issue How do I set up a Continuum system to do automatic log truncation to save database space? Product Line Andover Continuum Environment Continuum Trend logs Cause Database maintenance. Resolution Setting up Automatic Log Truncation with SQL Server and MSDE Database  MSDE Engine For MSDE, you can download the Stand Alone MSDE Database Utilities from Buildings Download Center.  These utilities are capable of automatically truncating the logs, as well making automated backups, checking for low hard drive space, etc.  SQL Server For full SQL Server, you can easily create a scheduled Job. Details are described below.   To create a scheduled Job that will truncate the Continuum logs in the SQL Server: Open up SQL Enterprise Manager  (Note that the SQL Server Agent service must be running in order to create a Job) Highlight the Continuum database From the Menu, select Tools \ Job Scheduling A wizard opens: "Welcome to the Create Job Wizard." Click Next Select Transact-SQL Command,  Click Next For the Database Name, select ContinuumDB (or whatever the name of the DB is) In the large white space for the Transact-SQL Command, cut and paste the code from our web site: ****** Replace 90 with the number of days to maintain in each log ******** delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 Click Next On the next screen, you are asked when you do want to run this job Select "On a recurring basis" and hit the Schedule button On the Schedule page, set up whatever schedule you desire Click OK to close the Schedule Page • Click Next On the Job Notifications screen, you can choose (if you want) any email or net send alerts. This is optional • Click Next In the final page, you are given a summary of the Job you have just created and you can change the name of your Job to anything you want. It might be a good idea to give it a more descriptive name like "Weekly Log Truncation" Click Finish and you are done. You should get a message that the job was created successfully. To verify that the Job is running correctly, you can go to the Enterprise Manager of SQL Server and click on the Management Folder, then expand the SQL Server Agent folder and click on Jobs. On the right-hand pane, you will see a list of created jobs. Scroll down and find the job that you just created. You can get information about the history of the Job, whether it ran successfully or not.

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 Renamed SQL server or Single User Cyberstation and now workstation will not connect to the database Environment SQL Server Single User Cyberstation Cause When initially installing the database the computer name is registered as part of the SQL Server/MSDE install. If after the SQL server/MSDE you change the computer name the database will not start up which in turn causes Cyberstation not to start up. Resolution The correct method to change the computer name of the computer running the SQL Server/MSDE database is to: Backup the database Uninstall SQL Server/MSDE Change the computer name Re-install SQL Server/MSDE Re-initialize a blank Continuum database Restore the backup database

Issue Import Export table and alarm delivery troubleshooting procedures for CX, Infinet controllers, and Cyberstation Environment CX Infinet controllers Cyberstation Cause The below troubleshooting outline can be used when trying to determine why point values are not being transferred from one controller to another. Also there is a section to troubleshoot why alarms are not being delivered correctly from the controllers. Resolution Programming import export problems: Open point editors for the source and destination points, verify whether or not the point value is being transferred. If the values are not being transferred then verify the program that is transferring the values is enabled and active. If the program is disabled then go to the runtime tab and determine why the program is disabled. If the program is not disabled then manually run the program, if it is a fall through, and see if the values update. If the values update when manually running the program then the problem is not an import/export problem but a programming problem. If everything with the programming side of things checks out then get a dumb terminal dump of the source and destination controllers. Use the command “Dump All” at the R prompt through dumb terminal. Look at the Import/Export entries in the source controller’s dump file and see if the Import/Export entry is in the dump file in the Import/Export section of the dump file. The format of the entry should look similar to the below. If the Import/Export entry is in the dump file then the problem is not an import/export problem but more than likely a communications problem. Verify the integrity of the Infinet bus and see if there are any problems there. If the bus integrity looks good then the problem could possibly be an intermittent communications problem. If the transfer of these point values are critical then one recommendation would be to add a “Point refresh” program that runs at certain intervals. If the import/export entry is not in the controller dump file then try selecting the first option, “Do not reload attached objects”, in the “Send to Controller” options and reload the controller. What this will do is resend just the Import/Export table down to the controller. Check to see if the point is now sharing correctly via the point editors. If so then the problem was a corrupt Import/Export entry in the controller. If the problem still exists then go to the next step. If the problem is still there then get another dumb terminal dump of the source and destination controllers and verify whether or not the Import/Export entries are in the controller. If the entries are there then review step 5. If the Import/Export entries are not there then run the Import/Export fix up utility against the database and repeat steps 6 through 8. If after going back to steps 6 through 8 the entry is still not there then backup the database and send it to TSD with all the specifics on the points that are not sharing, controller names that owns the points, and programs that transfer the point values. Open the point transfer program and re-save it. Go back to step 7 only.   Alarm Import/Export problems. The below describes how to check to see if an alarm delivery problem is Import/Export table related. Did the alarm get logged into the database? If the alarm did get logged then this is not an Import/Export problem. If the point is still in alarm does the point editor reflect that the point is in alarm? If not then this is not an Import/Export problem. If the point is in alarm and it is not logged check the NewAlarmCount system variable on the CX level controller. If the value of NewAlarmCount is NOT zero then this is not an Import/Export problem. If the point is in alarm and the NewAlarmCount system variable in the CX is zero and the alarm is not logged then this could be an Import/Export problem. If you disable the point and cycle it out of alarm and then back into alarm does the alarm come in? If the alarm comes in then this is more than likely a communications problem and not an Import/Export problem. Check the Continuum error log and see if there are any errors being posted for the delivery if this alarm. Run the ACCTrace utility, from the workstation that is supposed to be logging the alarm, when cycling the point in and out of alarm. Send trace file to TSD for review. To determine which workstation is logging the alarms use the below calculation: The Netcontroller will take it’s own AccNetid and mask it with 63 stripping off the 2 high bits of it’s id leaving a result in the range of 1 to 63. For those of you who are binary mask challenged, NetControllers with Ids between 1 and 63, result is their ID NetControllers with Ids between 64 and 127, result is their ID - 64 (ID range of 0 to 63) NetControllers with Ids between 128 and 190, result is their ID - 128 (ID range of 0 to 62) That result is then added to 190 and that is the ID of the first Workstation to get the Alarm and Log it in the Database. If there is no Workstation with that ID (or the workstation with that ID is offline), the NetController will send the alarm to the Workstation with the next highest ID above the one calculated by the ratcheting algorithm. If no Workstation Ids are higher than the one calculated, the routine will loop around and use the lowest Workstation ID to send to first. Do a dumb terminal dump of the controller that is having the problem. The command to dump it is “Dump All”. Capture this dump file to a text file and check the Import/Export table section of the dump file. The Import/Export section of the dump file should have an entry for the points that have alarms attached to them. The format of the entry is: pointname  to Alarm. If the Import/Export entry is in the dump file then the problem is not an import/export problem but more than likely a communications problem. Verify the integrity of the Infinet bus and see if there are any problems there. If the bus integrity looks good then the problem could possibly be an intermittent communications problem. If the transfer of these point values are critical then one recommendation would be to add a “Point refresh” program that runs at certain intervals. Using the calculation above to determine which workstation is logging the alarm verify that workstation exists in the database. If that workstation does exist in the database make sure that that workstation is pointing to the correct database. We have run into situations where one workstation switches between databases using the same workstation ACCNet ID and IP Address. Doing this will cause problems with alarm and Access Event delivery. If you are doing this kind of installation you must have a unique ACCNet ID and IP address for each database. If the import/export entry is not in the controller dump file then try selecting the first option, “Do not reload attached objects”, in the “Send to Controller” options and reload the controller. What this will do is resend just the Import/Export table down to the controller, it does not reset the controller. Go back and retest the point and see if it goes into alarm and delivers the alarm correctly. If so then the Import/Export entry for the point was corrupted in the controller. If the alarm still is not logged or delivered do step 8 again. If the Import/Export entries are not there then run the Import/Export fix up utility against the database and do steps 10 and 11 again. If the alarm is still not logged then backup the database and send it to TSD with all the specifics on the points that are not sending the alarms. Please include the controller names that owns the point and also what alarm link is not working correctly. Edit the point, remove the alarm attachment and save the point. Then re-edit the point, re-attach the alarm and resave the point. Check and verify that the alarm functions as it should.

Issue Continuum BACnet controllers are sending out incorrect or large amounts of unnecessary COV data on the network. Environment Continuum BACnet controllers Cause The Continuum BACnet controllers cannot be programmed the same as the Non BACnet Continuum controllers when it comes to points that are being exported to other controllers. There are 2 main differences that the programmer must be aware of when programming these exported points. Resolution The first difference to be aware of is that in a Continuum BACnet controller every change of the value of an exported point is immediately sent out at the time of the change regardless of when the point changed within the controller program scan. What this means is that unlike standard continuum programming which latches and exports the final value of a point after the entire controller scan is completed, the Continuum BACnet controller will send out any change it sees during the scan. So if you were toggling a point's value several times within the same program or within multiple programs, all the changes to the value are sent to recipient controllers during the scan, not just the final value. This will cause both incorrect and unnecessary data exports. The second difference is that, in the case of standard Continuum points such as InfinityNumerics and InfinityOutputs, some values can be sent to them that are not reflected directly when the values are translated into BACnet. For example if you had an InfinityNumeric and used it as a binary value in the BACnet world, a program could set it to "On" and later in a program you may perform Boolean logic on it and it would be set to a logical "1", or "true". In the Standard Continuum, these values would be different, however in BACnet, both of these values would be translated to the same value. Because the evaluation of the COV point change is done before we translate it to the BACnet standard we would transmit this as a change of value even though the value transmitted in both cases would be the same. In this case we would transmit the COV during the scan every time we saw this value toggled to what BACnet would think was no change. This would cause unnecessary COV data to be transmitted. The bottom line is that if you, through "Plain English" need your logic to set a value to a Continuum BACnet object more than once during the program scan and it is being exported, you will need to use an intermediate point such as a local variable or an InfinityNumeric to store the changes and only commit the final value to the exported point at the end of the manipulation.

Issue When swiping a card, an Invalid Parity error occurs in the Active Event view or in the Access Event log. Environment Active Event view Access Event log Cause This can either be caused by a reader malfunction or the reader being wired incorrectly. Specifically on the reader wiring they may have swapped the Data and Clock lines. Resolution Try swapping the Data and Clock line on the connector of the controller/IOU module.

Issue What is the pin out for a cable to commission a netcontroller (CX99xx)? Environment CX99xx Cause Need to create a cable to commission a controller. Resolution RJ Connector <- - - - -> 9 Pin RS232 PC Controller Comm3 Pin 1 - DTR <- - - - -> Pin 1 - CXD Pin 2 - CTS <- - - - -> Pin 7 - RTS Pin 3 - CXD <- - - - -> Pin 4 - DTR Pin 4 - RTS <- - - - -> Pin 8 - CTS Pin 5 - GND <- - - - -> Pin 5 - GND Pin 6 - RD <- - - - -> Pin 3 - TD Pin 7 - DSR <- - - - -> Pin 6 - DSR Pin 8 - TD <- - - - -> Pin 2 - RD On the RJ connector for the controller's comm3, Pin 1 is the furthest to the left with the insert clip facing away from you and the gold teeth facing you.

Issue What is the difference between the TimeOfLog and TimeStamp columns in an Alarm or AccessEvent listview? Environment Alarm or AccessEvent listview Cause One reason as to why there could be a difference between the two is that the controller did not have communications with the workstation that is logging the events so it buffered the events until such time as it could send them. Another reason is that this is a remote site (RAS) setup and the controller was buffering the events until the controller or workstation requested an update of the alarms and events. Resolution Generally these two timestamps should be close to the same value. The difference between these 2 columns is that the TimeStamp column is actually when the Alarm or Access Event happened, the TimeOfLog column is when these events were logged into the database.