Hello, I am fairly new to using FactoryTalk View Studio 13.00 and have encountered an issue while creating a runtime file for an application running version 8.00. The problem I am facing is that the values I set for a ramp button keep getting reverted. Specifically, I am trying to set my ramp down with a lower limit of 0 and a ramp value of 1, and my ramp up with an upper limit of 16 and a ramp value of 1. Initially, when I opened the project, the ramp values were the same as the limit values (0 for ramp down and 16 for ramp up). Despite multiple attempts to change these values to 1, they revert back to 0 and 16 when creating a new runtime file. In the button settings under the general tab, I have only selected the ramp up and ramp down options. I have also tried checking the "Use variable ramp value" box without any success. Additionally, in the connection tab, I have set the Ramp as 1 and the Limit as 0 for the ramp down button, and 16 for the ramp up button. Any assistance on resolving this issue would be greatly appreciated. Thank you for your help.
When creating a new runtime file in MBDry, the ramp numbers keep reverting back to 0 and 16. Are you noticing this behavior after downloading the project? When reopening the button properties, do the changed values still appear? It is possible that the issue lies in compatibility with v8, but this behavior is unexpected. It seems more likely that the changes are not being saved, or you are running an old runtime version instead of the new one. In the button settings under the general tab, ensure that only the ramp up and ramp down boxes are checked for their respective buttons. Attempting to check the "Use variable ramp value" box has not yielded success. In the connection tab, set Ramp to 1 and Limit to 0 (for ramp down) and 16 (for ramp up). Setting values in Ramp/Limit will only take effect if 'use variable ramp' or 'use variable limit' is selected respectively. The purpose is to link the connection to a tag, where the current tag value will act as the ramp or limit and can be adjusted in real-time. Since static values are desired, there should be no need for the variable options (uncertain if v8 supports them). It is recommended to leave both variable options unchecked and remove all connections except for the Value. While it may not be crucial, a variable limit setting once caused issues in a version without support (in a numeric input, not a ramp).
Before creating the runtime file, it is important to save the display.
plvlce asked if the behavior is based on post-download actions and if the changed values are reflected in the button properties within the project. To ensure accuracy, I will outline my process step by step. Upon saving changes to the page housing the ramp buttons, I compile a new runtime application. Initially, I only loaded the project into the HMI to test the buttons used for selecting recipes stored in the PLC. However, the ramp buttons currently fail to adjust values, hindering the selection of a different recipe. Regular checks by restoring the runtime application through the Application Manager reveal that the ramp value in the general tab consistently reverts to match the limit number. plvlce suggested excluding variable options and connections other than the Value, as static values are preferred and may not be supported in v8. Removing values from the Connections tab and manually entering the ramp value and limit in the General tab, followed by creating a new runtime and restoring it, did not solve the issue. Upon reviewing in FactoryTalk View Studio, the ramp value repeatedly shifted from 1 to the limit value for both ramp buttons.
Before developing a new runtime application, I always make sure to save the display. This step is crucial to avoid any loss of data or progress during the process. Save display prior to creating a new runtime application ensures that all changes are preserved and accessible at any time.
For a quick solution to the issue affecting FactoryTalk View ME (FTVME) versions 13 and 14 when creating a runtime lower than version 8.1, make sure to install a patch rollup released after June 2024. The additional patch is no longer needed as it has been integrated into the latest software patches. A tech note has been provided for reference regarding the problem with ramp buttons losing value when MER is restored in FactoryTalk View versions 13.00 and 14.00. For more information and assistance, visit rockwellautomation.custhelp.com. Explore XKCD's 'Wisdom of the Ancients' for a unique perspective on the issue. Best wishes!
It sounds like you're running into a frustrating issue! One thing you might want to check is if there are any overriding settings in the project that could be affecting your ramp values. Sometimes, the properties in the command settings or the data type of the variables being used can inadvertently cause values to revert. Also, make sure that you're not dealing with any version compatibility issues since you're using FactoryTalk View Studio 13.00 with a runtime targeting version 8.00. It might be worth looking through the project documentation or reaching out to Rockwell support, as they might have specific insights or patches for this kind of behavior. Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: The issue of values reverting back to default settings could be due to incorrect configuration settings or a potential software bug.
Answer: Answer: To troubleshoot the issue, ensure that the settings in the button properties, such as ramp up and ramp down values, are correctly configured. Check if the "Use variable ramp value" option is set properly and verify the connection tab settings for the ramp buttons.
Answer: Answer: If changing ramp values to 1 does not persist, consider reviewing your configuration settings, ensuring proper selection of options in the button settings, and verifying the connection tab settings for the ramp buttons. Additionally, checking for any compatibility issues between versions 13.00 and 8.00 could also be helpful.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.