When developing HMIs using Rockwell, I've always done RSView32. I now have a customer requesting SE simply because it is the 'latest'. This will be their first install of SE as well as mine. I have toolkit access to ABs download site, but there's a multitude of products under the FactoryTalk family, and I'm unsure where to start.
The installation will be single use HMIs (not distributed) on various parts of a production line, communicating to CLX processors. The HMI will be PC based.
Soooo....what in the devil do I need?
What's the difference between ME and SE? Can SE be standalone as it seems more tailored to distributed architectures? The various packages available are:
FactoryTalk ME StationRT (I assume a standalone Runtime)
FactoryTalk ME Studio Edition (Maybe development for the above)
FactoryTalk SE Station (is this RT only?)
FactoryTalk SE Client (how is this different from Station?)
FactoryTalk SE Server (Do I need for standalone)
Factory Talk V Studio for Enterprise (What is this?...The whole kit and kaboodle)
I'm used to RSView32 Runtime and Works...Works to develop, Runtime to run. What is the equivalent for FactoryTalk?
The installation will be single use HMIs (not distributed) on various parts of a production line, communicating to CLX processors. The HMI will be PC based.
Soooo....what in the devil do I need?
What's the difference between ME and SE? Can SE be standalone as it seems more tailored to distributed architectures? The various packages available are:
FactoryTalk ME StationRT (I assume a standalone Runtime)
FactoryTalk ME Studio Edition (Maybe development for the above)
FactoryTalk SE Station (is this RT only?)
FactoryTalk SE Client (how is this different from Station?)
FactoryTalk SE Server (Do I need for standalone)
Factory Talk V Studio for Enterprise (What is this?...The whole kit and kaboodle)
I'm used to RSView32 Runtime and Works...Works to develop, Runtime to run. What is the equivalent for FactoryTalk?