# FT Echo and Ignition

**URL:** <https://forum.inductiveautomation.com/t/ft-echo-and-ignition/93611>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [July 23, 2024, 4:12pm UTC](https://forum.inductiveautomation.com/t/ft-echo-and-ignition/93611 "2024-07-23T16:12:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jfchicat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jfchicat/32/63831_2.png) [@jfchicat](https://forum.inductiveautomation.com/u/jfchicat)\
**Post date:** [July 23, 2024, 4:12pm UTC](https://forum.inductiveautomation.com/t/ft-echo-and-ignition/93611/1 "2024-07-23T16:12:51Z")

</div>

What causes the gateway not to connect with a loopback address assigned to a controller in FT Echo? The device was created as an "Allen-Bradley Logix Driver"  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/c/bc6fe943f263bb6fc6a3dd8ba6feaab86c76fd2c.png)

---

<div class="post-metadata">

**Author:** ![jfchicat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jfchicat/32/63831_2.png) [@jfchicat](https://forum.inductiveautomation.com/u/jfchicat)\
**Post date:** [July 23, 2024, 4:43pm UTC](https://forum.inductiveautomation.com/t/ft-echo-and-ignition/93611/2 "2024-07-23T16:43:55Z")

</div>

To answer my own question, as the loopback does not work, just set up multiple non-loopback IPs following the instructions below:  
[How to Set up Multiple IP Addresses on a Computer (loadtestingtool.com)](https://www.loadtestingtool.com/help/how-setup-ip.shtml)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 23, 2024, 5:17pm UTC](https://forum.inductiveautomation.com/t/ft-echo-and-ignition/93611/3 "2024-07-23T17:17:09Z")

</div>

Have you tried using the `netstat` tool in a terminal to determine what IP address FT Echo is using for listening (on port 44818)?

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [July 23, 2024, 5:51pm UTC](https://forum.inductiveautomation.com/t/ft-echo-and-ignition/93611/4 "2024-07-23T17:51:52Z")

</div>

That would be my guess as to what is wrong. When you configure a controller in FT Echo, you have to specify the IP address on the computer you're assigning that controller to. I've got a server set up in our office with 10 IPs on it so we can run multiple controllers at different IPs as tests and whenever I create a new one, I have to specify the IP I want it to use.

Also, if you're using 127.0.0.1 that means you're running Ignition on the same PC which I don't know if I'd recommend that even for testing.

Example:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/a/eadf90fd320995c7838d99f3c039e2cd2f505825.png)