The information in this post is provided to assist in troubleshooting. Perform work at your own risk. ENSURE ANY POWER FROM DEVICES HAS BEEN DISCONNECTED BEFORE SERVICING ANY EQUIPMENT. If you do not feel comfortable performing the work, please contact us or your local service center. Be aware that ETC and its Affiliates are not responsible for any damage or injury caused by service of our products by anyone other than us or our authorized service providers, and such damage is excluded from the product’s warranty.
After a reset, MSCs look for a file called "LPC.cfg" on its FAT32 formatted SD memory card before using its current settings. MTPCs and MTS hardware look for a file called "TPC.cfg."
You can use a text editor (e.g. Notepad) to create this file and copy it to the memory card to force the issue, useful for transferring the IP settings on the card with the project data. Any settings within this file will override settings set from within Designer. The format of the text in the file should be:
ip 192.168.42.56 255.255.255.0 192.168.42.250
|ip||Required||Defines the IP address, subnet mask and default gateway for the controller|
|http||Optional||Defines the HTTP port used by the controller (default 80)|
|dns1/dns2||Optional||Defines a domain name server (DNS) for the controller to use to resolve host names|
|ntp||Optional||Defines the IP address of an ntp server that the controller should get its time from|
|syslog||Optional||Defines the IP Address of a syslog server on the network|
|loglevel||Optional||Defines the log level to be used by the controller|
|watchdog off||Optional||Disables the controller's watchdog (not recommended), omit line to enable watchdog|
Using the MTPC.cfg or MSC.cfg file to store the Controller's configuration on the memory card allows a Controller to be swapped, in case of failure for example, by just moving the memory card into another Controller.