Tutorial: Components
Navigation: Administration > Projects > ProjektAlpha (selected project) > RouterAlpha (selected device) > Interfaces
Depending on the device type, you can add and manage both components and tags for your device from the submenu "Interfaces".
- System: Here you find all possible device-specific system tags. Here you can only add tags from the type "Scripting Variable".
- IoT: Here you can, among other things, enable IoT services, make IoT settings and create mbEDGE tags.
- LAN: Here you can add Network Components (like a PLC, PC, print server, NAS, etc.) and manage them.
- Serial COM1(2): If you have chosen in the interface settings under Mode = Tag Server, you can add components to the serial port here and manage them.
- MPI/PROFIBUS: Here you can add MPI/PROFIBUS components and manage them.
Notice
After you have added a component, you can add tags for it.
1. Add component and activate logging
2. Why are the tag values invalid or why is the tag server not reachable?
1. Add component and activate logging
2. Why are the tag values invalid or why is the tag server not reachable?
If a tag at a network component has an invalid value (see screenshot below) or if the tag server is not reachable, please ensure the following:
Please note:
With a mouse-click on the red exclamanation mark you can see more information.
- The connected component must be reachable from the mbNET. You can ensure this with a ping-request on the device web interface under "Advanced" ~> "Status" ~> "Diagnostic" ~> "Ping":
- In the configuration of the component the access via PUT/GET-communication through distant partner (PLC, HMI, OPC, ...) must be allowed. At a Siemens® component you must configure this under "General" -> "Protection" -> "Connection mechanism" in the TIA® portal:
- Furthermore, the configured "Port" / "Slot" / "Rack" at the tag server must accord with the PLC configuration:
Please note:
If needed, you can select the type "ModbusTCP" as the tag server. But this depends on your component, what is possible.
The tag server is in the mbNET integrated. So, the mbNET acts as a Master in this case.
Revision: V1.1 |
---|