2080 rn001 - en P

Release Notes
Micro800 Programmable Controllers

Catalog Numbers Bulletin 2080
Topic
Page
About This Publication
Firmware Revision History
Features
Anomalies
10
Additional Resources
21
About This Publication

These release notes supplement the existing documentation supplied with your
product.
Read this document before using Micro800 controllers.
Firmware Revision History

Firmware Revision History for Micro810 Controllers
Revision
Description
1.011
First revision release
1.012
Minor revision release
1.013
2.011
Major revision release
2.012
2 Micro800 Programmable Controllers

Revision
Description
6.011
First major revision release

Revision
Description
1.011
1.012
1.013
2.011
4.011
4.012
4.013
6.011

Revision
Description
2.011
4.011
4.012
4.013
6.011
Firmware Backward Compatibility

Micro800 firmware is always backward compatible with previous revisions. It is
not necessary to flash upgrade a controller to a previous revision to match an
Rockwell Automation Publication 2080-RN001I-EN-P - December 2013
Micro800 Programmable Controllers 3

earlier project revision. For example, a Connected Components Workbench
project configured with a controller revision of 2.x can be downloaded into a
controller with firmware revision 2.x 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 Fixes

Enhancements 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
Features for Micro820 Controllers
Feature(1)
Description
Firmware
Revision
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
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
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
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
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

Features for Micro820 Controllers
Feature(1)
Description
Firmware
Revision
Backup and restore

through the
microSD card
Project backup and restore are supported on

Micro820 controllers through the microSD card.
6.011
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
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
OxF033
If 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
(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. This plug-in module is newly introduced with firmware revision 6.011 and is supported on
most Micro800 controllers.
(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.
Enhancements for Micro830 and Micro850 Controllers

Enhancement
Description
Firmware
Revision
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 0100%.
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 failure
If 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

Enhancement
Description
Firmware
Revision
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

4.011
client function is available through the addition of
the MSG_MODBUS2 function block.
This feature is not available for Micro830 controllers.
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.
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), can still work with
firmware revision 4, but will not work in conjunction
with the digital I/O configuration feature in firmware
revision 4. This means that on firmware revision 4,
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 projects onwards.
4.011

Enhancement
Description
Firmware
Revision
Motion control
Firmware revision 2 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 can

support up to four expansion I/O configuration.
2.011
Communication
connections
The following communication protocols are

supported with firmware revision 2:
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.
Enhancement for Micro810 Controllers

Enhancement(1)
Description
Firmware
Revision
Controller security
Controller password can be enforced to restrict

access to the programming software connection to
the controller.
(1)
See Micro810 User Manual, publication 2080-UM001 for more information.
Anomalies
Known Anomalies for Micro820 Controllers
Anomaly
Description
Affected
Firmware
Revisions
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.
6.011
APBC00017196
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.
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.
6.011
APBC00017743
6.011
APBC00017633
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.
6.011
APBC00018270
Corrected
Firmware
Revision

Known Anomalies for Micro820 Controllers
Anomaly
Description
Affected
Firmware
Revisions
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.
6.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.
Corrected
Firmware
Revision
APBC00017502
6.011
APBC00017400
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).
6.011
APBC00018658
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.
6.011
APBC00018944
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.
6.011
APBC00019113
Known and Corrected Anomalies for Micro830 and Micro850 Controllers

Anomaly
Description
Affected
Firmware
Revisions
Incorrect
conversion of
REAL/LREAL
variables using
Any_To_String

6.011
Corrected
Firmware
Revision
APBC00018944
Controller faults
when restoring
an older project
from memory
module to a
controller
containing a
project created
with Connected
Components
Workbench
revision 6
Project restore (from a memory module

that contains a project created by a
pre-revision 6 Connected Components
Workbench) will fail on a
Micro810/Micro830/Micro850 controller
with firmware revision 1 or 2 that has a
project created by Connected Components
Workbench revision 6 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.
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.
2.0xx
1.0xx
4.0xx
4.012
4.011
2.011
4.013
4.011
2.011
4.012
APBC00017367
APBC000016906
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

Anomaly
Description
Affected
Firmware
Revisions
Corrected
Firmware
Revision
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.
4.011
6.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.
4.011
2.0xx
1.0xx
6.011
4.011
6.011
4.011
APBC000014849
APBC00015308
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
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.
APBC000015030

Anomaly
Description
Affected
Firmware
Revisions
Corrected
Firmware
Revision
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.
4.011
6.011
4.011
4.012
4.011
2.011
1.0xx
6.011
4.011
2.011
6.011
4.011
2.011
1.0xx
6.011
APBC000015191
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
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.
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.
APBC000014284
APBC00011729
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

Anomaly
Description
Affected
Firmware
Revisions
Corrected
Firmware
Revision
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.
2.011
1.0xx
4.011
Incomplete home
URL string in EDS
file
The EDS file includes an incomplete home

URL text string.
2.011
1.0xx
4.011
Password
mismatch status
is not correct
Password mismatch status is not correct

after power cycle if Load on Error is set.
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.
1.011
2.011
1.011
2.011
1.011
2.011
APBC00009305
APBC000009490
APBC00011949
APBC00006755
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 Errorset.
Clear the fault and use the controller
normally.
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.
APBC00005287
APBC00007660

Anomaly
Description
Affected
Firmware
Revisions
Corrected
Firmware
Revision
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).
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.
1.011
2.011
1.011
1.013
APBC00007864
APBC00007923
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

Anomaly
Description
Affected
Firmware
Revisions
Corrected
Firmware
Revision
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.
1.011
1.013
1.011
1.013
1.012
1.013
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
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.
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
APBC00005198
APBC00005332 / APBC00005357

Anomaly
Description
Affected
Firmware
Revisions
Corrected
Firmware
Revision
Generic plug-in
modules
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.
1.012
1.011
1.013
1.011
1.012
APBC00007064
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)
This anomaly does not apply to Micro830 controllers.
Known and Corrected Anomalies for Micro810 Controllers

Anomaly
Description
Affected
Firmware
Revision
Incorrect
conversion of
REAL/LREAL
variables using
Any_To_String

6.011
APBC00018944
Corrected
Firmware
Revision

Anomaly
Description
Affected
Firmware
Revision
Corrected
Firmware
Revision
Controller faults
when restoring
an older project
from memory
module to a
controller
containing a
project created
with Connected
Components
Workbench
revision 6
Project restore (from a memory module

that contains a project created by a
pre-revision 6 Connected Components
Workbench) will fail on a
Micro810/Micro830/Micro850 controller
with firmware revision 1 or 2 that has a
project created by Connected Components
Workbench revision 6 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.
2.0xx
1.0xx
4.0xx
APBC00017367
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.
2.0xx
1.0xx
APBC00019113
No I/O force
indication
There is no I/O force indication on the LCD

display I/O status screen.
2.011
1.0xx
2.012
Password
mismatch status
is not correct
Password mismatch status is not correct

after power cycle if Load on Error is set.
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.
2.011
1.0xx
2.012
Incomplete
home URL string
in EDS file
The EDS file includes incomplete home

URL string.
2.011
1.0xx
2.012
APBC00011949
APBC00013978
APBC00009490

Anomaly
Description
Affected
Firmware
Revision
Corrected
Firmware
Revision
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.
2.011
1.0xx
2.012
User application
cannot back up
and restore
A project configured with a revision 1.x

controller cannot be backed up or restored
successfully using the LCD module with a
firmware revision 2.011 controller.
2.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.
1.011
2.011
1.012
1.013
1.012
1.012
APBC00013978
APBC00014192
APBC00006755
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
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
Firmware Update
Instructions 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
Look for the Resources tab, then click Firmware to download the latest
firmware.
Additional Resources
These documents contain additional information concerning related
Rockwell Automation products.
Resource
Description

User Manual, publication 2080-UM001
xxxxx
Detailed description of features and how to

install and use the Micro810, Micro820,
Micro830, and Micro850 programmable
controllers.

User Manual, publication 2080-UM005
Micro830 and Micro850 Programmable
Controllers User Manual, publication
2080-UM002 xxxxxxx
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.

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.
Notes:
Rockwell Automation Support

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 Assistance
If 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.
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.
New Product Satisfaction Return

Rockwell 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.
United States
Contact 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.
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/.
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 Otomasyon Ticaret A.., Kar Plaza Merkezi E Blok Kat:6 34752 erenky, stanbul, Tel: +90 (216) 5698400
Publication 2080-RN001I-EN-P- December 2013

Supersedes Publication 2080-RN001H-EN-P - October 2013
Copyright 2013 Rockwell Automation, Inc. All rights reserved.

2080 rn001 - en P

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

2080 rn001 - en P

Diunggah oleh

Hak Cipta:

Format Tersedia

Release Notes

Micro800 Programmable Controllers

About This Publication

Firmware Revision History

About This Publication

Firmware Revision History

First revision release

Minor revision release

Minor revision release

Major revision release

Minor revision release

2 Micro800 Programmable Controllers

Firmware Revision History for Micro820 Controllers

First major revision release

Firmware Revision History for Micro830 Controllers

First revision release

Minor revision release

Minor revision release

Major revision release

Major revision release

Minor revision release

Minor revision release

Major revision release

Firmware Revision History for Micro850 Controllers

First revision release

Major revision release

Minor revision release

Minor revision release

Major revision release

Firmware Backward Compatibility

Micro800 Programmable Controllers 3

Availability of Enhancements and Anomaly Fixes

Rockwell Automation Publication 2080-RN001I-EN-P - December 2013

4 Micro800 Programmable Controllers

The DeviceNet plug-in serves as scanner and client

The high-speed counter plug-in provides enhanced

The Remote LCD module serves as a simple

microSD card slot

Industrial grade(4) microSD cards are supported

Datalogging and recipe is supported through the

Rockwell Automation Publication 2080-RN001I-EN-P - December 2013

Micro800 Programmable Controllers 5

Backup and restore

Project backup and restore are supported on

Controller settings on powerup can be set through

Error codes specific

The following error codes have been added for the

For more information, see the following User Manuals:

Rockwell Automation Publication 2080-RN001I-EN-P - December 2013

6 Micro800 Programmable Controllers

Enhancements for Micro830 and Micro850 Controllers

The DeviceNet plug-in serves as scanner and client

The high-speed counter plug-in provides enhanced

RS-485 serial port

The RS-485 serial port supports ASCII

PWM function is added via PTO motion parameter

PTO motion parameters 1006 and 1007 are added to

This error code pertains to unexpected software

The following error codes have been added:

Rockwell Automation Publication 2080-RN001I-EN-P - December 2013

Micro800 Programmable Controllers 7

CIP Generic and CIP

CIP Generic and CIP Symbolic client messaging