So, the system is running, with a 5/04, CH0 (Serial Nine Pin D Connector) connected AIC+ ? Or, directly to the 550 using a RS232 cable?
If it's working and you want PC connectivity, I suggest you utilize the DH+ channel if practical for your needs, since it could be more expensive initially.
It will then allow up to a 10,000 foot "blue hose" to wherever you want, and you can do all your troubleshooting, and careful programming remotely. The cable is cheap, and the protocol, "Allen Bradley DH+" is very easy to work with, diagnostics are simple and ladder accessible. and you can do LOTS of data gathering at 57.6K. It's very noise resistant. I know a guy who found DH+ working intermittently and went to reterminate a phoenix plug and got shocked. He measured 120VAC and found a control power wire touching the terminal blocks. It ran through rectangular steel raceway with multiple servo motor and VFD leads and it simply worked. When it broke, it took five minutes to diagnose.
I LOVE DH+!
[/soap_box]
Now if you just want temporary connectivity, then laptop tap into the existing AIC module. You should be able to use the 1747-CP3 (working from memory here Mickey, double check me on this!)...
BUT, you configure the RS232-Devices Driver as DH485, then connect to a RS232 port on the AIC+, and have access to both the SLC and the PV550 Standard.
You need to know the node numbers of the PV550 and the SLC CH0, so, make sure you choose a node number for your DH485 driver in RSLinx that isn't being used, then browse the driver (RSWho) until you see both of them, and note their node numbers, then stop the driver and set your RSLinx node number to the lowest number not in use...this will improve data rates due to the successive token passing scheme of DH485. Then reconnect with PanelBuilder32 and/or RSLogix500.