Author Topic: TCP-IP and ID goes to 0xFF  (Read 336 times)

acxysty

  • Newbie
  • Posts: 35
  • I'm a llama!
    • View Profile
TCP-IP and ID goes to 0xFF
« on: April 13, 2022, 07:29:47 AM »
Dear All
We are a FMD-88 in a larger electronic device to exchange modbus information by RS232 and RS485.
From time to time  we are losing  TCP-IP and ID communication parameters on a power-down/power-up sequence. Typically an emergency stop sequence.
As it happens rarely, it is difficult to understand the reason behind that.
We can recover the FMD using TLServer over RS232 to retrieve a "new" ID, to re-configure / re-connect again by TCP-IP
What could be the reason of that ?
Does this has to do with eeprom ?
Thank in advance for your ideas and support.
Regards
Thierry

support

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3139
    • View Profile
    • Internet Programmable PLCs
Re: TCP-IP and ID goes to 0xFF
« Reply #1 on: April 13, 2022, 09:56:25 AM »
Does your FMD PLC have FRAM-RTC?

If the PLC does not have FRAM-RTC installed, then are you using a power failure interrupt routine to save parameters using SAVE_EEPx to non-volatile memory  during a power failure? Or is your program running the SETTIMERSV or SETCTRSV command during operation and need to be saved to non volatile memory before power failure?

Please refer to Section "1.7.2  Non-Volatile Data Store" in the FMD PLC User Manual which explains how the pseudo EEPROM works and why you could lose data if power failure interrupt routine is not given enough time to back up the pseudo EEPROM data to flash memory.

When you power down a machine by turning off the AC power, the DC output of the power supply usually have enough capacitance to gradually decay to zero so the power failure interrupt routine can work properly.

When you press the emergency stop button, did you cut off the DC power supply to the PLC immediately? If so then the interrupt service routine is not given enough time to save the parameters. What happens is that the flash sector is erased but the CPU did not have enough time to copy the pseudo EEPROM data to the flash and therefore you lose the Ethernet parameters as well.

If you wire your emergency stop button such that it only cuts off power to the I/O but not to the PLC, then this issue should not happen.

Alternatively, organize your program so that if you need to save some data to non-volatile memory or need to change the timer or counter set values using the SETTIMERSV or SETCTRSV, then do so in the main program itself and execute the SETSYSTEM 252, 0 command to backup the new data to the flash memory  immediately so that the CPU will not attempt to save the changed data to flash memory during power failure. Of course you should take into consideration that there is a 100K erase/write limit to flash memory and therefore your program must avoid erasing/rewriting to the flash memory so often that exceeds its life cycle limit and wear out the flash memory.
« Last Edit: April 14, 2022, 07:10:35 AM by support »
Email: support@triplc.com
Tel: 1-877-TRI-PLCS

acxysty

  • Newbie
  • Posts: 35
  • I'm a llama!
    • View Profile
Re: TCP-IP and ID goes to 0xFF
« Reply #2 on: April 13, 2022, 11:31:12 PM »
Thank you for all these information.
Yes we have read many times the User manual, but obviously we are missing a point ...
Is there a kind of 'automatic' (not programmed by us) routine that interact with the EEPROM ?
We will review again our program and report to you.
Regards
Thierry