Congratulations on being the 10.000th person to get caught by the .local extension when defining EPIC hostname. Let’s hope Opto22 can resolve this annoying “feature/bug” this year. It seems more of an EPIC application level problem than an operating system level problem as the Ignition Edge internal access has no problem in handling 127.0.0.1 “as is”
If you feel happy using PAC Control and your only problem in life is providing a VIEW operator interface for Profibus devices or integrating limited Profibus data into the PAC Control Engine environment, then perhaps the answer is to use the Ignition Edge Gateway to handle your Siemens connectivity and then read/write the data into the PAC Control Engine, using PAC Control Subroutines.
Obviously, using HTTPS Get/Post commands is not the most optimized highspeed industrial polling protocol out there, but for low capacity requirements, they are good enough and at least you get to go home at night, which is more than you are going to manage, diving into the murky depths of CODESYS.
You can check out the subroutines at:
Integrating Ignition Edge Gateway Tags into the EPIC Control Engine