FactoryTalk Logix Echo and IBA - Communication on 2 virtual machines

General Discussion
1

Once i successed to make communication between FT logix echo and IBA and i had signals for monitoring.

But i dont know what i did before, i tried everything and it is not working.

Both VMs can ping each other. I make indipendent address for FT logix echo(in network settings). IBA is on other VM and can read Produced tags from controler, and after going "OK" to establish IBA, everything seems okay but there is no connection and iba is not collecting nothing.

Also on the picture there is no IP address of the simulated PLC. So there is no connection.

Does somebody know what need to be done?

IBAacq
IBAacq1511×212 17.3 KB

2

What is IBA?

You posted this in the Ignition category, but does it really belong in General Discussion?

3

I think it's this, but no one here will probably be able to help since it's not Ignition related and specialized software that many probably haven't used.

4

Ah, sorry. I just descover this forum so i don't know how to use.

5

Yes, correct, it is this one. I will post in General Discussion. Thanks!

6

Have you tried turning off the firewall on both VMs? I've had this happen with other software, the cause was that their communication use multiple ports, some of which were blocked by the firewall.

7

Yes of course. All firewalls are down on all virtual machines also on the host.

8

Did you ever get this to work? With Echo Emulator being a Rockwell development tool I would think this should work and be beneficial to anyone wanting to develop an ignition system to work with Rockwell controllers.

I recently got a project and will want to use this configuration.

9

Reading produced tags is a Class1 operation, and has different firewall requirements (and typically required non-NAT addresses for each participant).

10

So I got off phone with Ignition support and figured out the problem. When using the Echo Emulator when you create a Compact Logix device it is not part of a Chassis slot 0,1,2,3,etc but instead uses the A1 and A2 ethernet ports. I have ignition on one VM and the Emulator on a second VM set up with NAT 10.10.10.128 for Emulator and 10.10.10.129 for ignition.

The secret is that the A2 ethernet port on the CompactLogix device on the Emulator must be set to 10.10.10.128 NOT the A1 port which I originally set to 10.10.10.128

Once this change was made Ignition connected and in the designed, I was able to browse all the tags.