Recently, I started using the Inovance HU5 series PLC, and I am documenting the methods for configuring I/O and the pitfalls encountered.
Since I did not use Inovance’s I/O but instead configured a certain brand of EtherCAT remote I/O module, the first step in configuring EtherCAT is to download the XML file from the official website and then import the relevant files. However, I overlooked a specific folder named <FOR AutoShop> in the downloaded folder and directly imported an XML file from the download directory. The import was successful, and after double-clicking to configure, various issues arose. First, when I closed the program and reopened it after configuration, it reported that some garbled XML files were missing from the EtherCAT configuration. Then, the information for the newly configured I/O module reported errors, and the software crashed. Various attempts to configure, including uninstalling and reinstalling the software, did not resolve the issue. It was only during the last reinstallation that I noticed there was another folder named <FOR AutoShop> within the XML folder. Upon opening it, I found a document stating, “The contents of this folder are specifically for use with the Inovance Autoshop platform.” After reading this, I could only cry silently…
After re-importing the new XML file, everything worked perfectly. I will also document the method for directly mapping the remote I/O to XY without needing to write a program. First, create a new variable based on the variable type of the remote I/O, and then enter the input/output addresses you want to bind in the soft component address of the variable. This way, during configuration, the module address is directly bound to XY.