So it is getting late, and I could use a sanity check on my understanding of how to set up my network.
I want my strategy to send a daily status email. The problem is my controller is currently only on the machine network, and can't see the email server.
Each machine has an attached Windows computer running PAC Display that has dual NIC's, one on the corporate network and one on the machine network. However, the PAC Display email functionality is sort of limited, sending only alarm points. Emails sent by a controller appear to be easier to customize, with more formatting and content control.
The primary ethernet port of the R1 controller is on the machine network. The second ethernet port is available. However, to wire it, I'd need to add a switch for the corporate network to the machine because there is only a single hard line dropped (connected to the computer). The existing machine network switch is unmanaged, so even if I had spare ports, mixing traffic in the switch probably wouldn't be the best. The cost of swapping out the unmanaged switches for something better (VLAN support) would add up quick. Also, I'm already approaching the limit for simultaneous charts running in the strategy. Adding the email functionality to one already running would be a logical hack, but I don't want to spend one of my chart allocations on a chart that will barely run.
Another alternative might be to run SoftPAC on the PAC Display computer to handle email requirements. If I want SoftPAC to see the tags in the controller to populate an email, what is the best way to do that, given PAC Display is also running on the same computer... OptoOPCServer? The computer's resources are substantially used to run a vision inspection program, but if SoftPAC isn't too heavy, that could be a clean solution.
Any thoughts? Wifi is not an option.
Machine network architecture
PAC Display Computer
R1 Controller+I/O modules on the rack
8+ TCP/IP or Modbus TCP controlled devices
Machine Windows Computer responsibilities (right now)
Vision inspection (fed by two dedicated gigabit NIC's)
FTP (for file transfer with the controller)
TightVNC (remote admin via corporate network)