Thank you, Mickey. It seems like the RIO module is functioning now. This is the same module we discussed a few weeks ago. I purchased a RIO scanner card in an attempt to resolve the issue, but while I was able to clear the fault, I have been unable to successfully run it. I am currently working on getting it up and running. I also tried adding a 2Gb memory card, but unfortunately, it did not work. My main priority now is to establish communication with the PV 600, which is currently displaying a flashing fault.
Apologies for the oversight, I recently conducted a search for Rockwell PV600 and inadvertently overlooked that the manual that appeared was actually for the PV+ model. It's important to double-check search results for accuracy and relevance.
Thank you for your assistance, it's greatly appreciated. I have successfully reset the device, but the red Fault LED is still flashing. This issue is specific to the RIO version, with the cable properly connected. I need guidance on addressing this issue effectively. Any tips or advice would be greatly appreciated. Thank you.
Have you attempted to establish a connection to the RS232 port via RSLinx and upload a new program using a straight thru cable with the DF1 driver?
I haven't installed the printer driver yet. Do you recommend that I do so?
The RS232 interface serves as a connection point for printers.
The device also features an AUX input/output port, which is its standard configuration. This port allows for easy uploading and downloading of data.
Check out the image of the default settings. Just a heads up, I haven't configured a RIO PV yet.
I recently created a program in Panelbuilder32 that includes a single maintained push button. The program settings involve PV600, RIO, and the aux port for downloading PLC information for an SLC504 type system. Specifically, the configuration includes Name: 542, Rack 0, Module: 0.2, and the last chassis checked. When it comes to block transfer, it is important to enable certain options. Should I have anything enabled for block transfer - such as R or W, and what should the length be? Additionally, should pass through be checked as well?
I am currently encountering an error while validating my program: the tag assigned to Discrete Block or Block Transfer Channels does not have a valid address in the terminals. What address should be used in this case? I have used B3:0/0 as the address. Can you please guide me on where to correctly address these terminals?
Thank you, Mickey, for your help. I successfully connected online with the PV600 using a straight-through cable. The next challenge is setting up communication between the PLC (SLC5/04, L541) and RIO. I am currently stuck at this stage and would appreciate any assistance. Thank you.
BestTime expressed gratitude to Mickey for the assistance in setting up the PV600 online using a straight-through cable. The next challenge is getting the PLC (SLC5/04, L541) to communicate with the RIO, which is where they are currently facing a roadblock. Any guidance on this issue would be greatly appreciated. If you have experience setting up a RIO PanelView, please share your knowledge. It is advised to refer to the manuals, attempt the setup, and return with any questions. The experts in the field will surely provide assistance.
Hello Mickey, I wanted to provide an update on my progress. I have been conducting various trials and it seems like I am getting closer to a fully functioning setup, although I have encountered a minor issue. The SLC504 CPU's green LED indicates that communication is okay, and the RIO scanner card shows no faults with a steady green COMM LED. However, I am facing an error on the PV600 stating "Write to Controller logic failed." I am only utilizing 1 bit (B3:0/0) and when I press the PV button, it should activate on the PLC ladder but it is not working as expected. Currently, I have the B3:0 bit set to READ, but when I try to change it to WRITE, I receive an error stating "Tag does not have address in the terminals assigned Discrete Rack or Block Transfer Channels." There seems to be a minor mistake somewhere, but I am unsure where it is originating from.
Posting the programs is a great way to receive assistance from others. Make sure to zip both the SLC and PV files before sharing. This will make it easier for others to access and assist with your project.
Download the attachment Panelview.zip for the latest information.
I am currently using the PV600 FRN version 3.02, and I am considering upgrading to version 4 or higher. I searched on the AB website but couldn't find the information I needed. Should I upgrade my PV600 FRN to a higher version for better performance?
To enhance the functionality of your SLC, it may be beneficial to incorporate additional programming. For detailed instructions, refer to chapter 4 of the following link: [insert clickable link].
BestTime expressed gratitude to Mickey for their assistance, mentioning successful progress with a variety of trials. Despite getting closer to a complete setup, a minor issue remains. The SLC504 CPU's green LED indicates good communication, and the RIO scanner card shows no faults with a steady green COMM LED. However, an error message appears on the PV600: "Write to Controller logic failed." The issue arises when using only one bit, B3:0/0, for a push button function in the PLC ladder. Changing it from READ to WRITE results in an error message regarding tag addresses.
Setting up RIO Panelviews can be challenging due to the need for proper block transfers and adherence to specific addresses in applications. The initial I/O addresses assigned to the Panelview may not suffice based on its logical configuration. Configuring block transfers for efficient data exchange requires careful consideration of transfer size, especially for multiple reads and writes. Opting for larger transfers than necessary can be beneficial in future modifications.
It is advisable to establish both block write (BTW) and block read (BTR) operations with ample data space to accommodate potential needs. Utilizing a mirrored addressing pattern can streamline data display and editing processes within the PLC. For example, assigning addresses like N10:12 for display and N11:12 for editing ensures clear organization. Control bits and words should be designated in the write group (BTR) while indicators belong in the read group (BTW).
In situations where "B" addresses are used for buttons, ensuring distinct lengths for BTR groups can prevent overlap with other address groups like "N11." This precaution helps avoid confusion and potential errors in data transfer configurations. While software specifics may vary, following these guidelines can help maintain a structured and efficient setup for RIO Panelview operations.
I appreciate your advice. I will make sure to be mindful of these 10,000 unclear aspects, especially when I am setting it up for the first time.
I want to thank OkiePC for the amazing recommendations. They were very helpful, and I followed them. However, I am still encountering the error message "Write to logic controller failed." Should I update the FRN3.02 to version 4 or higher, or is it advisable to continue working with the existing 3.02 version?
After trying out OkiePC's helpful recommendations, I still encountered the error message "Write to logic controller failed." Should I update the FRN from 3.02 to 4 or higher, or stick with the current version? It's possible that the firmware update may not resolve the issue entirely. The problem could lie in the block transfers or in the mismatch of sizes between the logic on the PLC side and the Panelview. Double-checking these settings is crucial for resolving the issue. For more insights on this topic, you can refer to a discussion on plctalk.net. It's essential to ensure that all settings are aligned for the system to function smoothly.
I programmed the PLC with a length of 100 for N10. The BTR in PV is set to 50. For N11, the length in the PLC is also 100 with a BTW of 50 in PV. Should the rack number be adjusted or left as is?
In order to avoid errors in the PLC, it is crucial for the BTR and BTW lengths to align with the sizes specified in the Panelbuilder32 application. The data table size can exceed the limit of 64 words but should not be shorter. These instructions must function smoothly without any issues and may need to be synchronized or repeated to prevent simultaneous execution. Maintaining consistency between the BTR and BTW sizes is essential for efficient PLC performance.
Indeed, that is the scenario I am currently facing. I am puzzled as to why the COMM LED on the RIO scanner card is consistently glowing green, indicating proper communication, yet the communication settings are still not quite correct. It took me a significant amount of time to establish a successful connection. Despite resolving the communication issue, the error message only appears sporadically, about once every minute. However, the PB bit on the PLC fails to activate when I press the field button. I am using only one bit, specifically N10:0/0, a maintained PB. While the PV600 display shows the signal, nothing registers in the PLC.
BestTime mentioned using only 1 bit, specifically N10:0/0, which is maintained as a Push Button. While the Panelview 600 is illuminated, there is no activity in the PLC. It is important to note that a bit written by the Panelview cannot be used as an indicator for the same button. The Panelview can only display bits that are part of its read block and control bits that are part of its write block. Check if your block transfers in PLC logic are repeating accurately and without any errors. This ensures seamless communication between the Panelview and the PLC.
In my PLC program, I have assigned my N10:0/0 bit as a relay contact (XIC) in a rung to activate the output O:3.0. The communication between the two is smooth with no errors, and the process value (PV) is validating correctly. One thing I am considering is the placement of the RIO scanner card. In my setup, it is located in the first slot after the CPU, with the second slot being an input (I:2) and the third slot being an output (O:3). Typically, the first slot after the CPU should be address 0, but in my case, it is 1, giving me access to 32 words on the RIO card (I:1.0 - I1.31). Shouldn't these addresses be I:0.0 - I:0.31 instead?
The CPU slot, also known as Slot 0, is located in the first position. Slot 1 is situated adjacent to Slot 0 on the right. Your understanding of the slot layout is accurate.
That aspect seems fine. However, where exactly is the issue located?
Share screenshots of your Panelview RIO configuration along with the BTR and BTW ladder logic rungs for a comprehensive look at your setup.
I attempted to reduce the size of the files on my phone by zipping them, but they still exceeded 400KB. I will attempt to transfer them using my camera instead.
Please find the attached pictures.
Another consideration to take into account here is the checked mark on the pass-through, along with the setting of System Bits S:34/0 and S:34/5 to ON. It is important to determine if this action is necessary and if it may be contributing to the problem at hand.
I conducted tests on passthrough effectiveness, comparing Bits S:34/0 and S:34/5 with both 1 and 0. No discernible difference was found in the results.
When displaying the block transfer setup in Panelbuilder32, be sure to show all enabled block transfers by checking the tick box on the left. Instead of using a camera, try using the ALT + PrintScreen shortcut on your keyboard to capture a screenshot of your computer screen. Afterwards, paste the screenshot into your preferred bitmap editor where you can crop, add notes, circle important details, and save the image. For step-by-step instructions on how to take a screenshot, visit http://www.take-a-screenshot.org/.
Two pictures are enclosed in a Word format document.
If you're unsure, it might be necessary to assign a tag to the "W" block to prevent it from being deleted. According to the PB32 user manual, an unused Block Transfer Channel will be deleted. This means that any block transfer set up in the Block Transfer dialog but not utilized by the application should be removed or referenced. You can find more information in the manual PDF located here: http://support.elmark.com.pl/rockwell/Literatura/2711-60.pdf.
Sure, I'm willing to give it a shot.
I successfully completed the task, but there seems to be an issue with the additional circle (pilot light) as it is now showing an error. This is causing problems with the reading and writing processes.
I am encountering an error.
See the image below for reference.
It appears that you are attempting to utilize a tag within the "W" block for indication. Unfortunately, this is not permitted.
I utilize a component from the N11:0 series. How would you approach this?
For optimal control system performance, it is important to assign specific tags to the N11 group for writing and the N10 group for reading. The N10 group consists of outputs transmitted by the Programmable Logic Controller (PLC) and read by the Human-Machine Interface (HMI). Conversely, the N11 group includes inputs sent to the PLC and written by the HMI. By organizing tags in this manner, system integration and communication are streamlined.
If I neglect to utilize any of the components in N11, the transfer process will not include them. This can impact the overall functionality and efficiency of the transfer. It's important to make sure all elements are properly integrated to ensure a successful transfer.
BestTime stated that failing to utilize any of the N11 bits would result in them not being transferred during the transfer process. To avoid this error, it is recommended to include these bits in the tag database, even if they are not currently being used on any pages. It is advised to assign each button with both an indicator tag and a control tag to ensure proper functionality (note: terminology may differ from Panelbuilder).
To establish a data base with tags, I require the corresponding addresses. In RS5000, tags function as a data base. How can this be achieved in Rs500?
Do you think it's possible to achieve success solely through tags, or even with the push of a button? Share your thoughts!
Currently, my Tag address is set to N11:0/0. However, the tag form is prompting me to enter an address. Which address should I input? For example, I created a tag address called "Run" in a process variable. What corresponding address should I use in the programmable logic controller (PLC) to activate the "Run" bit from the SLC504?
When configuring a tag address in a PLC, it is important to input the correct address in order for the system to function properly. For instance, if you have set a tag address as "Run" in your PV, you will need to use the corresponding address in the PLC, such as N10:0/0. To activate the "Run" bit from the SLC504, you can utilize the device's state to trigger the output instruction for N10:0/0. Alternatively, you can check the status of the button by using the XIC N11:0/0 OTE N10:0/0 command. This will allow you to properly control the outputs in the PLC based on the input signals received.
I am confused about the functionality of this setup. Currently, I am using it in the exact opposite way you described. My PB on PV is N10:0/0 and I am utilizing it as an XIC to trigger N11:0/0 OTE based on the state of N10:0/0 in the PLC. Essentially, I am monitoring N10:0/0 and activating N11:0/0 as an output. If I monitor the state of N11:0/0 with an XIC, it will only turn ON if set as an OTE. Can you confirm if my understanding is accurate?
BTR/BTW Instructions play a crucial role in configuring the SLC program. It seems like you may not be utilizing the required RSLogix 500 Block Transfer Read (BTR) and Block Transfer Write (BTW) instructions in your program. Paul (OkiePC) has asked for screenshots of the BTR and BTW rungs, which are essential for data exchange between the SLC and the remote device via the scanner.
To ensure proper data transfer, the M Buffer Files in the scanner handle BTR and BTW data. Each buffer can transfer up to 64 words of data to and from a device. The interaction between the scanner and the end device, like the PanelView, requires correct configuration of data exchange settings in the G File and PanelBuilder32. This setup is necessary for enabling data exchange beyond the scanner level.
If you do not see the BTR/BTW instructions in your program, it might be due to the selected processor type. The Series A or B processors do not support these instructions, while an OS401 FRN 3 Series C processor is required for BTR/BTW instructions. Make sure to select the appropriate processor type in RSLogix 500 to access the BTR/BTW instructions.
If you have a Series C processor, select the corresponding option in RSLogix 500 to enable the BTR/BTW instructions. In case the selected processor does not support BTR/BTW instructions, an alternative method involving multiple rungs can be utilized to access the M Buffer Files manually.
Overall, the correct configuration of BTR and BTW instructions is essential for seamless data exchange between the SLC and remote devices. Stay tuned for more specific details once you confirm the processor type and setup requirements.
Mickey recommended loading a new program onto a PanelView 600, specifically the 2711-B6C1 model (Standard PanelView), in order to overwrite the old program. However, if an rslinxng.exe error is hindering the reload process, this solution may not be feasible.
Banandy remarked on a futile response, but the original poster acknowledged its value in the next comment. Meanwhile, your comment revived a decade-old thread just to express dissatisfaction with an unrelated matter. Maybe it's time to reassess the definition of "worthless."
Banandy inquired about the rslinxng.exe error potentially hindering a reload. Displeased with the initial response, Banandy sought a more practical solution. Have you encountered this issue before and, if so, how did you resolve it?