Building Automation Knowledge Base

Issue Do the MRs have the ability to run a time schedule without a MRI, MCI or I/SIT LAN? Environment I/NET MRs Cause If communications are lost to the MRI, MCI, or LAN, a stand alone time schedule will continue to work at the controller level. Resolution Yes, you can build a Standalone ATS in the MR functions editor or I/STAT. Standalone ATS (Automatic Time Schedule) is an MR-resident ATS schedule programmed into the MRs that allows a single start stop time for each day of the week for the point designated as the master Device Control point in the MR Parameters editor. These commands are only issued if the MR and MRI/MCI are NOT communicating. Refer to our System Operator Guide TCON 207 or TCON 236 for more details.

Issue OSTART and OSTOP not working on a temperature control extension Environment I/NET Resident I/O Temperature Control Extension Cause Optimal start requires the space temperature to meet the cooling/heating target temperature sometime after the optimized start time. Resolution Check that the space temperature has met the cooling/heating target temperature sometime after the optimized start time in order for the OSTART to work properly.

Issue Deleting doors in the access control editor Environment I/NET Site with Access Control Cause Deleting doors in the access control editor Resolution When deleting a door from a 7791 DPI, 7793 MCI or a 7798 I/Site LAN, make sure to delete the door Parameters before deleting the door (DO) point. Deleting the door (DO) point without previously deleting the door Parameters may cause unpredictable system performance. If the point has already been deleted first, the best way is to: Re-add the point again Save it in the NetCon Follow the correct sequence. Then it will work fine.

Issue Where do I find I/NET's phone entries? Environment I/NET 2000 Cause This file is only created if a dial setup is actually being used. Resolution The phone entries are stored in the file inet.phn in the directory c:\inet2000\data. 

Issue What type card readers can the Model 1119T interpret (Card Access Control Data Entry)? Environment I/NET site Cause What are the types of card readers that the Model 1119T interprets (Card Access Control Data Entry)? Resolution The unit can be used with any reader that has a wiegand output including most common proximity readers from HID, Motorola Indala, etc.

Issue This NPR 2000 communicates fine on one network segment but not another. Why? Environment I/NET Site Cause This NPR 2000 communicates fine on one network segment but not another. Why? Resolution A site has the NPR 2000 which refused to communicate on the Ethernet. When they moved it from a 400 foot LAN segment to a 100 foot segment, it worked. Although 300ft. is the standard limit, the ferrite ring on the internal network jumper may have some impact on that. For that matter, if that jumper is suspect for any reason, the network cable can be plugged directly into the NPR 2000s NIC card temporarily for diagnostic purposes.

Issue A 7792 is used specifically for what? Environment I/NET site Cause A 7792 is used specifically for what? Resolution It is the interface to Micro Regulators (MRs) and Application Specific Controllers (ASCs), (TCON 209, 1-21)

Issue A 7793 is used specifically for what? Environment I/NET site Cause A 7793 is used specifically for what? Resolution A 7793 is the interface for Micro Regulators (MRs), Application Specific Controllers (ASCs), and Door Processing Units (DPUs). (TCON209, 1-20).

Issue What is the maximum cable length for NPRs on a controller LAN (C-LAN)? Environment I/NET site Cause What is the maximum cable length for NPRs on a controller LAN (C-LAN)? Resolution NPRs on controller LANs are still limited to 1500 meters or 5000 feet. (TCON 209 2-25)

Issue What are 7805 Link Taps? Environment I/NET site Cause What are 7805 Link Taps? Resolution This series of Taps connect a workstation to controller LAN Taps (Site Taps) through a Direct Distance Dial (DDD) telephone network. They communicate to a companion model in the 7806 Taps, which forms the connection from a workstation to the remote controller LAN. (Refer to TCON 101, Model 7805 Link Taps.)

Issue How will I know if an output relay on the 7716 is energized? Environment I/NET site Cause How to know if an output relay on the 7716 is energized? Resolution An LED (Light Emitting Diode) indicator adjacent to each output relay will illuminate when the relay is energized.

Issue How do I get the system information using the serial channel RS-232 B? Environment I/NET RS-232 B Serial port Cause This information cannot be gathered using a web browser. Resolution Get system information using serial channel RS-232 B (See below how to connect terminal emulator to serial channel) Command err a Displays all error messages in the system error log. Print it to terminal emulator.  Command sysinfo Displays all system information such as software versions etc. Print it to terminal emulator. Disconnect and connect power. Print what is displayed on the screen during boot to terminal emulator.

Issue In I/NET version 2.16 and above, after installation, the first thing that needs to be set up is a profile. It can be a new one or use the existing one profile. Environment In I/NET version 2.16 and above, after installation, the firs thing that needs to be set up is a profile. It can be a new one or use the existing one profile. Cause In I/NET version 2.16 and above, after installation, the first thing that needs to be set up is a profile. It can be a new one or use the existing one profile. Resolution Start the I/O Configuration, log in using the default username and password. Select the default settings and once the editor opens up, choose the link set up that will be used for this configuration, like Direct Connect, Com number, Baud Rate.  For Direct Connect the Hardware address must be 0. In the Workstation Options, click on the connect button and verify that the correct Database is being connected to. For a Server/Client Option, verify that the local host is set to Remote Client if using a different database that resides elsewhere (this is only for versions 2.40 and higher). Enable Access Control and CCTV if this is being used or leave unchecked if not. Leave the default save directories, unless you plan on saving elsewhere. Enable TCP/IP if needed and Host number. Put in reference Hosts if applicable, set I/O Server to Shut down if no clients or Maintain, depending on what you want it to do. Click on the okay button, to close the editor and click on Make Active to enable the new editor to be the active profile. Close I/NET and I/O Server and then restart it again. The new profile should be active and running now after the correct user name and password has been entered.

Issue Implementing a pre-entry access card anti-passback using Plain English program Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 2 Controller Continuum ACX 4 Controller Cause The anti-passback implementation in Continuum engages when the credential holder enters the area as detected by the door switch/contact. (if no door switch is configured, then the credential holder is considered to have entered the area immediately after access has been granted by the system) When doors are located in close proximity to each other, as is the case with a bank of turnstiles, for example, the built-in anti-passback scheme is easily defeated as a cardholder is able to unlock multiple nearby turnstiles before triggering the door contact and engaging the built-in anti-passback functionality. Resolution The simplest solution to the issue described above is to configure the door objects WITHOUT a door switch/contact, this, however, is not always possible depending on on-site requirements. A second solution is to take control of the doors using Plain English. The solution presented here is for a bank of three turnstiles, (A, B, and C), it uses a PE program per turnstile. The solution can easily be adapted for a bank of less or more turnstiles. NOTE: The PE programming here is provided as a sample, for guideline purposes only, the programs are not intended as a complete solution, significant modifications may be required for site deployment. Program code for door/turnstile A 'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' |_____X______X______X______ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the 'initialization line which specifies which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileB, theTurnstileC 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_B, theLastCard_C, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_B, theLastCrdTime_C Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_A theTurnstileB = Turnstile_B theTurnstileC = Turnstile_C 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_A_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_A_CrdNum theLastCard_B = Trnstle_B_CrdNum theLastCard_C = Trnstle_C_CrdNum thisAlarmPoint = TurnstileA_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_A_EvntTm theLastCrdTime_B = Trnstle_B_EvntTm theLastCrdTime_C = Trnstle_C_EvntTm Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_B Value) and (Date - theLastCrdTime_B Value) < theTurnstileB DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_C Value) and (Date - theLastCrdTime_C Value) < theTurnstileC DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM '------------------------------------------------------------------------------------------ Goto MONITORING Line E If TS > 10 then Goto MONITORING Program code for door/turnstile B 'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' | ______X______X______X____ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of the following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the initialization line which specifies 'which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileA, theTurnstileC 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_A, theLastCard_C, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_A, theLastCrdTime_C '------------------------------------------------------------------------------------------ Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_B theTurnstileA = Turnstile_A theTurnstileC = Turnstile_C 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_B_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_B_CrdNum theLastCard_A = Trnstle_A_CrdNum theLastCard_C = Trnstle_C_CrdNum thisAlarmPoint = TurnstileB_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_B_EvntTm theLastCrdTime_A = Trnstle_A_EvntTm theLastCrdTime_C = Trnstle_C_EvntTm '------------------------------------------------------------------------------------------ Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_A Value) and (Date - theLastCrdTime_A Value) < theTurnstileA DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_C Value) and (Date - theLastCrdTime_C Value) < theTurnstileC DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM Goto MONITORING Line E If TS > 10 then Goto MONITORING Program code for door/turnstile C   'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' | ______X______X______X____ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the initialization line which specifies 'which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileA, theTurnstileB 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_A, theLastCard_B, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_A, theLastCrdTime_B '------------------------------------------------------------------------------------------ Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_C theTurnstileA = Turnstile_A theTurnstileB = Turnstile_B 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_C_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_C_CrdNum theLastCard_A = Trnstle_A_CrdNum theLastCard_B = Trnstle_B_CrdNum thisAlarmPoint = TurnstileC_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_C_EvntTm theLastCrdTime_A = Trnstle_A_EvntTm theLastCrdTime_B = Trnstle_B_EvntTm '------------------------------------------------------------------------------------------ Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_A Value) and (Date - theLastCrdTime_A Value) < theTurnstileA DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_B Value) and (Date - theLastCrdTime_B Value) < theTurnstileB DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM Goto MONITORING Line E If TS > 10 then Goto MONITORING        

Issue Technical Support Services occasionally receives calls concerning the use of DC/DM points in the Micro Regulator product line. The use of DC/DM points in MRs is possible but only when certain guidelines are followed. Environment SubLAN controllers MRs UCs Cause The functionality of the DC/DM points depends on what is actually controlling the DC point. If you use any of the extensions that reside only in the MRI, MCI or I/SITE LAN, etc., to control the DC point you will not have a problem. These extensions include: Time Scheduling, Temperature Control, Calculations and Event Sequences . As long as one of these editors controls the state of the DC point you should not see a problem with the functionality of the DC/DM points. Where you run into trouble is when an MR resident editor controls the DC point. These include all of the modules found in the MR Resident DDC editor, (PID, Floating, Two Position, Relay, Reset, Calculation module). If the state of a DC point is controlled by any of the MR resident DDC modules the associated DM point will always alarm in one state or the other. The same is true for the UCI/UC product line in that a DC point can not be controlled by a UC resident editor. This includes everything under the Unitary Control editor, (VAV, AHU, PID, FLT, HPMP ). In fact, currently if an attempt is made to enter a DC point in any of these editors an error is generated which will not allow such an entry, (this error is not generated in the MR Resident DDC editor). Resolution If you need positive feedback like that provided by the DC/DM points please follow the guidelines set below: Create Control Description and State Description Parameters: Refer to figure 1 and 2. Create an External DO point for Fan Control. Refer to Figure 3. Create an External DI point for Fan Status. Refer to Figure 4. Create an Internal DA Point for Fan Alarm. Refer to Figure 5.  Create a Calculation for the DA point: Refer to Figure 6. Anytime the Fan Control DO and the Fan Status DI follow each other’s state, the calculation remains True. If the DO does not equal the DI State, then the calculation becomes False. This results in an Alarm after the Time Delay of the DA has been met. The Time Delay acts in the same manner as the Time to State for a DM point. Please note if the DI 0 state was ON (the opposite of the DO), the calculation would be P0=~P1 .   *MSG* 09/21/95 12:34:29 Thu Control descriptions and commands Host 00 (CSI) Link 02 [78020] DCU 29 [DCU 7798] Enter up to 4 characters:  # Description Command Delay --+-----------+-------+-----  0 STRT 1 0  1 STOP 0 0  2 0 0  3 0 0  4 0 0  5 0 0  6 0 0  7 0 0  8 0 0  9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15 0 0 Figure 1: Control Description and commands *MSG* 09/21/95 12:35:14 Thu State descriptions Host 00 (CSI) Link 02 [78020] DCU 29 [DCU 7798] Enter up to 4 characters: # Description # Description --+----------- --+----------- 0 OFF 16 1 ON 17 2 ALRM 18 3 NORM 19 4 20 5 21 6 22 7 23 8 24 9 25 10 26 11 27 12 28 13 29 14 30 15 31 Figure 2: State descriptions *MSG* 09/21/95 12:36:19 Thu Resident I/O points Host 00 (CSI) Link 02 [78020] DCU 29 [DCU 7798] Point 0000 (02290000 DO) Enter up to 16 characters: Parameter Value Parameter Value ---------------------------------------- ------------------+-------- Point name Fan Control Distribution group 1 Point class Ext Distribution mask -------- Scan interval (seconds) 60 Alarm priority - Global level Local Message priority - State description 0 Cell number 0 Control description 0 Restart control action Reinforce Minimum trip (minutes) 0 Minimum close (minutes) 0 Three-state output N Figure 3: Resident I/O points *MSG* 09/21/95 12:36:19 Thu Resident I/O points Host 00 (CSI) Link 02 [78020] DCU 29 [DCU 7798] Point 0000 (02290000 DI) Enter up to 16 characters: Parameter Value Parameter Value ---------------------------------------- ------------------+-------- Point name Fan Status Distribution group 1 Point class Ext Distribution mask -------- Scan interval (seconds) 10 Alarm priority - Global level Local Message priority - State description 0 Cell number 0 Number of bits 1 Supervision None Figure 4: Resident I/O points *MSG* 09/21/95 12:38:56 Thu Resident I/O points Host 00 (CSI) Link 02 [78020] DCU 29 [DCU 7798] Point 0009 (02290009 DA) Enter up to 16 characters: Parameter Value Parameter Value ---------------------------------------- ------------------+-------- Point name Fan Alarm Distribution group 1 Point class Int Distribution mask Y------- Scan interval (seconds) 10 Alarm priority Priority Global level Local Message priority Priority State description 2 Cell number 0 Number of bits 1 Normal state 1 Alarm delay (seconds) 120 Supervision None Figure 5: Resident I/O points *MSG* 09/21/95 12:39:57 Thu Calculations Host 00 (CSI) Link 02 [78020] DCU 29 [DCU 7798] Point 0009 (Fan Alarm) Enter point address or name: Equation --------------------------------------------------------------------------- P0=P1 Operand Point Operand Constant -------+---------------- -------+---------------- P0 Fan Control P1 Fan Status Figure 6: Calculations   The above calculation will return the following DA conditions depending on the state of the DO and DI DO DI DA OFF OFF NORM ON OFF ALRM OFF ON ALRM ON ON NORM

Issue Definable Tool Settings are not Transferable Environment I/NET Seven Cause With the introduction of I/NET Seven, the Definable Tools button is a new feature providing a useful shortcut for applications to be more user friendly. Resolution The two kinds of tools available are Events and Shortcuts. The definition below gives the description of their uses: Event - Use this tool to execute an event sequence defined in a controller. Shortcut - Use this tool to launch another application, open a file, visit a website, etc. There is a misconception though, that they can be created on a graphic page, saved and then re-applied at another location. This is not the case. These Tools and Buttons are PC Specific and cannot be transferred from one PC to another because the SQL database does not save these settings. If the user wants to set up these Tools (Events and Shortcuts) then they would have to do it for each PC, that is looking at the data or each page that it exists on. This is providing the user has rights to these buttons through the Host Passwords.

Issue Can the DHCP protocol be implemented on a Niagara R2 UNC-410 controller? Environment Niagara R2, UNC-410 Cause IP Protocol Resolution Yes, UNC-410 can use the DHCP Protocol to assign an IP address. Static IP addresses provide the most reliable connectivity between Niagara hosts. It’s recommended that static IP be used over DHCP whenever possible. Reference “Niagara Networking & Connectivity Guide” for information.  

Issue Pinpoint crashes when Animation is selected under the Active Components menu.  The crash occurs both when editing an existing animation or when attempting to create a new animation. Environment Pinpoint Active Animation Crash Cause Domain account permissions were restricted Resolution The network administrator increased the permissions for the account user.  No further details are available.

Issue When attempting to install the Web Server software directly onto a site PC, an error is indicated and the installation fails. The error message is as follows; Unknown Error - 0X80042000 Environment Sigma. Web Server Installation. Antivirus Software. Cause The Antivirus software sees the installation as a threat and stops it. Resolution Disable the Antivirus software while the installation of the Sigma Web server takes place. This may require that the site IT department get involved.

Issue Should the Touchscreen "Time Master" setting still be set, when the Touchscreen is connected to a Xenta 555? Environment Micronet Xenta 555 Cause The Touchscreen would normally be configured as a "Time Master" when not connected to a Xenta 555. Resolution The functionality remains the same, the Touchscreen is set as a "Time Master" and will broadcast the time every 10 minutes, by default.