Issue If a controller will be offline for an extended period of time, is there a way to make it not show up in the Alarm View as offline? Environment CyberStation Network level controllers (CX, ACX, bCX) Cause If a controller will be offline for an extended period of time, is there a way to make it not show up in the Alarm View as offline? Resolution Edit the controller and on the general tab select the "Out of Service" checkbox. This sets the "To State" in the Active Alarm View to "Return to Normal" and the Value to "Out of Service". It also relieves the workstations from the task of probing and looking for a response to a probe until the out of service flag is removed.

Issue How to find the installation log file when SQL install fails during installation of Vista Server. Product Line TAC Vista Environment Vista 5.x.x SQL Server 2005 SQL Server 2008 Cause The SQL Server is installed with a silent install and error messages can only be found in the created installation log file. Resolution SQL Server 2005 Browse to C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Log\Summary.txt SQL Server 2008 Browse to C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Summary.txt Search the file using keywords "error" and "failed" to find the nature of any installation problems.

Issue How to add another TAC Vista server node into an existing server in TAC Workstation. Product Line TAC Vista Environment Vista Workstation Cause Multi-sever Vista system is the system which has more than one Vista Server in the network. One Vista Server will be assigned as the master and the rest will be assigned as slaves. The order of setting multi-sever system is very important in order to make the system work properly. Common mistakes are: Vista servers have different versions. Adding slave computers before adding the master computer. Using same names of Vista servers. Using dynamic IP address. Vista Server object names are the same. All folders and objects found at the root level of the servers must be changed to unique names before merging the databases. Resolution Before doing that, please back up all TAV Vista databases on all computers. All computers should run the same version of TAC Vista. Also make sure all your IP networks are functioning. In addition, all Vista Servers need to be the same version. (eg. Vista 5.1.3 server will not be able to communicate Vista 5.1.4 server when they are noded together.) All computers’ TAC Vista Servers need to have different names. The server name can be checked by opening your TAC Vista Server. By default, Server name is the computer name. If the sever name needs to be changed, please following the steps listed below: Go to TAC Vista Server Setup Go to Vista Database tab Under “Rename Vista Server to” text field, type the new name Click ok and start the Vista Server to make sure the name has been changed Choose one computer to be the Master and the rest of the computers will be Slaves. Start by shutting down all instances of TAC Vista Sever and TAC Vista Workstations. Add Slave Servers into the Master Server. Start the Master TAC Vista Sever, and then start its TAC Vista Workstation. Right click on the Vista Server object. Select New>Object>Node. Type $LAN.SlaveServerName. If the Slave Server name is different from its computer name, change the IP/DNS address in the property window. (Note: this step requires a static IP address) Right click on the Slave Server Node and select Properties. Type in the IP address in the IP address/DNS name field. Repeat steps a-e for any additional Slave Servers. Leave the Master Server on, and start the Slave Server. Follow steps 4 a-e for adding Master Server into Slave Server but use the Master Server’s server name and IP address this time. Then, right click on the TAC Server object in Slave Server computer, select Properties. Under the General tab, change the Network Master to the Master Server name. Then click OK. If you have multiple Slave Servers, add the Master Server into each of them. Shut down all instances of TAC Vista Workstation and TAC Vista Server. Restart the Master Server’s TAC Vista Server and its TAC Workstation first. Then start the Slave Servers’ TAC Vista Server and their TAC Workstation. You should be able to view the Slave Servers under Master Server. Note: Master Server can view all Slave Servers’ projects, and each Slave Server can view Master Server’s project. However, each Slave Server cannot see other Slave Servers unless you node Slave Servers to each other. Any change made in Slave Server’s TAC Workstation will be reflected in the Master Server’s TAC Workstation. Vice versa also works.

Issue Xenta 555/731 resets when an alarm is blocked or unblocked. Environment Xenta 555, 731 XBuilder Cause If you set an alarm object to email you when the alarm is blocked or unblocked, the Xenta will send the email, and change the alarm state to blocked or unblocked, but then performs a reset. Resolution Work around for now is to not check the blocked and unblocked condition to send emails in XBuilder

Issue What Ethernet port speeds are supported by Sigma controllers? Product Line Satchwell BAS & Sigma Environment Sigma controllers ARM 7(S-696, S-x96CPU-AE, S-796, S-x796CPU-AE, S-DNN3, S-DNN3-DT, S-632-E, S-632-AE and S-IC3's) V53 (S-ETH, S-496, S-596, S-532, S-DNN and S-IC's) Cause Sigma controllers come in different hardware generations. The newer ARM-7 based controllers support more Ethernet connection speeds and auto-negotiation features compared to the older V53-based controllers, which are more limited. Resolution Supported Ethernet Speeds by Hardware Type Hardware Type Ethernet Speed Duplex Mode Auto-Scan Support ARM-7 (New) 100Base-T 100M Half Duplex ✅ Yes   10Base-T Full/Half Duplex ✅ Yes V53 (Old) 10Base-T 10M Half Duplex ❌ No 🔌 Cable Type Requirements for Direct Connection Hardware Type Straight Cable Cross-over Cable ARM-7 (New) ✅ Supported ✅ Supported V53 (Old) ❌ Not Supported ✅ Required 📘 Additional Notes Most modern Ethernet switches and hubs auto-negotiate the best speed and duplex settings. When troubleshooting connectivity issues, verify: Cable type used (especially for older V53 hardware) Switch port configuration (fixed speed vs auto-negotiation) Controller hardware version

Issue Is a controller reload required when upgrading from v1.74 to v1.93 or 1.94 to 2.02? Environment CyberStation v1.74,1.93 1.94 and 2.02 NetControllers, Infinet controllers Cause We will be performing an upgrade on a site from v1.74 to v1.93. or  v1.94 to 2.02 Do we need to reload every network controller? Resolution In this case it is not a requirement of the CyberStation upgrade that dictates if a controller reload will be required. However, in order to keep the CyberStation and controller versions compatible, a flash upgrade of some controllers may be required. (Refer to Continuum Software and Firmware Compatibility Matrix)  The process of doing a flash upgrade usually requires a reload and is generally a good idea. There are some cases where a minor version upgrade (for only a bug fix, for example) in a controller with a valid flash backup will not require a reload because the controller will reload itself automatically from flash. Even if you think a reload is not required make sure you edit a few objects in the controller after the flash upgrade. If you get an error that the object cannot be found, reload the controller and then do a flash backup. Additionally, a planned "outage"  is a good opportunity to reload a controller that may not have been reloaded in a while. It would be better to know right after the upgrade if there is a problem, than to find out after you leave the site. The Infinet controllers typically do not need to be reloaded - but make sure you test a few infinet controller alarms on all upgraded network level controllers.  

Issue Access Expert V2 configured MR52 Interface with inputs and outputs showing as Not attached (See snapshot) Product Line EcoStruxure Access Expert Environment V2 SSC MR52 Interface Cause The MR52 interface was previously configured with elevator controls but now has been detached in some manner. Resolution Remove the configured elevator references on each input and output individually and resave the point. Delete and re-add the points and configure the I/O as needed.  V3 works differently then V2. V3 allows for a more granular configuration so that the I/O selection just allows for the specific elevator other I/O selections. In V3 the assignments doesn't need to be released, only reselected.

Issue When attempting to connect from a TAC Vista Remote Workstation, the following error appears: "Ensure that TAC Vista Server is started" This occurs even when DCOM settings appear to be configured correctly. Product Line TAC Vista Environment Vista Server Workstation Cause This issue typically arises when both the TAC Vista Server and the Remote Workstation are part of a workgroup rather than a domain. In such configurations, authentication and DCOM communication can fail if certain conditions are not met. Resolution To resolve this issue: Verify DCOM permissions are correctly configured on both the server and the workstation. Ensure that the Administrator account password is identical on both machines. This is necessary for authentication in a workgroup environment. Restart both the TAC Vista Server and the Remote Workstation after making changes. Additional Notes This issue does not typically occur in domain-joined environments, where centralized authentication handles these permissions. For more information on DCOM configuration, refer to the TAC Vista DCOM setup guide

Issue Upgraded CX9200 chips and not able to load Bacnet PTP xdriver Environment Continuum Cyberstation CX 9200 Bacnet Xdriver Cause Upgraded chips on CX9200 and cannot load the Bacnet PTP xdriver. Resolution Use the latest Bacnet PTP xdriver version BacnetPTP1.00001.xdr

Issue What X Drivers are available? Environment All Continuum controllers that support X Drivers (XDrivers) 3rd Party interfaces Cause How to find out what standard X Drivers are available to integrate with Continuum controllers. Resolution The Third Party Communicates Interface and Protocol Brochure can be found on The Exchange Download Center that lists all available X Drivers and product compatibility. Also all of these listed drivers are available for download from The Exchange Download Center here for use on X Driver enabled controllers. Should a new driver development be required, or other special interface; then you can contact the team that develop X Drivers: Adam.Summers@Schneider-Electric.com You will need to provide protocol details if you require a quotation.

Issue The Output Summary Report shows the outputs configured for the instance. The report will show the output, the address of the output, the programmed activation time, and the downstream the output is attached to. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Documentation does not detail the steps to run Output Summary Reports Resolution To run an Output Summary Report 1. Select the 'Access Control' Tab. 2. Select the "Reports" Button. 3. Select "Add Report". 4. Double-Click "Output Summary Report" 5. (OPTIONAL) Enter a Display Name if you would like to save this report configuration for later. 6. (OPTIONAL) Enable "Include Child Folders" if you would like to include all people within an Enterprise 7. Click "Generate" to run the report, or "Save & Generate"

Issue When many trend logs are linked to the same time object for emailing via a Receiver Group, some of the trend logs may not be sent. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause The Xenta Server cannot send more than approx. 50-60 simultaneous emails before some are lost.  The limit appears to be dependent on the size of attached trend logs and the number of addresses in the Receiver Group list. Resolution For a single email address, split the trend logs into groups of no more than 40.  Link the logs in each group to a different time object and stagger the times at which they are sent.  If the Receiver Group definition contains multiple email addresses, reduce the number of trend logs in each group accordingly.

Issue Alarms cannot be created in a BACnet b3 controller because the fields are grayed out. Product Line Andover Continuum Environment Continuum Cyberstation b3 BACnet MS/TP controllers Cause Alarms are created differently in a BACnet controller than with an Infinet controller.  These fields are grayed out since they are not used for alarm creation in a BACnet controller. Resolution There are instructions in the BACnet section in the Continuum help for creating an event notification and then mapping the point and the event notification within an alarm enrolment. For an example see AlarmCreatingAndConfiguring BACnet.doc

Issue Satchwell "AMS" and "AMSH" series Spring Return Rotary Actuator requires replacement by S-E M700 Spring Return Linear Actuator due to obsolescence. Product Line Field Devices Environment Satchwell "AMS" series Spring Return Rotary Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Satchwell "AMSH" series Spring Return Rotary Actuator installed on Satchwell MZF or VZF series 125mm and 150mm Plug and Seat Valve Body. N.B. Where a Satchwell "AMS" series Spring Return Rotary Actuator is installed on a Satchwell VV Butterfly Valve Body then NO simple Actuator replacement is available. See Replacement of Satchwell V V series Butterfly Valve Body Cause Obsolescence of Satchwell AMS and AMSH series Spring Return Rotary Actuator. Resolution The new actuator is 24Vac and the control signal will need to be converted from 230Vac to 24Vac, this could be achieved by a transformer and 2 off 230Vac relays. The old signals switch the coils of the relays. The relay contacts switch 24Vac to the new actuator. Replace Satchwell AMS or AMSH series Spring Return Rotary Actuator with S-E M700 Spring Return Linear Actuator and Linkage Kit: AMS = M700 + L7SV (880-0126-000) Linkage Kit. N.B. M700 is available with two different spring return actions M700 - SRSU (880-0430-000) = Spring Return Spring Up          ( M700 - SRSU will CLOSE a Satchwell Valve.) M700 - SRSD (880-0440-000) = Spring Return Spring Down     ( M700 - SRSD will OPEN a Satchwell Valve.) Should the Satchwell AMS series Actuator include a wired Auxiliary Switch then the following S-E M700 Actuator specifications which include 2 independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches should be considered as appropriate: M700 - S2 - SRSU (880-0431-000) M700 - S2 - SRSD (880-0441-000) Alternatively Auxiliary Switch Pack S2 (880-0104-000) - Two independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches may be purchased separately permitting local installation. Particular care should be taken when selecting a TAC Forta M700 Spring Return Actuator to replace an existing Satchwell AMS Spring Return Actuator. Please refer to Replacement of Satchwell "AL..S" series Spring Return Linear Actuator. Please check the latest catalog for current equipment.

Issue No alarms are being displayed in the alarm queue. This includes alarms from any automation server that has been added underneath an enterprise server database or enterprise server alarms. Product Line EcoStruxure Building Operation Environment WorkStation Alarm Queue Cause This is a result of the alarm queue filter containing active filter conditions. Resolution Remove alarm filters: Click the Alarm Filter icon on the toolbar of the alarm queue. In the Select Conditions window, make sure that all of the alarm conditions have been removed or only the filters that you want remain. To remove an alarm condition, simply click the trashcan button on the far right side of the condition. Note: If a blank condition is left behind, it will prevent any alarm from being displayed in the alarm queue.

Issue What is the best practice for migrating controllers from a stand alone Continuum system into an active LAN system? Product Line Andover Continuum Environment Migrating Continuum Database Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Controllers must be migrated from a stand alone system into an existing Continuum LAN system. The ACCID of some or all of the controllers on the stand alone system are already in use on the LAN system. Resolution All address conflicts should be dealt with before the controllers are brought onto the LAN system. With the workstation in Offline mode, each controller on the Stand alone system is manually created on the LAN system.  If the controllers ACC ID will conflict with a controller on the LAN system an appropriate change must be made when creating the controller on the LAN database. Where the controllers are BACnet controllers and the intent is to have all controller on the same network, the Network ID (UDP) id must be changed to match the id of the LAN system. The Comm2 network ID of each stand alone controller should be noted and should be changed in cases where the id is already in use on the LAN system. Import files should be used to build the IP level controllers

Issue Alarm Control Panel items created within the Enterprise Server are not been pushed down to the Automation Server. Product Line EcoStruxure Building Operation Environment StruxureWare Buildings Operation 1.3 SP1 Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause There seems to be a corrupt entry in the Automation servers Resolution Log into each Automation server and remove the Lead object from the Alarm panel. Refresh the automation server and the categories are now editable. Delete all user created categories leaving the default Energy Exceptions. Delete all the Cause Notes, Action notes and Check lists. Do the same procedure on all Automation Servers. Log back into the Enterprise Server and then on each Automation server add the Lead object back into the Alarm Control Panel that was removed in step 1. The Enterprise Server will now distribute the entries to the Automation server. If this fails, ensure that all firewalls are open between the AS and the ES. You may want to use the SBO Firewall Config Tool.

Issue Need to download the XIF and NXE files for a SVEA Lon I/O Module DR-N-3D1M (0-10V) module, but having difficulty locating these files on the Extranet. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment SVEA XIF NXE Cause The difficulty in locating these files, is due to them being identified by their article number, in this case DR-N 3DIM. This number was used when these were classified as the SVEA devices. The Schneider version is now known as MTN881001, and not DR-N 3DIM. Resolution The Schneider Electric (MTN881001) files are located on The Exchange Download Center Download the XIF / NXE files for the SE MN881001 Download the XIF / NXE files for the SVEA DR-N 3DIM Note: It appears that although these devices are both classified as Lon I/O Module 1-10V, the XIF / NXE files are different.

Issue I/NET Seven elevator control configuration and setup. (Traditional versus Extended elevator control) Product Line TAC INET Environment I/NET Seven Extended elevator control: DPU Firmware 3.20 or above. (DPU7920 with 48K MIP or SCU1284) Cause There are two types of elevator control that you can implement within TAC I/NET: Traditional Elevator Control – Tradition elevator control allows each elevator to support up to 62 floors. This type of control has been used for as long as elevators have been supported within TAC I/NET. Extended Elevator Control – Extended elevator control does away with floor mapping and allows you to assign floors directly to tenants. Using this type of elevator control, each elevator can support up to 79 floors. Resolution Elevators The Elevator control function will work with the access control parameters and personnel schedules to control access to banks of elevators. Activating () the elevator option in the Door Extension editor will cause the DPU to process each reader transaction as though it were an entry into an elevator cab. Note: An elevator DPU will support only one door reader. Changing a Door from elevator to non-elevator, or vice versa will cause the DPU to purge its database. In addition to supplying the above parameters at the door (DPU) level, it will also be necessary to supply the DPI/MCI with the information required to associate an elevator cab with the discrete output points that enable the floor relays, and the discrete input points that monitor the button selection. There will be an elevator extension on each door point in the DPI/MCI that is assigned as an elevator. After adding the extension to the point, you must define the Elevator parameters such as floor selection time, floor designation description, button enable point, and button selection point. Elevator Control Schemes There are two types of elevator control that you can implement within I/NET Seven: Traditional Elevator Control – Tradition elevator control allows each elevator to support up to 62 floors. This type of control has been used for as long as elevators have been supported within I/NET. Extended Elevator Control – Extended elevator control does away with floor mapping and allows you to assign floors directly to tenants. Using this type of elevator control, each elevator can support up to 79 floors. You can use either type of control, or a combination of both, to implement elevators within your system. By allowing you to mix both types of control, I/NET gives you the ability to begin using extended elevator control without reconfiguring your traditional elevator control system. The following sections describe each elevator control type. Traditional Elevator Control Traditional elevator control allows each elevator to support up to 62 floors. To implement this type of control, you assign the elevator door point to one or more tenants. You then create floor maps that associate floors with personnel schedules (see “Defining Floor Maps”, below). After performing these tasks, any individual (or group) assigned to the elevator can gain access to the floors that are associated with their personnel schedule Assigning the Elevator to Tenants Traditional elevator control requires you to assign the elevator to one or more tenants. Until you perform this task, the Floors button in the Elevator editor will not be available (i.e., it remains grey). Defining Floor Maps Floor maps are only necessary when configuring your I/NET system for traditional elevator control. Floor maps determine which floors are enabled during each schedule that a tenant defines for the elevator. For example: Tenant 1 has a personnel schedule named “24 Hour” defined for the elevator. This schedule provides 24-hour access, seven days a week. The elevator’s floor map associates the floor enable points for floors 1 and 2 with Tenant 1’s “24 Hour” schedule. This allows Tenant 1 individuals using the “24 Hour” schedule to select floor 1 or floor 2 at any time. Use the Floors button in the Elevator editor to create floor maps as follows: Choose a tenant. Select a schedule from up to 31 personnel schedules defined for the elevator. Select an entry from up to seven access intervals defined for the schedule. Assign floor enable points to the schedule’s access interval. Floor enable points cause the elevator buttons for those floors to be enabled for selection by the key/card holder. Up to 62 floor enable points can be assigned to each access interval. Any floor enable points beyond 62 are unavailable when using traditional elevator control. These higher floor enable points are only available for use with extended elevator control, as described below. Note: Extended elevator control is only available with the 7920 48k DPU. Repeat these steps as necessary to create floor maps for each of up to 31 personnel schedules assigned to the elevator by a tenant. Extended Elevator Control I/NET Seven now offers an alternative to the traditional elevator control just described. Enhancements to the I/NET system support up to 79 floors per elevator. Instead of assigning the elevator door point to the tenant, you can implement extended elevator control by assigning floors to the tenant. The DI/DO pairs that you add to an elevator from the Elevator editor are listed in the Tenant editor, much like normal door points. Select the floors that you wish to assign to the tenant. Implementing Elevator Control Note: Extended elevator control is only available with the 7920 48k DPU. Adding an elevator extension to the door point provides access to elevator-related features and editors within I/NET and allows floors to be assigned. Each floor assigned to an elevator must have an associated DO and DI point. The DO point enables the elevator button for the specific floor. The DI point provides feedback indicating whether the floor button has been selected. Preliminary Requirements Before defining an elevator, you must do the following: Define a door point as an elevator in the Door Extensions editor. Use the Resident I/O Points editor to define a floor enable point (DO) and a floor selection point (DI) for each floor that will be assigned to an elevator. Use the Personnel Schedules editor to define up to 31 schedules for the selected elevator door point. Adding an Elevator Extension Use the following procedure to add an elevator extension: Select Edit Controller Elevators from the main menu. The system displays the Resident I/O Points Editor. This screen lists the available door (elevator) points. Choose a point that does not have a Y in the EL column and select the Add button. The system displays the Elevators window. Enter a Floor selection time (sec) (1 to 255). This is the amount of time in seconds that the key/card user has to make a selection from the floor buttons in the elevator cab. The default is 5. Select Add. The system displays the Elevators - Floor Parameters window. This window allows you to define the floor index attached to this elevator extension. Enter the Floor index number (1 to 62). This is the line number in the list. Enter the Floor designation (up to two characters). This identifies the floor. For example, the first level of a basement could be represented as B1. For each elevator floor extension assigned to a point in the DPI/MCI, there must be an associated DO and DI point attached to the elevator extension. This association of DO and DI points produces closed-loop feedback allowing the controller to identify an elevator floor selection with each successful key/card reader access. In the Button enable field to choose a point from the drop-down list of all possible discrete output points in the controller  In the Button selection field, choose a point from the list of all possible discrete input points in the controller. Select OK. The system returns to the Elevators window. How you proceed from this point will depend upon the type of elevator control you are implementing. Use the appropriate steps below: Traditional Elevator Control: From the Elevators window, select Floors. The system displays the Tenant Selection window. Choose a tenant from the list and select the Select button. The system displays the Elevators - Floor Schedules window. Choose a schedule from the list and select the Select button. The system displays the Elevators - Access Intervals window. Choose an access interval from the list and select the Select button. The system displays the Elevators - Floor Map editor. Choose the DO points which enable the floor selection buttons for the appropriate floors. Points marked with "[X]" will enable their respective floor selection button in the elevator cab. When you have finished choosing the appropriate DO points, select OK. The system returns to the Elevators - Access Intervals window. You may continue assigning floors to access intervals, or you may back out of the elevator functions by selecting Close at each window. Extended Elevator Control (See also article Extended Elevator control (Step by step instructions) ) From the Tenant Editor, assign floors (i.e., door enable points) to the tenant. Assign floors to individuals and/or groups as necessary.

Issue Values sent from a 102-AX via SNVT bindings are not making it to the receiving controller. Viewing the outbound SNVT on the 102-AX shows a value, but the inbound SNVT on another controller is invalid or a default value. Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX LNS SNVT bindings LonMaker NL220 Cause The Node Configuration parameters are set with a send heartbeat of 0 seconds, which tells the controller to never send an update on the output SNVT.  All 102-AXs come with a default send heartbeat of 0 seconds, so for them to function in an LNS network where they must send data to another controller, the send heartbeat must be set to something greater than 0 seconds. Resolution Open the Xenta 102-AX device Plug-in Go to the Node Configuration Tab Set the Node Minimum Send Time (SCPTminSendTime) to a non-zero value. The range is 0-6553.4 seconds. nvoSpaceTemp nvoStatOccBtn nvoSetPtOffset nvoLocalOccLatch nvoEmergCmd nvoUnitStatus nvoBoxFlow nvoTerminalLoad nvoEffectSetPt nvoFlowControlPt nvoOccpncyStatus Set the Node Send Heartbeat (SCPTmaxSendTime) to a non-zero value. The range is 0-6553.4 seconds. nvoAirFlow nvoAuxTemp1 nvoAuxTemp2 nvoUnvInput1 nvoUnvInput2 nvoUnvInput3 nvoUnvInput4 nvoCO2sensor nvoFanLoad nvoHeat1Load nvoHeat2Load nvoMotorPositn nvoActualValue nvoOAirFlowRatio nvoAirPressure It is typical to set the Node Minimum Send Time and the Node Send Heartbeat to 60 seconds and the Node Receive Heartbeat to 0 seconds.