New ✨ Introducing Oxmaint Asset Hub for Machine Builders and OEMs. Explore Now
Seeking to see if others are facing the same problem as me. I am unable to establish a connection with a new 1769-L16ER-BB1B Ser. C controller straight out of the box, whether through USB or Ethernet. The "OK" LED is flashing a slow red. Upon plugging it in via USB, Windows 10 does not detect any connection (confirmed that the cable is functioning with other devices). When connected via Ethernet directly to the computer, Windows displays a message stating that the network cable is unplugged. I have attempted multiple Ethernet cables with the same result. Despite returning the controller to the distributor and receiving a replacement with the same part number and series, the issue persists. Tech support has directed me to tech note QA14426, where I have exhausted all relevant solutions to no avail. I am considering the possibility of a faulty batch of PLCs being produced. Has anyone else encountered this issue? Any other suggestions to resolve this? Thank you.
Have you attempted using a different computer?
JeremyM recommended trying a different PC to solve the issue. I have tested a total of three computers.
Are you experiencing any errors in the Windows Device Manager when connecting devices via USB?
When you connect your device to a USB port and access the Windows Device Manager, check for any error messages associated with connected devices. I have noticed that when I plug or unplug my device, no new devices appear in the device manager, and there is no system sound notification indicating a successful USB connection. This lack of refreshed device information may indicate an issue with the USB connection.
cjarvis64 mentioned that upon connecting or disconnecting devices, they do not see any new devices appearing in the device manager, and the system does not perform the usual "refresh" action when a new device is connected. There is also no system sound notification for "USB Connected." Have you tried accessing hidden devices by going to View > Show Hidden Devices? This may help in identifying any unrecognized devices.
When trying to find hidden devices on your computer, go to the "View" tab and select "Show Hidden Devices." Is there a specific category where the device should appear?
The flashing red OK LED indicates a significant unrecoverable fault in the controller. If this issue occurs without any programming being downloaded, it is likely a sign of a defective controller. I recommend contacting your distributor to inquire about the source of the controllers, as they may be of poor quality or counterfeit. This could potentially lead to further issues with the functionality of the controller.
According to tlf30, a flashing red OK LED indicates a significant unrecoverable fault in the controller. If this is occurring without any programming ever being downloaded, it is likely due to a faulty or counterfeit controller. It is recommended to inquire with the distributor about the source of the controllers. The manual suggests that a firmware flash may be necessary, which makes sense for a new controller straight out of the box.
It is important to note that the device can be accessed using either USB or Ethernet connectivity.
Is the back end plate properly installed in place?
BachPhi inquired about the installation of the back end plate. The L16ER-BB1B system utilizes Point IO technology. Click to learn more!
tlf30 commented that the device should support communication through USB or Ethernet. However, after consulting with Rockwell TS, they are recommending returning the current device and trying a different one. Doubts remain about whether this will truly solve the issue at hand.
Can anyone tell me the name of this plate? I'm referring to the one shown in the following image: [insert hyperlink].
BachPhi asked about the name of the plate shown in the link provided. It appears to be a piece of plastic protecting the Point I/O contacts, but regardless, it is securely installed. Click the link to view the image.
After troubleshooting, I realized the issue was with the power supply- the original provided only 0.42 amps, which was not enough for the task at hand. Replacing it with a new power supply delivering 1.25 amps solved the problem. It just goes to show the importance of having a sufficient power supply for electronic devices.
If you encounter issues with your distributor, communicate the problem and request assistance from their technician to troubleshoot the connection. A successful connection indicates a problem within your office, while an unsuccessful attempt suggests an external issue. I am aware of a circuit board shop that specializes in manufacturing Rockwell PLC circuit boards, receiving rejected boards daily from various customers, including Rockwell.
If you're experiencing issues with your Rockwell PLC, when you report the problem to your distributor, make sure to mention the issue and ask if their technician can attempt to connect to it. If they are successful in connecting, the issue may be within your office; if not, there may be a problem with the PLC itself. I have knowledge of a circuit board shop that used to produce numerous Rockwell PLC circuit boards, including those returned as rejects by Rockwell and other customers daily. Could a bad batch of 1769-L16ER Controllers be the root of the issue? After diagnosing the problem, it turns out that a larger power supply was required. The previous one supplied 0.42 amps, while the replacement delivers 1.25 amps, resolving the issue. Make sure to ensure the proper power supply for your device's needs. For more information and assistance, visit www.plctalk.net.
Could investing time in reading the manual have been a more efficient strategy?
padees suggested that taking the time to read the manual may have been beneficial in saving time. In my experience, most PLC's typically only require around 200 to 300 mA. Despite informing RA Tech support of the power supply size I was using, they did not believe it was the root of the issue. Additionally, consulting the manual revealed that the current draw for this PLC was not specified, making it less helpful. Thank you for your insightful input.
After consulting the manual, I found it lacking in helpful information, so I refrained from commenting. Besides considering the power supply size, I also pondered the potential impact of its quality, such as excessive ripple issues.
I have observed that PanelView Plus devices have both a starting current and a running current, similar to PLCs which may experience difficulties booting up if there is a voltage drop caused by power supply current limits.
After consulting the manual without much success, I questioned whether the quality of the power supply could have been a factor in its performance issues. Could excessive ripple in the original power supply have caused problems? My suspicion is that the initial power supply may have struggled with inrush current. Despite this, I plan to have a reliable AB 120W power supply on hand for my desktop programming needs.
On my desk, I have a 2.5A Sola that was salvaged from a decommissioned machine. Interestingly, this is the same machine that contributed the -L33ER component...
cjarvis64 mentioned that the PLCs they have worked with typically only use 200 to 300 mA. Despite notifying RA Tech support about the size of the power supply being used, they did not believe it was the problem. The manual does not provide clear information on the current draw for this PLC, which is not very helpful. Thank you for your valuable input. If you are looking for more information, it can be found on page 10 of the manual (1769-td005_-en-p), which unfortunately is too large to upload here.
In a forum post, a user named padees remarked on the enjoyment of a particular task, suggesting that the necessary information could be found in a manual on page 10 (1769-td005_-en-p). Due to its size, the manual couldn't be uploaded to the post. Providing input after a solution has been found, solely to suggest that the manual could have been consulted, does not contribute constructively to the discussion.
padees mentioned with amusement that the information is available on page 10 of the manual (1769-td005_-en-p), but it's too large to be uploaded here. Good job on noticing that. The manual I checked didn't contain the information I needed, and I can't even locate the table I referenced before, which provided power requirements for various models excluding OP's.
When chiming in after a solution has already been found, simply stating "could have just read the manual" does not contribute constructively. I apologize if my comment seemed offensive, but the instructions are crystal clear in the manual. Best of luck!
Considering that, if the manuals were read and comprehended, this thread would not be necessary.
After thoroughly reviewing the thread, it became apparent that the original poster (OP) and I had both taken the time to study a manual on the CPU. However, it became evident that we had been referencing the incorrect manual. The specific information we were seeking was actually present in the manual that you shared, but lacking in the manual we initially consulted. While it is important to be helpful rather than smug and dismissive, it was valuable that you were able to point out which manual contained the necessary information and where to find it. The remainder of the interaction could have been more beneficial.
Answer: Answer: If you are facing connectivity issues with your controller, it could be due to various reasons such as faulty hardware, incorrect configurations, or issues with the network setup.
Answer: Answer: A slow red flashing "OK" LED could indicate a problem with the controller's status or connectivity. It is essential to troubleshoot this issue to identify the root cause.
Answer: Answer: To troubleshoot connection problems, you can start by checking the hardware connections, verifying the network settings, ensuring the cables are functioning correctly, and exploring any relevant technical notes or resources provided by the manufacturer.
Answer: Answer: If you have tested multiple Ethernet cables and encounter the same issue, it is recommended to verify the network port settings, check for any software conflicts, and consider reaching out to technical support for further assistance or possible hardware replacement.