New ✨ Introducing Oxmaint Asset Hub for Machine Builders and OEMs. Explore Now

Q&A Community

Troubleshooting Card Mapping Error When Upgrading PLC from 1769 to 5069 Model

Question:

Hello, I'm fairly new to this but we just upgraded from our 1769-l32e to the latest 5069-L320erm PLC model. After transferring the file, I ran a Verify on the Controller and encountered an error message "Error: Rung 0, CPS, Operand 0: Invalid member specifier." I'm unsure of the next steps to get the new PLC up and running. Any assistance on resolving this issue would be greatly appreciated. Thank you.

Top Replies

The newer model appears to lack a corresponding "Data" tag, requiring each bit to be mapped individually at the destination. It is necessary to align the bits up to 15OG for proper data transmission.

As OG pointed out, in the 1769 module, all inputs were contained in a single INT tag 'Data', whereas in the 5069 module, each input is its own channel with separate BOOL for data. Unfortunately, there doesn't seem to be a built-in method to map all inputs in a single instruction like before, unless you create your own Add-On Instruction (AOI). This difference in handling inputs may require some adjustments in your programming approach.

I will attempt to individually map out Operaghost and plvlce and test the system. Thank you for your help!

Unfortunately, I am not familiar with a method to efficiently map all inputs in a single instruction as was possible before. It seems Rockwell has introduced changes that make this process more challenging.

KuulKuum expressed frustration over Rockwell's tendency to make future advancements unnecessarily complicated. Despite the introduction of new features, some may argue that they are unnecessary and only cause added difficulty.

More Replies

On their website, there should be a feature like an AOI or subroutine available to convert 5069 tags into regular tags. Keep an eye out for this conversion tool when browsing their site.

I will examine it, alan_505.

According to alan_505, there is an AOI or subroutine available for converting 5069 tags to regular tags, which should be accessible on their website. Hopefully, this converter is not as problematic as the SLC500 logic converter mentioned earlier.

Frequently Asked Questions (FAQ)

FAQ: FAQs:

Answer: 1. What does the error message "Error: Rung 0, CPS, Operand 0: Invalid member specifier" indicate when upgrading from 1769 to 5069 PLC model? - This error typically indicates a card mapping issue during the upgrade process from the 1769 to 5069 PLC model. It points to a problem with specifying a member within a data structure, which needs to be addressed for the new PLC to function correctly.

FAQ: 2. How can I troubleshoot the "Invalid member specifier" error after upgrading to a 5069 PLC model?

Answer: - To troubleshoot this error, you may need to review and adjust the card mapping settings for the new 5069 PLC model. Verify that the data structures and member specifiers in your program match the configuration of the new PLC hardware.

FAQ: 3. What are the recommended steps to resolve the card mapping error when transitioning to a 5069 PLC model?

Answer: - First, carefully review the card mapping settings to ensure compatibility with the new 5069 PLC model. Check for any discrepancies in data structure definitions and member specifiers between the old and new PLC models. Make necessary adjustments and re-verify the program to resolve the error.

FAQ: 4. Is there any specific documentation or resources available to assist in resolving card mapping errors during PLC upgrades?

Answer: - Yes, you can refer to the user manuals, technical guides, or online resources provided by the manufacturer for guidance

You must be a registered user to add a comment. If you've already registered,
sign in. Otherwise, register and sign in.