I love your videos and have learned so much from them. I'm not sure if you have a video on open loop control of a proportional valve or not. If not I'd love to see how you'd program a proportional valve to work with an analog card and some photoeye inputs to detect mid and end position of a cylinder. My goal would be speed control of a cylinder without the full cost of tempo cylinders and a motion controller on a plc500.
Hello Tim, I have a problem with 1769-L33ER. The PLC displays a solid red indicator. The plc is not detected in the studio5000 and that frustrates me. Why did it happen? And what's the solution? thanks!
Great video! I have so many questions, but first that came to mind - how are system faults like wire breaks, short circuits, etc. reported? Is this automatic or done programmatically? Thanks, Tim!
While this information is important and vital to know, let's ask ourselves if faulting PLCs is something that should even be considered acceptable? To the best of my knowledge, AB/Rockwell is pretty much the only PLC on the market that does this. The venerable old GE Series Six would shrug off a divide by zero or an out of bounds access attempt on an array. The fact that you can prevent this by adding fault recovery routines can be looked at either as "Nice of them to provide a method of recovery", or pragmatically, "Why the heck isn't this already in the firmware?" I'm firmly in the "WTH?" camp. You can argue that a DIV0 event should be considered catastrophic, and shut down the PLC, while I'll point out that the operation that caused it probably only flashes an indicator and isn't a threat or hazard to livestock nor navigation. There really is no excuse on Rockwell's part for this to still be a thing. And remember folks, every time that you divide by zero, a new universe is born!
Hello Tim, do you know if Logix controllers (compact, control etc.) are able to scan the fault status bits while faulted similar to a MicroLogix series controller? ( S:1/13, Major Error Halted for example) I’ve tried several different ways of moving the fault bits from a GSV, or energizing a coil when the fault bits are equal, but of course, with the controller being faulted, they won’t scan. I’ve also never used fault handler routines. Does the answer lie in there? Thanks!
I'm having trouble connecting to my micro820 serially and through ethernet. The fault light is flashing in addition to the run and comm lights. Have any idea what's causing this?
Please look into the Rockwell tech note for saving the fault record to the SD card in this fault routine. Often the call I got was there was a fault but someone cleared it already to keep it running. There is no record anywhere without saving to the SD card to find the root cause!
@Tim Wilborne I am using rockwell compact logicx plc, its shwoing Red light for ok and its glowing. But there is no light showing for Run, Force & I/O only communication lights are glowing in Red
Saludos amigo estoy colocando un vlt fc 302 en una red devicenet con un procesador rslogix 5550 y me dice esta falla rsnetwort cuando le doy a diagnostico dnet 0018 MAJOR RECOVERABLE FAULT
@TimWilborne how does resetting faults with the switch have nothing to do with resetting faults? It's a way to reset faults without logging in to the controller. It's very useful so I don't have to remote into a PLC just to click 2 buttons.
No. That is a myth. If a programmer writes a power up handler then a transition to run mode, which includes cycling the power or switching the program switch from program to run, may clear the fault. But we've talked about why this is a poor practice in previous videos.
I made a practice of saving the faulted program to a folder I have named Faulted PLC and documenting the fault info. I unfortunately learned this the hard way.
Great question. It's about memory allocation. This Compactlogix has 384 kB available. Each double integer is going to be 4 bytes. Four times 1 million would be 1 megabyte. You'd be over its memory size for that single array..
I love your videos and have learned so much from them. I'm not sure if you have a video on open loop control of a proportional valve or not. If not I'd love to see how you'd program a proportional valve to work with an analog card and some photoeye inputs to detect mid and end position of a cylinder. My goal would be speed control of a cylinder without the full cost of tempo cylinders and a motion controller on a plc500.
Hello Tim,
I have a problem with 1769-L33ER. The PLC displays a solid red indicator. The plc is not detected in the studio5000 and that frustrates me. Why did it happen? And what's the solution?
thanks!
As the video says, solid fault light is bad. Probably going to need some new hardware.
Great video! I have so many questions, but first that came to mind - how are system faults like wire breaks, short circuits, etc. reported? Is this automatic or done programmatically? Thanks, Tim!
With most standard PLC inputs, you will need a meter. Some inputs and outputs have diagnostics features, but people do not use them nearly enough.
While this information is important and vital to know, let's ask ourselves if faulting PLCs is something that should even be considered acceptable? To the best of my knowledge, AB/Rockwell is pretty much the only PLC on the market that does this. The venerable old GE Series Six would shrug off a divide by zero or an out of bounds access attempt on an array.
The fact that you can prevent this by adding fault recovery routines can be looked at either as "Nice of them to provide a method of recovery", or pragmatically, "Why the heck isn't this already in the firmware?" I'm firmly in the "WTH?" camp. You can argue that a DIV0 event should be considered catastrophic, and shut down the PLC, while I'll point out that the operation that caused it probably only flashes an indicator and isn't a threat or hazard to livestock nor navigation.
There really is no excuse on Rockwell's part for this to still be a thing.
And remember folks, every time that you divide by zero, a new universe is born!
Hello Tim, do you know if Logix controllers (compact, control etc.) are able to scan the fault status bits while faulted similar to a MicroLogix series controller? ( S:1/13, Major Error Halted for example) I’ve tried several different ways of moving the fault bits from a GSV, or energizing a coil when the fault bits are equal, but of course, with the controller being faulted, they won’t scan. I’ve also never used fault handler routines. Does the answer lie in there? Thanks!
It will run the fault handler when a fault occurs. That is where you need to put your GSV. I should do a video on that.
@@TimWilborne Thanks!!! I'll play around with it this weekend.
@@TimWilbornedid you ever do a video for this? If not that would be an awesome one to do!
I'm having trouble connecting to my micro820 serially and through ethernet. The fault light is flashing in addition to the run and comm lights. Have any idea what's causing this?
Is this a SLC 500?
Have you done a piece yet on writing a fault handler routine?
That would be a good one. Let me put it on the list.
Please look into the Rockwell tech note for saving the fault record to the SD card in this fault routine. Often the call I got was there was a fault but someone cleared it already to keep it running. There is no record anywhere without saving to the SD card to find the root cause!
@Tim Wilborne I am using rockwell compact logicx plc, its shwoing Red light for ok and its glowing. But there is no light showing for Run, Force & I/O only communication lights are glowing in Red
Glowing solid or flashing? Solid is a hardware failure.
Hi sir am using compact logic L18ER it is going in fault mode while switch on off of main supply what may be the issue pls help sir.
Go to communications, go to fault and see what it tells you
@@TimWilborne power up fault is coming sir how to rectify
That means someone has assigned a power up fault routine and not actually written the code to handle and clear it. Is it empty?
@@TimWilborne dont more about this sir how to do can u send step sir thrgh watsap
Saludos amigo estoy colocando un vlt fc 302 en una red devicenet con un procesador rslogix 5550 y me dice esta falla rsnetwort cuando le doy a diagnostico dnet 0018 MAJOR RECOVERABLE FAULT
Would be more useful if you would've also explained how to do it with the run/rem/prog switch.
I have...but that has zero to do with resetting faults. Why do you think it would be useful in this video?
@TimWilborne how does resetting faults with the switch have nothing to do with resetting faults? It's a way to reset faults without logging in to the controller. It's very useful so I don't have to remote into a PLC just to click 2 buttons.
No. That is a myth. If a programmer writes a power up handler then a transition to run mode, which includes cycling the power or switching the program switch from program to run, may clear the fault.
But we've talked about why this is a poor practice in previous videos.
Great video lesson
Thank you 🤓
I made a practice of saving the faulted program to a folder I have named Faulted PLC and documenting the fault info. I unfortunately learned this the hard way.
Good point!
Why is there a limit to the range? Set them all to 1 million, yes?
Great question. It's about memory allocation. This Compactlogix has 384 kB available. Each double integer is going to be 4 bytes. Four times 1 million would be 1 megabyte. You'd be over its memory size for that single array..
I love this video, can you please help me I have one plz is faulty please please