Machine networks

SMOKE

Member
Join Date
May 2006
Location
East and West of Kaos
Posts
475
Wish I knew new more about the subject.
How do you protect your machine from the network.
Do you use 2 Ethernet cards on the rack or processor and rack?
Or do you have a configurable switch with the PLC behind... If I even know what I am saying.
 
sorta old funny thing from old days. Can you expound. I am in need of an education here. Not on the 2 PLC ethernet thing but on the switch.
 
Last edited:
The best way to protect the machine from the network is to keep it away from it completely.

Second best thing is to use a separate network for automation.

If you need to connect the automation network to the outside world (IT and further), place a tightly controlled firewall in between and make sure YOU control it, not the IT guys. Usually they don't have a clue what automation needs and mostly they don't even bother to give a damn about it.

Kind regards,
 
Dont let IT guys do PLC work and dont let PLC guys do IT work and it works out ... LOL that ways the roads dont cross paths. Its like railroads and DOT guys .... keep em seperate to put it simple. In some plants people like to dabble in every thing but like the man said keep information on one highway and automation on another highway. Only exchange data when necessary. As a PLC guy you decide what is necessary and you will keep YOUR stuff safe
 
My arrangement uses two firewalls, with a "DMZ" in the middle, the DMZ contains machines that need access to both networks, typical DMZ applications are data historians, configuration apps., and perhaps backup devices (tape, data storage units etc...)


Business LAN (BLAN)-|firewall| historian |firewall|---Process control network
 
Last edited:
Yes - this arrangement is good. Keeping the networks separate is better (from a security perspective), but not usually possible. If you have the resources, you can expand on this idea with separate subnets and VLANs and routers in between.

Elitheei's comment has a little practical merit, but is way off base. Most PLC guys are pretty clueless about networking and security, which is where IT can help. Just use discretion when working with them - they need to know to do things differently like not automatically patching workstations, or installing anything for that matter. Similarly, IT guys won't know a thing about PLCs and process control - that's your realm as the PLC guy. It's a matter of communication, policy/procedure, and where the line is drawn.

My arrangement uses two firewalls, with a "DMZ" in the middle, the DMZ contains machines that need access to both networks, typical DMZ applications are data historians, configuration apps., and perhaps backup devices (tape, data storage units etc...)


Business LAN (BLAN)-|firewall| historian |firewall|---Process control network
 
Thanks for replies.
I got a second EBNT card I think even with a router between the switch my system needs it. I am using some Enet/IP for I/O. I have 6 gateways on the system each can handle 64 inputs and 64 outputs. A 2 axes RMC and a VersaView. Then there is a SQL server on the other side.
 

Similar Topics

Hello Everybody Anybody knows where I can get this version of SoMachine? The new machine expert version won't open my project saying there is a...
Replies
0
Views
32
Hello, As part of our project, we are using an M241 controller. This controller interfaces with an industrial computer and a router via a switch...
Replies
2
Views
97
I'm getting frustrated creating arrays of variables in Machine edition. I need to make 2 variable arrays that are 102x2 in size, with varying...
Replies
3
Views
103
Hello, I am still new to PLC programming and I just got this job two year out of school so I don’t remember much. I was given a task were I have...
Replies
1
Views
167
I am trying to connect with a Schneider plc which has a firmware version only available in Somachine v4.2. In Machine expert After taking upload...
Replies
0
Views
110
Back
Top Bottom