Micro800 Programmable Controllers

Transcription

1 Release Notes Micro800 Programmable Controllers Catalog Numbers Bulletin 2080, firmware revision 10 or earlier Topic Page About This Publication 1 History 1 Features 5 Anomalies 19 Additional Resources 47 About This Publication These release notes supplement the existing documentation supplied with your product. Read this document before using Micro800 controllers. History The latest firmware revision for your Micro800 controllers can be downloaded from the Rockwell Automation Product Compatibility and Download Center website at IMPORTANT This publication contains information on firmware revision 10 or earlier. For information on firmware revision 11 or later, refer to publication 2080-RN004.

2 2 Micro800 Programmable Controllers History for Micro810 Controllers Description (1) First revision release (1) Minor revision release Minor revision release Major revision release Minor revision release Minor revision release Major revision release Minor revision release (1) This firmware revision is obsolete and is no longer available for download. History for Micro820 Controllers Description (1) First major revision release Minor revision release Minor revision release Major revision release Minor revision release Minor revision release Major revision release Major revision release Major revision release Minor revision release (1) This firmware revision is obsolete and is no longer available for download.

3 Micro800 Programmable Controllers 3 History for Micro830 Controllers Description (1) First revision release (1) Minor revision release Minor revision release Major revision release Major revision release Minor revision release Minor revision release Major revision release Major revision release Major revision release Minor revision release Major revision release Major revision release (1) This firmware revision is obsolete and is no longer available for download. History for Micro850 Controllers Description First revision release Major revision release 4.012, Minor revision release Minor revision release Major revision release Major revision release

4 4 Micro800 Programmable Controllers History for Micro850 Controllers Description Major revision release Major revision release Major revision release Backward Compatibility Micro800 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 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.

5 Micro800 Programmable Controllers 5 Features Enhancements for Micro810 Controllers Enhancement (1) Various software features support Controller security Power failure handling German language support on the LCD Description 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. Controller password can be enforced to restrict access to the programming software connection to the controller. 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 German language support is now available on the LCD menu. Available From (1) See Micro810 User Manual, publication 2080-UM001 for more information.

6 6 Micro800 Programmable Controllers Enhancements for Micro820 Controllers Enhancement (1) Description Available From Ethernet configuration retained after power cycle Indirect bit addressing support Performance improvement for RMC Performance improvement for project Download and Build User Defined Functions (UDF) support Ethernet configuration, including the IP address, is retained after you cycle power to the controller. 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. 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 upload Actual performance improvement depends on the project, PC, and communications interface. Connected Components Workbench Developer Edition release 10 or later software is required. 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. 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.

7 Enhancements for Micro820 Controllers Micro800 Programmable Controllers 7 Enhancement (1) Description Available From Ethernet configuration and password can be saved during firmware upgrade or downgrade Optional module option for plug-in I/O and expansion I/O modules PID instruction added Communication access to bits of integers Communication access to Date and Time data types Data protection for project download and restore 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 feature. 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. The PID instruction is similar to the MicroLogix instruction for the parameter names and configuration. Does not natively support autotune. This feature is for writing bits of an integer using the CIP Read-Modify-Write service (0x4E). Typically used by HMI terminals. To set the date and time in the controller or to set timer presets. Typically used by HMI terminals. 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.

8 8 Micro800 Programmable Controllers Enhancements for Micro820 Controllers Enhancement (1) Description Available From FIFO instructions added Wall Clock Time change in Run Mode BSL and BSR instructions added Sockets communication protocol support Run Mode Configuration Change (RMCC) Performance improvement for Datalogging and Recipe Bit access of integer array elements support CIP passthrough to DeviceNet using 2080-DNET20 DeviceNet scanner plug-in support FFL and FFU instructions added. These instructions have been added to aid migration for MicroLogix users. The real time clock can now be updated during run mode over CIP protocol and through the user program using a Loopback message. 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. 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. 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. This firmware release improves the performance of the Datalogging and Recipe features. For typical applications, datalogging can now occur once every two seconds. This firmware release supports bit access of integer array elements for Micro820 controllers. 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 or later is required.

9 Enhancements for Micro820 Controllers Micro800 Programmable Controllers 9 Enhancement (1) Description Available From Update controller firmware from microsd card Run Mode Change (RMC) Micro820 Series B controller support PanelView Plus Variable/Tag browsing support Open Platform Communications (OPC) support Various software features support 2080-DNET20 DeviceNet scanner plug-in support (2) This firmware release enables the controller to be flash updated from the microsd card, in addition to using ControlFLASH. 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. This firmware release adds support for Micro820 Series B controllers. 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. 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. This firmware release also supports these features Retentive Timer On-Delay (RTO) and Data Value Upload/Download. 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 (5)

10 10 Micro800 Programmable Controllers Enhancements for Micro820 Controllers Enhancement (1) Description Available From 2080-MOT-HSC High-speed Counter plug-in support (2) 2080-REMLCD Remote LCD module support microsd card slot Datalogging and Recipe Backup and restore through the microsd card 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. 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. 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. 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. Project backup and restore are supported on Micro820 controllers through the microsd card. (5) (5) (5) (5) (5)

11 Enhancements for Micro820 Controllers Powerup settings through ConfigMeFirst.txt file Error codes specific to Micro820 Micro800 Programmable Controllers 11 Enhancement (1) Description Available From 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. 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. (5) (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: (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. (5) This firmware revision is obsolete and is no longer available for download.

12 12 Micro800 Programmable Controllers Enhancements for Micro830 and Micro850 Controllers Enhancement Description Available From Indirect bit addressing support Performance improvement for RMC Performance improvement for project Download and Build User Defined Functions (UDF) 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. 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 upload Actual performance improvement depends on the project, PC, and communications interface. Connected Components Workbench Developer Edition release 10 or later software is required. 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. 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.

13 Enhancements for Micro830 and Micro850 Controllers Micro800 Programmable Controllers 13 Enhancement Description Available From Ethernet configuration and password can be saved during firmware upgrade or downgrade Optional module option for plug-in I/O and expansion I/O modules PID instruction added Communication access to bits of integers Communication access to Date and Time data types Data protection for project download 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 feature. 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. The PID instruction is similar to the MicroLogix instruction for the parameter names and configuration. Does not natively support autotune. This feature is for writing bits of an integer using the CIP Read-Modify-Write service (0x4E). Typically used by HMI terminals. To set the date and time in the controller or to set timer presets. Typically used by HMI terminals. 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 but only for project restore.

14 14 Micro800 Programmable Controllers Enhancements for Micro830 and Micro850 Controllers Enhancement Description Available From FIFO instructions added Wall Clock Time change in Run Mode BSL and BSR instructions added Sockets communication protocol support for Micro850 controllers Run Mode Configuration Change (RMCC) for addresses Bit access of integer array elements support CIP passthrough to DeviceNet using 2080-DNET20 DeviceNet scanner plug-in support FFL and FFU instructions added. These instructions have been added to aid migration for MicroLogix users. The real time clock can now be updated during run mode over CIP protocol and through the user program using a Loopback message. 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. 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. 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. This firmware release supports bit access of integer array elements for Micro830/Micro850 controllers. 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 or later is required.

15 Enhancements for Micro830 and Micro850 Controllers Micro800 Programmable Controllers 15 Enhancement Description Available From High Speed Counter (HSC) Feedback Axis Run Mode Change (RMC) PanelView Plus Variable/Tag browsing support Open Platform Communications (OPC) support Various software features support 2080-DNET20 DeviceNet scanner plug-in support 2080-MOT-HSC high-speed counter plug-in support 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. 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. 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. 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. This firmware release also supports these features Retentive Timer On-Delay (RTO), Data Value Upload/Download, and Data Protection. 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. 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

16 16 Micro800 Programmable Controllers Enhancements for Micro830 and Micro850 Controllers Enhancement Description Available From RS-485 serial port for ASCII communication PWM function PTO motion parameters 1006 and 1007 Additional error code: OxF019 Additional error codes: 0xF017 and 0xF018 CIP Generic and CIP Symbolic client messaging Modbus TCP client function on Micro850 controllers The RS-485 serial port supports ASCII communications on Micro800 controllers from firmware revision. PWM function is added via PTO motion parameter The duty cycle of the PTO can now be set using MC_WriteParameter. The value ranges from , indicating 0 100%. PTO motion parameters 1006 and 1007 are added to read Pulses per Revolution and Unit per Revolution configuration in user program. This error code pertains to unexpected software error due to memory or other controller resource issue. 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. 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. 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.

17 Enhancements for Micro830 and Micro850 Controllers Micro800 Programmable Controllers 17 Enhancement Description Available From Memory Copy function Digital I/O plug-in module support 1 GAIN renamed to MOV Motion control 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 onwards, this function block no longer requires an array for the source and destination. 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. 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. 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.

18 18 Micro800 Programmable Controllers Enhancements for Micro830 and Micro850 Controllers Enhancement Description Available From Expansion I/O support Communication connections Controller security Digital output variables 0xF000 and 0xF002 Fault Handling on Powerup Micro850 controllers with firmware revision 2.xxx can support up to four expansion I/O configuration. 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. Controller password can be enforced to restrict access to the programming software connection to the controller. All digital output variables driven by the IO scan gets cleared on powerup or during transition to RUN mode. Controller attempts to recover user program and clear user variables upon powerup. (1) UDFBs and sample Micro800 programs for Connected Components Workbench can be downloaded from the Sample Code Library:

19 Micro800 Programmable Controllers 19 Anomalies Known and Anomalies for Micro810 Controllers Copy operation copies unwanted variable data Variables not retained after power cycle Blank LCD screen during power up L00 information displays on LCD Controller returns 0xF004 fault when memory module is cleared and then restored 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. APBC Variables for which the Retain checkbox have been checked are sometimes not retained after power cycle. APBC When the controller is powered up, the LCD displays a blank screen and communication is not allowed. APBC The LCD screen displays the indicator L00, which is no longer applicable for Micro810 controllers. APBC 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. APBC

20 20 Micro800 Programmable Controllers Known and Anomalies for Micro810 Controllers OS Series value in SYS_INFO block shows wrong controller series Controller with program in memory module malfunctions when power cycled during firmware flash process Changes to retained user variable values are lost upon exit of Program Debug mode Analog input calibration offset must be positive Controller faults when restoring an older project from memory module to a controller containing a project created with Connected Components Workbench revision 6.00 The OS Series value in the SYS_INFO function block does not display the correct controller series. APBC 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. APBC 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. APBC 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. APBC 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. APBC

21 Micro800 Programmable Controllers 21 Known and Anomalies for Micro810 Controllers Incorrect conversion of REAL/LREAL variables using Any_To_String KEY_READ function block reads keystrokes even while in system menu LCD displays unwanted characters and the controller resets when editing locked variables Flag F disappears after page change in LCD TONOFF instructions do not work properly at maximum value Watchdog timer less than 10 ms causes controller fault 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 APBC 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. APBC 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. APBC Flag F disappears from LCD after shifting from one page to another. APBC TONOFF instructions do not work properly at their maximum value. APBC The controller goes into a fault when watchdog timer value entered is less than 10 ms. APBC

22 22 Micro800 Programmable Controllers Known and Anomalies for Micro810 Controllers Misleading PwrUp Behavior menu options in LCD F004 fault when controller with firmware revision 2.xxx backs up firmware revision 1.xxx project through LCD No I/O force indication User application cannot back up and restore Password mismatch status is not correct Wrong language on localized LCD options LCD instruction causes controller fault 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. APBC 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. APBC There is no I/O force indication on the LCD display I/O status screen. A project configured with a revision 1.xxx controller cannot be backed up or restored successfully using the LCD module with a firmware revision controller. APBC Password mismatch status is not correct after power cycle if Load on Error is set. APBC Certain menu strings still display in English on localized (French, Italian, Spanish) LCD menu display. APBC 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. APBC

23 Micro800 Programmable Controllers 23 Known and Anomalies for Micro810 Controllers Incomplete home URL string in EDS file ErrorMode parameter does not handle errors RHC instruction in Micro810 controllers is not accurate The controller may report a fault (error code 0xD011) when continuously powered on for more than days The EDS file includes incomplete home URL string. APBC ErrorMode input of IPIDCONTROLLER instruction does not handle errors as expected and does not recognize any input values. APBC The RHC function block uses a time base of μs and returns counter times 5, instead of a 40 μs timer with a return counter times 4. APBC Under certain conditions, when the controller is continuously powered on for more than 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 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. APBC / KnowledgeBase ID

24 24 Micro800 Programmable Controllers Known and Anomalies for Micro820 Controllers s [CF] command in ConfigMeFirst.txt file changes Clear fault startup setting of Connected Components Workbench project Controller sends ARP broadcasts even if Detect duplicate IP address field is unchecked CIP connection timeout outside ODVA specification required time upgrade over serial port appears to fail 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 The controller sends ARP broadcasts even if the Detect duplicate IP address field in the Connected Components Workbench project is unchecked /APBC /APBC 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 /APBC 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 /APBC

25 Micro800 Programmable Controllers 25 Known and Anomalies for Micro820 Controllers s Premature AutoTune failure Connection to REMLCD module lost after changing embedded port setting from Modbus back to CIP Serial 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 /APBC 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 /APBC 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 /APBC

26 26 Micro800 Programmable Controllers Known and Anomalies for Micro820 Controllers s Pass-through of connected CIP messages with more than one class and instance will fail Long Real data values used on DLG that are either too big or too small affect scan time performance UID and UIE instructions cancel pending user interrupts MSG_MODBUS instruction s Q output is not cleared after controller is power cycled 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/APBC 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) /APBC 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 /APBC 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 /APBC

27 Micro800 Programmable Controllers 27 Known and Anomalies for Micro820 Controllers s Output turns off for one program scan when RTC_SET is enabled Controller faults when performing RMC after power cycle A false error may occur when UDFB input parameters are used for SOCKET_READ RSLinx Classic takes a long time to discover a Micro800 controller over Ethernet. 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 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 APBC 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. APBC 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, :EIP. APBC

28 28 Micro800 Programmable Controllers Known and Anomalies for Micro820 Controllers s TCP connection does not close immediately when CIP connection is closed Copy operation copies unwanted variable data IPIDCONTROLLER derivative gain setting not applied Controller with firmware revision faults when restorsing a project backup made by a controller with an earlier firmware revision from the microsd card 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. APBC 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. APBC 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) APBC When a controller with firmware revision 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 or later and backup the project to the microsd card. APBC

29 Micro800 Programmable Controllers 29 Known and Anomalies for Micro820 Controllers s Unable to restore project from microsd card although indicated as compatible in Connected Components Workbench Controller faults when changing EtherNet/IP configuration after restoring project from the memory module or microsd card REMLCD backlight briefly turns on before startup message Hard fault on controller when card is removed during backup and restore MicroSD card sometimes cannot be detected after the controller is power cycled 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. APBC 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. APBC 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. APBC 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. APBC 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. APBC / APBC

30 30 Micro800 Programmable Controllers Known and Anomalies for Micro820 Controllers s SD LED indicator may remain off on card insertion The controller may report a fault when powered up from out of the box Modbus RTU errors due to slow interrupt performance Controller does not turn off PWM output in invalid status condition and after downloading a new program Occasional 0xF004 fault when doing a project backup or restore Changes to retained user variable values are lost upon exit of Program Debug mode 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. APBC Under rare occasions, the controller may boot up with a fault and display an incomplete catalog name in RSLinx. APBC 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. APBC 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. APBC 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. APBC For retained user variables, any changes made in Debug mode to the value in Program mode will be lost when transitioning to Run mode. APBC

31 Micro800 Programmable Controllers 31 Known and Anomalies for Micro820 Controllers s Analog input calibration offset must be positive Incorrect conversion of REAL/LREAL variables using Any_To_String Communication breaks if project backup or restore fails Error message Memory card is not present takes approximately 30 seconds to be displayed after card is ejected SD LED continues to blink after card is ejected 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. APBC 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 APBC 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. APBC 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. APBC 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. APBC

32 32 Micro800 Programmable Controllers Known and Anomalies for Micro820 Controllers s RTC module may run for a short time when controller is powered down Fault LED indicator continues to blink red even after fault is cleared Data retention fails in certain scenarios KEY_READ_REM function block fails to reset output in certain condition KEY_READ_REM function block reads keystrokes even while in system menu When the controller is powered down, the RTC module may run for less than four days at room temperature. APBC Micro820 controller Fault LED indicator continuously blinks red even after fault is cleared in Connected Components Workbench. APBC 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. APBC The KEY_READ_REM function block is unable to reset its output when the ENABLE input of the instruction goes from TRUE to FALSE. APBC 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. APBC

33 Micro800 Programmable Controllers 33 Known and Anomalies for Micro830 and Micro850 Controllers s Controller faults 0xF293 even if correct expansion I/O generic configuration is downloaded (Micro850 only) Controller sends ARP broadcasts even if Detect duplicate IP address field is unchecked (Micro850 only) CIP connection timeout outside ODVA specification required time Premature AutoTune failure 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 The controller sends ARP broadcasts even if the Detect duplicate IP address field in the Connected Components Workbench project is unchecked /APBC 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 /APBC 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 /APBC

34 34 Micro800 Programmable Controllers Known and Anomalies for Micro830 and Micro850 Controllers s TCP retry timeout for Micro850 controller RSLinx unable to browse for CIP bridge device from controller plug-in module slot 4 and 5 CIP messaging communication may be affected by cable break UID and UIE instructions cancel pending user interrupts 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 /APBC When a serial plug-in module is connected to controller slot 4 or 5, RSLinx cannot browse to the device /APBC 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 /APBC 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 /APBC