Good afternoon, I am experiencing HMI communication challenges with FactoryTalk View ME. I am attempting to update an existing program that has been operational, but after downloading the updated runtime file, the HMI displays question marks instead of data. I saved the runtime under a new filename and loaded the updated application, selecting "No" when prompted to replace communication settings. Despite selecting the most recent development file with the same name as the current runtime, I am unable to upload the file from the HMI due to the "Never Allow Conversion" setting. I confirmed that the communication setup in RSLinx Enterprise matches the settings in "Application Settings->Device Shortcuts." Even though I have not changed the communication setup or selected a different file, I am unable to establish communication after the update. Could there be a setting in FactoryTalk causing this communication issue?
By utilizing the GoTo Config button when downloading this file, users can easily validate the communication path on the live screen and make any necessary adjustments. The F3 application settings on the configuration screen provide quick access to view and edit the communication path shortcut. This feature allows for convenient monitoring and editing of communication paths directly from the running screen.
Are the tags functioning properly in FTView Studio's runtime test feature? If they are not working, there may be an issue with your shortcut configuration.
Do you have any information on the resolution for this issue? I am encountering the same problem when downloading a restored HMI back into a remote HMI system. The original runtime functions properly when downloaded again, but the modified version does not. I manually added my RSLink Enterprise runtime targets as I am accessing remotely, and testing it on my PC shows it working fine. However, when I try to download it, all I see are question marks.
I am currently working on a 10-inch PanelView Plus 1000 with version 5.1 firmware. My project is in FactoryTalk View version 7.0 on a 32-bit Windows 7 virtual machine.
Canuck_Programmer inquired about a solution to a common issue faced when downloading a restored HMI remotely. The original runtime works after downloading it back into the HMI, but the modified version does not. By manually adding RSLink Enterprise runtime targets and testing it on a local PC, the runtime runs smoothly. However, when downloaded, only question marks appear. The underlying issue seems to be related to the remote path on the PC differing from the path between the physical PanelView and the PLC. To resolve this, ensure that the communication path referenced to the PanelView is correctly set to the PLC.
Hello, it sounds like a tricky problem but I've encountered something similar with FactoryTalk View ME before. There's a chance your new version of the application could have triggered unexpected changes that impact data communication, even if you haven't altered the communication setup. An initial step could be trying to verify if your HMI tags are configured correctly, since incorrect tags may cause data to display as question marks. Also, remember that FactoryTalk uses two sets of communication settings: Design-time and Runtime. Even though you selected 'No' to replace the communication settings when loading the new application, try checking the Runtime communication setup just to be sure. The 'Never Allow Conversion' setting usually block the process of uploading the application from the terminal, so you might want to check with your system's integrator about adjusting it to allow normal conversion.
It sounds like you're taking all the right steps. One possible issue could be that the "Never Allow Conversion" setting isn't allowing the HMI to recognize the updated program data and files. I'd suggest you temporarily disable this setting to see if that improves the connection. Another thing to check is consistency of the file names being used between the HMI, RSLinx, and FactoryTalk. It’s also possible that any mismatch in data type definitions in the runtime file compared to the PLC could be causing the question marks to appear. I'd recommend a double-check on these areas. Always make sure to back up your data before making changes!
Hi there, it sounds like you're having quite a hassle with FactoryTalk View ME. Your approach seems sound to me, but maybe you're dealing with a tag conflict issue? Make sure any tags associated with the HMI are correctly defined in your PLC program. Another common issue I've found is related to the version of FactoryTalk View ME Station, which needs to be matched on both the HMI and your computer. If you're using different versions, it may cause communication problems. If both of these seem fine, you might want to consider contacting Rockwell Automation support. Their team can usually provide a deeper analysis of what's going wrong.
It sounds like you’ve covered a lot of the common troubleshooting steps, but I’d recommend checking a few more things. First, ensure that the tags in your updated runtime are still mapped correctly to the devices they’re supposed to communicate with—sometimes a name mismatch can cause those question marks to appear. It might also help to verify that the paths in your data logging or display items haven’t changed with the update. Lastly, consider reviewing the communication settings in FactoryTalk for things like the “HMI Server” settings and ensure that the correct runtime project is set as active. Good luck, and I hope you resolve the issue soon!
It sounds like you're facing a frustrating situation with the HMI! One thing to check is if there are any data tags that might have changed during the update, particularly if they were renamed or if the data types don't match between the HMI and the controller. Also, double-check the version of the HMI and the controller firmware; sometimes a mismatch can lead to communication issues. If you've confirmed that the communication settings in RSLinx are intact, you might also want to explore the "Display Device Configuration" settings to ensure everything aligns correctly. Sometimes, re-creating the device shortcut or even restarting the RSLinx service can help clear out any lingering connection issues. 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: - This issue could be caused by mismatched communication settings between the runtime file and the updated application. Make sure to carefully select the correct communication settings during the update process.
Answer: - The "Never Allow Conversion" setting may prevent file uploads if it is enabled. Check the settings in FactoryTalk View ME to see if this option is causing the communication issue.
Answer: - To troubleshoot communication challenges, ensure that the communication setup in RSLinx Enterprise matches the settings in "Application Settings->Device Shortcuts." Verify that the correct file with the same name as the current runtime is selected during the update process. Additionally, check for any potential settings in FactoryTalk that might be causing the communication issue.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.