In the mechatronics program, at clover park technical college, I learned about different busses, protocols, standards, and basic components for networking. Such as Ip-addressing, I2C, etc. I got a very hands-on learning experience, including walking up to different systems and documenting the current condition, composing a maintenance plan, and creating technical documentation on the system as a whole.
Profibus technical documentation with visuals:
A visual representation of a topology for an existing profibus network. As well as any notes, things I felt I might find useful for future reference
Maintenance plan:
A visual representation of how to maintain this profibus network. Including pictures, tables, explicit instructions on how to maintenance properly, etc. (This being the same network as mentioned above.)
Hands-on industrial networking:
In one of the labs for industrial networking, some of my peers and I created a master-slave bus network, where the master could tell the slaves to, for example, turn on their LEDs, or, where the slave sends the master a specific message signal in the serial monitor.
As one of the labs in Industrial Networking we managed to make 3 Arduinos (slave devices) to send messages to the master.
As one of the labs in Industrial Networking, we managed to make a master Arduino tell the slave Arduino to turn on, or off it's LED.
Examples of code:
In one of the networking labs I cut several ethernet cables to specific lengths, then hand wired them to different standards.
In this video I will be testing 3 different CAT5e ethernet cables that I wired according to the T-568B, T-568A, and a crossover where its simply the A and B on the opposite sides.
For one of the labs in networking we connected several Click PLC's to a hub, changed their IP addresses, and then connected the laptop/computer to the hub to "ping" each one (using the command prompt on the computer, you can type in "ping 'IP address' ", and it will detect if its connected, and on the network). We created a deployment map, and any technical documentation that we thought we needed.
Click Deployment map:
Technical documentation:
For one of the labs in networking, I connected 3 Siemens PLC's to a hub; And then using a laptop with the Siemens Proneta on it connected to the same hub, and from there it would automatically detect all the devices on that network, showing the topology, and each individual IP address and subnet masks. We created a deployment map, and any technical documentation that we thought we might need for future reference.
Siemens Deployment Map:
Technical documentation:
We also learned about things like the OSI model, HMI's, RS485 or RS232 standards etc.,
(taken from BMC online: https://www.bmc.com/blogs/osi-model-7-layers/)