AI for RSLogix 500 and MicroLogix

Altitude lays an SLC 500 or MicroLogix project out the way RSLogix 500 does, rungs drawn with their titles, symbols and descriptions, and reads, checks and changes it in the ASCII export RSLogix 500 opens again.

Rockwell Automation
Vendor
Rockwell Automation
Languages
Ladder
Files
.SLC.SY6.SY5.EAS
Covers
SLC 5/01 to 5/05MicroLogix 1000MicroLogix 1100MicroLogix 1200MicroLogix 1400MicroLogix 1500
  1. 1 Save the project as .SLC from RSLogix 500, with its .SY6 beside it
  2. 2 Review the changed rungs and record an approval if required
  3. 3 Open the selected .SLC in RSLogix 500 and download from there

Everything a RSLogix 500 file holds, in one conversation

Follow the cited source and review edits in the project copy. File History keeps the versions so your team can choose what to release.

  • Follow an address or symbol through program files and subroutines, writes first, with a Cross Reference panel beside the rungs
  • Check the program for defects, and compare two versions rung by rung
  • Change rungs, data values, symbols and descriptions in the .SLC, writing back only what changed
  • Write rung titles and address descriptions for undocumented logic
  • Translate the program to a ControlLogix or CompactLogix .L5X, with every address mapped to its new tag
  • Check against industrial standards such as IEC 61131-3, ISA-88, ISA-95 and PackML, or your own

Requests engineers type every day

  • Which rungs use this timer’s done bit?
  • Map the SLC addresses to tags for our CompactLogix upgrade.
  • Describe every undocumented B3 bit from how the logic uses it.

The work RSLogix 500 projects need most

See Altitude on your RSLogix 500 files

We'll walk through the requests that matter to your team on the platforms you run, from review and troubleshooting to documents and migration.