Guia do Usuário do Controlador Carrier SYSVU SystemVu

Controlador SystemVu da Carrier

CONSIDERAÇÕES DE SEGURANÇA

• A instalação e a manutenção de equipamentos de ar condicionado podem ser perigosas devido à pressão do sistema e aos componentes elétricos. Somente pessoal de serviço treinado e qualificado deve instalar, reparar ou fazer a manutenção de equipamentos de ar condicionado.
• Pessoal não treinado pode realizar funções básicas de manutenção de serpentinas e filtros de limpeza e substituição de filtros. Todas as outras operações devem ser realizadas por pessoal de serviço treinado. Ao trabalhar em equipamentos de ar condicionado, observe as precauções na literatura, tags e etiquetas afixadas à unidade, e outras precauções de segurança que podem ser aplicadas.
• 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.Quando vir este símbolo na unidade e nas instruções ou manuais, esteja alerta para a possibilidade de ferimentos pessoais.
• Compreenda as palavras de sinalização PERIGO, AVISO, CUIDADO e OBSERVAÇÃO. Estas palavras são usadas com o símbolo de alerta de segurança. PERIGO identifica os perigos mais graves que resultarão em ferimentos graves ou morte. ADVERTÊNCIA significa perigos que podem resultar em ferimentos pessoais ou morte. CUIDADO é usado para identificar práticas inseguras, que podem resultar em ferimentos leves ou danos ao produto e à propriedade. NOTA é usado para destacar sugestões que resultarão em melhor instalação, confiabilidade ou operação.

PERIGO

RISCO DE CHOQUE ELÉTRICO

• O não cumprimento deste aviso resultará em ferimentos pessoais ou morte.
• Antes de executar operações de serviço ou manutenção na unidade, desligue o interruptor de alimentação principal da unidade e instale a(s) trava(s) e o bloqueio tag(s). Certifique-se de que o serviço elétrico da unidade rooftop esteja de acordo com o volumetage e ampidade listada na placa de identificação da unidade. A unidade pode ter mais de um botão liga/desliga.

CUIDADO

• PERIGO DE DANOS NA UNIDADE
• 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.

AVISO

• OPERAÇÃO DA UNIDADE E RISCO DE SEGURANÇA
• O não cumprimento deste aviso pode causar ferimentos pessoais, morte e/ou danos ao equipamento.
• 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.

AVISO 

• RISCO DE DANOS À PROPRIEDADE OU PESSOAIS
• 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.
• Descarte o refrigerante adequadamente, de acordo com as regulamentações federais ou locais.

AVISO

• DANOS PESSOAIS E RISCOS AMBIENTAIS
• O não cumprimento deste aviso pode causar ferimentos pessoais ou morte.
• Alivie a pressão e recupere todo o refrigerante antes do reparo do sistema ou do descarte final da unidade.
• Use óculos de segurança e luvas ao manusear refrigerantes. Mantenha tochas e outras fontes de ignição longe de refrigerantes e óleos.

AVISO

RISCO DE INCÊNDIO OU EXPLOSÃO

• Se as informações deste manual não forem seguidas exatamente, pode ocorrer um incêndio ou explosão, causando danos materiais, ferimentos pessoais ou morte.
• Não armazene ou use gasolina ou outros vapores e líquidos inflamáveis ​​nas proximidades deste ou de qualquer outro aparelho.

O QUE FAZER SE VOCÊ SENTIR CHEIRO DE GÁS

• Não tente acender nenhum aparelho.
•  Não toque em nenhum interruptor elétrico nem use nenhum telefone no seu prédio.
• Saia do prédio imediatamente.
• Ligue imediatamente para o seu fornecedor de gás do telefone de um vizinho. Siga as instruções do fornecedor de gás.
• Se você não conseguir falar com seu fornecedor de gás, ligue para o corpo de bombeiros.

PROPÓSITO

• O objetivo deste documento é fornecer uma visão geral.view 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.

O que é um controlador 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. Marcas registradas e logotipos de terceiros são propriedade de seus respectivos proprietários.

Protocolos suportados pelo 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”.

CONFIGURAÇÃO DO PROTOCOLO

• Configure o protocolo de comunicação usando a interface do usuário (UI), conforme mostrado na Figura 2.
• Configurando o protocolo SystemVu BAS para 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.

Configurando o SystemVu para 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.

Configurações de configuração BACnet do SystemVu

O SystemVu suporta as seguintes taxas de transmissão (Baud rates) para BACnet MS/TP.

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

OBSERVAÇÃO: 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.
Para configurar a taxa de transmissão (Baud Rate) e o endereço MAC, acesse as Configurações BAS na Interface do Usuário através de Menu/Configurações/Configurações de Rede/BACNET. Veja a Figura 3.

OBSERVAÇÃO: 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

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

OBSERVAÇÃO: 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.

INTEGRAÇÃO SOBRE 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.

Cabos e fios de comunicação

• Os cabos e fios de comunicação utilizados em redes podem impactar significativamente o desempenho da comunicação de rede. Siga as instruções da Tabela 1 como boas práticas para cabeamento em redes MS/TP BACnet.

Tabela 1 — Especificação de fiação BACnet MS/TP

NOTAS)

•  Marcas registradas e logotipos de terceiros são propriedade de seus respectivos proprietários.

PARA INSTALAR O CABO DE COMUNICAÇÃO

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.

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

OBSERVAÇÃO: 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 no escudo torna-se muito grande em relação ao solo terrestre, então o excesso de volumetagO vazamento é realizado por meio de dispositivos de proteção no PROT485 ou nos controladores.

Design de rede

Com controladores com polarização local, de acordo com os padrões RS-485, o número máximo recomendado de nós por segmento/tronco depende da taxa de transmissão (baud rate) da rede.

• 38,400 baud = máximo de 15 nós e um roteador
• 76,800 baud = máximo de 31 nós e um roteador

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: É OBRIGATÓRIO o uso de um resistor de 120 ohms para terminar o barramento em ambas as extremidades, de acordo com os requisitos padrão do RS-485. Recomenda-se o uso do dispositivo TERM485.
• 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.
• Recomenda-se fortemente o uso do dispositivo PROT485 para todos os segmentos de rede com controladores SystemVu. Consulte o Guia de Cabeamento de Rede do Controlador Aberto para obter instruções detalhadas de instalação do PROT485.
• 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.
• Os controladores SystemVu devem ter a fiação BAS conectada ao positivo, ao negativo e o fio de blindagem ao COM, conforme mostrado nas Figuras 7 e 8.

Topologia de rede

• 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 exampPor exemplo, se o roteador for o primeiro nó da rede, ele deverá ter o endereço MAC mais baixo. A próxima unidade na cadeia deverá ter um endereço MAC um número maior, e assim por diante.

Aterramento e Polaridade

• Um aterramento de qualidade é essencial para garantir o funcionamento adequado da unidade e a comunicação correta do sistema de automação predial (BAS).
• 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 no escudo torna-se muito grande em relação ao solo terrestre, então o excesso de volumetagO vazamento é realizado por meio de dispositivos de proteção no PROT485 ou nos controladores.

Segmentação de Pacotes

• A pilha BACnet usada com o produto SystemVu NÃO suporta atualmente segmentação de pacotes.
• A segmentação deve ser DESATIVADA em dispositivos de terceiros.
• Please be aware that the segmentation feature is NOT required for the current BTL (BACnet Testing Laboratories) certification.

i-Vu Integration Tips – Source Files e variações de versão

• 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.
• Todas as atualizações i-Vu mais recentes devem ser instaladas ao conectar-se aos produtos SystemVu. Elas podem ser obtidas na seção "Download de Controles" do HVACPartners ou no site da Carrier Controls. webSeção de software do site.
• Muitas vezes é necessário adicionar manualmente a fonte SystemVu. files to the i-Vu server and place them into the appropriate folder.
• Observe que a fonte fileOs softwares estão localizados no HVACPartners (atualmente em SUPORTE > SUPORTE PÓS-VENDA > SOFTWARE DE SERVIÇO).

COV (Alteração de Valor) e Roteadores de Terceiros

• O recurso COV no BACnet MS/TP é amplamente utilizado por alguns fornecedores terceirizados.
• No entanto, o SystemVu suporta apenas um número limitado de pontos COV. Solicitações do roteador para pontos COV que não são suportados pelo controlador SystemVu podem levar a erros de rede e baixo desempenho da rede.
• Desativar a função COV em dispositivos de terceiros pode ser uma ferramenta útil na resolução de problemas de tráfego de rede.
• Determinados locais de trabalho ou clientes podem exigir o uso do recurso COV.
• Nesse caso, a Tabela 2 mostra os pontos de COV exatos suportados pelo controlador SystemVu.

Tabela 2 — Objetos do SystemVu que suportam o COV-Guide

Tabela 3 — Ex abreviadoamplista de pontos

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

• Não é incomum precisar ajustar diversas configurações do roteador, que variam significativamente de um trabalho para outro.
• Infelizmente, não existem valores "imbatíveis" que funcionem em todos os trabalhos.
• Observe que alguns desses valores incluem taxas de tempo limite de APDU, taxas de sondagem e taxas de tempo limite de 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.

Taxas de quadros e roteadores de terceiros

• 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.
• As unidades de produção A2L atuais possuem taxas de quadros e valores máximos de master ajustáveis.

Integração do SystemMVU com o System Touch através da porta MS/TP.

O que é o 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 Website

• System Touch Installation and Setup Guide
• Guia do usuário do 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

O controlador SystemVu pode solicitar os valores de temperatura e umidade do sensor System Touch. Para solicitar esses valores do System Touch, é necessário configurá-lo conforme descrito abaixo.

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.

INTEGRAÇÃO DO SYSTEMVU COM EQUIPAMENTOS TOUCH OVER RNET

O que é o Equipment Touch?

• The Equipment Touch is a touchscreen device with a colour LCD display that you connect to the SystemVu controller to view ou alterar seus valores de propriedade, programar equipamentos, view Tendências, alertas e muito mais, sem precisar acessar o servidor i-Vu.

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

• 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

OBSERVAÇÃO: 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 do dispositivo SystemVu, conforme mostrado na 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

Os sensores de temperatura e umidade Equipment Touch podem ser usados ​​pelo controlador SystemVu. Para solicitar esses valores do Equipment Touch, precisamos configurá-los conforme abaixo.

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.

PROCESSO DE ATUALIZAÇÃO DE FIRMWARE PARA EQUIPAMENTO TOUCH/SYSTEM TOUCH

Etapas de atualização de firmware

1. Create a folder on the flash drive called “touch”, then put the ETxxxxx.hex or STxxxxx.hex file na pasta.
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. Uma mensagem de aviso aparece. Toque em Sim para continuar.
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.

Integração do SystemMVu com o sensor ZS via RNET

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

A funcionalidade do sensor ZS é determinada por:

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

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

Conector SystemVu RNET

INDICADORES DE ATIVIDADE DO CONSELHO

LED vermelho de status
O funcionamento correto da placa SystemVu pode ser verificado visualmente observando o LED vermelho de status (veja a Fig. 20).

A Tabela 4 fornece informações sobre o LED de status.

LED de status verde

• 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 amarelo indicando status
• 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.

SOLUÇÃO DE PROBLEMAS BACNET MS/TP

Configurações BACnet MS/TP

• 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
• Observe que a fonte fileSão necessários componentes para a detecção adequada de unidades SystemVu por um sistema i-Vu. Fonte 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.

Endereçamento do controlador

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

Diretrizes de solução de problemas

• Se um controlador SystemVu não for detectado na rede MS/TP, verifique todas as configurações, como taxa de transmissão (Baud Rate), endereço MAC e protocolo BAS. Em redes i-Vu, certifique-se de que a fonte 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.

CAMADA FÍSICA

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

• Diversos fatores podem causar distorções na forma de onda na camada física. Má higiene da fiação, segmentos de fios danificados, circuitos transceptores RS-485 danificados em placas individuais e interferência elétrica proveniente de ambientes ruidosos são apenas alguns dos problemas que podem contribuir para distorções na camada física. Isolar partes do segmento de rede dividindo o barramento de comunicação ao meio repetidamente, embora trabalhoso, é a melhor técnica para isolar defeitos na camada física.
• 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.
• Verifique se o cabo correto está sendo usado e se está conectado adequadamente em cada dispositivo e no roteador. Os resistores de terminação devem estar no início e no final de cada segmento de barramento. Certifique-se de que os resistores de polarização de rede não estejam sendo usados, pois o SystemVu já possui polarização local. Esses são os problemas mais comuns encontrados durante a solução de problemas.

CAMADA DE REDE

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

CAMADA DE APLICAÇÃO

• Dependendo do roteador utilizado, uma vez resolvidos os problemas das camadas física e de rede, um estudo detalhado dos alarmes e alertas presentes no roteador pode revelar o momento e a origem dos alertas. filee problemas de software. É uma boa prática que todos os roteadores e dispositivos da rede tenham patches de firmware e patches cumulativos atualizados, quando aplicável.

LISTA DE PONTOS DE REDE PARA BACNET

• Lista de pontos BACnet do SystemVu
• 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

Lista de alarmes do 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.

Perguntas frequentes