Panduan Pengguna Pengawal SYSVU SystemVu Pembawa

Pengawal SYSVU SystemVu Pembawa

PERTIMBANGAN KESELAMATAN

• Pemasangan dan servis peralatan penyaman udara boleh menjadi berbahaya kerana tekanan sistem dan komponen elektrik. Hanya kakitangan perkhidmatan yang terlatih dan berkelayakan harus memasang, membaiki, atau menservis peralatan penyaman udara.
• Kakitangan yang tidak terlatih boleh melaksanakan fungsi penyelenggaraan asas untuk membersihkan gegelung dan penapis serta menggantikan penapis. Semua operasi lain hendaklah dilakukan oleh kakitangan perkhidmatan terlatih. Apabila bekerja pada peralatan penyaman udara, perhatikan langkah berjaga-jaga dalam literatur, tags dan label yang dilampirkan pada unit, dan langkah berjaga-jaga keselamatan lain yang mungkin dikenakan.
• 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.Apabila anda melihat simbol ini pada unit dan dalam arahan atau manual, berhati-hati dengan potensi kecederaan diri.
• Fahami perkataan isyarat BAHAYA, AMARAN, AWAS dan CATATAN. Perkataan ini digunakan dengan simbol amaran keselamatan. BAHAYA mengenal pasti bahaya yang paling serius yang akan mengakibatkan kecederaan peribadi yang teruk atau kematian. AMARAN menandakan bahaya yang boleh mengakibatkan kecederaan diri atau kematian. AWAS digunakan untuk mengenal pasti amalan tidak selamat, yang boleh mengakibatkan kecederaan peribadi kecil atau kerosakan produk dan harta benda. NOTA digunakan untuk menyerlahkan cadangan yang akan menghasilkan pemasangan, kebolehpercayaan atau operasi yang dipertingkatkan.

BAHAYA

BAHAYA RENJAKAN ELEKTRIK

• Kegagalan mematuhi amaran ini akan mengakibatkan kecederaan peribadi atau kematian.
• Sebelum menjalankan operasi servis atau penyelenggaraan pada unit, matikan suis kuasa utama ke unit dan pasang kunci dan kunci keluar tag(s). Pastikan perkhidmatan elektrik ke unit atas bumbung bersetuju dengan voltage dan ampera yang disenaraikan pada plat penarafan unit. Unit mungkin mempunyai lebih daripada satu suis kuasa.

AWAS

• BAHAYA KEROSAKAN UNIT
• 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.

AMARAN

• UNIT OPERASI DAN BAHAYA KESELAMATAN
• Kegagalan mematuhi amaran ini boleh menyebabkan kecederaan diri, kematian dan/atau kerosakan peralatan.
• 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.

AMARAN 

• BAHAYA HARTA HARTA ATAU KECEDERAAN DIRI
• 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.
• Buang penyejuk dengan betul mengikut peraturan persekutuan atau tempatan.

AMARAN

• KECEDERAAN DIRI DAN BAHAYA PERSEKITARAN
• Kegagalan mematuhi amaran ini boleh menyebabkan kecederaan peribadi atau kematian.
• Hilangkan tekanan dan pulihkan semua bahan pendingin sebelum pembaikan sistem atau pelupusan unit akhir.
• Pakai cermin mata dan sarung tangan keselamatan semasa mengendalikan penyejuk. Jauhkan obor dan sumber pencucuhan lain daripada penyejuk dan minyak.

AMARAN

RISIKO KEBAKARAN ATAU LETUPAN

• Jika maklumat dalam manual ini tidak diikuti dengan tepat, kebakaran atau letupan mungkin berlaku, menyebabkan kerosakan harta benda, kecederaan diri atau kehilangan nyawa.
• Jangan simpan atau gunakan petrol atau wap dan cecair mudah terbakar lain di sekitar ini atau mana-mana perkakas lain.

APA YANG PERLU DIBUAT JIKA ANDA BAU GAS

• Jangan cuba menyalakan sebarang perkakas.
•  Jangan sentuh mana-mana suis elektrik; jangan gunakan sebarang telefon di dalam bangunan anda.
• Tinggalkan bangunan dengan segera.
• Segera hubungi pembekal gas anda dari telefon jiran. Ikut arahan pembekal gas.
• Jika anda tidak dapat menghubungi pembekal gas anda, hubungi bomba.

TUJUAN

• Tujuan dokumen ini adalah untuk memberikan umumview 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.

Apakah itu Pengawal 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. Tanda dagangan dan logo pihak ketiga adalah hak milik pemiliknya masing-masing.

Protokol Disokong oleh 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”.

KONFIGURASI PROTOKOL

• Tetapkan protokol Komunikasi menggunakan UI (antara muka pengguna) seperti yang ditunjukkan dalam Rajah 2.
• Mengkonfigurasi Protokol SystemVu BAS kepada 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.

Mengkonfigurasi SystemVu kepada 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.

Tetapan Konfigurasi SystemVu BACnet

SystemVu menyokong kadar Baud berikut untuk BACnet MS/TP.

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

NOTA: 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.
Untuk mengkonfigurasi Kadar Baud dan Alamat MAC, navigasi ke Tetapan BAS dalam Antara Muka Pengguna menggunakan Menu/Tetapan/Tetapan Rangkaian/BACNET. Lihat Rajah 3.

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

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

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

INTEGRASI MELALUI 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.

Kabel dan Wayar Komunikasi

• Kabel komunikasi dan wayar yang digunakan dalam rangkaian boleh memberi kesan besar kepada prestasi komunikasi rangkaian melalui wayar tersebut. Ikuti butiran yang ditunjukkan dalam Jadual 1 sebagai amalan terbaik dengan pendawaian pada rangkaian BACnet MS/TP.

Jadual 1 — Spesifikasi Pendawaian BACnet MS/TP

NOTA

•  Tanda dagangan dan logo pihak ketiga adalah hak milik pemiliknya masing-masing.

UNTUK MENDAWAI KABEL KOMUNIKASI

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.

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

NOTA: 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 pada perisai menjadi terlalu besar, berbanding dengan tanah bumi, maka lebihan voltage dibuang dengan peranti pelindung pada PROT485 atau pada pengawal.

Reka Bentuk Rangkaian

Dengan pengawal berat sebelah tempatan, mengikut piawaian RS-485, bilangan maksimum disyorkan nod bagi setiap segmen/batang bergantung pada kadar baud rangkaian.

• 38,400 baud = maksimum 15 nod dan penghala
• 76,800 baud = maksimum 31 nod dan penghala

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.
• NOTA: Nota: Perintang 120 Ohm MESTI digunakan untuk menamatkan bas di kedua-dua hujungnya mengikut keperluan standard RS-485. Peranti TERM485 disyorkan.
• 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.
• Penggunaan peranti PROT485 sangat disyorkan untuk semua segmen rangkaian dengan pengawal SystemVu. Sila rujuk Panduan Pendawaian Rangkaian Pengawal Terbuka untuk arahan pemasangan PROT485 terperinci.
• 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.
• Pengawal SystemVu harus mempunyai pendawaian BAS yang disambungkan ke tambah, tolak, dan wayar perisai ke COM seperti yang ditunjukkan dalam Rajah 7 dan 8.

Topologi Rangkaian

• 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 exampOleh itu, jika penghala ialah nod pertama pada rangkaian, ia sepatutnya mempunyai alamat MAC yang paling rendah. Unit seterusnya pada rantaian daisy harus mempunyai alamat MAC satu nombor lebih tinggi, dsb.

Pembumian dan Polariti

• Tanah bumi yang berkualiti adalah penting untuk memastikan operasi unit yang betul DAN fungsi komunikasi BAS yang betul.
• 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 pada perisai menjadi terlalu besar berbanding dengan tanah bumi, maka lebihan voltage dibuang dengan peranti pelindung pada PROT485 atau pada pengawal.

Segmentasi Paket

• Tindanan BACnet yang digunakan dengan produk SystemVu TIDAK menyokong pembahagian paket pada masa ini.
• Pembahagian hendaklah dimatikan pada peranti pihak ketiga.
• Please be aware that the segmentation feature is NOT required for the current BTL (BACnet Testing Laboratories) certification.

i-Vu Integration Tips – Source Files dan Variasi Versi

• 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.
• Semua tampung i-Vu semasa mesti dipasang apabila menyambung kepada produk SystemVu. Ini boleh didapati daripada bahagian "Muat Turun Kawalan" HVACPartners atau daripada Kawalan Pembawa webbahagian perisian tapak.
• Selalunya perlu menambah sumber SystemVu secara manual files to the i-Vu server and place them into the appropriate folder.
• Sila ambil perhatian bahawa sumber files terletak di HVACPartners (Ketika ini terletak di bawah TAB SOKONGAN > SOKONGAN PASCA JUALAN > PERISIAN PERKHIDMATAN).

COV (Perubahan Nilai) dan Penghala Pihak Ketiga

• Ciri COV dalam BACnet MS/TP digunakan secara meluas oleh sesetengah vendor pihak ketiga.
• Walau bagaimanapun, SystemVu hanya menyokong bilangan mata COV yang terhad. Permintaan penghala untuk titik COV yang tidak disokong oleh pengawal SystemVu boleh menyebabkan ralat rangkaian dan prestasi rangkaian yang lemah.
• MEMATIKAN fungsi COV dalam peranti pihak ketiga boleh menjadi alat yang berguna apabila menyelesaikan masalah trafik rangkaian.
• Tapak kerja atau pelanggan tertentu mungkin memerlukan ciri COV digunakan.
• Jika ini berlaku, Jadual 2 menunjukkan titik COV tepat yang disokong oleh pengawal SystemVu.

Jadual 2 — Objek SystemVu Menyokong Panduan COV

Jadual 3 — Singkatan Cthample daripada Senarai Mata

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

• Ia adalah perkara biasa untuk perlu melaraskan beberapa tetapan penghala yang berbeza dengan ketara dari satu kerja ke satu kerja.
• Malangnya, tidak ada nilai "set in stone" yang berfungsi pada setiap kerja.
• Harap maklum bahawa beberapa nilai ini termasuk kadar tamat masa APDU, kadar pengundian dan kadar tamat masa 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.

Kadar Bingkai dan Penghala Pihak Ketiga

• 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.
• Unit pengeluaran A2L semasa mempunyai kadar bingkai boleh laras dan nilai induk maksimum.

INTEGRASI SYSTEMVU DENGAN SENTUH SISTEM ATAS PORT MS/TP

Apakah itu Sentuhan Sistem

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

• System Touch Installation and Setup Guide
• Panduan Pengguna Sentuhan Sistem
• 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

Sensor Suhu dan Sensor Kelembapan Sistem Touch boleh diminta oleh pengawal SystemVu. Untuk meminta nilai ini daripada System Touch, kami perlu mengkonfigurasi seperti di bawah.

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.

INTEGRASI SYSTEMVU DENGAN PERALATAN SENTUH ATAS RNET

Apakah itu Sentuhan Peralatan

• The Equipment Touch is a touchscreen device with a colour LCD display that you connect to the SystemVu controller to view atau menukar nilai hartanya, peralatan jadual, view trend dan penggera, dan banyak lagi, tanpa perlu mengakses pelayan i-Vu.

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

• 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

NOTA: 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 daripada peranti SystemVu, seperti yang ditunjukkan dalam Rajah 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

Penderia Suhu Sentuh dan Kelembapan Peralatan boleh digunakan oleh pengawal SystemVu. Untuk meminta nilai ini daripada Equipment Touch, kami perlu mengkonfigurasi seperti di bawah.

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.

PROSES NAIK TARAF PERISIAN TEGAR UNTUK SENTUHAN PERALATAN/SENTUHAN SISTEM

Langkah Kemas Kini Perisian Tegar

1. Create a folder on the flash drive called “touch”, then put the ETxxxxx.hex or STxxxxx.hex file dalam folder.
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. Mesej amaran muncul. Sentuh Ya untuk meneruskan.
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.

INTEGRASI SYSTEMVU DENGAN ZS SENSOR MELALUI RNET

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

Fungsi Penderia ZS ditentukan oleh:

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

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

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

Penyambung SystemVu RNET

PETUNJUK AKTIVITI LEMBAGA

LED Status Merah
Pengendalian Betul Papan SystemVu boleh disemak secara visual dengan melihat LED status merah (lihat Rajah 20).

Jadual 4 menyediakan maklumat tentang LED Status.

LED Status Hijau

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

MENYELESAIKAN MASALAH BACNET MS/TP

BACnet MS/TP Konfigurasi

• 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
• Sila ambil perhatian sumber itu files diperlukan untuk pengesanan unit SystemVu yang betul oleh sistem i-Vu. Sumber 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.

Pengalamatan Pengawal

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

Garis panduan penyelesaian masalah

• Jika pengawal SystemVu tidak dikesan melalui rangkaian MS/TP, sahkan semua tetapan konfigurasi seperti Baud Rate, alamat MAC dan tetapan Protokol BAS. Pada rangkaian i-Vu, pastikan sumbernya 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.

LAPISAN FIZIKAL

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

• Beberapa faktor boleh menyebabkan herotan bentuk gelombang pada lapisan fizikal. Kebersihan pendawaian yang lemah, segmen wayar yang rosak, litar transceiver RS-485 yang rosak pada papan individu dan gangguan elektrik daripada persekitaran "bising" hanyalah beberapa isu yang semuanya boleh menyumbang kepada herotan lapisan fizikal. Mengasingkan bahagian segmen rangkaian dengan membelah bas komunikasi kepada separuh berulang kali, walaupun membosankan, adalah teknik terbaik untuk mengasingkan kecacatan lapisan fizikal.
• 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.
• Sahkan wayar yang betul sedang digunakan dan disambungkan dengan betul pada setiap peranti dan penghala. Perintang penamatan mestilah pada permulaan dan penghujung setiap segmen bas. Pastikan perintang pincang rangkaian tidak digunakan memandangkan SystemVu sudah pincang tempatan. Item ini ialah isu yang paling biasa ditemui semasa penyelesaian masalah.

LAPISAN RANGKAIAN

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

LAPISAN APLIKASI

• Bergantung pada penghala yang digunakan, setelah masalah lapisan fizikal dan lapisan rangkaian telah diselesaikan, kajian terperinci tentang penggera dan makluman yang terdapat pada penghala boleh mendedahkan masa, sumber file, dan isu perisian. Amalan terbaik untuk semua penghala dan peranti pada rangkaian mempunyai tampung perisian tegar dan tampung kumulatif yang dikemas kini sebagaimana yang berkenaan.

SENARAI TITIK RANGKAIAN UNTUK BACNET

• Senarai Mata 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

Senarai Penggera 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.

Soalan Lazim