Micro800 Programmable Controllers

Transcription

1 Release Notes Micro800 Programmable Controllers Catalog Numbers Bulletin 2080 Topic Page About This Publication 1 History 1 Features 5 Anomalies 15 Additional Resources 38 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

2 2 Micro800 Programmable Controllers History for Micro810 Controllers Description (1) First revision release (1), Minor revision release Major revision release 2.012, 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 Major revision release Minor revision release Minor revision release Major revision release Major 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 Major revision release Major revision release 4.012, Minor revision release Major revision release Major revision release Major revision release Minor 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 Major revision release Major revision release Major revision release Major revision release

4 4 Micro800 Programmable Controllers 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 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 Update controller firmware from microsd card 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. This firmware release enables the controller to be flash updated from the microsd card, in addition to using ControlFLASH.

7 Enhancements for Micro820 Controllers Micro800 Programmable Controllers 7 Enhancement (1) Description Available From 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) 2080-MOT-HSC High-speed Counter plug-in support (2) 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. See the latest Connected Components Workbench software release notes for more information. 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. 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 (5) (5)

8 8 Micro800 Programmable Controllers Enhancements for Micro820 Controllers Enhancement (1) Description Available From 2080-REMLCD Remote LCD module support microsd card slot Datalogging and Recipe Backup and restore through the microsd card Powerup settings through ConfigMeFirst.txt file 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. 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. (5) (5) (5) (5) (5)

9 Enhancements for Micro820 Controllers Error codes specific to Micro820 Micro800 Programmable Controllers 9 Enhancement (1) Description Available From 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) (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.

10 10 Micro800 Programmable Controllers Enhancements for Micro830 and Micro850 Controllers Enhancement Description Available From 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 High Speed Counter (HSC) Feedback Axis 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. 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.

11 Enhancements for Micro830 and Micro850 Controllers Micro800 Programmable Controllers 11 Enhancement Description Available From 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 RS-485 serial port for ASCII communication 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. See the latest Connected Components Workbench software release notes for more information. 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 The RS-485 serial port supports ASCII communications on Micro800 controllers from firmware revision.

12 12 Micro800 Programmable Controllers Enhancements for Micro830 and Micro850 Controllers Enhancement Description Available From 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 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.

13 Enhancements for Micro830 and Micro850 Controllers Micro800 Programmable Controllers 13 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.

14 14 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:

15 Micro800 Programmable Controllers 15 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

16 16 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

17 Micro800 Programmable Controllers 17 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

18 18 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

19 Micro800 Programmable Controllers 19 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

20 20 Micro800 Programmable Controllers Known and Anomalies for Micro820 Controllers s 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. Connection to REMLCD module lost after changing default configuration related to serial port remote LCD MSG_MODBUS instruction s Q output is not cleared after controller is power cycled 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 After changing the default configuration related to serial port remote LCD, connection to the REMLCD module is lost. Workaround is to power cycle the controller. 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

21 Micro800 Programmable Controllers 21 Known and Anomalies for Micro820 Controllers s 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. 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 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 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.) 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

22 22 Micro800 Programmable Controllers Known and Anomalies for Micro820 Controllers s Controller with firmware revision faults when restoring a project backup made by a controller with an earlier firmware revision from the microsd card 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 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 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

23 Micro800 Programmable Controllers 23 Known and Anomalies for Micro820 Controllers s Hard fault on controller when card is removed during backup and restore MicroSD card sometimes cannot be detected after the controller is power cycled 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 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 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

24 24 Micro800 Programmable Controllers Known and Anomalies for Micro820 Controllers s 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 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 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 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

25 Micro800 Programmable Controllers 25 Known and Anomalies for Micro820 Controllers s 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 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 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 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

26 26 Micro800 Programmable Controllers Known and Anomalies for Micro820 Controllers s KEY_READ_REM function block fails to reset output in certain condition KEY_READ_REM function block reads keystrokes even while in system menu 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

27 Micro800 Programmable Controllers 27 Known and Anomalies for Micro830 and Micro850 Controllers s A false error may occur when UDFB input parameters are used for SOCKET_READ (Micro850 only) RSLinx Classic takes a long time to discover a Micro800 controller over Ethernet. MSG_MODBUS instruction s Q output is not cleared after controller is power cycled Copy operation copies unwanted variable data 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. 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 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. 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

28 28 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 Controller faults after a different project is downloaded if the previous project was not downloaded successfully 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 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. APBC

29 Micro800 Programmable Controllers 29 Known and Anomalies for Micro830 and Micro850 Controllers s Last PTO output state is not completed when changing PTO frequency on the fly Controller faults when changing EtherNet/IP configuration after restoring project from the memory module Duplicate IP address error display remains after new configuration is downloaded to the controller Unable to obtain IP address automatically using DHCP 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 for Micro830 controllers only. This anomaly is fixed in firmware revision for Micro830 and Micro850 controllers. APBC The controller goes into a hard fault when changing the EtherNet/IP configuration after a project is restored from the memory module. APBC 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. APBC 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 disabled Users 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. APBC (Micro830 only)

30 30 Micro800 Programmable Controllers Known and Anomalies for Micro830 and Micro850 Controllers s Modbus RTU errors due to slow interrupt performance OS Series value in SYS_INFO block shows wrong controller series Restore function does not work again after a successful restore operation Memory Module backup operation fails and may cause a hard fault in the controller Incorrect conversion of REAL/LREAL variables using Any_To_String DN and Error bits do not go false on certain ASCII instructions 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 OS Series value in the SYS_INFO function block does not display the correct controller series. APBC Using the restore from memory module function a second time does not work when performed immediately after a successful restore operation. APBC 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. 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 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. APBC

31 Micro800 Programmable Controllers 31 Known and Anomalies for Micro830 and Micro850 Controllers s Possible data packet loss with Ethernet communication (1) CIP Symbolic and CIP Generic messages not supported on Logix serial port CIP symbolic pass-through not supported Micro800 serial ports do not support control lines 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. APBC 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. APBC 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. APBC 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. APBC

32 32 Micro800 Programmable Controllers Known and Anomalies for Micro830 and Micro850 Controllers s Axis Decelerating flag turns on for non-zero jerk moves while axis is accelerating ASCII connection only works with RS-232 interface Controller faults when restoring an older project from memory module to a controller containing a project created with Connected Components Workbench revision 6.00 Embedded serial port may shut down on powerup 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. APBC The ASCII protocol for Micro800 controllers only supports RS-232 media. The RS-485 interface is not 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 It has been observed that the embedded serial port shuts down if the controller encounters power supply disruption at a certain time after powerup. APBC xx 1.0xx xx 4.013

33 Micro800 Programmable Controllers 33 Known and Anomalies for Micro830 and Micro850 Controllers s CIP Serial communication on embedded serial port may be temporarily disrupted CIP Serial client messaging to a PC running RSLinx software is not supported ASCII communication buffer is not cleared Incomplete home URL string in EDS file Password mismatch status is not correct ErrorMode parameter does not handle errors CIP Serial server and client messaging via Micro830 and Micro850 controller embedded serial port is disrupted for seconds before resuming normal operation. This may happen when CIP Serial communication is operating continuously for more than 17 days. APBC 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. APBC A new program download should automatically clear the buffer for ASCII serial communication messages but the buffer does not get cleared. APBC The EDS file includes an incomplete home URL text string. APBC Password mismatch status is not correct after power cycle if Load on Error is set. APBC ErrorMode input of IPIDCONTROLLER instruction does not handle errors as expected and does not recognize any input values. APBC

34 34 Micro800 Programmable Controllers Known and Anomalies for Micro830 and Micro850 Controllers s ControlFlash firmware update results in a red flashing fault Modbus configured target address returns illegal address error Fault translation error STI configuration reloaded when UID and UIE are used 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. APBC A Modbus client read to a valid Modbus boundary address of in the controller results to an illegal address error in the client. APBC 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). APBC 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. APBC

35 Micro800 Programmable Controllers 35 Known and Anomalies for Micro830 and Micro850 Controllers s CRC errors and timeouts in Modbus packet communications High Speed Counter (HSC) instruction configuration causes controller Hard Reset High Speed Counter (HSC) user interrupt does not work for 10/16-point controllers Universal Plug-In Module (UPM) interrupt configuration causes controller Hard Reset 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. APBC / APBC 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. APBC HSC ID HSC1 does not work for 2080-LC30-10QVB/QWB, and 2080-LC30-16QVB/QWB. APBC Adding UPM interrupts in the Interrupt Properties page may cause a controller Hard Reset APBC / APBC