Currently, I am encountering a problem with a FactoryTalk View ME application file for a PanelView Plus 1500 related to macros. This is my first time making edits to this specific application file, as it was initially developed by the OEM. I am looking to enhance its functionality by incorporating additional features. Although I am familiar with how macros function, this is my first time working with them. There are a total of 5 straightforward macros in the application. Each macro is designed to assign different integer values to SystemMemory\UserLevel. These macros are associated with logins and determine access to various screens based on the user. By using visibility and checking if SystemMemory\UserLevel is equal to or greater than a specific number, the macros operate effectively. Upon startup, the application executes the macro with the lowest security level. In the original application, a message indicating "running startupmacro" appears before the graphics load, which is not the case in the edited version. The edited application displays messages notifying that the macros failed to load and that the tag SystemMemory\UserLevel has not been activated. Additionally, due to the OEM's system, I had to create new logins linked to the same macros. Despite importing the .mcr (macros) files from the OEM's backup, the issues persist. It is worth noting that the MER file is version 4.
I am troubleshooting an issue with user access levels in system memory. I have attempted to resolve the problem by creating new variables, replacing old ones, creating new macros, and using different names. However, I am still receiving the same error messages with the new variable names. I am considering if this issue may be related to user or group policies, and if access permissions need to be configured for system memory access. Any thoughts on what the root cause of this issue could be?
Are you certain that the macros are functioning properly? Test them with an emulator and check the runtime application on your computer. It's possible that the macros were not included in the .mer file. Confirm this by restoring the .mer file. Are the user levels not activated or missing in the Logix path? Verify by checking the communications and the tag database for any user level definitions.
After testing the application on my PC, I did not encounter any macro errors. Logging in was successful and the various buttons for accessing different screens were visible. To test the restored .mer file, I had to save it as a version higher than 4. The restored version also worked without any issues, with no macro errors during login. I am considering taking a spare panelview from stock to try loading the application onto it.
Experiencing ongoing issues with log-in functionality on a test PLC and panelview, mirroring the setup in the field. Error messages persist when attempting to write values, such as during the loading of the startup macro. For example, receiving notifications like "Error writing value 'DEFAULT' to item 'SystemUser'." Additionally, encountering difficulties writing values to a system memory variable designated for access levels, with messages like "Failed to write to SystemMemory\AccessLevel = 0 tag" and "Write to SystemMemory\AccessLevel was unsuccessful."
If you're having trouble with communications in PV and Logix, be sure to check the error message for more details. It could be a firmware issue, so consider using a v5 on a version 5 capable PV if you converted it to v5 and created a v4 MER file. This could potentially resolve the issue.
✅ 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 issues could stem from various factors such as incorrect macro configurations, missing macro files, compatibility issues with the application version, or improper linking of macros to user access levels.
Answer: Answer: Macros on the PanelView Plus 1500 can assign integer values to SystemMemory\UserLevel, which in turn determine user access to different screens based on predefined security levels.
Answer: Answer: These messages could appear due to discrepancies in the way macros were integrated into the application, potential issues with the macro files, or errors in linking the macros to user logins.
Answer: Answer: The persistence of issues after importing .mcr files could be due to version incompatibility of the MER file, inadequate configuration of the imported macros, or mismatches in the setup of user logins and associated macros.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.