Carrier SYSVU SystemVu Controller

सुरक्षितता विचार

• एअर कंडिशनिंग उपकरणांची स्थापना आणि सर्व्हिसिंग सिस्टम प्रेशर आणि इलेक्ट्रिकल घटकांमुळे धोकादायक असू शकते. केवळ प्रशिक्षित आणि पात्र सेवा कर्मचार्‍यांनी एअर कंडिशनिंग उपकरणे स्थापित, दुरुस्ती किंवा सेवा द्यावीत.
• अप्रशिक्षित कर्मचारी कॉइल आणि फिल्टर साफ करणे आणि फिल्टर बदलणे ही मूलभूत देखभाल कार्ये करू शकतात. इतर सर्व ऑपरेशन्स प्रशिक्षित सेवा कर्मचार्‍यांनी केली पाहिजेत. वातानुकूलित उपकरणांवर काम करताना, साहित्यात सावधगिरी बाळगा, tags आणि युनिटला जोडलेली लेबले आणि लागू होऊ शकणार्‍या इतर सुरक्षा खबरदारी.
• Follow all local building codes and appropriate national electrical codes (in the USA, ANSI/NFPA 70, National Electrical Code (NEC); in Canada, CSA C22.1) for special requirements. Wear safety glasses and work gloves. Use a quenching cloth for unbrazing operations. Have a fire extinguisher available for all brazing operations.
• It is important to recognise safety information. This is the safety-alert symbol.जेव्हा तुम्ही हे चिन्ह युनिटवर आणि सूचना किंवा मॅन्युअलमध्ये पाहता तेव्हा, वैयक्तिक इजा होण्याच्या संभाव्यतेबद्दल सावध रहा.
• DANGER, WARNING, CAUTION, आणि NOTE हे सिग्नल शब्द समजून घ्या. हे शब्द सुरक्षा-सूचना चिन्हासह वापरले जातात. DANGER सर्वात गंभीर धोके ओळखतो ज्यामुळे गंभीर वैयक्तिक इजा किंवा मृत्यू होतो. चेतावणी हे धोके दर्शवते ज्यामुळे वैयक्तिक इजा किंवा मृत्यू होऊ शकतो. सावधगिरीचा वापर असुरक्षित पद्धती ओळखण्यासाठी केला जातो, ज्यामुळे किरकोळ वैयक्तिक इजा किंवा उत्पादन आणि मालमत्तेचे नुकसान होऊ शकते. सूचना हायलाइट करण्यासाठी NOTE चा वापर केला जातो ज्यामुळे वर्धित स्थापना, विश्वासार्हता किंवा ऑपरेशन होईल.

धोका

इलेक्ट्रिकल शॉक धोका

• या चेतावणीचे पालन करण्यात अयशस्वी झाल्यास वैयक्तिक इजा किंवा मृत्यू होईल.
• युनिटवर सेवा किंवा देखभाल ऑपरेशन्स करण्यापूर्वी, युनिटचा मुख्य पॉवर स्विच बंद करा आणि लॉक आणि लॉकआउट स्थापित करा. tag(s). छतावरील युनिटला विद्युत सेवा खंडाशी सहमत असल्याची खात्री कराtage आणि ampयुनिट रेटिंग प्लेटवर सूचीबद्ध erage. युनिटमध्ये एकापेक्षा जास्त पॉवर स्विच असू शकतात.

खबरदारी

• युनिटच्या नुकसानीचा धोका
• This unit uses a microprocessor-based electronic control system. Do not use jumpers or other tools to short out components or to bypass or otherwise depart from recommended procedures. Any
• Shorting to ground of the control board or accompanying wiring may destroy the electronic modules or electrical components.

चेतावणी

• युनिट ऑपरेशन आणि सुरक्षितता धोका
• या चेतावणीचे पालन करण्यात अयशस्वी झाल्यास वैयक्तिक इजा, मृत्यू आणि/किंवा उपकरणांचे नुकसान होऊ शकते.
• R-454B is an A2L refrigerant. All service equipment or components must be A2L refrigerant rated. Do not use non-A2L-rated equipment or components on R-454B refrigerant equipment.

चेतावणी 

• मालमत्ता किंवा वैयक्तिक इजा होण्याचा धोका
• Risk of fire. Flammable refrigerant is used.
• To be installed and/or repaired only by trained service personnel. Do not puncture refrigerant tubing.
• Auxiliary devices which may be ignition sources shall not be installed in the ductwork, other than the auxiliary devices listed for use with the specific appliance. See instructions.
• फेडरल किंवा स्थानिक नियमांनुसार रेफ्रिजरंटची योग्य प्रकारे विल्हेवाट लावा.

चेतावणी

• वैयक्तिक इजा आणि पर्यावरणीय धोका
• या चेतावणीचे पालन करण्यात अयशस्वी झाल्यास वैयक्तिक इजा किंवा मृत्यू होऊ शकतो.
• सिस्टम दुरुस्ती किंवा अंतिम युनिट विल्हेवाट लावण्यापूर्वी दबाव कमी करा आणि सर्व रेफ्रिजरंट पुनर्प्राप्त करा.
• रेफ्रिजरंट हाताळताना सुरक्षा चष्मा आणि हातमोजे घाला. टॉर्च आणि इतर प्रज्वलन स्त्रोतांना रेफ्रिजरंट्स आणि तेलांपासून दूर ठेवा.

चेतावणी

आग किंवा स्फोट होण्याचा धोका

• या नियमावलीतील माहितीचे अचूक पालन न केल्यास, आग किंवा स्फोट होऊन मालमत्तेचे नुकसान, वैयक्तिक इजा किंवा जीवितहानी होऊ शकते.
• या किंवा इतर कोणत्याही उपकरणाच्या परिसरात गॅसोलीन किंवा इतर ज्वलनशील बाष्प आणि द्रव साठवू नका किंवा वापरू नका.

तुम्हाला गॅसचा वास येत असल्यास काय करावे

• कोणतेही उपकरण पेटवण्याचा प्रयत्न करू नका.
•  कोणत्याही विद्युत स्विचला स्पर्श करू नका; तुमच्या इमारतीत कोणताही फोन वापरू नका.
• इमारत ताबडतोब सोडा.
• शेजाऱ्याच्या फोनवरून तुमच्या गॅस पुरवठादाराला ताबडतोब कॉल करा. गॅस पुरवठादाराच्या सूचनांचे अनुसरण करा.
• तुम्ही तुमच्या गॅस पुरवठादारापर्यंत पोहोचू शकत नसल्यास, अग्निशमन विभागाला कॉल करा.

उद्देश

• The Purpose of this document is to give a general overview of the SystemVu controller (see Fig. 1) and to provide guidance for integration with various other devices and systems. The focus in this
• document will be on networking practices with BACnet®1 and Rnet. For CCN practices follow the Carrier Comfort Network® guide.

What is a SystemVu Controller

• SystemVu is a factory-installed integrated HVAC unit controller utilised in a variety of Carrier Light Commercial products.
• The SystemVu controller is fully communicating and cable-ready for connection to Carrier Comfort Network (CCN) or BACnet MS/TP building systems. The SystemVu controller can also communicate with Rnet Sensors, Equipment Touch™ devices, and System Touch™ devices.

1. तृतीय-पक्ष ट्रेडमार्क आणि लोगो त्यांच्या संबंधित मालकांची मालमत्ता आहेत.

Protocols Supported by SystemVu
The SystemVu controller supports the following Building Automation System (BAS) protocols.

• CCN (Carrier’s Comfort Network)
• BACnet over MS/TP

Please note that the default BAS Protocol setting (BMS_CFG) for SystemVu is configured as “None”.

PROTOCOL CONFIGURATION

• Set the Communication protocol using UI (user interface) as shown in Fig. 2.
• Configuring SystemVu BAS Protocol to CCN
• For Configuring the SystemVu Communication Protocol to CCN (Carrier Comfort Network®), navigate to “Network Settings” in the User Interface using Menu/Settings/Network Settings/BAS
• PROTOCOL. Controller will prompt for “ENTER PASS-WORD”, Type in “1111” as password and select “1 – CCN” as shown in Fig. 2.

Configuring SystemVu to BACnet

• For Configuring the SystemVu Communication Protocol to ‘BACnet’, navigate to “Network Settings” in UI using Menu/Settings/Network Settings/BAS PROTOCOL and select BACNET. Controller will
• Prompt for “ENTER PASSWORD”, Type in “1111” as the password.

SystemVu BACnet Configuration Settings

SystemVu supports the following Baud rates for BACnet MS/TP.

• 9600
•  19200
•  8400
• 57600
• 76800
•  115200

टीप: 115,200 baud rate can only be used with certain devices, such as the iVu® XT-RB router. It can NOT be used on the same MS/TP network with devices such as RTU Open controllers as they do not support this baud rate.
For configuring the Baud Rate and MAC Address, navigate to BAS Settings in User Interface using Menu/Settings/Network Settings/BACNET. See Fig. 3.

टीप: You must cycle power after changing any Network Settings. SystemVu can be connected to the following devices

• All i-Vu BACnet MS/TP routers
• All current i-Vu CCN devices
• Third-party BACnet MS/TP routers
• System Touch over MS/TP
• Equipment Touch over Rnet
•  Carrier Rnet Zone Sensors

टीप: SystemVu is a BACnet MS/TP master controller. Valid MAC addresses for master nodes are 0 – 127.

टीप: If SystemVu cannot be communicated with over BACnet, then ensure that the protocol has been correctly set and the controller has been power cycled if the protocol settings were changed.

INTEGRATION OVER BACNET MS/TP

• In general, all wiring and installation techniques should follow the Open Controller Network Wiring Guide, Catalogue No. 11-808-461-01, instructions. However, please note the following details and exceptions that MUST be observed on networks containing SystemVu controllers.

Communication Cable and Wire

• The communication cable and wire used in networking can greatly impact the performance of the network communication over that wire. Follow the details shown in Table 1 as best practice with wiring on MS/TP BACnet networks.

तक्ता 1 — BACnet MS/TP वायरिंग तपशील

टीप(एस)

•  तृतीय-पक्ष ट्रेडमार्क आणि लोगो त्यांच्या संबंधित मालकांची मालमत्ता आहेत.

TO WIRE THE COMMUNICATION CABLE

1.  Partially cut, then bend and pull off 1 in. of the outer jacket of the cable(s). Do not nick the inner insulation. See Fig. 4.
2. Strip about 0.25 in. (0.6 cm) of the inner insulation from each wire. See Fig. 4.
3. If wiring two cables to the controller, twist together the shield wires from both cables.
4. Insert the wires into the appropriate terminal block (see Figs 7 and 8 on page 6). Take care that the drain wire is electrically isolated, where exposed.
5.  All connections should be made with power turned off to all the network devices and SystemVu controllers.

खबरदारी
POSSIBLE COMMUNICATIONS FAILURE

• Do not allow more than 0.125 inch (0.3 cm) bare communication wire to protrude. See Fig. 5.
• If bare communication wire contacts the cable’s foil shield, shield wire, or a metal surface other than the terminal block, communications may fail.
• Best practice is to tape wires up to the BAS plug to prevent contact with any metal. See Fig. 6.

टीप: Do not ground the shield to earth ground or to the controller’s power ground. The PROT485 and the individual controllers allow the shield to float a limited amount so that there are no ground loops. If the voltage on the shield becomes too great, relative to the earth ground, then the excess voltage is bled off with protective devices on the PROT485 or on the controllers.

नेटवर्क डिझाइन

With a locally biased controllers, per RS-485 standards, the maximum recommended number of nodes per segment/trunk depends on the baud rate of the network.

• 38,400 baud = maximum of 15 nodes and a router
• 76,800 baud = maximum of 31 nodes and a router

Please note that the SystemVu controller is a LOCALLY biased device as opposed to the OPEN product line, which are NETWORK biased device.

• Therefore, the BT485 device is NOT used in a SystemVu-only network, and  NOT used in a network composed of SystemVu and OPEN products together.
• In addition, the end-of-line / end-of-net switches on OPEN products and routers are NOT used with SystemVu controllers on the bus. Since these switches may also add network biasing, they are not  needed with a locally biased product. There are no end-of-line switches on SystemVu products.
• NOTE: Note: A 120 Ohm Resistor MUST be used to terminate the bus at both ends in accordance with standard RS-485 requirements. The TERM485 device is recommended.
• With careful wiring practices, one network segment can use up to 4,000 feet of network wire. However, the best results are achieved when the total wire length on a trunk is limited to 2000 feet.
• In addition, the use of a repeater (the REP485 is the only currently allowed repeater) for network segments over 2000 feet of wire is encouraged, but not mandatory. Please refer to the Open Controller
• Network Wiring Guide for detailed REP485 installation instructions. Note that the REP485 counts as a node on both network segments it connects.
• The use of the PROT485 device is highly recommended for all network segments with SystemVu controllers. Please refer to the Open Controller Network Wiring Guide for detailed PROT485 installation instructions.
• Finally, please note that rigorous adherence to the wiring hygiene recommendations here and in the Open Controller Network Wir-ing Guide will produce the best network results.
• SystemVu controllers should have the BAS wiring connected to plus, minus, and the shield wire to COM as shown in Fig. 7 and 8.

नेटवर्क टोपोलॉजी

• All BACnet MS/TP networks should be wired in a true “daisy-chain” configuration.
• BACnet MS/TP network best practices dictate that the MAC ad-dressing of the nodes on the network should be sequential with the physical location of the units. For example, if the router is the first node on the network, it should have the lowest MAC address. The next unit on the daisy-chain should have a MAC address one number higher, etc.

ग्राउंडिंग आणि पोलॅरिटी

• A quality earth ground is essential to ensure proper unit operation AND proper BAS communication function.
• There is not one standard ground resistance threshold that is recognised by all agencies.
• However, the NFPA (National Fire Protection Association) and IEEE have recommended a ground resistance value of 5.0 ohms or less. The NEC has stated: “Make sure that system impedance to
• ground is less than 25 ohms specified in NEC 250.56.” In facilities with sensitive equipment, it should be 5.0 ohms or less. The telecommunications industry has often used 5.0 ohms or less as its value for grounding and bonding.
• If you suspect you may have grounding issues at a facility, specialised earth grounding testers are used by qualified electrical contractors to test for correct grounding.
• In addition, control power polarity should be maintained throughout the BAS network AND communication wiring polarity should be maintained as well. Per the recommendations in the Open Controller Network Wiring Guide regarding the PROT485, shield wires should NOT be grounded to any earth ground or to the controller’s power ground. The PROT485 and the individual control-lers allow the shield to float a limited amount so that there are no ground loops. If the voltage on the shield becomes too great relative to the earth ground, then the excess voltage is bled off with protective devices on the PROT485 or on the controllers.

Packet Segmentation

• The BACnet stack used with the SystemVu product does NOT currently support packet segmentation.
• Segmentation should be turned OFF on the third-party devices.
• Please be aware that the segmentation feature is NOT required for the current BTL (BACnet Testing Laboratories) certification.

i-Vu Integration Tips – Source Files and Version Variations

• The current SystemVu products are compatible with i-Vu versions 7.0 and later. Older versions of i-Vu software may not work cor-rectly with current SystemVu products.
• All current i-Vu patches must be installed when connecting to SystemVu products. These may be obtained from the “Controls Download” section of HVACPartners or from the Carrier Controls website software section.
• It is often necessary to manually add the SystemVu source files to the i-Vu server and place them into the appropriate folder.
• Please note that the source files are located on HVACPartners (Currently located under the SUPPORT TAB > POST SALE SUPPORT > SERVICE SOFTWARE).

COV (Change of Value) and Third-Party Routers

• The COV feature in BACnet MS/TP is used extensively by some third-party vendors.
• However, SystemVu only supports a limited number of COV points. Router requests for COV points that are not supported by the SystemVu controller can lead to network errors and poor network performance.
• Turning the COV function OFF in the third-party devices can be a helpful tool when troubleshooting network traffic issues.
• Certain job sites or customers may require that the COV feature be used.
• If this is the case, Table 2 shows the exact COV points supported by the SystemVu controller.

Table 2 — SystemVu Objects Supporting COV-Guide

वर्णन	BACNET OBJECT NAME	BACNET TYPE	BACNETINSTANCE NUMBER	BACNET DESCRIPTION
Linkage equipment mode reported to the zones.	lnk_mode	एव्ही:	261	Linkage Equipment Mode
A discrete hardware input that when configured for use can beused as part of the logic that determines the occupied or unoccupied state of the control.	remocc	BV:	29	RemoteOccupancy Switch
Indoor Air Quality that has been resolved from all of the possible indoor air quality sources available in the system.	iaq	एव्ही:	1009	Indoor Air Quality Level
Indoor air quality that is received over the network.	iaq_net	एव्ही:	7001	Network IAQ Value
Outdoor Air Quality (OAQ) Level (sensor).	oaq	एव्ही:	1012	OA Quality Level
Network Outdoor Air Quality (OAQ) Level Sensor.	oaq_net	एव्ही:	7002	Network OAQ Value
Outside Air Relative Humidity that has been resolved from all of the possible outdoor air humidity sources available in the system.	ओअर	एव्ही:	1022	OA सापेक्ष आर्द्रता
Outdoor air relative humidity network sensor.	oarh_net	एव्ही:	7003	Network OARH Value
Outside Air Temperature that has been resolved from all of the possible outdoor air temperature sources available in the system.	oa_temp	एव्ही:	1003	बाह्य हवेचे तापमान
Outdoor air temperature from the BMS network.	oat_net	एव्ही:	7007	Network OAT Value
Outdoor Air CFM that is received over the network.	ocfm_net	एव्ही:	371	Network OACFM Value
Outdoor fan: High temperature override.	odfhtovr	एव्ही:	9066	ODF Override Temperature
Return Air Relative Humidity is the result of the engineering conversion performed on the sensor in the return air ductwork.	rarh	एव्ही:	30	RA सापेक्ष आर्द्रता
Relative Air Relative Humidity (RARH) Sensor read in from the network sensor.	rarh_net	एव्ही:	7004	Network RARH Value
Return Air Temperature that has been resolved from all of the possible return air temperature sources available in the system.	ra_temp	एव्ही:	1010	हवेचे तापमान परत करा
Return air temperature from the network.	rat_net	एव्ही:	7005	Network Return Air Temp
Supply Air Temperature that has been resolved from all of the possible supply air temperature sources available in the system. This represents the temperature of the air being output from the packaged unit.	sa_temp	एव्ही:	1008	पुरवठा हवा तापमान
Space Relative Humidity (SPRH) Sensor read in from the network sensor.	sprh_net	एव्ही:	376	Network SPRH Value
Space Temperature is a legacy point that has typically been used for writing space temperature values over a CCN network.	space_temp	एव्ही:	2007	Pilot Space Temp Value
Space Temperature is the reading from the network.	spt_net	एव्ही:	7006	Network Space Temp Value
System Touch Space Temperature reading from the network.	stst_net	एव्ही:	8023	System Touch Temp Value

Table 3 — Abbreviated Example of Point List

POINT DESCRIPTION	POINT ACESS	युनिट्स	BACnet ऑब्जेक्टचे नाव	BACnet आयडी	मूल्य श्रेणी	CNN POINT EQUIVALENT
BACnet device for IAQ	R/W		devlag	AV:8001	८०० ते ८९९	DEAVIAQ
BACnet device for OAQ	R/W		devoaq	AV:8002	८०० ते ८९९	DEVOAQ
BACnet device for OARH	R/W		devoarh	AV:8004	८०० ते ८९९	DEVOARH
BACnet device for OAT	R/W		devoat	AV:8003	८०० ते ८९९	DEVOAT
BACnet device for RARH	R/W		devrarh	AV:8005	८०० ते ८९९	DEVRARH
BACnet device for RAT	R/W		devrat	AV:8006	८०० ते ८९९	DEVRAT
BACnet device for SPRH	R/W		devsprh	AV:8028	८०० ते ८९९	DEVSPRH
BACnet device for SPT	R/W		devspt	AV:8007	८०० ते ८९९	DEVSPT

APDU Timing, Polling Rates, etc. with Third-Party Routers

• It is not uncommon to need to adjust a number of router settings that vary significantly from job to job.
• Unfortunately, there are not “set in stone” values that work on every job.
• Please be aware that some of these values include APDU timeout rates, polling rates, and NPDU timeout rates.
• In general, longer polling rates for BACnet objects are to be preferred (polling too frequently increases bus traffic). Polling/refresh rates should not be set below every 30 seconds. It is best to keep the polling/refresh rates between 1 and 5 minutes. In general, the recommendations in Othe APN022 application tip regarding read and write rates should be observed.
• It is a best practice to set timeout rates, such as APDU timeout rates at the highest timeout rate of any device on the network. Many devices default at 3000 milliseconds. SystemVu is defaulted to 6000ms and cannot be changed. When applying SystemVu controls on a BACnet bus with other devices, all devices should be set to match SystemVu at 6000ms. The SystemVu APDU segment length is fixed at 480 bytes. Since the BACnet stack used for SystemVu controllers does NOT support packet segmentation, some third-party routers may need to have the  APDU segment size or RPM “chunking” or “bin packing” algorithms mare manually adjusted to properly work with features such as Read Property Multiples.

Frame Rates and Third-Party Routers

• Many third-party vendors default their router “MS/TP Max Info Frames” value to “100”. This is too high for SystemVu nodes – a value of “20” will provide a more stable network.
• All legacy production SystemVu software versions have the “Max Info Frames” value default to “10”. Older versions defaulted to “1” which can cause network issues. If a network with an older SystemVu
• units is experiencing issues; upgrading to current production software is recommended.
• The current A2L production units have adjustable frame rates and max master values.

SYSTEMVU INTEGRATION WITH SYSTEM TOUCH OVER MS/TP PORT

What is System Touch

• The System Touch is a touchscreen device with a color LCD dis-play that provides as a user interface to controllers on a single BACnet network. The System Touch has built-in temperature and humidity sensors. These values can be read by controllers to con-trol equipment. You can also wire an external thermistor to the System Touch and use its value instead of the built-in temperatur e sensor’s value.

For more details about the System Touch, refer the below docu-ments available on HVACPartners or the Carrier Controls Webसाइट

• System Touch Installation and Setup Guide
• सिस्टम टच वापरकर्ता मार्गदर्शक
• System Touch Product data sheet.

Steps to Connect SystemVu and System Touch over MS/TP Port

NOTE: You must configure the SystemVu Communication Protocol to ‘BACnet’ for proper System Touch interface with the SystemVu controller and System Touch device.

1. Update the SystemVu to the latest firmware.
2. Enable BACnet in the BAS Protocol (Menu > Settings > Network Settings).
3. Connect System Touch to SystemVu over MS/TP as shown in Fig. 9.
4. Once the connection is established, click on ‘Setup’ of System Touch from the home screen.
5. Enter the password (the default password is ‘admin’)
6. Click on the “Discovery”. Verify System Touch tries to communicate with SystemVu and displays the SystemVu controller.
7. For more details about the System Touch, refer to the documents mentioned above.

Using System Touch’s Temperature and Humidity Sensors

The System Touch’s Temperature sensor and Humidity Sensor can be requested by the SystemVu controller. For requesting these values from System Touch, we need to configure as below.

1. Connect the System Touch and the SystemVu Board as described above.
2. On System Touch, navigate to Setup > Touchscreen Setup > Sensor Setup.
3. Select “Internal” and “Deg F” as shown in Fig. 10.
4. Using UI on the SystemVu board, navigate to SETTINGS > NETWORK SETTINGS > BACNET > SYSTEM TOUCH.
5. Set DEVICE INSTANCE to System Touch Device Instance.
6. Set POLLING Rate (System Touch Poll Rate) to at least 10. NOTE: The default is 0 to prevent scanning.
7. Set SPACE TEMP AI = 1.
8. Set SPACE RH AI = 4.
9. With these settings, SystemVu Board will poll the Space Temperature and Humidity Sensor values from System Touch.
10.  For more information about the default value and the configuration values, refer to “APPENDIX A” in the Controls and user manual document for the SystemVu unit you are using.

SYSTEMVU INTEGRATION WITH EQUIPMENT TOUCH OVER RNET

What is Equipment Touch

• The Equipment Touch is a touchscreen device with a colour LCD display that you connect to the SystemVu controller to view किंवा त्याची मालमत्ता मूल्ये, वेळापत्रक उपकरणे बदला, view trends and alarms, and more, without having to access the i-Vu server.

For more details about the Equipment Touch, refer to the documents below available on HVACPartners or the Carrier Controls Webसाइट

• Equipment Touch User Guide
•  Equipment Touch Installation and Setup Guide
•  i-Vu Equipment Touch Product Data Sheet

Steps to Connect SystemVu and Equipment Touch over Rnet Port

टीप: You must configure the SystemVu Communication Protocol to ‘BACnet’ for proper Equipment Touch interface with th e SystemVu controller and Equipment Touch device.

1.  Update the SystemVu to latest firmware.
2. Enable BACnet in the BAS Protocol (Menu > Settings > Network Settings).
3.  Connect the Equipment Touch to SystemVu over Rnet as shown in Fig. 11.
4.  Once the connection is established, Equipment Touch will start uploading the touch file from the SystemVu device, as shown in Fig. 12.
5. After successful upload, Equipment Touch displays the following screen (Fig. 13).
6. For more details about the Equipment Touch, see the Equipment Touch Installation and Setup Guide.

Using Equipment Touch Temperature and Humidity Sensors

The Equipment Touch Temperature and Humidity sensors can be used by the SystemVu controller. For requesting these values from Equipment Touch, we need to configure as below.

1.  Connect Equipment Touch and SystemVu Board as described above.
2. On Equipment Touch, navigate to Setup > Touchscreen Setup > Sensor Setup.
3. Select the check box ‘Enable Transmit’ for both ‘Tempera-ture Sensor’ and ‘Humidity Sensor’ (see Fig. 14).
4. With these settings, Equipment Touch will transmit the Temperature Sensor and Humidity Sensor Values to SystemVu.

FIRMWARE UPGRADE PROCESS FOR EQUIPMENT TOUCH/SYSTEM TOUCH

फर्मवेअर अपडेट टप्पे

1. Create a folder on the flash drive called “touch”, then put the ETxxxxx.hex or STxxxxx.hex file फोल्डरमध्ये.
2.  Plug the flash drive into the Equipment/System Touch’s USB port.
3.  From the System Screen, touch Setup > Touchscreen Setup > Reload Firmware.
4. एक चेतावणी संदेश दिसेल. सुरू ठेवण्यासाठी होय ला स्पर्श करा.
5.  The following series of messages appears:
   •  Verifying Firmware Image.
   • Reading Firmware image from USB.
   • Installing Application.
   •  Verifying Firmware Image.
6. Aftera  successful firmware update, remove the flash drive.

SYSTEMVU INTEGRATION WITH ZS SENSOR OVER RNET

ZS सेन्सर्स

• ZS Sensors are thermistor-based temperature sensors that can op-tionally sense humidity, motion, and either CO2 or VOC. ZS Sen-sors communicate with the HVAC system through the Rnet.

ZS Sensor functionality is determined by:

• The sensor models
•  The sensor’s sensing capabilities (temperature, humidity, motion, CO2, VOC)
• The control program that runs the associated equipment’

ZS Sensors are wired to the Rnet port on SystemVu controllers. For more information about Zone Sensor, refer to the documents available on HVACPartners or the Carrier Controls Webसाइट

•  ZS Sensors User Guide
•  ZS Sensors Installation Guide

Steps to Connect SystemVu and ZS Sensor Over Rnet Port

• Each ZS Sensor connected via the Rnet port must have a unique address, but addresses do not have to be sequential.
• Open the hinged cover on the sensor enclosure, and then use the DIP switches to set an address from 0 to 14. (1 is factory default.) Each DIP switch has the value shown in Figure 15 below. Turn on as many DIP switches as you need so that their total value equals the address.

EXAMPलेः DIP switches 1 and 4 below are on. Their values (1 + 8) total 9, so the sensor’s address is 9.

1. . Connect the SystemVu Controller and Zone Sensor over the Rnet Port as shown in Fig. 16-17.
2.  On SystemVu User Interface, navigate to SETTINGS / NET-WORK SETTINGS / ZS SENSOR CFG and set the ZS Sen-sor address (see Fig. 18).
3. SystemVu supports up to 5 Zone Sensors which can be connected over Rnet Port (see Fig. 19).
4.  Please note that there is a 500mA VA limit for the Rnet plug. Check the total VA consumption of the sensors prior to connecting them to the SystemVu board.

SystemVu RNET Connector

BOARD ACTIVITY INDICATORS

लाल स्थिती एलईडी
Proper Operation of the SystemVu Board can be visually checked by looking at the red status LED (see Fig. 20).

Table 4 provides information on Status LED.

Red Status LED Condition	Board Software Status
बंद सतत	The board is unpowered or the power supply is defective
फ्लॅशिंग ON 200 ms, OFF 200 ms	Board is in Bootloader mode
फ्लॅशिंग ON 1000 ms, बंद 1000 ms	The boot loader is not running, application software is running
ON सतत or FLASHING at कोणतेही other frequency	The board or software is defective

ग्रीन स्टेटस एलईडी

• The SystemVu controller has one Green LED. This LED (indicates Local Equipment Network) should always be blinking whenever power is ON. If LENLED is not blinking, check LEN connection for
• potential communication errors (MBB J15, J16, J17, and J2 on the Display).
• Yellow Status LED
• Yellow LED is used to indicate Building Automated Systems (BAS) communication activity. The LED will blink when the MBB transmits a message on the BACnet bus.

TROUBLESHOOTING BACNET MS/TP

BACnet MS/TP Configurations

• SystemVu can use the BACnet MS/TP protocol for communications. This section in the document contains Carrier’s recommendations for configuring and wiring an MS/TP network that will provide the best network performance with Carrier controllers. However, Carrier controllers will work on any BACnet-compliant MS/TP network. Controllers can communicate on an MS/TP network at 9600  bps, 19.2 kbps, 38.4 kbps, 57.6 kbps, 76.8 kbps, or 115.2 kbps.
• For configuring SystemVu BACnet Baud Rate, navigate to the menu below in the user interface and select the Baud Rate. UI Menu > SETTINGS / NETWORK SETTINGS / BACNET
• Please note that source files are needed for proper detection of SystemVu units by an i-Vu system. Source files are included in cumulative patches, OR can be manually imported into i-Vu. Source files  and the process for importing them are located on HVACPartners.

i-Vu MODSTAT

• For additional debugging on iVu systems, use the MODSTA T command in i-Vu which, when requested, will trigger the System Software Information along with BACnet Firmware version as shown in the images below.

1. Select the Controller listed under Router (see Fig. 21).
2. Right click and select the MODSTAT (Module Status) command. (see Fig. 22). A new Pop up window will come with the list of Controller Software and BACnet firmware versions as shown in Fig. 23.

Controller Addressing

• Each SystemVu controller on the MS/TP network must have a unique BACnet MS/TP MAC address, which is set by the User In-terface Menu. Valid addresses are 1-99.
• BACnet MS/TP network best practices dictate that the MAC ad-dressing of the nodes on the network should be sequential with th e physical location of the units. I.E. If the router is the first node on the
• network, it should have the lowest MAC address. The next unit on the daisy-chain should have a MAC address one number higher, etc.

समस्यानिवारण मार्गदर्शक तत्त्वे

• If a SystemVu controller is not detected over MS/TP network, verify all the configuration settings like Baud Rate, MAC address and BAS Protocol settings. On i-Vu networks, make sure the source files
• have been manually imported.
• NOTE: Use the same polarity throughout the network. Also, use a 120-ohm resistor at each end of the network.
• Network troubleshooting needs to be deliberate and sequential. In the event of rolling communication failures or no communications at all, the best approach is to start with the physical layer, then
• progress to the network layer, and finally the application layer.

भौतिक स्तर

• The use of an oscilloscope as described in the Open Controller Network Wiring guide is always the first step. If your wave-forms are not clean, packet collisions will occur, which will cause losses of communication. Waveforms should look similar to the one shown in Fig. 24, NOT like the distorted (noisy ) waveform shown in Fig. 25.

• A number of factors can cause waveform distortions on the physical layer. Poor wiring hygiene, damaged wire segments, damaged RS-485 transceiver circuits on individual boards, and electrical interference from “noisy” environments are just a few of the issues that can all contribute to physical layer distortions. Isolating portions of the network segment by splitting the communication bus in half repeatedly, while tedious, is the best technique to isolate physical layer defects.
• Please note that collisions caused by incorrect network software settings can also lead to distorted waveforms. While not as common as physical layer defects, this should be taken into consideration – see section addressing the network layer.
• Verify the proper wire is being used and is connected properly at each device and the router. Termination resistors must be at the beginning and end of each bus segment. Ensure network bias resistors are not used since SystemVu is already locally biased. These items are the most common issues found during troubleshooting.

NETWORK LAYER

• Once any physical layer issues are resolved, the next step is to analyse the network layer. The use of network bus traffic monitoring tools is very valuable when trying to isolate network problems. There are a number of tools available, such as Wireshark®1, which allows the diagnosis of issues such as COV over polling, APDU timing, duplicate MAC addresses, etc.
• The most common network layer issues are with APDU timeout, BACnet point writes, COV increments, and segmentation settings. SystemVu products are hard-set to a 6000ms APDU timeout; all devices on the same bus should be set to 6000ms for best results. COV should be disabled unless clearly being used. If COV is being used, ensure the refresh increments are set so that COV requests do not occur too frequently. The goal should be for COV requests to occur no more often than every 60 seconds. Ensure BACnet writes/refresh or broadcast rates are reasonable and not occurring too frequently. Usually, point writes should not be greater than once per minute. Lastly, ensure packet segmentation is disabled on the network bus.

APPLICATION LAYER

• Depending on the router being used, once the physical layer and network layer issues have been resolved, a detailed study of the alarms and alerts present on the router can reveal timing, source file, and software issues. It is best practice for all routers and devices on the network to have updated firmware patches and cumulative patches as applicable.

NETWORK POINT LIST FOR BACNET

• SystemVu BACnet Points List
• The BACnet point list may vary from product to product and software version to software version of SystemVu. For the specific list of supported BACnet Points, refer to “APPENDIX E – BACNET
• POINTS LIST” in the Controls document for the SystemVu product you are using

SystemVu Alarm List

• The alarms list may vary from product to product and software version to software version of SystemVu. For the list of alarms supported, refer to the Controls document for the SystemVu product you are using.

वारंवार विचारले जाणारे प्रश्न

Can untrained personnel perform maintenance on the SystemVu controller?

Untrained personnel can perform basic maintenance tasks such as cleaning coils and filters, but all other operations should be handled by qualified service personnel.

कागदपत्रे / संसाधने

Carrier SYSVU SystemVu Controller [pdf] वापरकर्ता मार्गदर्शक SYSVU-001-SUPP, SYSVU SystemVu Controller, SYSVU, SystemVu Controller, Controller

संदर्भ

• वापरकर्ता मॅन्युअल