Timbert
Member
I've currently writing a best practices/guidelines for a system I'm working on. The system consists of eight Guardlogix processors connected over EtherNet/IP using Stratix 8300 switches. Several of the GuardLogix systems are embedded in other subcontractors' systems. I will be doing the rest; I'm also co-ordinating the project.
So, I want to write a document that outlines how to program and configure the system so that it will be easy to integrate and will have consistency between systems when troubleshooting years down the road.
The project is nearing the end of the conceptual design stage.
Things I have on my list to include are IP address, subnet masks, VLANs. Naming convention for processors, I/O modules, controller-scoped tag names. I'm providing sample code for various functions, emergency stop, end-of-travel limits, etc.
1) What should I include in such a document?
2) What should I not include in such a document?
If you've worked on such a project in the past what pitfalls were there. What did you do right; what did you do wrong?
So, I want to write a document that outlines how to program and configure the system so that it will be easy to integrate and will have consistency between systems when troubleshooting years down the road.
The project is nearing the end of the conceptual design stage.
Things I have on my list to include are IP address, subnet masks, VLANs. Naming convention for processors, I/O modules, controller-scoped tag names. I'm providing sample code for various functions, emergency stop, end-of-travel limits, etc.
1) What should I include in such a document?
2) What should I not include in such a document?
If you've worked on such a project in the past what pitfalls were there. What did you do right; what did you do wrong?