Be aware that the drivers in InteractX do not work with Logix processor versions greater than the 5375, 5575 and not with any GuardLogix models. See the FAQ link below. For all Logix processors it is necessary to set "Protocol Type" to Symbolic in the device settings. See the image in the FAQ.
You can do all your testing from the laptop. Once it works from the laptop, it will work when downloaded to the IXA. There is no reason to download it to the IXA if the Laptop has not all ready run the application successfully.
The latest Studio 5000 also defaults to a state which blocks external access to tags.
InteractX FAQs.
Create your Com Servers connection first since the addresses used in tags require it in the address description. ChannelName.DeviceName.AllenBradleyTag
Information on data types and syntax are accessed by hitting help button while in the device definition screens.
In the Comm Server, Add a Channel and select the Allen Bradley ControlLogix Driver
Accept all the defaults in the Channel Configuration screens.
Create a Device under the Channel CH1
Select a Device Model
For Device ID enter the IP address of the PLC followed by ,1,0 (Comma 1 Comma 0)
Accept all the defaults until you get to the "Logix Options" screen and under "Protocol Options" set it to "Symbolic" (Blocking Modes do not work on processors with firmware greater than 15)
On the Logix Database Settings screen, if you are connected to the PLC set it to "Create tag database from device"
If you do not have access to the PLC but do have the PLC programming software and current program, do a "Save Program As" and select L5K for the PLC program.
Then you select "Create tag database from import file" and point at the L5K file you saved from AB Programming software
Accept the defaults on the next screen and the Comm Server configuration is compete.
The next step is to import the AB Logix tags from the PLC or L5K into the Comm Server by opening the device and the "Database Creation" tab.
Leave the default settings and click the "Auto Create" button. It will attempt to connect to the PLC or find the L5K file based on your settings.
You may need to hit this button twice to get the Comm Server to register the upload. If it is unable to connect to the PLC or find the L5K nothing will be imported.
If the import is successful, you will see group names appear below the Device in the Comm Server Tree.
Before upload
After Upload successful
This gets the PLC tags loaded into the Comm Server database. To use them in your application you can now import them into InteractX and have it create InteractX tags and assign them to the Allen Bradley tags in the Comm Server.
The Blue tag on the COMMServer line is to import tags from the Comm Server
"Prepend String to Tag Names" is referring to the InteractX tags it is going to create. Choose something that is meaningful and shows that the tag was created by the import function.
Select a group to import and hit the "Import" Button (Greyed out till valid branch selected.
The imported InteractX tags created have the Address have the appropriate Channel.Device.ABAdressformat
For String tags, add .Data/82 (Dot Data slash 82) String tags are actually two tags. One as Data and One as Length and you need to tell InteractX which one you mean. The /82 sets it to expect up to 82 characters.
You can now use these tags on the appropriate tools and know that the Syntax is correct.
dom 02202020
