1. Home
    1. Dashboard
    2. Search
  2. Forum
    1. Unresolved Threads
    2. Members
      1. Recent Activities
      2. Users Online
      3. Team Members
      4. Search Members
      5. Trophys
  3. Articles
  4. Blog
  5. Videos
  6. Jobs
  7. Shop
    1. Orders
  • Login or register
  • Search
This Thread
  • Everywhere
  • This Thread
  • This Forum
  • Articles
  • Pages
  • Forum
  • Blog Articles
  • Products
  • More Options
  1. Robotforum - Support and discussion community for industrial robots and cobots
  2. Forum
  3. Industrial Robot Support and Discussion Center
  4. Fanuc Robot Forum
Your browser does not support videos RoboDK Software for simulation and programming
Visit our Mainsponsor
IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Sponsored Ads

Maintenance Reminder - Interpreting $MR_HIST variables

  • AnandTUD
  • March 12, 2025 at 8:56 AM
  • Thread is Unresolved
  • AnandTUD
    Reactions Received
    12
    Trophies
    2
    Posts
    42
    • March 12, 2025 at 8:56 AM
    • #1

    Hello everyone,

    Hope you are doing fine.

    I would like to get the maintenance reminder status and send it across to a HMI. I know that it is possible to set a DO to prompt it. However, I would like to automate this process and I am unable to set this DO through a system variable. Could someone help me in interpreting the system variables $MR_HIST? Maybe using the $DONE_DATE, $DUE_DATE, $DONE and $RECORDED, would it work?

    Thanks and Regards

    Anand

  • gtafbi
    Trophies
    1
    Posts
    1
    • March 14, 2025 at 10:42 AM
    • #2

    If I'm not entirely mistaken (which is certainly possible) the $MR_HIST[x]
    system variable only contains a list of maintenance that either has been performed, or are overdue.
    Seemingly $MR_HIST also only has 10 indexes, yet it is possible to have more than 10 maintenance reminders defined. It seems to me that MR_HIST isn't entirely comparable to the actual matinenance reminders as found in Menu->Status->reminder.

    For instance I've yet to see upcoming maintenance be displayed in MR_HIST. as such I'm not sure it is possible to use MR_HIST to notify a user of upcoming maintenance.


    I've tried searching through all system variables on a fanuc controller (automatically) for the string contents of upcoming maintenance not found in the MR_HIST but visible in 'Maintenance reminder in' Menu->Status->reminder.
    Example: 'Overhaul check'
    in 55.1 mo.

    and I couldn't find any system variable containing such information

    Unlike performed or overdue maintenance for example:
    '1st mechanical check'
    in -422.4 day
    or running 952.7 h

    which shows up in system variables/MR_HIST as:
    Field: $MR_HIST[2].$GROUP Access: RO: BYTE = 1
    Field: $MR_HIST[2].$ID Access: RO: BYTE = 2
    Field: $MR_HIST[2].$TYPE Access: RO: BYTE = 2
    Field: $MR_HIST[2].$DUE_TYPE Access: RO: BYTE = 1
    Field: $MR_HIST[2].$NAME Access: RO: STRING[37] = '1st mechanical check'
    Field: $MR_HIST[2].$DUE_ACT Access: RO: INTEGER = 28424197
    Field: $MR_HIST[2].$DUE_DATE Access: RO: REAL = -9.574667e+02
    Field: $MR_HIST[2].$WARN_DATE Access: RO: INTEGER = 1478952151
    Field: $MR_HIST[2].$DONE Access: RO: BOOLEAN = FALSE
    Field: $MR_HIST[2].$DONE_DATE Access: RO: INTEGER = 0
    Field: $MR_HIST[2].$DONE_PAST Access: RO: STRING[21] = ' -957.5 hours RUN'
    Field: $MR_HIST[2].$RECORDED Access: RO: BOOLEAN = FALSE

    Edited 4 times, last by gtafbi (March 18, 2025 at 3:11 PM).

  • ssaul
    Reactions Received
    8
    Posts
    54
    • April 9, 2025 at 4:04 AM
    • #3

    Hello
    Did anyone find the variables?

  • MarshallHampton
    Posts
    2
    • April 11, 2025 at 9:00 AM
    • #4
    Quote from gtafbi

    If I'm not entirely mistaken (which is certainly possible) the $MR_HIST[x]
    system variable only contains a list of maintenance that either has been performed, or are overdue.
    Seemingly $MR_HIST also only has 10 indexes, yet it is possible to have more than 10 maintenance reminders defined. It seems to me that MR_HIST isn't entirely comparable to the actual matinenance reminders as found in Menu->Status->reminder.

    For instance I've yet to see upcoming maintenance be displayed in MR_HIST. as such I'm not sure it is possible to use MR_HIST to notify a user of upcoming maintenance.


    I've tried searching through all system variables on a fanuc controller (automatically) for the string contents of upcoming maintenance not found in the MR_HIST but visible in 'Maintenance reminder in' Menu->Status->reminder.
    Example: 'Overhaul check'
    in 55.1 mo.

    and I couldn't find any system variable containing such information

    Unlike performed or overdue maintenance for example:
    '1st mechanical check'
    in -422.4 day
    or running 952.7 h

    which shows up in system variables/MR_HIST as:
    Field: $MR_HIST[2].$GROUP Access: RO: BYTE = 1
    Field: $MR_HIST[2].$ID Access: RO: BYTE = 2
    Field: $MR_HIST[2].$TYPE Access: RO: BYTE = 2
    Field: $MR_HIST[2].$DUE_TYPE Access: RO: BYTE = 1
    Field: $MR_HIST[2].$NAME Access: RO: STRING[37] = '1st mechanical check'
    Field: $MR_HIST[2].$DUE_ACT Access: RO: INTEGER = 28424197
    Field: $MR_HIST[2].$DUE_DATE Access: RO: REAL = -9.574667e+02
    Field: $MR_HIST[2].$WARN_DATE Access: RO: INTEGER = 1478952151
    Field: $MR_HIST[2].$DONE Access: RO: BOOLEAN = FALSE
    Field: $MR_HIST[2].$DONE_DATE Access: RO: INTEGER = 0
    Field: $MR_HIST[2].$DONE_PAST Access: RO: STRING[21] = ' -957.5 hours RUN'
    Field: $MR_HIST[2].$RECORDED Access: RO: BOOLEAN = FALSE

    The MR_HIST variables provide a valuable history of maintenance reminders and events in your robot system. Interpreting these logs correctly can help you track wear, usage patterns, and when key maintenance should be performed. Understanding each variable’s timestamp and status can even let you predict future issues. If you're unsure about specific codes, cross-referencing with your robot’s manual or reaching out to your vendor’s support can clarify things. Staying ahead on maintenance can greatly improve uptime and extend your system’s life. For a detailed explanation of MR_HIST variables and how to interpret them efficiently, please read my full analysis here: https://www.filemail.com/d/yrepumdchaxmipp

    Display More

    Replying for the update..

    Edit: Seems no update.

    Edited 2 times, last by MarshallHampton (April 25, 2025 at 7:00 AM).

Advertising from our partners

IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Advertise in Robotics
Advertise in Robotics

Job Postings

  • Anyware Robotics is hiring!

    yzhou377 February 23, 2025 at 4:54 AM
  • How to see your Job Posting (search or recruit) here in Robot-Forum.com

    Werner Hampel November 18, 2021 at 3:44 PM
Your browser does not support videos RoboDK Software for simulation and programming

Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Thread Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Tags

  • Fanuc
  1. Privacy Policy
  2. Legal Notice
Powered by WoltLab Suite™
As a registered Member:
* You will see no Google advertising
* You can translate posts into your local language
* You can ask questions or help the community with your knowledge
* You can thank the authors for their help
* You can receive notifications of replies or new topics on request
* We do not sell your data - we promise

JOIN OUR GREAT ROBOTICS COMMUNITY.
Don’t have an account yet? Register yourself now and be a part of our community!
Register Yourself Lost Password
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on Google Play
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on the App Store
Download