Question 1

How do I update my Smart-UPS firmware using the command line interface of my Network Management Card?

Accepted Answer

Issue:Because the Firmware Upgrade Wizard is the most universal and preferred method of updating, we recommend using the APC Firmware Upgrade Wizard whenever possible. The APC Firmware Upgrade Wizard guides you through the update process and provides a consistent update experience. The Firmware Upgrade Wizard is available in FA279197. Instructions are being provided here for users that are unable use the Firmware Upgrade Wizard and wish to update their Smart-UPS Firmware using command line tools and an APC Network Management Card (NMC). For those who wish to update their Smart-UPS Firmware using the NMC’s web interface, see FA170679.Product Line:Smart-UPS models with the prefixes SMT, SMX, SRT, SRTL, XU, and XP with a SmartSlot or Embedded NMC. If the ID of your UPS is not available in the table below, it means there are no firmware updates available for that UPS at this time. Environment: Command line terminal emulator and file transfer toolsSupported UPS model listed aboveUPS Network Management Card 2 (AP9630, AP9630CH, AP9631, AP9631CH, or embedded NMC2) with SUMX application firmware v6.4.0 or higher UPS Network Management Card 3 (AP9640, AP9641, AP9643, or embedded NMC3) with SU application firmware 1.0 or higherCorrect firmware file for the particular UPS available in the table below Resolution:Follow the steps below to determine your current NMC type and firmware revision, select the proper UPS firmware image, and update the UPS firmware via the Network Management Card’s Command Line Interface (CLI). Step 1 - Using an SSH client of your choice, connect to the IP address of the Network Management Card.Note: If required, Open SSH can be added using Windows Manage Optional Features.Example of using Windows Command Prompt to connect via SSH:ssh -c aes256-cbc apc@10.0.0.1Notes: This SSH command is for OpenSSH. The command may differ depending on the SSH tool used.The username may be different that the “apc” username used in this example. Using the web interface of the NMC, navigate to the “SSH Host Key” in the “Console” found in the “Network” section of the “Configuration” menu. Verify and take note of the SSH Key.Compare the SSH key to the RSA fingerprint displayed in the command line terminal window. To display the fingerprint in the same format as shown in the NMC web interface, the <-o FingerPrintHash=md5> argument can be used. Example:ssh -c aes256-cbc -o FingerPrintHash=md5 apc@10.0.0.1Notes: Telnet can be used if enabled, but it is not recommended due to lack of encryption, and the examples shown here are just for reference.Example of using Windows Command Prompt to connect via Telnet: From a computer that has access to the network on which the NMC is installed, at a command prompt, type telnet and the IP address for the NMC (for example, telnet 10.216.253.128, when the NMC uses the default Telnet port of 23), and press ENTER.This example works for command prompt based Telnet clients. The commands may differ for different Telnet clients. If the NMC uses a non-default port number (from 5000 to 32768), you must include a colon or a space, depending on your Telnet client, between the IP address (or DNS name) and the port number. (These are commands for general usage: some clients don’t allow you to specify the port as an argument and some types of Linux might want extra commands). Enter the user name and password.Step 2 - Check if you have a Network Management Card 2 running Smart-UPS / Matrix Application, or a Network Management Card 3 running Smart-UPS Application and ensure there are no active alarms reported.Use the command to display the Network Management Card application module:Network Management Card 2 installed in a Smart-UPS uses “sumx” Application Module: Network Management Card 3 installed in a Smart-UPS uses “su” Application Module:Use the command to ensure there are no active alarms:Step 3 - If using Network Management Card 3, go to Step 4.If using Network Management Card 2: Verify the firmware revision of your Network Management Card. The firmware must be v.6.4.0 or higher, but we recommend you always run the latest available NMC firmware. To update the firmware of your Network Management Card, refer to FA156047.Use the command to display the Network Management Card firmware version:Step 4 - IMPORTANT: For Smart-UPS Ultra models with ID 1226 & 1227, the firmware of the Network Management Card must be updated to version 2.5.4.4 or later before updating the UPS firmware. Refer to FA156047 to update the firmware of the Network Management Card. Note: always download the latest NMC firmware for SUCAN application from se.com: Step 5 – Identify the correct UPS Firmware file. Use the command.Identify the "ID" number to select the proper firmware file for your UPS. For example, for a UPS with ID 1024 the proper filename will be SRTL1024UPS_xx-x.enc Download the appropriate firmware file available in the table below. The "ID" is a unique identifier for the hardware platform of your UPS. You need to use the "ID" number to make sure to select the correct firmware file. A particular UPS model may have different "ID" numbers depending on when it was manufactured, or its current firmware version. Always check the "ID" number of the UPS before starting the update, and ensure you use a firmware file with the compatible ID. If the incorrect file is used, the update will be refused, and will need to be restarted using the correct firmware file. Use the table below to determine the correct firmware file for your UPS. Click here to view details UPSSeriesUPSIDFirmware FileLatest FirmwareVersionReleaseNotesFirmwareUpdate withOutput OnAvailableCrypto-graphycallySignedFirmwareUpdatevia NMCSCL1029SCL1029UPS_15-6.encUPS 15.6YesYesEnabledSCL1048SCL1048UPS_16-6.encUPS 16.6YesYesEnabledSMC1005SMC1005UPS_15-1.encUPS 15.1NoNoConfigurableSMT1015SMT1015UPS_18-0.encUPS 18.0YesYesConfigurableSMT1027SMT1027UPS_18-0.encUPS 18.0YesYesConfigurableSMT1031SMT1031UPS_15-6.encUPS 15.6YesYesConfigurableSMT1039SMT1039UPS_15-5.encUPS 15.5NoYesConfigurableSMT1040SMT1040UPS_15-0.encUPS 15.0NoNoConfigurableSMT1041SMT1041UPS_15-0.encUPS 15.0NoNoDisabledSMT1050SMT1050UPS_16-6.encUPS 16.6YesYesConfigurableSMT1059SMT1059UPS_16-5.encUPS 16.5YesYesConfigurableSMT1060SMT1060UPS_02-0.encUPS 02.0YesYesConfigurableSMT17SMT17UPS_07-1.encUPS 07.1NoNoEnabledSMT18SMT18UPS_15-1.encUPS 15.1NoNoConfigurableSMT20SMT20UPS_15-0.encUPS 15.0NoNo ConfigurableSMTL1026SMTL1026UPS_15-5.encUPS 15.5YesYesConfigurableSMTL1047SMTL1047UPS_16-5.encUPS 16.5YesYesConfigurableSMTL1064SMTL1064UPS_01-8.encUPS 01.8YesYesConfigurableSMX1003SMX1003UPS_15-0.encUPS 15.0NoNoConfigurableSMX1031SMX1031UPS_15-6.encUPS 15.6NoYesConfigurableSMX1050SMX1050UPS_16-6.encUPS 16.6NoYesConfigurableSMX20SMX20UPS_15-0.encUPS 15.0NoNoConfigurableSMX23SMX23UPS_15-0.encUPS 15.0NoNoConfigurableSRT1001*SRT1001UPS_02-9.encUPS 02.9NoNoEnabledSRT1002SRT1002UPS_15-1.encUPS 15.1NoNoDisabledSRT1010SRT1010UPS_15-5.encUPS 15.5NoYesEnabledSRT1013SRT1013UPS_15-1.encUPS 15.1NoNoDisabledSRT1014SRT1014UPS_15-1.encUPS 15.1NoNoDisabledSRT1019SRT1019UPS_15-5.encUPS 15.5NoYesEnabledSRT1020SRT1020UPS_15-8.encUPS 15.8NoYesEnabledSRT1021SRT1021UPS_15-6.encUPS 15.6NoYesEnabledSRT1024SRT1024UPS_15-6.encUPS 15.6NoYesEnabledSRT1025SRT1025UPS_15-5.encUPS 15.5NoYesEnabledSRTL1024SRTL1024UPS_15-6.encUPS 15.6NoYesEnabledSRTL1034SRTL1034UPS_10-1.encUPS 10.1YesYesEnabledSRTL1035SRTL1035UPS_10-1.encUPS 10.1YesYesEnabledSRTL1062SRTL1062UPS_10-1.encUPS 10.1YesYesEnabledSRTL1063SRTL1063UPS_10-1.encUPS 10.1YesYesEnabledSRTL1226**SRTL1226UPS_3-8.encUPS 03.8NoYesEnabledSRTL1227**SRTL1227UPS_01-2.encUPS 01.2NoYesEnabledSRYL1225***SRYL1225UPS_18-0.encUPS 18.0NoYesEnabledXP1016XP1016UPS_15-1.encUPS 15.1NoNoEnabledXU1017XU1017UPS_15-7.encUPS 15.7NoYesDisabledXU1025XU1025UPS_15-5.encUPS 15.5NoYesEnabledXU1033XU1033UPS_15-7.encUPS 15.7NoYesDisabled Notes: *For SRT UPS models with ID of 1001, the UPS firmware must be updated in two steps. First update the UPS firmware using SRT1001UPS_02-9.enc. This will change the UPS ID to 1013. Once the update to UPS 02.9 is completed, perform the firmware update again using SRT1013UPS_15-0.enc.** For SRTL UPS models with ID 1226 & 1227, always perform a Logic Reset or "Brain Dead" before initiating the firmware update. Refer to FAQ000269051 for more information.*** For SRTL UPS models with ID 1225, refer to FAQ000261838 for additional update instructions.It is not recommended to perform a firmware downgrade to a lower firmware version.In rare situations, the UPS firmware update may not install automatically after the firmware file was transferred to the UPS. Refer to FAQ000258690 to complete the UPS firmware update.For more information about enabling or disabling firmware updates via the NMC for the UPS models that support this feature, refer to FAQ00024438.Once firmware updates via the NMC have been disabled, attempts to update the UPS firmware using the NMC will be refused:For SRYL (Smart UPS Modular Ultra), if upgrading from 13.2 or greater you may put the UPS into Manual Bypass. See Set the UPS to Manual Bypass Mode section in the Smart UPS Modular Ultra Manual. Step 6 – The majority of UPS models support firmware update with output on. Refer to the above table, and if you have a UPS that supports firmware update with output on, go to Step 7.NOTE: For UPS devices that require the UPS output to be off before initiating the update, ensure that network access is not dependent on the UPS for power, when updating via the Network Management Card.If network access is dependent on the UPS for power, refer to FA279197 for instructions on updating the UPS firmware using the Firmware Upgrade Wizard.If network access is not dependent on the UPS for power, ensure the attached load is correctly shut down before proceeding with turning off the UPS output.Use the command to turn off the UPS output, then use the command to verify the UPS output status:Step 8 Via SCP:Use the command to disconnect from the SSH or Telnet session:Copy the UPS firmware file to the NMC using the following command:NOTE: This SSH command is for OpenSSH. The command may differ depending on the SSH tool used. In this example, the file will be copied to the “tmp” folder on the NMC.Via FTP:FTP may be disabled by default on the NMC, and must be enabled before continuing.Use the command to enable FTP and use the command followed by to reboot the NMC and apply the changes.Use the command to disconnect from the SSH or Telnet session:Using an FTP client of your choice, FTP the UPS firmware file onto the “tmp” folder on the NMC.Here’s an example of loading a UPS firmware file onto the “tmp” folder on the NMC using Windows Command Prompt:ftp User (:(none)): NMC UsernamePassword: NMC Passwordftp> binftp> hashftp> cd tmpftp> put “”ftp> quitStep 9 - Reconnect to the NMC, and use the command followed by the command to verify that the file has been copied to the “tmp” folder on the NMC:Initiate the UPS Firmware Update using the command to check the status of the UPS Firmware Update:The update may take several minutes. Once the command returns “Status: No firmware update is in progress”, the UPS firmware update is completed.Verify that the new UPS firmware version is shown using the command:If the update does not complete, or if any errors are displayed, ensure that the conditions in Step 2 are met. Try updating the UPS firmware with the UPS output turned off. If no alarms are shown, try updating the UPS firmware using the Firmware Upgrade Wizard, which can be found in FA279197 .Step 10 – If the UPS output was turned off in Step 6, the UPS output should now be turned back on.Use the command to turn the UPS output back on.The attached load can now be turned on.For any issues encountered during the update process or any additional questions, please contact APC Tech Support.

Question 2

Modbus Slave Communication protocol on PowerLogic P5 Protection Relays

Accepted Answer

Issue: How to configure and use Modbus Slave protocol for PowerLogic P5 relays, including supported modes, function codes, and integration requirements. Product: PowerLogic P5 Protection Relay Environment: SCADA systems using Modbus RTU (RS-485/fiber) or Modbus TCP/IP (Ethernet)Industrial networks with multi-protocol supportConfiguration tools: eSetup Easergy Pro, Web HMI, front panel Cause: Modbus is widely used for simple and reliable data exchange in automation systems. Incorrect configuration of addressing, scaling, or function codes can lead to communication errors, data mismatch, or control failures. Resolution: Protocol Support: Modbus RTU: RS-485/fiber, 1200–115200 bps, 2/4-wireModbus TCP/IP: Ethernet, port 502, up to 3 IP addresses/subnetsSupports up to 8 clients and 4 slave instances Configuration: Set protocol via COMMUNICATION menu or eSetup Easergy Pro/Web HMIParameters: Slave address (1–247), baud rate, parity, scaling, IP filtering Function Codes: 03 (Read Holding), 04 (Read Input), 06 (Write Single), 16 (Write Multiple), 23 (Read/Write Multiple), 07 (Read Exception Status), 08 (Diagnostics), 11 (Comm Event Counter), 43/14 (Device ID), 20 (Disturbance file) Data Model: Extensive register mapping for protection, measurement, control, alarms, events, and settingsData types: Bool, Enum, Int16/32/64, UInt16/32/64, float32, stringScaling examples: 1.00 s = 100, 50.00 Hz = 5000 Features: Real-time measurements, event logs, disturbance recordsControl commands: Open/Close, Select/Execute, latch release, setting group changeClock sync via registers (2504–2507) Security: No encryption; use VLANs, firewalls, IP whitelisting (CIDR, up to 8 entries)Port/protocol enable/disable; sFTP for secure file transfer Integration: Compatible with SCADA, EvoPact HVX, external AI/DI/DOSupports redundancy (PRP, HSR, RSTP) Modbus Point List Check the document named "Powerlogic P5 Protection Relay Communication Manual" available here: FAQ000280966 (look for the Point list in the Modbus Slave Protocol section)

Question 3

DC - שימוש במא"זים ליישום זרם ישר

Accepted Answer

מא"זים מסדרות Acti9 iC60 (N/H/L) מתאימים ליישומי DC, החל מ-12VDC ועד 250VDC, בכפוף למספר הקטבים המחוברים בטור וכושר ניתוק המאושר.ראו בקבצים המצורפים המייצג בטבלה את מספר הקטבים הדרושים כדי להיות מחוברים בטור ביחס למתח האספקה ולכושר הניתוק המושגת. ACTI9 iC60N:ACTI9 iC60H:ACTI9 iC60L:

Question 4

איפה מוצאים רשימת תקלות לווסתים ATV?

Accepted Answer

כאשר ווסת נכנס למצב תקלה, קוד התקלה יופיע בתצוגה. מאפייני קוד התקלה ופתרונה נמצאים במדריך התכנות של הסדרה הרלוונטית. מצורף קבצים.

Question 5

What is meant by Unicast, Multicast, and Broadcast communications over a TCP/IP network?

Accepted Answer

A Unicast communication is from one device on the network to another device on the network. A MultiCast communication is from one device on the network to many, but not all, devices on the network. A Broadcast communication is from one device on the network to all devices on the network.

Question 6

About Unica MGU3.701.xx keys

Accepted Answer

1) How many keys are delivered with the switch? 2 keys are delivered with each product. 2) Are these keys unique (for one device) or all of one series - same? All products have the same key. 3) How and where is possible to order spare keys? Keys are not delivered as spare parts. 4) Where can be removed the key? In which position? You can remove the key only in 0 position.

Question 7

What is the cause of the EF2 fault code on the ATV21 and ATV212 drives?

Accepted Answer

Issue:ATV212: EF2 FaultProduct line:Altivar ATV212Environment:All models, all serial numbersCause:Ground Fault on the output of the drive.Resolution:EF2= Ground FaultTroubleshooting tips Check the motor ground connections. Make sure the ground is going to the chassis of the drive.Remove the motor leads from the drive and Megger with a 1KV Megger to see if there is a short to ground in the motor windings. Reference the ATV212 programming manual S1A53838 (attached).

Question 8

How do we configure a Varlogic RT controller?

Accepted Answer

Following is a general QuickStart for basic configuration of the RT6, RT8 or RT12 controllers. For detailed explanations, please find the user manual attached to the FAQ. Wiring Wiring must be done according to schematic found on page 1 section 4. The CT must be mounted to P1. P2 must be connected to the 400V terminal. P3 must be connected to the 0V terminal. This is important as the controller uses the connections to take the correct readings and apply the power factor correction required. Configuration The following are the minimum required information for programming the controller. - Number of capacitors (steps). - Capacitor values from smallest to largest. - CT primary value. Must be 5 at the secondary of the CT (see page 4, section 6.8). Here are the paramaters to be configured. - 5.3 -> CosPHI - 5.5 -> STEP - 5.6 -> PROGRAM - 5.7 -> C/K - 5.8 -> CT Entering program mode, press SET button for 3 seconds.UP and DOWN arrows are used to scroll between parameters and modify values.Press SET to enter the parameter adjustment.After adjusting to the required value, pressing SET will accept the new value and the controller returns to normal operating mode. Example Configuration Configure the RT6 with the following known information. - Number of capacitors (steps) = 5 - Capacitor values (kVAR) = 12, 12, 25, 33, 33 - CT = 1250/5 5.3 -> CosPHI = 0.95 This value is provided by the client, integrator or may be kept at default. 5.5 -> STEP = 5 5.6 -> Pro9 = PS9 This is given by the ratios available on page 3 of the manual (section 6.4). The ratios all based on the first capacitor value. For this example, the ratios are: 1:1:2:3:3. It is an approximation and some cases may be possible for 2 program selections. From the table gives PS9 for our ratio. 5.7 -> C/K = 0.05 This can be attained from the table on page 4, section 6.6. Look down the CTR column and across to the first capacitor step value. It may also be calculated by the following formula:

מרכז תמיכה

מרכז הורדות

מרכז תמיכה

מרכז הורדות

מרכז תמיכה

מרכז הורדות

מוצרים

תמיכה

חברה

קישורים מהירים

שותפים

קיימות

אירועים

תובנות
opens new tab