Kontwolè SystemVu Carrier SYSVU

KONSIDERAsyon SEKIRITE

• Enstalasyon ak sèvis ekipman èkondisyone ka danjere akòz presyon sistèm ak konpozan elektrik. Se sèlman pèsonèl sèvis ki antrene ak kalifye ki ta dwe enstale, repare oswa fè sèvis pou ekipman èkondisyone.
• Pèsonèl ki pa antrene ka fè fonksyon antretyen debaz nan netwaye bobin ak filtè epi ranplase filtè yo. Tout lòt operasyon yo ta dwe fèt pa pèsonèl sèvis ki resevwa fòmasyon. Lè w ap travay sou ekipman èkondisyone, obsève prekosyon nan literati a, tags ak etikèt ki tache sou inite a, ak lòt prekosyon sekirite ki ka aplike.
• 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.Lè ou wè senbòl sa a sou inite a ak nan enstriksyon oswa manyèl yo, se pou w vijilan ak posiblite pou blesi pèsonèl.
• Konprann mo siyal DANGER, AVÈTISMAN, ATANSYON, ak REMAK. Yo itilize mo sa yo ak senbòl alèt sekirite a. DANGER idantifye danje ki pi grav ki pral lakòz blesi pèsonèl grav oswa lanmò. AVÈTISMAN vle di danje ki ka lakòz blesi pèsonèl oswa lanmò. ATANSYON yo itilize pou idantifye pratik ki pa an sekirite, ki ka lakòz blesi pèsonèl minè oswa domaj pwodwi ak pwopriyete. REMAK yo itilize pou mete aksan sou sijesyon ki pral lakòz enstalasyon, fyab, oswa operasyon amelyore.

DANJE

DANJE CHÒK ELEKTRIK

• Si w pa suiv avètisman sa a, sa pral lakòz blesi pèsonèl oswa lanmò.
• Anvan ou fè operasyon sèvis oswa antretyen sou inite a, fèmen switch prensipal la nan inite a epi enstale fèmen (yo) ak bloke. tag(s). Asire sèvis elektrik nan inite twati a dakò ak voltage ak ampepòk ki nan lis sou plak evalyasyon inite a. Inite a ka gen plis pase yon switch pouvwa.

ATANSYON

• DANJE DEGAJ INITE
• 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.

AVÈTISMAN

• OPERASYON INITE AK DANJE SEKIRITE
• Si w pa suiv avètisman sa a ka lakòz blesi pèsonèl, lanmò ak/oswa domaj ekipman.
• 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.

AVÈTISMAN 

• DANJE PWOPRIYETE OUBYEN BLESYON PÈSONÈL
• 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.
• Jete refrijeran yo byen dapre règleman federal oswa lokal yo.

AVÈTISMAN

• BLESI PÈSONÈL AK DANJE ANVIWÒNMAN
• Si w pa suiv avètisman sa a, sa ka lakòz blesi pèsonèl oswa lanmò.
• Soulaje presyon epi rekipere tout febrifuj anvan reparasyon sistèm oswa jete final inite a.
• Mete linèt sekirite ak gan lè w ap manyen frigorigènes. Kenbe flanbo ak lòt sous ignisyon lwen frigorigènes ak lwil.

AVÈTISMAN

RISK POU DIFE OSWA ESPLOZYON

• Si yo pa swiv enfòmasyon ki nan manyèl sa a egzakteman, yon dife oswa yon eksplozyon ka lakòz, sa ki lakòz domaj pwopriyete, blesi pèsonèl oswa pèt lavi.
• Pa sere oswa itilize gazolin oswa lòt vapè ak likid ki ka pran dife nan vwazinaj sa a oswa nenpòt lòt aparèy.

KISA POU FÈ SI OU SANT GAZ

• Pa eseye limen nenpòt aparèy.
•  Pa manyen okenn switch elektrik; pa sèvi ak okenn telefòn nan bilding ou an.
• Kite bilding lan imedyatman.
• Menm lè a rele founisè gaz ou nan telefòn yon vwazen. Swiv enstriksyon founisè gaz la.
• Si ou pa ka kontakte founisè gaz ou a, rele depatman ponpye a.

OBJEKTIF

• Objektif dokiman sa a se bay yon apèsi jeneral souview 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.

Ki sa ki yon kontwolè SystemVu?

• 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. Mak twazyèm pati ak logo yo se pwopriyete mèt pwopriyete respektif yo.

Pwotokòl SystemVu sipòte yo
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”.

KONFIGIRASYON PWOTOKÒL

• Mete pwotokòl kominikasyon an lè l sèvi avèk koòdone itilizatè (UI) jan yo montre nan Fig. 2.
• Konfigirasyon Pwotokòl SystemVu BAS pou 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.

Konfigirasyon SystemVu pou 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.

Paramèt Konfigirasyon SystemVu BACnet

SystemVu sipòte vitès Baud sa yo pou BACnet MS/TP.

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

REMAK: 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.
Pou konfigire Vitès Transmisyon an ak Adrès MAC la, ale nan Anviwònman BAS nan Entèfas Itilizatè a avèk Menu/Anviwònman/Anviwònman Rezo/BACNET. Gade Fig. 3.

REMAK: 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

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

REMAK: 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.

ENTEGRASYON SOU 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.

Kab ak Fil Kominikasyon

• Kab ak fil kominikasyon yo itilize nan rezo a ka gen yon gwo enpak sou pèfòmans kominikasyon rezo a sou fil sa a. Swiv detay ki nan Tablo 1 kòm pi bon pratik pou fil elektrik sou rezo MS/TP BACnet yo.

Tablo 1 — BACnet MS/TP Filing Specification

NÒT (YO)

•  Mak twazyèm pati ak logo yo se pwopriyete mèt pwopriyete respektif yo.

POU KONEKTE KAB KOMINIKASYON AN

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.

ATANSYON
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.

REMAK: 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 sou plak pwotèj la vin twò gwo, parapò ak tè a, lè sa a vòltaj depase atagYo senyen li ak aparèy pwoteksyon sou PROT485 la oswa sou kontwolè yo.

Konsepsyon rezo

Avèk yon kontwolè ki polarize lokalman, dapre estanda RS-485 yo, kantite maksimòm ne rekòmande pou chak segman/tronk depann de vitès baud rezo a.

• 38,400 baud = maksimòm 15 nœuds ak yon routeur
• 76,800 baud = maksimòm 31 nœuds ak yon routeur

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.
• REMAK: Remak: Yo DWE itilize yon rezistans 120 Ohm pou mete fen nan tou de bout bis la, dapre egzijans estanda RS-485 yo. Yo rekòmande aparèy TERM485 la.
• 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.
• Li rekòmande anpil pou itilize aparèy PROT485 la pou tout segman rezo ki gen kontwolè SystemVu yo. Tanpri gade Gid Fil elektrik pou Kontwolè Ouvè a pou enstriksyon detaye sou enstalasyon PROT485 la.
• 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.
• Kontwolè SystemVu yo ta dwe gen fil BAS yo konekte sou plis, mwens, epi fil pwoteksyon an sou COM jan yo montre nan Fig. 7 ak 8.

Rezo Topoloji

• 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 exampPa egzanp, si routeur la se premye nœd sou rezo a, li ta dwe gen adrès MAC ki pi ba a. Pwochen inite sou daisy-chain nan ta dwe gen yon adrès MAC yon nimewo pi wo, elatriye.

Tè ak polarite

• Yon bon kalite koneksyon tè esansyèl pou asire bon fonksyònman inite a AK bon fonksyon kominikasyon BAS la.
• 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 sou plak pwotèj la vin twò gwo parapò ak tè a, lè sa a vòltaj depase atagYo senyen li ak aparèy pwoteksyon sou PROT485 la oswa sou kontwolè yo.

Segmantasyon pake

• Pil BACnet ki itilize ak pwodwi SystemVu a PA sipòte segmentasyon pake kounye a.
• Segmantasyon an ta dwe dezaktive sou aparèy twazyèm pati yo.
• Please be aware that the segmentation feature is NOT required for the current BTL (BACnet Testing Laboratories) certification.

i-Vu Integration Tips – Source Files ak Varyasyon Vèsyon

• 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.
• Tout patch i-Vu aktyèl yo dwe enstale lè w ap konekte ak pwodwi SystemVu yo. Ou ka jwenn yo nan seksyon "Telechaje Kontwòl" HVACPartners oswa nan Carrier Controls. webseksyon lojisyèl sit la.
• Li souvan nesesè pou ajoute sous SystemVu a manyèlman. files to the i-Vu server and place them into the appropriate folder.
• Tanpri sonje ke sous la fileYo sitiye sou HVACPartners (Kounye a li sitiye anba ONGLET SIPÒ > SIPÒ APRÈ VANT > LOJISYÈL SÈVIS).

COV (Chanjman Valè) ak Routeur Twazyèm Pati

• Gen kèk vandè twazyèm pati ki itilize fonksyon COV nan BACnet MS/TP a anpil.
• Sepandan, SystemVu sèlman sipòte yon kantite limite pwen COV. Demann routeur pou pwen COV ki pa sipòte pa kontwolè SystemVu a ka lakòz erè rezo ak pèfòmans rezo ki pòv.
• Dezaktive fonksyon COV la nan aparèy twazyèm pati yo kapab yon zouti itil lè w ap depanaj pwoblèm trafik rezo a.
• Sèten sit travay oswa kliyan ka mande pou yo itilize fonksyon COV la.
• Si se ka sa a, Tablo 2 a montre pwen COV egzak kontwolè SystemVu a sipòte yo.

Tablo 2 — Objè SystemVu ki sipòte Gid COV la

DESKRIPSYON	NON OBJÈ BACNET	BACNET TYPE	BACNETINSTANCE NUMBER	DESKRIPSYON BACNET
Mòd ekipman koneksyon rapòte bay zòn yo.	mòd_lnk	DE:	261	Mòd Ekipman Koneksyon
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	DE:	1009	Nivo Kalite Lè Andedan Kay la
Kalite lè andedan kay la ki resevwa sou rezo a.	iaq_net	DE:	7001	Valè IAQ Rezo a
Nivo Kalite Lè Deyò (OAQ) (detèktè).	oaq	DE:	1012	Nivo Kalite OA
Capteur Nivo Kalite Lè Deyò (OAQ) sou Rezo a.	oaq_net	DE:	7002	Valè OAQ Rezo a
Imidite Relatif Lè Eksteryè a ki te rezoud apati tout sous imidite lè deyò posib ki disponib nan sistèm nan.	oarh	DE:	1022	OA Imidite relatif
Capteur rezo imidite relatif lè deyò a.	oarh_net	DE:	7003	Valè Rezo OARH la
Tanperati lè deyò a ki te rezoud apati tout sous tanperati lè deyò posib ki disponib nan sistèm nan.	oa_tanperati	DE:	1003	Tanperati lè deyò
Tanperati lè deyò a soti nan rezo BMS la.	oat_net	DE:	7007	Valè OAT Rezo a
CFM lè deyò ki resevwa sou rezo a.	ocfm_net	DE:	371	Valè Rezo OACFM
Outdoor fan: High temperature override.	odfhtovr	DE:	9066	Tanperati Siprime ODF la
Return Air Relative Humidity is the result of the engineering conversion performed on the sensor in the return air ductwork.	rarh	DE:	30	RA Imidite relatif
Relative Air Relative Humidity (RARH) Sensor read in from the network sensor.	rarh_net	DE:	7004	Valè Rezo RARH la
Return Air Temperature that has been resolved from all of the possible return air temperature sources available in the system.	ra_temp	DE:	1010	Tanperati lè retounen
Tanperati lè retounen soti nan rezo a.	rat_net	DE:	7005	Tanperati lè retou rezo a
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_tanperati	DE:	1008	Pwovizyon pou Tanperati lè
Space Relative Humidity (SPRH) Sensor read in from the network sensor.	sprh_net	DE:	376	Valè SPRH Rezo a
Space Temperature is a legacy point that has typically been used for writing space temperature values over a CCN network.	space_temp	DE:	2007	Valè Tanperati Espas Pilòt la
Tanperati espas la se lekti ki soti nan rezo a.	spt_net	DE:	7006	Valè Tanperati Espas Rezo a
Lekti tanperati Sistèm Touch Space la nan rezo a.	sst_net	DE:	8023	Valè Tanperati Manyen Sistèm

Tablo 3 — Egzanp abrejeampLis Pwen yo

POINT DESCRIPTION	POINT ACESS	INITE	NON OBJÈ BACnet	ID BACnet	VALÈ RANJE	CNN POINT EQUIVALENT
BACnet device for IAQ	R/W		devlag	AV:8001	0 POU 4194303	DEAVIAQ
BACnet device for OAQ	R/W		devoaq	AV:8002	0 POU 4194303	DEVOAQ
BACnet device for OARH	R/W		devoarh	AV:8004	0 POU 4194303	DEVOARH
BACnet device for OAT	R/W		devoat	AV:8003	0 POU 4194303	DEVOAT
BACnet device for RARH	R/W		devrarh	AV:8005	0 POU 4194303	DEVRARH
BACnet device for RAT	R/W		devrat	AV:8006	0 POU 4194303	DEVRAT
BACnet device for SPRH	R/W		devsprh	AV:8028	0 POU 4194303	DEVSPRH
BACnet device for SPT	R/W		devspt	AV:8007	0 POU 4194303	DEVSPT

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

• Li pa estraòdinè pou bezwen ajiste yon kantite paramèt routeur ki varye anpil de yon travay a yon lòt.
• Malerezman, pa gen valè "grave nan wòch" ki mache nan chak travay.
• Tanpri sonje ke kèk nan valè sa yo gen ladan yo to delè APDU, to sondaj, ak to delè NPDU.
• 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.

Vitès imaj ak routeur twazyèm pati

• 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.
• Inite pwodiksyon A2L aktyèl yo gen vitès imaj reglabl ak valè mèt maksimòm.

ENTEGRASYON SYSTEMVU AK SISTÈM TOUCH SOU PÒ MS/TP

Ki sa ki 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 Websit

• System Touch Installation and Setup Guide
• Gid itilizatè System Touch
• 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

Kontwolè SystemVu a ka mande Capteur Tanperati ak Capteur Imidite System Touch la. Pou mande valè sa yo nan men System Touch, nou bezwen konfigire jan sa a.

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.

ENTEGRASYON SYSTEMVU AK EKIPMAN TOUCH SOU RNET

Ki sa ki Ekipman Touch?

• The Equipment Touch is a touchscreen device with a colour LCD display that you connect to the SystemVu controller to view oswa chanje valè pwopriyete li yo, pwograme ekipman yo, view tandans ak alam, ak plis ankò, san yo pa bezwen jwenn aksè nan sèvè i-Vu a.

For more details about the Equipment Touch, refer to the documents below available on HVACPartners or the Carrier Controls Websit.

• 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

REMAK: 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 soti nan aparèy SystemVu a, jan yo montre nan 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

Kontwolè SystemVu a ka itilize detèktè tanperati ak imidite Equipment Touch yo. Pou mande valè sa yo nan men Equipment Touch, nou bezwen konfigire jan sa a.

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.

PWOSESIS MIZAJOU FIRMWAYÈL POU EKIPMAN TOUCH/SISTÈM TOUCH

Etap Mizajou Firmware

1. Create a folder on the flash drive called “touch”, then put the ETxxxxx.hex or STxxxxx.hex file nan katab la.
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. Yon mesaj avètisman parèt. Touche Wi pou kontinye.
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.

ENTEGRASYON SYSTEMVU AK DETÈKTÈ ZS SOU RNET

ZS Detèktè

• 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.

Fonksyonalite Capteur ZS la detèmine pa:

• 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 Websit.

•  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.

EXAMPOU: 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.

Konektè SystemVu RNET

ENDIKATÈ AKTIVITE KONSÈY ADMINISTRASYON AN

Wouj Ki ap dirije Status
Ou ka verifye bon fonksyònman tablo SystemVu a vizyèlman lè w gade LED wouj la (gade Fig. 20).

Tablo 4 la bay enfòmasyon sou LED Estati a.

Kondisyon LED wouj la	Estati lojisyèl tablo a
OFF Kontinyèlman	The board is unpowered or the power supply is defective
KLAPE ON 200 ms, OFF 200 ms	Board is in Bootloader mode
KLAPE ON 1000 ms, OFF 1000 ms	The boot loader is not running, application software is running
ON Kontinyèlman or FLASHING at nenpòt other frequency	The board or software is defective

Green Status LED

• 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).
• LED estati jòn
• 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.

DEPANAJ BACNET MS/TP

Konfigirasyon BACnet MS/TP yo

• 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
• Tanpri note sous sa a fileYo nesesè pou yon sistèm i-Vu ka byen detekte inite SystemVu yo. Sous 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.

Adrès Kontwolè

• 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.

Gid pou depanaj yo

• Si yo pa detekte yon kontwolè SystemVu sou rezo MS/TP a, verifye tout paramèt konfigirasyon yo tankou vitès transmisyon (Baud Rate), adrès MAC ak paramèt pwotokòl BAS. Sou rezo i-Vu yo, asire w ke sous la 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.

KOUCH FIZIK

• 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.

• Yon kantite faktè ka lakòz distòsyon fòm ond sou kouch fizik la. Move ijyèn fil elektrik, segman fil ki domaje, sikwi transceiver RS-485 ki domaje sou chak kat, ak entèferans elektrik ki soti nan anviwònman "ki fè bwi" se jis kèk nan pwoblèm ki ka kontribye nan distòsyon kouch fizik la. Izole pòsyon nan segman rezo a lè w divize bis kominikasyon an an de plizyè fwa, byenke li anmèdan, se pi bon teknik pou izole domaj kouch fizik la.
• 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.
• Verifye ke fil ki kòrèk la ap itilize epi li byen konekte nan chak aparèy ak routeur la. Rezistans tèminasyon yo dwe nan kòmansman ak nan fen chak segman bis. Asire w ke ou pa itilize rezistans polarizasyon rezo a paske SystemVu deja polarize lokalman. Pwoblèm sa yo se pwoblèm ki pi komen yo jwenn pandan depanaj.

KOUCH REZO

• 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.

KOUCH APLIKASYON

• Tou depan de routeur y ap itilize a, yon fwa pwoblèm kouch fizik ak kouch rezo a rezoud, yon etid detaye sou alam ak alèt ki prezan sou routeur la ka revele tan, sous file, ak pwoblèm lojisyèl. Li pi bon pou tout routeurs ak aparèy sou rezo a gen patch firmwèr ki ajou ak patch kimilatif jan sa aplikab.

LIS PWEN REZO POU BACNET

• Lis Pwen SystemVu BACnet
• 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

Lis Alam SystemVu

• 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.

FAQ

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.

Dokiman / Resous

Kontwolè SystemVu Carrier SYSVU [pdfGid Itilizatè SYSVU-001-SUPP, Kontwolè SystemVu SYSVU, SYSVU, Kontwolè SystemVu, Kontwolè

Referans

• Manyèl itilizatè