12/11/2012 4:51 PM | |
Posts: 38 Rating: (0) |
hello you can make a print screen to diagnostic de buffer and send or post here , or send your project Thanks Nilton Junior |
12/17/2012 1:10 PM | |
Posts: 90 Rating: (1) |
Hi Ganes There is no hardware issue in this error. I know that the description of the error indicates the unplugingof the modules.We are 100% sure that no oneunpluged the modules. Thevery similar problem is discussed in: /tf/WW/en/Posts/75571 and /tf/WW/en/Posts/69975 but, in the answers no one indicated the real cause of the problem. Kind regards, |
12/17/2012 4:33 PM | |
Joined: 7/7/2010 Last visit: 11/6/2024 Posts: 15385 Rating: (2443)
|
There is a possible firmware problem with one or more modules in your system. Send your project to Siemens via Support Request to see if there are new firmwares available to address mystery module removal/reinsertion as your system seems to have. It is also possible the sliding connector is not properly seating or has a damaged pin. I had one where the electrician wiring and installing it forced the slider, pushing a pin in. Needlenose pliers pulling the pin flush with the other pins corrected that problem. I had a problem with a TC module reporting weird (wildly incorrect) values or being removed even though none of that happened. Updating the TC module firmware corrected both issues. When looking at the odd problems like this, having that OB82 is essential to allow you to detect how long the problem exists and let your plc logic determine the proper course of action. For example, if the problem persists for just one scan, you can typically tolerate that and handle it within the user logic by retaining prior values and only updating when the module is actually online. It takes more time/effort, but your programming will be more robust and handle a lot more abuse until you discover the root cause. You can also just "throw parts at the problem" by buying replacements with the latest firmware/hardware and see if the problem goes away. There are sometimes problems with a specific firmwawe level between modules that can cause all kinds of odd problems. I have seen communications issues with one firmware revision good for RS485 but bad for TCP/IP, and another FW rev bad for RS485 and good for TCP/IP. Updating firmware on RS485 module corrected problem, but we basically bought a replacement 485 module and the problem went away. It was only when we went online and saw the FW was different that we realized there was a difference. Knowing is half the battle |
science guy |
|
Follow us on