Category Archives: Schneider Electric

AS-BDAU-204 Analog Output Module

December 22, 2016Modicon, Schneider Electric, WiringAS-BDAU-204, ASBDAU204, BDAU-204, DAU204jadmin

AS-BDAU-204 Wiring

For this module, use 60/75 copper (Cu) for the power connections and 4.5 in-lb. of torque for the set screws.
To prevent errors in field device operation, follow these guidelines:

Use shielded, twisted-pair cable (such as Belden 9418).
Ground the shield of each signal cable at the AS-BDAU-204 only. At the other end of each signal cable, peel back the shield and insulate it from contact with the signal-carrying wires.
Route each signal cable as far as possible from the sources of electrical noise (such as motors, transformers, contactors, and especially AC drives.
If the signal cables must corss AC or power cables, ensure that they cross at right angles.
When connecting field devices to the module, keep the unshielded portions of the signal-carrying wires as short as possible

After wiring the terminal blocks, use the supplied keys to prevent the blocks from being switched inadvertently.

DAU-204 Wiring Diagram: The following illustration is a wiring diagram and simplified schematic for the DAU-204 analog output module.

We reccomend that you connect the AS-BDAU-204 to the same 24 Vdc power supply being used to power the PLC (even if the module is in the rack but not being used). If this is not possible, we recommend that you supply power to the PLC before the DAU 204 using a power supply similar to the P120 (quick startup voltage). Failture to observe this precaution can cause abnormal operation.

Ensure that the voltage loads driven by the module can tolerate transients during rack and module startup. During startup, transients as great as 2 V may appear on the voltage output terminals for as long as 5 ms due to the characteristics of semiconductor devices. This does not occur with the module’s current output terminals.

Terminals 3, 5, 9, and 11 (- current out, and – voltage out) are internally tied as a group. Terminals 14, 16, 20, and 22 (- current out, and – voltage out) are internally tied as a group. Be sure not to cross groups.

You should short all unused current output terminals to disable the red current loop LEDs and alarm bit.

MRO Stock stocks a large number of AS-BDAU-204’s. To order a replacement/spare, or for technical support, call 800-691-8511 or email sales@mrostock.com

140CPS11420 Manual Anthologies

August 11, 2016Manual, Modicon, Schneider Electric140cps11420, 140cps11420 manual, modicon 140cps11420jadmin

140CPS11420: Manual Anthologies

Click now to visit our Modicon 140CPS11420 Product Page

There exists some important design differences between various models of Quantum power supplies that require careful consideration by the system designer in order to achieve maximum system performance. The principal difference lies in the generation within the power supply of important backplane signals related to the health of the power supply and the status of the input power. All Quantum power supplies include on-board early power fail detection logic which is used to signal all other modules on the backplane that input power has failed. This signal is called POK (power OK) and is active high (i.e., when the signal is high, power is OK). There is both an internal (to the power supply) and an external (as seen by the backplane and all other modules) version of the POK signal. The internal POK signal is represented by the Pwr ok LED (light emitting diode) on the front panel of all power supplies. The system POK signal is generated so that there is sufficient time between the negative going edge of system POK (power has failed) and the actual interruption of power to the backplane. This early warning of power failure is necessary for the Quantum executive to perform an orderly system shutdown.

The 140CPS11420 is a Summable Power Supply. A summable power supply may be used as a standalone power supply without reservation in any Quantum system.

Continue reading 140CPS11420 Manual Anthologies →

140NOE77101 Firmware Executive Release Notes

July 22, 2016Firmware, Modicon, Schneider Electric140NOE77101, 140NOE77101 Executive Release Notes, 140NOE77101 Firmware, 140NOE77101 Firmware Executive Release Notesjadmin

140NOE77101 Firmware Executive Release Notes (V5.4-V6.7)

Click Now to Visit our 140NOE77101 Product Page.

V6.7

2/24/2016

Problem fixed / Enhancement

Details

Improves Global Data and IO Scanner performance after a swap over in a Hot Standby System

Removed a Remote Code Execution vulnerability in the websSecurityHandler (Advisory ICSA-15-351-01)

V6.6

10/19/2015

Problem fixed / Enhancement

Details

Removed a web server vulnerability to a remote file inclusion attack. (ICS-ALERT-15-224-02)

When using I/O Scanner control bits to turn On/Off I/O Scanner entries, it can intermittently cause the NOE to reboot causing a 20 second outage of Ethernet communications. Corrected the control bit disable feature from forcing the I/O Scanner state machine to finish.

V6.5

8/15/2015

Problem fixed / Enhancement

Details

In a Hot Standby system, Global Data services may stop after a switchover of the PLC.
Issue has been managed with updated code. Refer to the Global Data Addendum for further details.

Enhancement

Resolves Java 1.8 issues.

V6.4

12/12/2014

Problem fixed / Enhancement

Details

After an application download via Concept,the NOE77101 IO Scanner communications does not restart. In Unity PLC the NOE will ARP for DUP IP after every Application down load. In Concept the NOE will only ARP if the IP parameters have changed when Concept logs out. The Health Timeout timer is stopped on a Link Down,so the Health bits are not updated in the CPU. Now the IO Scanner Health Bits will go unhealthly on link down and not glitch on Link Up.

V6.3

9/5/2014

Problem fixed / Enhancement

Details

MBP_MSTR block reports an error 1001 after an application download. During an application download, the IP component was temporarily applying the broadcast IP which disrupted the MSTR block. Code modifications were made and the MSTR block works as expected.

V6.2

6/30/2014

Problem fixed / Enhancement

Details

In HTTP using directory traversals an attacker can bypass the basic authentication mechanism. (Advisory ICSA-14-273-01) Checks have been put in so that this is no longer possible.

Web page issue with Java Version 1.7. Files did not have security signature. The Java dialog box provides a warning indicating that this is a unsigned application. The files all have been properly signed.

On Hot Standby switchover, under extremely high traffic loads, there was a possibility that the NOE would not come online. Situation was corrected and the NOE comes online regardless of the traffic.

With a Concept Hot Standby application, under unusual test conditions, there is a chance an NOE could lose its IP address. The NOE module will configure its IP address under those conditions.

Quantum CPU may crash with error EC0E after completing a download of an application. Fixes a potential CPU EC0E crash issue where configuration data was not cleared when a smaller program was downloaded over a larger one that was previously installed. I/O Scanner configuration data is now cleared before the new data is downloaded and reconfigured.

V6.1

11/11/2013

Problem fixed / Enhancement

Details

SNMP webFailedAttempts (1.3.6.1.4.1.3833.1.5.4) and webSuccessfulAccess (1.3.6.1.4.1.3833.1.5.4) do not The MIB structure and MIB Agent have been corrected. webSuccessfulAccess (1.3.6.1.4.1.3833.1.5.4) do not increment

Client communications do not start on swap over in HSBY system On swap over, the communications now start as soon as possible after the switchover

When Using code 15 in a MBP_MSTR function block the first Fixed the first request fault condition.

When the IO Scanner breaks out FC23 to FC16 and FC3, any change to the data being written in FC16 will toggle between the old and new data for a number of scans. The function sends the correct data in all messages

I/O scanner using a Radio Modem cannot establish contact. The timeout algorithm was adjusted to accomadate low communication data rates.

Client communications do not start on swap over in HSBY system On swap over, the communications now start as soon as possible after the switchover

After a cable pull, communications does not re-establish with certain Moxa or Sixnet switches Communications now resumes when the cable is reinserted.

V6.0

3/30/2013

Problem fixed / Enhancement

Details

This is a special security release. The Unity configuration features listed require Unity hotfix V7.0_HF20050608

Enhancement

The default behavior of enabled FTP/TFTP and HTTP Service at module boot up has changed On power up the NOE module will have the FTP/TFTP servers and HTTP service enabled when in non-configured mode, or when configured by an older version of Unity Pro/DTM that does not have FTP/HTTP Cyber Security control.
Concept will not have any changes to enable/disable FTP/TFTP or HTTP in the configuration. When using Concept, both FTP/TFTP and HTTP will be enabled in the configuration at all times allowing MSTR to control the enable/disable of the services.

The MSTR block now supports the OpCode 0xFFF0 to be used by the user to enable and disable FTP/TFTP and HTTP services in the module on-the-fly, when Unity has enabled the service.
Once the enabled state of the services are changed by a MSTR they remain unchanged until the next MSTR block call with OpCode 0xFFF0, or the load of a new application, or the module is reset/power cycled . This OpCode works on Concept and Unity controller installations. In Concept the Web server/pages must be updated by the user to be able to control HTTP state of enable/disable, using the file NOE77101_WEB.zip. Bring the Web version up to V5.00 or above.

New Log Out Web Page Users click on Diagnostics and go to Controller Status in the side menu. Below the applet is the logout button.

Web Restrictions: When the FTP is disabled and HTTP is enabled there will be some Web restrictions as they require a FTP access.

Data Editor/Viewer is not fully functional: the user does not have the ability to save or retrieve tables, or get variables from the namespace.

When FTP/TFTP is disabled the corresponding ports 21(FTP), and 69(TFTP) are be closed . If the ports have an open connection when the MSTR is executed to disable FTP, the connection is be closed.

V5.4

12/20/2012

Problem fixed / Enhancement

Details

NOE77101 connection closure mechanism can cause error 6003 in M1E MSTR function block. A special socket option was added to all Modbus server connections called “No Linger” to facilitate HSBY switchovers. However that state was inadvertently added to two paths which caused the problem seen

Communications gradually degrades then stop after running for about 16 months. Due to mishandling of a 32 bit timer overflow in the stack as the timer approached the overflow point the performance of the NOE would degrade and at the point of overflow it would stop. It would recover on its own.

In Quantum Ethernet modules I/O Scanning causes excessive ARP traffic when using a gateway. Each line of an I/O scanner issues its own ARP prior to establishing a connection. This can cause excessive traffic for a router or gateway. The I/O scanner will now issue an ARP for each IP address rather than for each line of the scanner. This will eliminate multiple ARPS to the same device.

If the cable is pulled from the Ethernet port and notreconnected for approximately 70 hours or longer, the connection is not re-established. A slow memory leak, caused by the web server polling the port resulting in a lack of resources, was corrected.

Enhancement

OpCode 16 to close connections available for Concept. Request for functionality similar to Unity where OpCode 16 in the MBP_MSTR block aborts the Ethernet connections.

Thank you for reading our post on the 140NOE77101 Firmware Executive Release Notes.

You can call 1-800-691-8511 or email sales@mrostock.com to request a 140NOE7701 price quote.

140CPU43412A Firmware Part II

July 21, 2016Firmware, Modicon, Schneider Electric140Cpu43412A, 140Cpu43412A firmware, modicon 140Cpu43412A, modicon 140Cpu43412A firmwarejadmin

Phase 1 of firmware restoration is described in our previous blog post on the 140CPU43412A firmware.

140CPU43412A Firmware Part II

Restoring a 140CPU43412U (Unity) to 140CPU43412A (Concept):

Phase 2

During the download:

• Do not power OFF the PLC

• Do not power OFF the PC

• Do not disconnect the cable

• Do not shut down OS loader

Any loss of communication during the update procedure can cause severe damage to the CPU or NOE module. Failure to follow these instructions can result in injury or equipment damage.

Reset the PLC

Once the download of the intermediate binary file has completed, the PLC has to be initialized. This task can be performed by one of the two following actions: Reset the PLC by pushing on the Restart button located on the CPU (for more information, refer to the PLC technical documentation). Power OFF then ON the PLC. Once the PLC has restarted, go to Phase 3: download the final Concept OS.

Phase 3

Presentation

The final binary file “q5rv135E.bin ” (140CPU34312 in our example) has to be downloaded. For that, follow the same procedure as the one described in the Phase 1.

Checking Version (optional)

If needed, you can check the new CPU version. For that Open the OS loader tool. Select the communication protocol. Click on “Connect.” Then Click on “Properties.”

For ordering info or for a 140CPU43412A price quote you can call 1-800-691-8511 or email sales@mrostock.com.

140CPU43412A

140CPU43412A Firmware Part I

July 20, 2016Firmware, Modicon, Schneider Electric140Cpu43412A, 140Cpu43412A firmware, modicon 140Cpu43412A, modicon 140Cpu43412A firmwarejadmin

140CPU43412A Firmware Restoration

In order to restore firmware in a 140CPU43412U (Unity) to a 140CPU43412A (Concept), three main phases are required.

Phase 1 – Restore the PLC to Concept with an intermediate OS.

Phase 2 – Power OFF then ON the PLC.

Phase 3 – Restore the Operating System with the appropriate file.

These phases are mandatory and cannot be by-passed.

Phase 1:

Launching the OS Loader

The OS loader (provided with Unity) allows the user to download the Operating System to the PLC. To open it click on Start/Program/SchneiderElectric/Unity-PRO/OS loader.

Select the Communication Protocol

From the main screen of the OS loader, click on the “Next” button. To download the Operating System into the PLC, select the right communication protocol (in accordance with established physical link) and click on the “Next” button.

Select the Target Device

On the Device Type field, select Processor and the other needed parameters (Modbus address….). Then connect to the selected PLC (Node).

Select the Download Function

From the screen described above press the “Next” button. A new screen is proposed: select “Download OS to device”.

Select the File to be Downloaded

Click on the “Browse…” button in order to select the file to download into the PLC. In this example we will restore the OS from 140CPU43412U to 140CPU43412A firmware. For that select the following folders: Quantum\Processor_modules\Unity_to_Concept. To restore the OS from Unity to Concept, two binary files can be selected: Unity_to_Concept_43412A.bin (allows to “format” the processor to Concept) q5rv135E.bin is the OS that will finally be downloaded in the processor. In our example we have to “format” the processor (remember, we still are in the Phase 1) then select and Validate “Unity_to_Concept_43412A.bin”. Once done click on the “Next” button.

Download the Intermediate OS

Once the previous screen is validated a warning is displayed: Click the “Okay” button. Two screens that give information regarding the file, the processor and the download are now displayed. Note: If the system detects a discrepancy on the hardware or on the OS version, the download will not be possible. This is indicated by a red cross and the “Next” button becomes unavailable. Solve this issue and continue. When the hardware – OS are compatible, click on the “Download” button to launch the download of the intermediate OS file.

Click for the MRO Stock Blog Post on 140CPU43412A Firmware Part II