{"id":757,"date":"2016-02-12T15:34:30","date_gmt":"2016-02-12T22:34:30","guid":{"rendered":"https:\/\/pncommander.wpengine.com\/?page_id=757"},"modified":"2022-08-24T13:16:41","modified_gmt":"2022-08-24T20:16:41","slug":"faq","status":"publish","type":"page","link":"https:\/\/profinetcommander.com\/faq\/","title":{"rendered":"FAQ"},"content":{"rendered":"<h2>Tips<\/h2>\n<ul>\n<li>Make sure to assign your device names properly<\/li>\n<li><span>I\/O display update rate: the default is 32ms and should be equal or above the device update time set in the project<\/span><\/li>\n<li><span>NIC selections can be saved by selecting the option from the options menu<\/span><\/li>\n<\/ul>\n<h2>Frequently Asked Questions<\/h2>\n<p>Click on a Frequently Asked Question below for the appropriate answer. If you\u00a0have an\u00a0issue that isn&#8217;t addressed\u00a0here, <a href=\"https:\/\/profinetcommander.com\/contact\/\">Contact Us<\/a>\u00a0or reference the <a href=\"https:\/\/profinetcommander.com\/documentation\/\">Documentation<\/a>.<\/p>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>TIA Configuration Software lists a \u201cCompile Error\u201d without any details.<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>This usually means that the XML File in use by PROFINET Commander can\u2019t 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)<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>When importing the XML file I get the error \u2018invalid configuration\u2019 or \u2018invalid file argument\u2019.<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>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.<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>PROFINET Commander won\u2019t start or immediately closes.<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>Double-check the dependencies from the installation section (especially Npcap for V5.1.0.8 or higher, or WinPcap for V5.1.0.7 or lower).\u00a0 Try to restart your computer and check again if problems continue. <\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>Will PROFINET Commander work while plugged into a switch monitor (mirror) port?<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>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.<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>Device is not coming up (always offline).<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>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 \u201cdisplay\u201d 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. Try to set the update time to the slowest value in the engineering tool (512ms). Also ensure that there is no firewall\/antivirus\/malware scanner on the PC which could block the communications (port 34964 and Ethertype 0x8892 should be possible). Usually Windows Firewall is OK, but if there is another firewall it should be disabled or an exception set. Check that you have selected the right network interface for communications. <\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>Device always shows a diagnostic or error.<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>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.<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>Device keeps going online then offline continuously.<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>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\u2019t need to see if that helps.<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>Diagnostic LED in commander never turns off.<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>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.<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>The diagnostic alarms from the device(s) are only showing a number, no text.<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>This can happen if the GSD files cannot be found on your system in the following folders:<\/p>\n<ul>\n<li>TIA GSD<\/li>\n<li>PROFINET Commander GSD<\/li>\n<li>User supplied (via Options)<\/li>\n<\/ul>\n<p>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<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>The device keeps sending a remote mismatch error and clearing the error and it\u2019s right beside the PC.<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>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.<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>Do I need a separate license for TIA Portal configuration tool?<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>No, PROFINET Commander only needs one license because it uses the PN Driver object in TIA Portal. This is considered a \u201cPC Station\u201d and does not require an additional license for TIA. TIA requires a license if programming Siemens PLC\u2019s (like S7 1500, 1200, 300 \/ 400, etc.).<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>Under my NIC selections it just shows \u201cMicrosoft\u201d on my adapters?<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>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. Once you find the correct card you can turn on \u2018save NIC selections\u2019 under the options menu to save the setting.<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>The software keeps stating 'not a valid adapter' or similar<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>Make sure to select a valid adapter prior to importing and starting the controller or browsing the network. If network adapters have changed in the meantime restart the software and try again. If you are using a USB adapter this may require restarting the Npcap (or WinPcap) service. Start a command prompt with admin rights and type net stop npcap then hit enter. Then once the service stops type net start npcap and enter again. (or use npf for WinPcap) Then restart PROFINET commander and try again. Make sure the adapter in question works with Wireshark as well.<\/p>\n<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>How to get the latest software updates?<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>To use the automatic update feature a license and 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.<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>When starting the controller (online\/run) I get 'ModDiffBlock was detected'?<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>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 \u2018shared device\u2019 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.<\/div><\/div>\n<div class=\"su-spoiler su-spoiler-style-simple su-spoiler-icon-plus su-spoiler-closed\" data-scroll-offset=\"0\" data-anchor-in-url=\"no\"><div class=\"su-spoiler-title\" tabindex=\"0\" role=\"button\"><span class=\"su-spoiler-icon\"><\/span>Oops, I loaded the latest PROFINET Commander version 5.1.0.8 or higher with Npcap, which deleted WinPcap, but need compatibility on the same system with some older software based on WinPcap<\/div><div class=\"su-spoiler-content su-u-clearfix su-u-trim\">\n<p>In this case you can go under the application directory (usually C:\\Program Files (x86)\\PROFINET Commander) and Redistributable folder.\u00a0 In this folder you will find Version 5.1.0.7 which is the last version supporting WinPcap.\u00a0 Simply install this and run the uninstall for PNC and Npcap during the process, then the installer will ask you to install WinPcap and you&#8217;ll be good to go.<\/p>\n<\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>Tips Make sure to assign your device names properly I\/O display update rate: the default is 32ms and should be equal or above the device update time set in the project NIC selections can be saved by selecting the option from the options menu Frequently Asked Questions Click on a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-757","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/profinetcommander.com\/wp-json\/wp\/v2\/pages\/757","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/profinetcommander.com\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/profinetcommander.com\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/profinetcommander.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/profinetcommander.com\/wp-json\/wp\/v2\/comments?post=757"}],"version-history":[{"count":0,"href":"https:\/\/profinetcommander.com\/wp-json\/wp\/v2\/pages\/757\/revisions"}],"wp:attachment":[{"href":"https:\/\/profinetcommander.com\/wp-json\/wp\/v2\/media?parent=757"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}