This usually means that the XML File in use by PROFINET Commander can’t be overwritten. If you are compiling, shut down PROFINET Commander prior to compile or copy the XML file to a different location each time (ex: Desktop)
This means that your TIA Portal configuration is invalid or you are using the wrong file type. Typical reasons include not putting the device in the configuration and attaching to the controller, only the controller. Or another reason might be that you are importing the wrong file (for example a device GSDML file) instead of an actual configuration file. If you still have trouble after checking these items see the manual for a configuration example or contact support.
Double-check the dependencies from the installation section. Double-check for a valid license or if another window appears (license window).
No, connecting to a monitoring port on a switch causes duplicate frames to be sent to the driver and this can cause communication issues. A switch port monitor is not supported at the same time. Disable any monitor ports on the switch prior to running PROFINET Commander.
Make sure you have set the controller to operate mode. Check that the name has been set and you can see the device with the PN browser. Note that the configuration tool “display” name and device name may not match. You can see what the actual name should be by clicking on the device in commander and viewing its properties or looking in the engineering tool at the PROFINET device name setting in the devices properties.
See if alarms window shows any information. Check that you have configured the device and modules properly with the correct fw and revision. Highlight the device and under read/write record read the diagnostics (0xF80C) to determine the error (or see alarm info). Also you can see the module diff block record (0xE002) to determine what modules might not be configured properly.
Check the update time set on the device(s). As Windows is not a real time OS, some other tasks could interrupt PROFINET communications at fast update times. Set the device(s) to 512 ms and try again as a test, and then you can adjust down incrementally to see what works best on your system to a minimum of 32 ms. You can also try to figure out what tasks are running simultaneously and close other programs you don’t need to see if that helps.
This can happen if there was a preexisting diagnostic prior to the startup on a device and is a known issue. Fix the diagnostic issue on the device and then stop and start the controller again to clear it. We are planning a fix in a future version.
This can happen if the GSD files cannot be found on your system in the following folders:
- TIA GSD
- PROFINET Commander GSD
- User supplied (via Options)
Make sure the GSDs for the devices are located on your system and you are running the software with Admin rights. Also make sure the GSD file name conventions are correct as it helps the tool find the correct GSDs
If you have configured a topology based system for diagnostics testing or device replacement the device is signaling an error because the PC is likely sending multiple LLDP messages (like Windows LLDP + PROFINET info) and confusing the interface. Be sure to disable other LLDP protocols under your network adapter settings. LLDP is already built into the PROFINET Commander driver.
No, PROFINET Commander only needs one license because it uses the PN Driver object in TIA Portal. This is considered a “PC Station” and does not require an additional license for TIA. TIA requires a license if programming Siemens PLC’s (like S7 1500, 1200, 300 / 400, etc.).
In some special cases, this is an issue coming from the underlying drivers when requesting the NIC information and there is no current workaround. In this case, you should try each selection where Microsoft is listed and see which card it applies to (ex: wired or wireless NIC). Once you find the correct card you can turn on ‘save NIC selections’ under the options menu to save the setting.
To use the automatic update feature a license an Internet connection are required. The software will check the server at startup if an update exists and notify the user if so with a dialog. Another way to get the update is to manually download the latest (free) version from the website. Install the latest free version and the license will be detected and all updates activated.
A ModDiffBlock can mean multiple things. For example, it could be a mismatch between the actual device configuration and the offline configuration (fw rev not matching, missing modules/submodules, wrong modules/submodules), that the device is locked by another controller/process, or that there could be an active (in place) diagnostic. Select the device in question and enter the R/W Record dialog. Read record 0xE002 (Module Diff block for one AR) to see what modules/submodules have the issue and then correct the underlying problem. A substitute module/submodule is usually OK (probably a firmware difference, check the GSD file and versions) and the device will continue normal operation even with the ModDiffBlock; however, a wrong or missing (unplugged) module will not work until corrected. Check your configuration if a wrong module and change the device configuration or check real hardware if a module is missing, not plugged in. If a diagnostic is detected you can read diagnostics to attempt to get more info or check the alarms/info pane from the main window display. If the device is locked by another controller it means that no more than one controller has access to the device at a time, check shared device settings if trying to setup ‘shared device’ in the device configuration. Note that sometimes a ModDiffBlock may be incorrectly signaled with a device under development if the modules are not plugged into the device firmware/stack correctly. Or sometimes this may happen with gateways / proxies if they are using virtual modules or are not ready for startup.