Author Topic: MX-RTC  (Read 11489 times)

Mark York

  • Guest
MX-RTC
« on: September 19, 2005, 05:40:18 PM »
I installed a T100MD1616 with the MX-RTC option on a piece of equipment that was shipped to a customer about 2000 miles away. The equipment is in a remote location so no phone lines are available. The customer has hinted that he might want me to make some modifications to the program. My question is this; Is the program stored in the non-volitile memory of the MX-RTC option? Can I purchase a new MX-RTC, install it in a T100MD1616 here in the office, download the revised program, remove the MX-RTC, and send it to the customer in an overnight envelope? Or does the MX-RTC option only store register values.
Thank you
Mark

dan

  • Newbie
  • Posts: 47
    • View Profile
Re:MX-RTC
« Reply #1 on: September 20, 2005, 07:11:08 AM »
Mark,

"One important new addition for OEM is the ability to export compiled code to a file which can be uploaded into the PLC using a standalone "TL5 Uploader" program. This makes it easier for OEM to distribute software self-upgrade for their equipment without giving the source code to the end user and without the need to purchase the production version of Internet TRiLOGI software for the end user."

I used this feature several times and it works.
I hope this will help

Dan

support

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3174
    • View Profile
    • Internet Programmable PLCs
Re:MX-RTC
« Reply #2 on: September 20, 2005, 09:19:40 AM »
The TL5Uploader is a good option to distribute software update. Of course other means is by using modem or Internet connection if these are available.  One last resort is to buy the expansion memory module M2018P (US$20). You can transfer program to M2018P and use it to replace the M2017P module on the PLC. M2018P gives you more program memory (8190 words) and data EEPROM memory (7700 words) than the original M2017P and is available in stock for single quantities purchase.

(Note: The standard M2017P module is not available for retail except through special order direct from factory and there is a minimum order of 10 units).
« Last Edit: November 14, 2005, 02:21:42 PM by support »
Email: support@triplc.com
Tel: 1-877-TRI-PLCS

benb2000

  • Jr. Member
  • Posts: 56
  • I love YaBB 1G - SP1!
    • View Profile
Re:MX-RTC
« Reply #3 on: November 14, 2005, 01:42:49 PM »
What is the expected number of Write Cycles ( Lifetime)  of the the M2018P module?

support

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3174
    • View Profile
    • Internet Programmable PLCs
Re:MX-RTC
« Reply #4 on: November 14, 2005, 02:24:01 PM »
The EEPROM has written life of 100,000 cycles. This means that it is not meant to be written to every scan of the ladder program (such as to prevent loss of data due to power failure). the EEPROM is to be written to upon a certain condition such as an event occurence. If you wish to maintain non volatility during a power failure then you should use the MX-RTC together with DIP Switch #1 to achieve it.
Email: support@triplc.com
Tel: 1-877-TRI-PLCS

benb2000

  • Jr. Member
  • Posts: 56
  • I love YaBB 1G - SP1!
    • View Profile
Re:MX-RTC
« Reply #5 on: November 14, 2005, 02:29:07 PM »
If I write 7700 words to the unit does this mean 7700 write cylcles have been used? so that I have only 13 occasions to do this, or is this one write cylce with 7700 elements written?

support

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3174
    • View Profile
    • Internet Programmable PLCs
Re:MX-RTC
« Reply #6 on: November 14, 2005, 07:56:59 PM »
Each memory location can have write cycle of 100,000 times. Thus  if you move the memory pointer around so that you "spread" out the saving it can extend the life of the EEPROM.

However, please note that SAVE_EEP is very processor intensive because during SAVE_EEP execution (about 10ms) the CPU shut off all interrupts to prevent corrupting the EEPROM. So use it prudently.
« Last Edit: November 15, 2005, 08:53:49 AM by support »
Email: support@triplc.com
Tel: 1-877-TRI-PLCS