I developed a solution in Ignition 8.3.3, but the client wants 8.3.0. I created a new development VM (Windows 11) and installed Ignition 8.3.0. I backed up the views, UDTs, and tags and restored them to the new 8.3.0 VM. I set up the gateway to be the same as the 8.3.3 version, with the device connection pointing to the new VM. The device will not connect to the new VM emulator (BATO-Ign830). I threw in the old configuration (just the machine name), and it connected to the 8.3.3 emulator (BATO-IgnEdge).
Not if they're smart. The first release of any minor or major version is rarely completely production ready.
What’s the error that appears on that plc connection? (if one does)
Did you set up the firewall in the new vm to allow ignition to connect to the right plc ports?
2 Likes
It is a new VM using the same Windows template VM. All fresh installs of Rockwell and Ignition. Run the latest patch rollup from Rockwell, and run the firewall utility. No error message, only the RECONNECTWAIT status.
Still worth checking if the firewall ports are open
I turned the firewalls off for all connection types, same results, cannot connect to the local emulator.
Have you tried changing the hostname on the PLC connection settings to localhost or 127.0.0.1?
If that works it could be a DNS (windows vm name issue).
Also, to rule out rockwell issue (some rockwell service failed to run) are you able to connect to the PLC on the new vm from the 8.3.3 gateway as it could be an bug with 8.3.0.
Lastly, I would try telneting to port 44818 to see if the vm is listening on it.
telnet 127.0.0.1 44818
The telnet didn’t work for any of the VMs. I did do a gateway backup of the VM that did not connect, and created a new VM from a Windows 11 template (same one). I restored from the backup in the new VM, and it worked fine. I had also sent a backup to my client, who restored it and was able to connect to a real PLC.
