There are a handful of things that might be getting confused here.
Add-On Instructions (AOI) are little packaged routines that you can call from your ControlLogix program. While they are sometimes used to configure or scale or manage third party devices, they are not part of the I/O tree configuration.
Add-On Profiles (AOP) are a way to get a new device into the available I/O module lists when you're creating the I/O tree.
When RA releases a new device, they typically have an AOP you can install in older releases of RSLogix 5000 to make that device available. These 'native' AOPs have an installation wizard of their own. RA partner companies like Prosoft often get help creating and testing AOPs so they work just like Rockwell's own.
In v20, RA introduced a new method for creating and managing AOPs that used a special section in the EDS file instead of a traditional native AOP installer. When you registered the EDS file, the "EDS-Based AOP" was created in RSLogix 5000 and the new device was available in the I/O tree.
It's these EDS-based AOPs that haven't been successful, in my experience. In every case I worked on, the Support people from the third party had either never heard of the technology or had no information on how it was supposed to work.
ABB's drive interfaces are really very good, but they may not have a working EDS-based AOP either.
If you are entering the Instance numbers, it sounds like you are using the good old Generic Ethernet Module object, which has been simple and reliable for a long time.
Grab that error message and we can start working from there.