INGEAR offers multiple PLC driver software solutions for Allen-Bradley development, offering efficiency and cost-savings for programmers and development teams of all sizes. Allen-Bradley Software for PLC, SLC, MicroLogix, ControlLogix and CompactLogix programmable logic.
Need an HMI, SCADA, interface, or logging application, but short on resources?You provide the specifications, we design and build your application, then provide you with sourcecodefor ongoingdevelopments.We can also help with all phases of project management including creating specifications, scopedocumentgeneration,and user documentation.We are expert developers and are intimately familiar with our products, so we can generallydeliversolutionsmuch quicker than developers that may have a learning curve.
RSLinx Classic version 3.90.00 has the following system features and enhanced features:System featuresCompact harmonyThis release allows you to compact existing harmony typologies through the RSLinx Classic userinterface. With this enhancement, you no longer need to locate and delete harmony files manually fromyour computer's hard drive. This reduces the waiting time to open RSLinx Classic, or to expand the drivernodes in the RSWho. For more information, see Compact harmony files in RSLinx Classic in the RSLinxClassic Online Help.Enhanced featuresEnhanced installation wizardThe installation setup wizard's user interfaces and installation process are updated to align with otherRockwell Automation software products to improve usability and convenience. For more details, seeRSLinx Classic Getting Results Guide.New operating system support. Windows 10 Professional. Windows 10 Enterprise.
Windows 10 IoT Enterprise 2016 Long Term Servicing Branch (LTSB) Embedded. After you set up an OPC topic in RSLinx Classic and connect to an OPC client, the values in the Item Properties dialog box are incorrect. First identified in RSLinx Classic version 3.80.00. 361748In this release, after the same operations on RSLinx Classic, the values in the Item Properties dialog box shows correctly. For a controller that supports Ethernet/IP mode switching (for example, 5069-L320ER and 5069-L310ER), after you switch the controller’s IP mode from A1/A2: Dual-IP to A1/A2: Linear/DLR, the two Ethernet networks are merged without an warning message. First identified in RSLinx Classic version 3.81.00. 361760In this release, a warning message is added to indicate the networks merging.
When changing the IP address on a module, if the IP changes fail to be saved and the TCP/IP connection is reset (RST), RSLinx Classic does not show an error messages upon this IP change failure. First identified in RSLinx Classic version 3.74.00. 356344In this release, an error message is added to indicate the IP change failure. After connecting an Allen-Bradley 1790D-0B16 device to a Micro800 DeviceNet Plug-in Module, the Allen-Bradley 1790D-0B16 device shows as an unknown device with a yellow question mark under the Micro800 DeviceNet Plug-in Module in RSLinx Classic.
First identified in RSLinx Classic version 3.72.00. 352867In this release, the Allen-Bradley 1790D-0B16 device shows correctly with no question mark. When using RSLinx Classic version 3.81.00 with Connected Components Workbench, you may randomly experience connection failures to Micro820 devices, or backplane missing upon browsing.
First identified in RSLinx Classic version 3.81.00. 363386In this release, RSLinx Classic runs normally with Connected Components Workbench upon the same operation. RSLinx Classic stops responding on startup with a fully qualified domain name (FQDN) of more than 32 characters.
First identified in RSLinx Classic version 3.80.00. 362172In this release, RSLinx Classic runs normally with a fully qualified domain name (FQDN) of more than 32 characters. 1770-KFC device. RSLinx Classic version 2.42.00 or later fails to browse remote ControlLogix controllers under 1770-KFC15DF1 passthrough. First identified in RSLinx Classic version 2.42.00.
354274There is currently no work around for this anomaly. To communicate with a 1770-KFC15 module via DF1protocol, use RSLinx Classic version 2.41.00 or earlier.DH+ and DH485. If you attempt to go online with a controller through a 1784-PKTX card to a remote DH-485 to DH+ network, RSLogix 5 may stop responding.
Firstidentified in RSLinx Classic version 2.55.00. 263358There is currently no work around for this anomaly.Emulator. RSLinx Classic may exit if click Cancel button when adding a SLC 500 (DH485) Emulator driver.When adding a SLC 500 (DH485)Emulator driver in RSLinx Classic, if you click Cancel on the Configure SLC 500 (DH485) Emulator Driver dialog box, RSLinx Classic may exit unexpectedly on Windows 7operating systems. First identified in RSLinx Classic version 2.57.00. 269134There is currently no work around for this anomaly.EtherNet and EtherNet/IP. Devices on previous subnet are not removed after configuration changes.If an EtherNet/IP driver's configuration is changed to a newremote Ethernet subnet, the devices browsed on previous Ethernet subnet were not removed.
First identified in RSLinx Classic version 3.51.00. 273876There is currently no workaround for this anomaly.EDS file upload and registration. RSWho cannot upload and register EDS files with path length more than 256 bytes.For an online device whose path length exceeds 256 bytes, RSWho cannot upload andregister the EDS file of the device, neither automatically nor manually.
First identified inRSLinx Classic version 3.80.00. 357201To work around this problem, change the location where the computer is connected, sothat the path length of the device is less than 256 bytes. RSWho may fail to upload and register all the EDS files from unregistered devices, if there are too many EDS files (for example, 400 files) or multiple RSWho instances(for example,5 instances). First identified in RSLinx Classic version 3.80.00. 357152To work around this problem, upload and register several EDS files (for example, 10 files)with a single RSWho instance each time, or manually upload and register the EDS filesusing the EDS Hardware Installation Tool. If an EDS file is removed using the EDS Hardware Installation Tool while RSLinx Classic isrunning, the EDS file cannot be uploaded and registered in the RSWho, neither automatically nor manually.
First identified in RSLinx Classic version 3.80.00. 357375To solve this problem, restart RSLinx Classic to upload and register the EDS file (eitherautomatically or manually). FactoryTalk View Studio startup performance tends to degrade over time when there are alarge number of devices on the network. First identified in RSLinx Classic version 2.56.00. 218691To solve this problem, compact existing harmony typologies through RSLinx Classic:. In RSLinx Classic menu bar, click File Compact Harmony,or. In RSLinx Classic Launch Control Panel, click Tools Compact Harmony.Operating systems.
When running RSLinx Classic on Windows 10 Professional or Enterprise v1607 operating systems, initiating a network connectivity break by disabling NIC adaptors in Device Manager can cause application failures requiring a restart of the application. This issue was introduced in the Windows 10 v1607 feature build.
363223To avoid this problem, run the Microsoft Hotfix outlined in Answer ID in the Rockwell Automation Knowledgebase. This hotfix will be released in the December 2016 or January 2017 Windows Update pack. Alternatively, you can run Windows 10 v1511 where this issue is not present. Because of the timing of the RSLinx Classic version 3.90.00 release, RSLinx Classic is not fully qualified to run on Windows Server 2016 operating systems.
While RSLinx Classic version 3.90.00 does not prevent installation on Windows Server 2016 operating systems, additional changes may be required in order to function properly. 363223For more information, refer to Rockwell Automation Knowledgebase Answer ID.
![Rslinx Rslinx](/uploads/1/2/5/6/125628259/670763170.png)
RSLinx Classic version 3.90.00 is not tested to run on Windows Embedded 8.1 Industry Professional operating system, while RSLinx Classic does not prevent installation on this operating systems. Additional changes may be required in order to function properly. First identified in RSLinx Classic version 3.90.00. 363223To avoid this problem, use another supported operating system that is listed in the System requirements topic.RSLinx Gateway. From a client, you cannot browse the Remote Devices via RSLinx Classic Gateway driver, which was configured on a RSLinx Classic Gateway server. First identified in RSLinx Classic version 2.31.00.
21836There is currently no work around for this anomaly.Stratix. RSLinx Classic may stop responding when viewing the module statistics of Stratix 5410 switches on the Port Diagnostics tab.
First identified in RSLinx Classic version 3.74.00. 355521There is currently no work around for this anomaly. RSLinx Classic version 3.90.00 has the following changes in functionality since the last release:EDS file updatesThe EDS files for some devices have been added or updated in this release. This includes support for newhardware devices.