Micro800 Programmable Controllers - Rockwell...

Release Notes

Micro800 Programmable ControllersCatalog Numbers Bulletin 2080, firmware revision 10 or earlier

About This PublicationThese release notes supplement the existing documentation supplied with your product.

Read this document before using Micro800® controllers.

Firmware Revision HistoryThe latest firmware revision for your Micro800 controllers can be downloaded from the Rockwell Automation Product Compatibility and Download Center website athttp://www.rockwellautomation.com/rockwellautomation/support/pcdc.page

Topic Page

About This Publication 1

Firmware Revision History 1

Features 5

Anomalies 19

Additional Resources 47

IMPORTANT This publication contains information on firmware revision 10 or earlier.For information on firmware revision 11 or later, refer to publication 2080-RN004.

http://www.rockwellautomation.com/rockwellautomation/support/pcdc.page

http://literature.rockwellautomation.com/idc/groups/literature/documents/rn/2080-rn004_-en-e.pdf

2 Micro800 Programmable Controllers

Firmware Revision History for Micro810® Controllers

Revision Description

1.011(1)

(1) This firmware revision is obsolete and is no longer available for download.

First revision release

1.012(1) Minor revision release

1.013 Minor revision release

2.011 Major revision release





Firmware Revision History for Micro820™ Controllers


6.011(1)


First major revision release










Rockwell Automation Publication 2080-RN001T-EN-P - March 2018

Micro800 Programmable Controllers 3



1.011(1)


First revision release

1.012(1) Minor revision release














2.011 First revision release


4.012, Minor revision release






Firmware Backward CompatibilityMicro800 firmware is always backward compatible with previous revisions. It is not necessary to flash downgrade a controller to a previous revision to match an earlier project revision. For example, a Connected Components Workbench™ project configured with a controller revision of 2.xxx can be downloaded into a controller with firmware revision 2.xxx or higher. It is, however, recommended that you always upgrade to the latest software, as older software revisions cannot recognize newer firmware revision controllers when discovering, uploading, and downloading.

Availability of Enhancements and Anomaly FixesEnhancements are available in the controller only if the controller is at the required firmware revision or higher, and the Connected Components Workbench project contains a controller configured with the required firmware revision or higher. If the project contains a controller revision that is lower than the required revision for an enhancement, then the project is still valid but the enhancement will not be available until the project is upgraded to the minimum supported revision.

Fixes for firmware anomalies will be available as long as the controller firmware revision is at the minimum revision or higher. The configured controller revision in the project does not matter.

The following tables provide a list of enhancements, known anomalies, and corrected anomalies for the Micro800 firmware revisions.








Features

Enhancements for Micro810 Controllers

Enhancement(1)

(1) See Micro810 User Manual, publication 2080-UM001 for more information.

Description Available From FirmwareRevision

Various software features support

This firmware release also supports these features – Retentive Timer On-Delay (RTO) and Micro810 LCD Variable Display.See the latest Connected Components Workbench software release notes for more information.

7.011

Controller security Controller password can be enforced to restrict access to the programming software connection to the controller.

2.011

Power failure handling

When the power failure routine is not completed properly, controller Fault 0xF000 will be reported at next powerup. If the system variable __SYSVA_USER_DATA_LOST is set, the controller is able to recover the user program, but user data is cleared. User Program is copied to backup Flash memory when there is User Program change in the controller as downloaded from Connected Components Workbench or restored from Memory Module.If a Hard Fault occurs, after power cycle, user can recover the user program if the system variable __SYSVA_USER_DATA_LOST is set

2.015

German language support on the LCD

German language support is now available on the LCD menu.

2.015


http://literature.rockwellautomation.com/idc/groups/literature/documents/um/2080-um001_-en-e.pdf



Enhancement(1) Description Available From FirmwareRevision

Ethernet configuration retained after power cycle

Ethernet configuration, including the IP address, is retained after you cycle power to the controller.

10.011

Indirect bit addressing support

Indirect bit addressing allows the use of a variable to index though the bits of an integer. For example, Data.[x]. This method uses up less memory than using a boolean array. This support has been added to aid migration for MicroLogix users.

10.011

Performance improvement for RMC

This firmware release improves the performance of RMC. For typical applications, average improvements are:• 40% for test logic• 45% for undo• 60% for accept• 35% for uploadActual performance improvement depends on the project, PC, and communications interface.Connected Components Workbench Developer Edition release 10 or later software is required.

10.011

Performance improvement for project Download and Build

This firmware release improves the performance when downloading a project by around 58%, and build by 60% on average.Actual performance improvement depends on the project, PC, and communications interface.Connected Components Workbench release 10 or later software is required.

10.011

User Defined Functions (UDF) support

A UDF is similar to a traditional subroutine and uses less memory than a UDFB. This support has been added to aid migration for MicroLogix users.Connected Components Workbench release 10 or later software is required.

10.011



Ethernet configuration and password can be saved during firmware upgrade or downgrade

This firmware release supports the saving of the controller’s Ethernet configuration and password by default when performing a firmware upgrade or downgrade.The Ethernet configuration and password are not saved when downgrading from Release 10 to Release 9 or earlier, or when upgrading from Release 9 to Release 10 or later.Connected Components Workbench release 10 or later software is required if you want to clear the Ethernet configuration and password using the Update Firmware feature.

10.011

Optional module option for plug-in I/O and expansion I/O modules

Plug-in I/O and expansion I/O modules can be configured to not fault the controller when they are not physically installed. This is similar to the MicroLogix “Ignore Configuration Error” option.This option can be configured independently for each plug-in I/O and expansion I/O module.Added the MODULE_INFO instruction, which is used to verify the presence of a module.

10.011

PID instruction added

The PID instruction is similar to the MicroLogix instruction for the parameter names and configuration. Does not natively support autotune.

10.011

Communication access to bits of integers

This feature is for writing bits of an integer using the CIP Read-Modify-Write service (0x4E).Typically used by HMI terminals.

10.011

Communication access to Date and Time data types

To set the date and time in the controller or to set timer presets.Typically used by HMI terminals.

10.011

Data protection for project download and restore

This feature allows user defined global variables to have their values protected and not overwritten during project download or restore. This only applies to variables that are identical for both projects.

10.011





FIFO instructions added

FFL and FFU instructions added.These instructions have been added to aid migration for MicroLogix users.

10.011

Wall Clock Time change in Run Mode

The real time clock can now be updated during run mode over CIP protocol and through the user program using a Loopback message.

10.011

BSL and BSR instructions added

Bit Shift Left (BSL) and Bit Shift Right (BSR) are enhanced versions of the Shift Left and Shift Right instructions. These instructions have been added to aid migration for MicroLogix users.

9.011

Sockets communication protocol support

Sockets protocol is used for Ethernet communications to devices which do not support Modbus TCP and Ethernet/IP. Sockets support UDP and TCP client and server.

9.011

Run Mode Configuration Change (RMCC)

Run Mode Configuration Change (RMCC) allows users to reuse an identical program with multiple controllers on the same network. RMCC can be used to change the static Ethernet address and Modbus RTU Slave address from the user program in run mode.

9.011

Performance improvement for Datalogging and Recipe

This firmware release improves the performance of the Datalogging and Recipe features. For typical applications, datalogging can now occur once every two seconds.

8.011

Bit access of integer array elements support

This firmware release supports bit access of integer array elements for Micro820 controllers.

8.011

CIP passthrough to DeviceNet using 2080-DNET20 DeviceNet scanner plug-in support

Micro820 controllers support CIP generic messaging passthrough to a DeviceNet network using the 2080-DNET20 DeviceNet scanner plug-in.It is now possible to browse using RSLinx from the computer to the controller to DeviceNet.A 2080-DNET20 plug-in with firmware revision 2.011 or later is required.

8.011





Update controller firmware from microSD card

This firmware release enables the controller to be flash updated from the microSD card, in addition to using ControlFLASH.

8.011

Run Mode Change (RMC)

Run Mode Change (RMC) enables the user to make logic modifications to a running project without going to remote program mode and without disconnecting from the controller.Connected Components Workbench Developer Edition release 8 or later software is required.

8.011

Micro820 Series B controller support

This firmware release adds support for Micro820 Series B controllers.

7.014

PanelView Plus Variable/Tag browsing support

With release 8.00 of FactoryTalk View Studio, PanelView Plus can communicate to Micro800 controllers using CIP symbolic and can be used in place of Modbus addressing.

7.011

Open Platform Communications (OPC) support

Micro800 controllers support Open Platform Communications (OPC) using CIP symbolic and can be used in place of Modbus addressing.RSLinx Enterprise version 5.70 (CPR9 SR7) is required.

7.011


This firmware release also supports these features – Retentive Timer On-Delay (RTO) and Data Value Upload/Download.

7.011

2080-DNET20 DeviceNet scanner plug-in support(2)

The DeviceNet plug-in serves as scanner and client for explicit messaging to remote devices. The module can scan devices such as CompactBlock™ LDX, PowerFlex® drives, E1Plus overloads, and stacklights.User-defined function blocks (UDFB)(3) are required to configure the plug-in and scan the network.

6.011(5)





2080-MOT-HSC High-speed Counter plug-in support(2)

The high-speed counter plug-in provides enhanced high speed counter capabilities to the Micro800 controller. It supports up to 250 kHz differential line driver for improved noise immunity.User-defined function blocks (UDFB)(3) are required to configure and use the high-speed counter plug-in.

6.011(5)

2080-REMLCD Remote LCD module support

The Remote LCD module serves as a simple operator interface supporting ASCII text. It is an accessory to the Micro820 controller. It allows easier configuration of such controller settings as IP address.

6.011(5)

microSD™ card slot Industrial grade(4) microSD cards are supported through an embedded microSD card slot on Micro820 controllers. The microSD card enables project backup and restore, as well as datalogging and recipe, on Micro820 controllers.

6.011(5)

Datalogging and Recipe

Datalogging and recipe is supported through the DLG and RCP function blocks, respectively.The datalogging feature allows the capture of global and local variables with timestamp from the Micro800 controller into the microSD card. The recipe feature allows storage and loading of a list of data to and/or from a recipe data file on the microSD card.

6.011(5)

Backup and restore through the microSD card

Project backup and restore are supported on Micro820 controllers through the microSD card.

6.011(5)





Powerup settings through ConfigMeFirst.txt file

Controller settings on powerup can be set through the optional ConfigMeFirst.txt file in the microSD card. This configuration file contains such parameters as IP address, subnet mask, gateway, and directories for backup, restore, datalog and recipe.For detailed information about ConfigMeFirst.txt file and powerup settings on the Micro820 controller, see the Micro820 Programmable Controllers User Manual, publication 2080-UM005.

6.011(5)

Error codes specific to Micro820

The following error codes have been added for the Micro820 controllers. These codes indicate that power down information in persistent memory may not be written properly due to a noisy environment or an internal hardware failure.• OxF030• OxF031• OxF032• OxF033If the system variable __SYSVA_USER_DATA_LOST has been be set, the controller will be able to recover the user program but the user data will be cleared. If not, the Micro800 controller program will be cleared.

6.011(5)

(1) For more information, see the following User Manuals:- Micro820 Programmable Controllers User Manual, publication 2080-UM005 - Micro800 Plug-ins User Manual, publication 2080-UM004.

(2) Micro820 controllers support all Micro800 plug-in modules, except for the 2080-MEMBAK-RTC plug-in.

(3) UDFBs and sample Micro800 programs for Connected Components Workbench can be downloaded from the Sample Code Library: http://www.rockwellautomation.com/go/scmicro800.

(4) The slot supports Class 6 and 10 SDSC and SDHC microSD cards, with FAT32/16 formats, 32 GB maximum size. Micro820 controllers do not support Class 4 microSD cards.







http://www.rockwellautomation.com/go/scmicro800



Enhancements for Micro830 and Micro850 Controllers

Enhancement Description Available From FirmwareRevision

Indirect bit addressing support

Indirect bit addressing allows the use of a variable to index though the bits of an integer. For example, Data.[x]. This method uses up less memory than using a boolean array. This support has been added to aid migration for MicroLogix users.

10.011

Performance improvement for RMC

This firmware release improves the performance of RMC. For typical applications, average improvements are:• 40% for test logic• 45% for undo• 60% for accept• 35% for uploadActual performance improvement depends on the project, PC, and communications interface.Connected Components Workbench Developer Edition release 10 or later software is required.

10.011

Performance improvement for project Download and Build

This firmware release improves the performance when downloading a project by around 58%, and build by 60% on average.Actual performance improvement depends on the project, PC, and communications interface.Connected Components Workbench release 10 or later software is required.

10.011

User Defined Functions (UDF) support

A UDF is similar to a traditional subroutine and uses less memory than a UDFB. This support has been added to aid migration for MicroLogix users.Connected Components Workbench release 10 or later software is required.

10.011



Ethernet configuration and password can be saved during firmware upgrade or downgrade

This firmware release supports the saving of the controller’s Ethernet configuration and password by default when performing a firmware upgrade or downgrade.The Ethernet configuration and password are not saved when downgrading from Release 10 to Release 9 or earlier, or when upgrading from Release 9 to Release 10 or later.Connected Components Workbench release 10 or later software is required if you want to clear the Ethernet configuration and password using the Update Firmware feature.

10.011

Optional module option for plug-in I/O and expansion I/O modules

Plug-in I/O and expansion I/O modules can be configured to not fault the controller when they are not physically installed. This is similar to the MicroLogix “Ignore Configuration Error” option.This option can be configured independently for each plug-in I/O and expansion I/O module.Added the MODULE_INFO instruction, which is used to verify the presence of a module.

10.011

PID instruction added

The PID instruction is similar to the MicroLogix instruction for the parameter names and configuration. Does not natively support autotune.

10.011

Communication access to bits of integers

This feature is for writing bits of an integer using the CIP Read-Modify-Write service (0x4E).Typically used by HMI terminals.

10.011

Communication access to Date and Time data types

To set the date and time in the controller or to set timer presets.Typically used by HMI terminals.

10.011

Data protection for project download

This feature allows user defined global variables to have their values protected and not overwritten during project download. This only applies to variables that are identical for both projects.This feature was first available in firmware revision 7.011 but only for project restore.

10.011





FIFO instructions added

FFL and FFU instructions added.These instructions have been added to aid migration for MicroLogix users.

10.011

Wall Clock Time change in Run Mode

The real time clock can now be updated during run mode over CIP protocol and through the user program using a Loopback message.

10.011

BSL and BSR instructions added

Bit Shift Left (BSL) and Bit Shift Right (BSR) are enhanced versions of the Shift Left and Shift Right instructions. These instructions have been added to aid migration for MicroLogix users.

9.011

Sockets communication protocol support for Micro850 controllers

Sockets protocol is used for Ethernet communications to devices which do not support Modbus TCP and Ethernet/IP. Sockets support UDP and TCP client and server.This feature is available for Micro850 controllers only.

9.011

Run Mode Configuration Change (RMCC) for addresses

Run Mode Configuration Change (RMCC) allows users to reuse an identical program with multiple controllers on the same network. RMCC can be used to change the static Ethernet address (Micro850 only) and Modbus RTU Slave address from the user program in run mode.

9.011

Bit access of integer array elements support

This firmware release supports bit access of integer array elements for Micro830/Micro850 controllers.

8.011

CIP passthrough to DeviceNet using 2080-DNET20 DeviceNet scanner plug-in support

Micro830/Micro850 controllers support CIP generic messaging passthrough to a DeviceNet network using the 2080-DNET20 DeviceNet scanner plug-in.It is now possible to browse using RSLinx from the computer to the controller to DeviceNet.A 2080-DNET20 plug-in with firmware revision 2.011 or later is required.

8.011





High Speed Counter (HSC) Feedback Axis

High Speed Counter (HSC) Feedback Axis provides similar functionality to PTO Motion Axis and is more efficient and easier to use.Connected Components Workbench release 8 or later software is required.

8.011

Run Mode Change (RMC)

Run Mode Change (RMC) enables the user to make logic modifications to a running project without going to remote program mode and without disconnecting from the controller.Connected Components Workbench Developer Edition release 8 or later software is required.

8.011

PanelView Plus Variable/Tag browsing support

With release 8.00 of FactoryTalk View Studio, PanelView Plus can communicate to Micro800 controllers using CIP symbolic and can be used in place of Modbus addressing.

7.011

Open Platform Communications (OPC) support

Micro800 controllers support Open Platform Communications (OPC) using CIP symbolic and can be used in place of Modbus addressing.RSLinx Enterprise version 5.70 (CPR9 SR7) is required.

7.011


This firmware release also supports these features – Retentive Timer On-Delay (RTO), Data Value Upload/Download, and Data Protection.

7.011

2080-DNET20 DeviceNet scanner plug-in support

The DeviceNet plug-in serves as scanner and client for explicit messaging to remote devices. The module can scan devices such as CompactBlock™ LDX, PowerFlex® drives, E1Plus overloads, and stacklights.User-defined function blocks (UDFB)(1) are required to configure the plug-in and scan the network.

6.011

2080-MOT-HSC high-speed counter plug-in support

The high-speed counter plug-in provides enhanced high speed counter capabilities to the Micro800 controller. It supports up to 250 kHz differential line driver for improved noise immunity.User-defined function blocks (UDFB)(2) are required to configure and use the high-speed counter plug-in

6.011





RS-485 serial port for ASCII communication

The RS-485 serial port supports ASCII communications on Micro800 controllers from firmware revision 6.011.

6.011

PWM function PWM function is added via PTO motion parameter 1005. The duty cycle of the PTO can now be set using MC_WriteParameter. The value ranges from 0...100, indicating 0…100%.

6.011

PTO motion parameters 1006 and 1007

PTO motion parameters 1006 and 1007 are added to read Pulses per Revolution and Unit per Revolution configuration in user program.

6.011

Additional error code: OxF019

This error code pertains to unexpected software error due to memory or other controller resource issue.

6.011

Additional error codes: 0xF017 and 0xF018

The following error codes have been added:• 0xF017 for unexpected hardware interrupt• 0xF018 for SPI communication failureIf the system variable __SYSVA_USER_DATA_LOST has been set, the controller will be able to recover the user program but the user data will be cleared. If not, the Micro800 controller program will be cleared.

6.011

CIP Generic and CIP Symbolic client messaging

CIP Generic and CIP Symbolic client messaging support is made available through the addition of two function blocks to the instruction set: MSG_CIPGENERIC and MSG_CIPSYMBOLIC. CIP Messaging is available on all serial (including embedded, plug-in) and Ethernet communication ports.

4.011

Modbus TCP client function on Micro850 controllers

On Micro850 controllers, support for Modbus TCP client function is available through the addition of the MSG_MODBUS2 function block.This feature is not available for Micro830 controllers.

4.011





Memory Copy function

The addition of the COP function block enables support for memory copy across data types. This function block is typically used in conjunction with the client messaging instructions. Source and destination must be a complete array with an optional offset.From firmware revision 7.011 onwards, this function block no longer requires an array for the source and destination.

4.011

Digital I/O plug-in module support

This firmware revision supports the configuration and upload of digital I/O plug-ins through Connected Components Workbench. I/O global variables are automatically generated for the inputs and outputs.Previous method of using RA_2080_IQ4x and RA_2080_O4x user-defined function blocks to configure the digital I/O modules (supported on earlier firmware revision 2.xxx), can still work with firmware revision 4.xxx, but will not work in conjunction with the digital I/O configuration feature in firmware revision 4.xxx. This means that on firmware revision 4.xxx, users are only allowed to either use the previous method of configuration (through user-defined function blocks) or the new method (through Connected Components Workbench configuration interface), but not both at the same time.An error will be reported by the function block should conflict occur.

4.011

1 GAIN renamed to MOV

1 GAIN instruction for setting one variable equal to another variable of the same data type is renamed to MOV for easier reference. 1 GAIN is no longer available from revision 4.xxx projects onwards.

4.011

Motion control Firmware revision 2.xxx supports motion control configuration on certain Micro830 and Micro850 controllers.This feature is supported through embedded Pulse Train Outputs (PTO) on Micro830 and Micro850 controllers with catalog numbers that end in QVB and QBB.

2.011





Expansion I/O support

Micro850 controllers with firmware revision 2.xxx can support up to four expansion I/O configuration.

2.011

Communication connections

The following communication protocols are supported with firmware revision 2.xxx:• Modbus/TCP Server (Micro850 controllers only

through Ethernet channel)• CIP Serial Server (RS-232 only)• EtherNet/IP Server (Micro850 controllers)These communication protocols are supported through the RS-232 and RS-485 communication channels and the RJ-45 Ethernet port.

2.011

Controller security Controller password can be enforced to restrict access to the programming software connection to the controller.

2.011

Digital output variables

All digital output variables driven by the IO scan gets cleared on powerup or during transition to RUN mode.

2.011

0xF000 and 0xF002 Fault Handling on Powerup

Controller attempts to recover user program and clear user variables upon powerup.

2.011

(1) UDFBs and sample Micro800 programs for Connected Components Workbench can be downloaded from the Sample Code Library: http://www.rockwellautomation.com/go/scmicro800.




http://www.rockwellautomation.com/go/scmicro800


Anomalies

Known and Corrected Anomalies for Micro810 Controllers

Anomaly Description Affected Firmware Revision

Corrected Firmware Revision

Copy operation copies unwanted variable data

If a copy instruction has been configured with a size larger than the source variable, the copy operation will also include data from other variables.

APBC00023033

7.011

Variables not retained after power cycle

Variables for which the Retain checkbox have been checked are sometimes not retained after power cycle.

APBC00025089

7.011 7.012

Blank LCD screen during power up

When the controller is powered up, the LCD displays a blank screen and communication is not allowed.

APBC00025393

7.011 7.012

L00 information displays on LCD

The LCD screen displays the indicator L00, which is no longer applicable for Micro810 controllers.

APBC00021869

7.0112.0152.0122.0111.0131.0121.011

7.012

Controller returns 0xF004 fault when memory module is cleared and then restored

When the memory module is cleared and then restored from the LCD menu, the controller reports the 0xF004 fault.In firmware revision 7.012, the following error codes have been added to provide a more detailed fault description:• 0xF300 - The memory module is empty.• 0xF301 - The memory module's project

is not compatible with the controller.• 0xF302 - The memory module password

is mismatched.• 0xF303 - The memory module is not

present.APBC00011470

7.0112.0152.0122.0111.0131.0121.011

7.012



OS Series value in SYS_INFO block shows wrong controller series

The OS Series value in the SYS_INFO function block does not display the correct controller series.

APBC00021580

2.0152.0122.011

7.011

Controller with program in memory module malfunctions when power cycled during firmware flash process

Controller will malfunction when power cycled during a firmware downgrade if a program is stored in the memory module with Load Always setting configured.

IMPORTANT: Do NOT power cycle the controller during the ControlFLASH process.

APBC00021101

2.0152.0122.011

7.011

Changes to retained user variable values are lost upon exit of Program Debug mode

For retained user variables, any changes made in Debug mode to the value while in Program mode will be lost when transitioning to Run mode.

APBC00020327

2.0152.0122.011

7.011

Analog input calibration offset must be positive

Analog input calibration only accepts positive values (or zero) when set from Connected Components Workbench or in the 2080-LCD. Negative values should also be supported.

APBC00019113

2.0152.0122.0111.0131.0121.011

7.011

Controller faults when restoring an older project from memory module to a controller containing a project created with Connected Components Workbench revision 6.00

Project restore (from a memory module that contains a project created by a pre-revision 6.00 Connected Components Workbench) will fail on a Micro810/Micro830/Micro850 controller with firmware revision 1.xxx or 2.xxx that has a project created by Connected Components Workbench revision 6.00 or later. A fault will be reported by the controller. Users are advised to clear the fault and power cycle the controller and then repeat the restore action.

APBC00019099

2.0152.0122.0111.0131.0121.011

7.011






Incorrect conversion of REAL/LREAL variables using Any_To_String

Any_To_String instruction converts REAL/LREAL variables erroneously. The conversion result has no proper data truncation and is incorrect for certain patterns, such as 0.0123456.

APBC00018944

2.0152.0122.011

7.011

KEY_READ function block reads keystrokes even while in system menu

The KEY_READ function block, when used in a program, is supposed to read keystroke values ONLY when USER_DISPLAY is being displayed. Instead, it also registers keypad activity when the LCD enters system menu (pressing ESC+OK), as well as while scrolling through the menu, acknowledging settings.

APBC00015368

2.0152.0122.011

7.011

LCD displays unwanted characters and the controller resets when editing locked variables

When editing I/O variables through the LCD and the variables are locked in Connected Components Workbench, the LCD displays unwanted characters and the controller resets.

APBC00019918

2.0122.011

2.015

Flag “F” disappears after page change in LCD

Flag “F” disappears from LCD after shifting from one page to another.

APBC00018917

2.0122.011

2.015

TONOFF instructions do not work properly at maximum value

TONOFF instructions do not work properly at their maximum value.

APBC00017580

2.0122.011

2.015

Watchdog timer less than 10 ms causes controller fault

The controller goes into a fault when watchdog timer value entered is less than 10 ms.

APBC00017561

2.0122.011

2.015






Misleading PwrUp Behavior menu options in LCD

Setting a controller to go to Program Mode through the LCD PwrUp Behavior menu does not take effect upon controller powerup. Instead, the controller assumes its last state before powerup.

APBC00017287

2.0122.011

2.015

F004 fault when controller with firmware revision 2.xxx backs up firmware revision 1.xxx project through LCD

Micro800 controllers with firmware revision 2.xxx goes into a fault when backing up project created with revision 1.xxx firmware using LCD. Fault F004 is displayed.

APBC00015719

2.0122.011

2.015

No I/O force indication

There is no I/O force indication on the LCD display I/O status screen.

2.0111.0131.0121.011

2.012

User application cannot back up and restore

A project configured with a revision 1.xxx controller cannot be backed up or restored successfully using the LCD module with a firmware revision 2.011 controller.

APBC00014192

2.011 2.012

Password mismatch status is not correct

Password mismatch status is not correct after power cycle if Load on Error is set.

APBC00011949

2.011 2.012

Wrong language on localized LCD options

Certain menu strings still display in English on localized (French, Italian, Spanish) LCD menu display.

APBC00013978

2.0111.0131.0121.011

2.012

LCD instruction causes controller fault

When the LCD instruction switches between user defined and default I/O status screens (for example, Enable input parameter goes from FALSE to TRUE or from TRUE to FALSE), there is a possibility that the controller faults and is no longer in run mode.

APBC00013978

2.0111.0131.0121.011

2.012






Incomplete home URL string in EDS file

The EDS file includes incomplete home URL string.

APBC00009490

2.0111.0131.0121.011

2.012

ErrorMode parameter does not handle errors

ErrorMode input of IPIDCONTROLLER instruction does not handle errors as expected and does not recognize any input values.

APBC00006755

1.0131.0121.011

2.011

RHC instruction in Micro810 controllers is not accurate

The RHC function block uses a time base of 49.86 μs and returns counter times 5, instead of a 40 μs timer with a return counter times 4.

APBC00005186

1.012 1.013

The controller may report a fault (error code 0xD011) when continuously powered on for more than 49.71 days

Under certain conditions, when the controller is continuously powered on for more than 49.71 days, the controller may report a recoverable fault (error code 0xD011), and the outputs are disabled. Certain time based instructions may not operate correctly within the 3 ms window immediately following 49.71 days.On Micro810 controllers, the power LED goes off. The LCD display changes from RUN mode to FAULT mode. On Micro830 controllers, the fault LED flashes red.

APBC00006019 / KnowledgeBase ID 450489

1.011 1.012







Anomaly Description Affected Firmware Revisions


[CF] command in ConfigMeFirst.txt file changes “Clear fault” startup setting of Connected Components Workbench project

The [CF] command in the ConfigMeFirst.txt file changes the startup setting of the Connected Components Workbench project in the controller from “Clear fault” to “Do not clear fault”. This change remains even when the microSD card is removed.

62861

10.01210.0119.0118.0117.0147.0137.0116.0156.0126.011

Controller sends ARP broadcasts even if Detect duplicate IP address field is unchecked

The controller sends ARP broadcasts even if the Detect duplicate IP address field in the Connected Components Workbench project is unchecked.

14620/APBC00030176/APBC00022647

10.01210.0119.011

CIP connection timeout outside ODVA specification required time

When the RPI value is large (for example 1 second or 10 seconds), the CIP connection timeout resolution will be outside the ODVA specification (CIP Node on EtherNet/IP CT13) required time of 250 milliseconds. Workaround is to use RPI values less than 400 milliseconds.

14617/APBC00029838

10.01210.0119.0118.0117.0147.0137.0116.0156.0126.011

Firmware upgrade over serial port appears to fail

When you upgrade the firmware revision over a serial port, an error appears to indicate that the process has failed even if the upgrade is successful.

14588/APBC00028240

10.01210.011



Premature AutoTune failure

IPIDCONTROLLER allowable time duration to complete AutoTune sequence becomes progressively shorter for each subsequent AutoTune after project download. A workaround is to re-download the project to avoid premature AutoTune failure.

14536/APBC00023007

10.01210.0119.0118.0117.0147.0137.0116.0156.0126.011

Connection to REMLCD module lost after changing embedded port setting from Modbus back to CIP Serial

After changing the embedded port setting from Modbus back to CIP Serial, connection is lost to the REMLCD module.Workaround is to power cycle the controller.

14527/APBC00022582

10.01210.0119.0118.0117.0147.0137.0116.0156.0126.011

TCP retry timeout Currently, TCP retry timeout is set to 1 second and is not adjustable. Performance may degrade under heavy load because the retry timeout may be too long.In Connected Components Workbench revision 7.00 you can examine the Ethernet diagnostic counters, specifically “MAC Received Errors”. This counter indicates that receive packets are being dropped by the controller due to heavy load. Reduce communications load to reduce the number of errors.

14517/APBC00021805

10.01210.0119.0118.0117.0147.0137.0116.0156.0126.011






Pass-through of connected CIP messages with more than one class and instance will fail

When Micro800 controller is the intermediate node for CIP pass-through of connected messages, messages with more than one class and instance will fail. (For example, Studio 5000 download of a CompactLogix program over USB to Micro800 which passes through over EtherNet/IP to a CompactLogix controller is not supported.)

14506/APBC00021406

10.01210.0119.0118.0117.0147.0137.0116.0156.0126.011

Long Real data values used on DLG that are either too big or too small affect scan time performance

Scan time is significantly longer when the program includes execution of one DLG function block that is configured with multiple Long Real data values which are either extremely huge (that is, >> ±1.0E+50), or extremely small (that is, -1.0E-50 << value <0, or +1.0E-50 >> value > 0).

14486/APBC00019047

10.01210.0119.0118.0117.0147.0137.0116.0156.0126.011

UID and UIE instructions cancel pending user interrupts

If a user interrupt such as STI occurs within a UID and UIE zone, the interrupt is canceled instead of going to the pending state and the interrupt will not execute after the UIE instruction.

14435/APBC00028977

10.01210.0119.0118.0117.0147.0137.0116.0156.0126.011

MSG_MODBUS instruction’s Q output is not cleared after controller is power cycled

After power cycling the controller, the MSG_MODBUS instruction’s Q output should be cleared but it is not. If there is logic that assumes the Q output is cleared, it will not operate properly. For example, using the Q output to re-trigger the instruction when false.For Micro820 controllers, this issue is only encountered if the “Retained” flag is enabled for the MSG_MODBUS instance.

14413/APBC00024636

10.01210.0119.0118.0117.0147.0137.0116.0156.0126.011






Output turns off for one program scan when RTC_SET is enabled

When the RTC_SET instruction is enabled during the program scan, the embedded digital and analog output turns off. The affected output returns to the correct output state in the next program scan. Embedded inputs and Plug-in inputs/outputs are not affected by this anomaly.

17236

10.0119.0118.0117.0147.0137.0116.0156.0126.011

10.012

Controller faults when performing RMC after power cycle

After downloading a project and performing an RMC that is accepted, if the controller is power cycled, the next RMC will fault the controller.For example:Download -> RMC with Accept -> Power Cycle -> RMC with two Test Logic -> Fault

APBC00028857

9.011 10.011

A false error may occur when UDFB input parameters are used for SOCKET_READ

When SOCKET_READ is inside a UDFB, input parameters to the UDFB cannot be directly used as inputs to the SOCKET_READ for Length and Offset because a false error may occur, “ErrorID code of 10, sub ErrorID code of 7”.Workaround is to avoid using SOCKET_READ inside a UDFB or use constants for the SOCKET_READ inputs.

APBC00027545

9.011 10.011

RSLinx Classic takes a long time to discover a Micro800 controller over Ethernet.

When RSlinx Classic is trying to discover a Micro800 controller that is connected using Ethernet, the process takes a long time.Workaround is to append “:EIP” to the end of the IP address. For example, 10.116.36.88:EIP.

APBC00027300

9.0118.0117.0147.0137.0116.0156.0126.011

10.011






TCP connection does not close immediately when CIP connection is closed

When the ConnClose attribute is set to TRUE, MSG_CIPGENERIC and MSG_CIPSYMBOLIC closes the CIP connection but the TCP connection had to wait for 60 seconds to timeout.

APBC00025290

9.0118.0117.0147.0137.0116.0156.0126.011

10.011



APBC00023033

9.0118.0117.0147.0137.0116.0156.0126.011

10.011

IPIDCONTROLLER derivative gain setting not applied

When IPIDCONTROLLER's Derivative action is disabled (Gain.TimeDerivative or Gain.DerivativeGain is set to 0.0), the derivative action is no longer applied even if the derivative action is re-enabled.Workaround is to download the project again with Gain.TimeDerivative and Gain.DerivativeGain not set to 0.0)

APBC00021654

9.0118.0117.0147.0137.0116.0156.0126.011

10.011

Controller with firmware revision 8.011 faults when restorsing a project backup made by a controller with an earlier firmware revision from the microSD card

When a controller with firmware revision 8.011 tries to restore a project backup made by a controller with firmware revision 6.xxx or 7.xxx from the microSD card, the operation fails and the controller reports an F004 fault.Workaround is to download the project again to the controller with firmware revision 8.011 or later and backup the project to the microSD card.

APBC00024957

8.011 9.011






Unable to restore project from microSD card although indicated as compatible in Connected Components Workbench

Connected Components Workbench indicates that the project is compatible and can be restored but actually the project is not in the correct directory on the microSD card. This problem occurs only after changing the name of the controller in the project.Users are advised to backup the project to the microSD card. The project will be placed in the correct directory.

APBC00024178

8.0117.0147.0137.0116.0156.0126.011

9.011

Controller faults when changing EtherNet/IP configuration after restoring project from the memory module or microSD card

The controller goes into a hard fault when changing the EtherNet/IP configuration after a project is restored from the memory module or microSD card.

APBC00022547

7.0147.0137.0116.0156.0126.011

8.011

REMLCD backlight briefly turns on before startup message

When backlight is configured using LCD_BKLT_REM for the REMLCD module, the backlight briefly turns on in blue color before it displays the startup message.

APBC00018544

7.0147.0137.0116.0156.0126.011

8.011

Hard fault on controller when card is removed during backup and restore

The controller goes into a hard fault when the microSD card is removed while backup and restore is in progress. (The hard fault is indicated by a solid red Fault LED indication.)Users are advised to power cycle the controller and clear the fault to recover the controller.

APBC00017761

7.0147.0137.0116.0156.0126.011

8.011

MicroSD card sometimes cannot be detected after the controller is power cycled

When the controller is power cycled, sometimes the MicroSD card cannot be detected.Users are advised to eject and re-insert the card if this issue is encountered.

APBC00022457 / APBC00024190

7.0137.0116.0156.0126.011

7.014






SD LED indicator may remain off on card insertion

It may be observed, in very rare instances, that the SD LED indicator may remain off when a good microSD card is inserted, instead of lighting On.Users are advised to eject and re-insert the card if this issue is ever encountered.

APBC00021567

7.0137.0116.0156.0126.011

7.014

The controller may report a fault when powered up from out of the box

Under rare occasions, the controller may boot up with a fault and display an incomplete catalog name in RSLinx.

APBC00023804

7.0116.015

7.013

Modbus RTU errors due to slow interrupt performance

Performance of interrupt latency increased if multiple interrupts occur at the same time with high frequency. This is mainly visible with Modbus RTU communications with baud rates higher than 9600 baud, resulting in transmit and receive errors.

APBC00022568

6.0156.0126.011

7.011

Controller does not turn off PWM output in invalid status condition and after downloading a new program

The PWM On parameter and PWM Enable parameter during invalid status conditions are set to FALSE. However the controller does not turn off the PWM output after downloading the program or when these conditions occur.

APBC00021616

6.0156.0126.011

7.011

Occasional 0xF004 fault when doing a project backup or restore

When backing up or restoring a project from the microSD card, the operation may occasionally fail with a 0xF004 fault.

Users are advised to clear the fault and repeat the operation.

APBC00021596

6.0156.0126.011

7.011

Changes to retained user variable values are lost upon exit of Program Debug mode

For retained user variables, any changes made in Debug mode to the value in Program mode will be lost when transitioning to Run mode.

APBC00020327

6.0156.0126.011

7.011






Analog input calibration offset must be positive

Analog input calibration only accepts positive values (or zero) when set from Connected Components Workbench or in the 2080-REMLCD. Negative values should also be supported.

APBC00019116

6.0156.0126.011

7.011



APBC00018944

6.0156.0126.011

7.011

Communication breaks if project backup or restore fails

Ethernet and/or serial ports communication may not work when project back up or restore fails. Users are advised to power cycle the controller to recover the connection.

APBC00018288

6.0156.0126.011

7.011

Error message “Memory card is not present” takes approximately 30 seconds to be displayed after card is ejected

“Memory Card is not present” message in Connected Components Workbench takes some time (approximately 30 seconds) to display after card has been ejected. The delay is only observed when ongoing upload or search of datalog or recipe files activities is interrupted by card ejection. The delay is attributed to card read/write retries.

APBC00017978

6.0156.0126.011

7.011

SD LED continues to blink after card is ejected

SD LED indicator continues to blink for a couple of seconds after card is ejected while datalog, recipe, backup, and restore activities are in progress. This continuous blinking is due to SD card read/write retries.

APBC00017751

6.0156.0126.011

7.011






RTC module may run for a short time when controller is powered down

When the controller is powered down, the RTC module may run for less than four days at room temperature.

APBC00020912

6.0126.011

6.015

Fault LED indicator continues to blink red even after fault is cleared

Micro820 controller Fault LED indicator continuously blinks red even after fault is cleared in Connected Components Workbench.

APBC00020240

6.011 6.012

Data retention fails in certain scenarios

There is a possibility of loss of retained user data or loss of initial values for retained variables, in one of the following situations:• when the controller encounters a loss

of power, or power dip, during powerup; or

• if the controller does not enter Run mode before it is powered down.

APBC00020085

6.011 6.012

KEY_READ_REM function block fails to reset output in certain condition

The KEY_READ_REM function block is unable to reset its output when the ENABLE input of the instruction goes from TRUE to FALSE.

APBC00019913

6.011 6.012

KEY_READ_REM function block reads keystrokes even while in system menu

The KEY_READ_REM function block, when used in a program, is supposed to read keystroke values ONLY when USER_DISPLAY is being displayed. Instead, it also registers keypad activity when the LCD enters system menu (pressing ESC+OK), as well as while scrolling through the menu, acknowledging settings.

APBC00020267

6.011 6.012






Known and Corrected Anomalies for Micro830 and Micro850 Controllers



Controller faults 0xF293 even if correct expansion I/O generic configuration is downloaded(Micro850 only)

After you correct a configuration error that previously existed in an expansion I/O module, a 0xF293 fault code (Expansion IO Module Fault) appears when you download the project to the controller.As a workaround, without changing the configuration, download the project to the controller again.

43065

10.0119.011

Controller sends ARP broadcasts even if Detect duplicate IP address field is unchecked(Micro850 only)

The controller sends ARP broadcasts even if the Detect duplicate IP address field in the Connected Components Workbench project is unchecked.

14620/APBC00030176

10.0119.0118.0117.0116.0114.0134.0124.0112.011

CIP connection timeout outside ODVA specification required time

This anomaly applies to Micro850 controllers only.When the RPI value is large (for example 1 second or 10 seconds), the CIP connection timeout resolution will be outside the ODVA specification (CIP Node on EtherNet/IP CT13) required time of 250 milliseconds. Workaround is to use RPI values less than 400 milliseconds.

14617/APBC00029838

10.0119.0118.0117.0116.0114.0134.0124.0112.0111.0131.0121.011

Premature AutoTune failure

IPIDCONTROLLER allowable time duration to complete AutoTune sequence becomes progressively shorter for each subsequent AutoTune after project download. A workaround is to re-download the project to avoid premature AutoTune failure.

14536/APBC00023007

10.0119.0118.0117.0116.011



TCP retry timeout for Micro850 controller

Currently, TCP retry timeout is set to 1 second and is not adjustable. Performance may degrade under heavy load because the retry timeout may be too long.In Connected Components Workbench revision 7.00 you can examine the Ethernet diagnostic counters, specifically “MAC Received Errors”. This counter indicates that receive packets are being dropped by the controller due to heavy load. Reduce communications load to reduce the number of errors.

14517/APBC00021805

10.0119.0118.0117.0116.0114.0134.0124.011

RSLinx unable to browse for CIP bridge device from controller plug-in module slot 4 and 5

When a serial plug-in module is connected to controller slot 4 or 5, RSLinx cannot browse to the device.

14496/APBC00020409

10.0119.0118.0117.0116.011

CIP messaging communication may be affected by cable break

For CIP messaging client function, if there is one or more devices with a cable break, the messaging client connection with other devices may become slower, with possible timeouts.This may happen if multiple messages are pending due to the cable break.

14462/APBC000015030

10.0119.0118.0117.0116.0114.0134.0124.011

UID and UIE instructions cancel pending user interrupts

If a user interrupt such as STI occurs within a UID and UIE zone, the interrupt is canceled instead of going to the pending state and the interrupt will not execute after the UIE instruction.

14435/APBC00028977

10.0119.0118.0117.0116.0114.0134.0124.0112.0111.0131.0121.011






MSG_MODBUS instruction’s Q output is not cleared after controller is power cycled

After power cycling the controller, the MSG_MODBUS instruction’s Q output should be cleared but it is not. If there is logic that assumes the Q output is cleared, it will not operate properly. For example, using the Q output to re-trigger the instruction when false.

14413/APBC00024636

10.0119.0118.0117.0116.0114.0134.0124.0112.0111.0131.0121.011

Controller faults when performing RMC after power cycle

After downloading a project and performing an RMC that is accepted, if the controller is power cycled, the next RMC will fault the controller.For example:Download -> RMC with Accept -> Power Cycle -> RMC with two Test Logic -> Fault

APBC00028857

9.011 10.011






Instructions added or deleted during RMC does not run after memory backup and restore

When adding or deleting any instructions during RMC, then performing a memory backup and restore after the RMC, the modification does not take effect.For example, when performing the following operation:1. Download LD program with single

TON_1 instance.2. Power cycle the controller.3. Go to RMC mode and add new TON_2

instance, then test and accept changes.

4. Backup project to memory module.5. Restore project from memory module.

The new TON_2 instance does not run.The anomaly only occurs on the controller which created the backup in the memory module.Workaround is after RMC, disconnect from the controller, then do a build, download, and backup.

APBC00028794

9.0118.011

10.011

A false error may occur when UDFB input parameters are used for SOCKET_READ (Micro850 only)

This anomaly applies to Micro850 controllers only.When SOCKET_READ is inside a UDFB, input parameters to the UDFB cannot be directly used as inputs to the SOCKET_READ for Length and Offset because a false error may occur, “ErrorID code of 10, sub ErrorID code of 7”.Workaround is to avoid using SOCKET_READ inside a UDFB or use constants for the SOCKET_READ inputs.

APBC00027545

9.011 10.011






RSLinx Classic takes a long time to discover a Micro800 controller over Ethernet.

When RSlinx Classic is trying to discover a Micro800 controller that is connected using Ethernet, the process takes a long time.Workaround is to append “:EIP” to the end of the IP address. For example, 10.116.36.88:EIP.

APBC00027300

9.0118.0117.0147.0137.0116.0156.0126.011

10.011

TCP connection does not close immediately when CIP connection is closed

This anomaly applies to Micro850 controllers only.When the ConnClose attribute is set to TRUE, MSG_CIPGENERIC and MSG_CIPSYMBOLIC closes the CIP connection but the TCP connection had to wait for 60 seconds to timeout.

APBC00025290

9.0118.0117.0116.0114.0134.0124.011

10.011



APBC00023033

9.0118.0117.0116.0114.0134.0124.011

10.011

IPIDCONTROLLER derivative gain setting not applied

When IPIDCONTROLLER's Derivative action is disabled (Gain.TimeDerivative or Gain.DerivativeGain is set to 0.0), the derivative action is no longer applied even if the derivative action is re-enabled.Workaround is to download the project again with Gain.TimeDerivative and Gain.DerivativeGain not set to 0.0)

APBC00021654

9.0118.0117.0116.0114.0134.0124.0112.0111.0131.0121.011

10.011






Controller faults after a different project is downloaded if the previous project was not downloaded successfully

A controller without a plug-in module is disconnected while downloading a project that includes a plug-in module. The next time a project without a plug-in module is downloaded, the controller will report a fault.Users are advised to download the project again to clear the fault.

APBC00014130

9.0118.0117.0116.0114.0134.0124.0112.011

Fixed in Connected Components Workbench Release 9 or later.

Last PTO output state is not completed when changing PTO frequency on the fly

When changing velocity parameters on the fly using the MC_MoveVelocity function block, the current PTO output frequency does not complete its last state before changing to the new frequency.This anomaly is fixed in firmware revision 8.012 for Micro830 controllers only.This anomaly is fixed in firmware revision 9.011 for Micro830 and Micro850 controllers.

APBC00025702

8.0117.0116.0114.0134.0124.0112.011

9.0118.012(Micro830 only)

Controller faults when changing EtherNet/IP configuration after restoring project from the memory module

The controller goes into a hard fault when changing the EtherNet/IP configuration after a project is restored from the memory module.

APBC00022547

7.0147.0137.0116.0156.0126.011

8.011

Duplicate IP address error display remains after new configuration is downloaded to the controller

Connected Components Workbench still displays the duplicate IP address error even after a new IP address has been configured and downloaded to the controller.Users are advised to reconnect the Ethernet cable to the controller after downloading the new configuration.

APBC00021290

7.011 8.011






Unable to obtain IP address automatically using DHCP

Controller is unable to obtain an IP address automatically using DHCP after downloading the program if a previous program had a valid IP address configured and the port state was set to disabledUsers are advised to set the port state to Disabled and save the configuration to the controller, then set the port state to Enabled and save the configuration to the controller.

APBC00020966

7.0116.011

8.011

Modbus RTU errors due to slow interrupt performance

Performance of interrupt latency increased if multiple interrupts occur at the same time with high frequency. This is mainly visible with Modbus RTU communications with baud rates higher than 9600 baud, resulting in transmit and receive errors.

APBC00022568

6.0114.0134.0124.0112.011

7.011

OS Series value in SYS_INFO block shows wrong controller series

The OS Series value in the SYS_INFO function block does not display the correct controller series.

APBC00021580

6.0114.0134.0124.0112.011

7.011

Restore function does not work again after a successful restore operation

Using the restore from memory module function a second time does not work when performed immediately after a successful restore operation.

APBC00021041

6.011 7.011

Memory Module backup operation fails and may cause a hard fault in the controller

If a Memory Module backup operation is performed on a controller that has been running for a long time, the operation fails and the controller will report a 0xF004 fault.

APBC00020596

6.011 7.011



APBC00018944

6.011 7.011






DN and Error bits do not go false on certain ASCII instructions

For some ASCII communications instructions, the DN and error output status bits do not go false when the instruction enable IN goes false. Done and Error status should immediately go false if IN is false. ACL status will never go false once true. ARD, ARL, AWA, AWT will go false only if IN goes false and then true.

APBC00015308

4.0134.0124.0112.0111.0131.0121.011

6.011

Possible data packet loss with Ethernet communication(1)

A heavily loaded Ethernet communication, with the client sending multiple message requests simultaneously, may result in data packet loss on a Micro850 controller. Connection timeouts may consequently occur. Other connections with other devices are not affected. This issue can happen to both client and server function. Client should only have one pending message to avoid this issue.

APBC000015191

4.0134.0124.011

6.011

CIP Symbolic and CIP Generic messages not supported on Logix serial port

MSG_CIPSYMBOLIC and MSG_CIPGENERIC are not supported on connected client messaging via serial communication when connected to a CompactLogix™ or ControlLogix® embedded serial port.A Micro800 controller as server and a Logix controller as client is supported.

APBC000014851

4.0134.0124.011

6.011

CIP symbolic pass-through not supported

CIP Symbolic pass-through fails with Micro800 as an intermediate bridge using unconnected messages. For example, with Micro850 controller, it is not possible to send an unconnected CIP symbolic message from device A to B with the Micro850 controller as a bridge in the middle. Connected messaging is supported.

APBC000014849

4.0134.0124.011

6.011






Micro800 serial ports do not support control lines

ASCII: Micro800 serial ports do not support control lines RTS and CTS, even though configuration is available for ASCII and Modbus RTU in the software.

APBC000014284

4.0134.0124.0112.0111.0131.0121.011

6.011

Axis Decelerating flag turns on for non-zero jerk moves while axis is accelerating

For a move from ConstantVelocity or Standstill state, if the jerk is not equal to 0, the Deceleration status is set for one Motion Engine interval before the axis starts to accelerate. The Deceleration and Acceleration flag do not turn on at the same time.This anomaly only occurs when program scan time is less than the Motion Engine interval.

APBC00011729

4.0134.0124.0112.011

6.011

ASCII connection only works with RS-232 interface

The ASCII protocol for Micro800 controllers only supports RS-232 media. The RS-485 interface is not supported.

APBC00011336

4.0134.0124.0112.0111.0131.0121.011

6.011

Controller faults when restoring an older project from memory module to a controller containing a project created with Connected Components Workbench revision 6.00

Project restore (from a memory module that contains a project created by a pre-revision 6.00 Connected Components Workbench) will fail on a Micro810/Micro830/Micro850 controller with firmware revision 1.xxx or 2.xxx that has a project created by Connected Components Workbench revision 6.00 or later. A fault will be reported by the controller. Users are advised to clear the fault and power cycle the controller and then repeat the restore action.

APBC00017367

2.0xx1.0xx

4.0xx






Embedded serial port may shut down on powerup

It has been observed that the embedded serial port shuts down if the controller encounters power supply disruption at a certain time after powerup.

APBC000016906

4.0124.0112.011

4.013

CIP Serial communication on embedded serial port may be temporarily disrupted

CIP Serial server and client messaging via Micro830 and Micro850 controller embedded serial port is disrupted for 15...16 seconds before resuming normal operation.This may happen when CIP Serial communication is operating continuously for more than 17 days.

APBC000015297

4.0112.011

4.012

CIP Serial client messaging to a PC running RSLinx software is not supported

CIP Serial client messaging (CIP Symbolic or CIP Generic) to a PC running RSLinx software is not supported. The controller may stop all communication functions with other communication ports when such unsupported messages are sent continuously.

APBC000015243

4.011 4.012

ASCII communication buffer is not cleared

A new program download should automatically clear the buffer for ASCII serial communication messages but the buffer does not get cleared.

APBC00009305

2.0111.0131.0121.011

4.011

Incomplete home URL string in EDS file

The EDS file includes an incomplete home URL text string.

APBC000009490

2.0111.0131.0121.011

4.011

Password mismatch status is not correct

Password mismatch status is not correct after power cycle if Load on Error is set.

APBC00011949

2.011 4.011

ErrorMode parameter does not handle errors

ErrorMode input of IPIDCONTROLLER instruction does not handle errors as expected and does not recognize any input values.

APBC00006755

1.011 2.011






ControlFlash firmware update results in a red flashing fault

Even when a ControlFlash update is successful, the Micro800 controller shows a fault code of 0xF004 (Memory Module transfer error), and the status indicator flashes red. This occurs when the firmware update is performed on a controller with a physical Memory module inserted, and with a user program in that memory module which has the “Load Always” or “Load Always on Memory Error” set.Clear the fault and use the controller normally.

APBC00005287

1.011 2.011

Modbus configured target address returns illegal address error

A Modbus client read to a valid Modbus boundary address of 65535 in the controller results to an illegal address error in the client.

APBC00007660

1.011 2.011

Fault translation error

Error code is not handled properly as soft fault EP_WDT_EXPIRED (0xD011) in a user interrupt POU is translated as hard fault EP_WDT_HARDFAULT (0xF002).

APBC00007864

1.011 2.011

STI configuration reloaded when UID and UIE are used

STI is erroneously disabled and then reloaded whenever UID and UIE are used so STI program may not execute at the configured periodic rate.Both UID and UIE functions are normally used to mask and unmask user interrupts in the user program to prevent conflict with simultaneous references to the same variables.

APBC00007923

1.011 2.011






CRC errors and timeouts in Modbus packet communications

When using the MSG_MODBUS instruction to communicate with any other Modbus Slave devices that require turnaround delay, setting TriggerType in LocalCfg to 1 may cause increased failure rates in modbus packets received/transmitted. Introduce a turnaround delay, such as 5 ms, at a user program level.

APBC00005317 / APBC00005339

1.011 1.013

High Speed Counter (HSC) instruction configuration causes controller Hard Reset

The following conditions may cause a controller Hard Reset.

• Value of HSCAppData underflow setting (UFSetting) and low preset setting (LPSetting) more than or equal to 0.

• Value of HSCAppData overflow setting (OFSetting) and high preset setting (HPSetting) less than or equal to 0.

• Setting the HSC user interrupt parameter for underflow (Mask for IN) to True, when counting up with HSC Mode 0 or 1.

APBC00005342

1.011 1.013

High Speed Counter (HSC) user interrupt does not work for 10/16-point controllers

HSC ID HSC1 does not work for 2080-LC30-10QVB/QWB, and 2080-LC30-16QVB/QWB.

APBC00005198

1.011 1.013

Universal Plug-In Module (UPM) interrupt configuration causes controller Hard Reset

Adding UPM interrupts in the Interrupt Properties page may cause a controller Hard Reset

APBC00005332 / APBC00005357

1.012 1.013






Generic plug-in module’s controller status byte may report inaccurate information

The Controller Status Byte may inaccurately report an Operation Error during normal RUN mode or on “Power Failure Triggered”.Internally developed UPM modules do not use the Controller Status Byte. Such modules are not affected by this anomaly. Third party UPM modules that are based on the Generic Plug-in module specifications and that use the result of the Controller Status Byte to perform certain actions, however, may be affected.

APBC00007064

1.0121.011

1.013

The controller may report a fault (error code 0xD011) when continuously powered on for more than 49.71 days

Under certain conditions, when the controller is continuously powered on for more than 49.71 days, the controller may report a recoverable fault (error code 0xD011), and the outputs will be disabled. Certain time based instructions may not operate correctly within the 3 ms window immediately after 49.71 days.On Micro810 controllers, the power LED goes off. The LCD display changes from RUN mode to FAULT mode. On Micro830 controllers, the fault LED flashes red.

APBC00006019 / KnowledgeBase ID 450489

1.011 1.012

(1) This anomaly does not apply to Micro830 controllers.






Firmware UpdateInstructions on how to flash update your controller with the latest firmware is provided in the User Manual for your Micro800 controller. See Additional Resources for the link to your online user manual.

To get the latest firmware for your Controller, go to the following links:

• Firmware for Micro810 • Firmware for Micro820 • Firmware for Micro830 • Firmware for Micro850

Look for the Resources tab, then click Firmware to download the latest firmware.

IMPORTANT To successfully flash update your controller over USB when using the ControlFLASH software, connect only one controller to your computer, and do not run ControlFLASH in a virtual machine such as VMware.

IMPORTANT After control flashing the controller, some microSD cards may not be detected. If this issue is encountered, eject and re-insert the card, or power cycle the controller.

WARNINGDo not change the mode of the Micro820 controller using the Remote LCD when flash updating the firmware.


http://ab.rockwellautomation.com/Programmable-Controllers/Micro810





Additional ResourcesThese documents contain additional information concerning related Rockwell Automation products.

You can view or download publications at http://www.rockwellautomation.com/literature/. To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.

Resource Description

Micro810 Programmable Controllers User Manual, publication 2080-UM001

Detailed description of features and how to install and use the Micro810, Micro820, Micro830, Micro850, and Micro870 programmable controllers.Micro820 Programmable Controllers

User Manual, publication 2080-UM005

Micro830, Micro850, and Micro 870 Programmable Controllers User Manual, publication 2080-UM002

Micro800 Programmable Controllers Release Notes (Firmware 11 or later), publication 2080-RN004

Release notes for Micro800 controllers with firmware revision 11 or later.

Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1

Provides general guidelines for installing a Rockwell Automation industrial system.

Product Certifications website, http://www.rockwellautomation.com/products/certification/

Provides declarations of conformity, certificates, and other certification details.





http://www.literature.rockwellautomation.com/idc/groups/literature/documents/in/1770-in041_-en-p.pdf

http://www.rockwellautomation.com/products/certification/

http://www.rockwellautomation.com/products/certification/

http://www.rockwellautomation.com/literature/

http://literature.rockwellautomation.com/idc/groups/literature/documents/rn/2080-rn004_-en-e.pdf

Rockwell Automation Support

Publication 2080-RN001T-EN-P- March 2018

Allen-Bradley, Rockwell Automation, Micro800, Micro810, Micro820, Micro830, Micro850, CompactLogix, ControlLogix, CompactBlock, PowerFlex, Connected Components Workbench, and TechConnect are trademarks of Rockwell Automation, Inc.Trademarks not belonging to Rockwell Automation are property of their respective companies.

Rockwell Automation provides technical information on the Web to assist you in using its products. At http://www.rockwellautomation.com/support/, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.

For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer TechConnect support programs. For more information, contact your local distributor or Rockwell Automation representative, or visit http://www.rockwellautomation.com/support/.

Installation AssistanceIf you experience a problem within the first 24 hours of installation, please review the information that's contained in this manual. You can also contact a special Customer Support number for initial help in getting your product up and running.

New Product Satisfaction ReturnRockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.

Documentation Feedback Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.

United States or Canada 1.440.646.3434

Outside United States or Canada

Use the Worldwide Locator at http://www.rockwellautomation.com/support/americas/phone_en.html, or contact your local Rockwell Automation representative.

United StatesContact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor to complete the return process.

Outside United States Please contact your local Rockwell Automation representative for the return procedure.

Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400

Rockwell Automation maintains current product environmental information on its website athttp://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page

Supersedes Publication 2080-RN001S-EN-P - June 2017 Copyright © 2018 Rockwell Automation, Inc. All rights reserved.

http://www.rockwellautomation.com/locations/

http://www.rockwellautomation.com/support/americas/phone_en.html

http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page

http://www.rockwellautomation.com/support/

http://www.rockwellautomation.com/support/

http://www.rockwellautomation.com/literature/

Micro800 Programmable Controllers - Rockwell...

Documents

Transcript of Micro800 Programmable Controllers - Rockwell...