Omron
Subforums
-
- 6.1k
- posts
-
- 1.4k
- posts
-
- 9.9k
- posts
-
- 1.9k
- posts
-
- 853
- posts
-
- 2.4k
- posts
-
- Omron c40k
- By kNk47,
4,476 topics in this forum
-
- 7 replies
- 240 views
-
- 4 replies
- 6.1k views
-
- 2 replies
- 271 views
-
- 0 replies
- 83 views
-
- 13 replies
- 32.3k views
-
- 1 reply
- 302 views
-
- 1 reply
- 277 views
-
- 1 reply
- 248 views
-
- 8 replies
- 371 views
-
- 0 replies
- 117 views
-
- 1 reply
- 161 views
-
- 12 replies
- 4.5k views
-
- 0 replies
- 281 views
-
- 21 replies
- 7.4k views
-
- 7 replies
- 1.1k views
-
- 1 reply
- 641 views
-
- 9 replies
- 3.7k views
-
- 2 replies
- 3.2k views
-
- 2 replies
- 496 views
-
- 14 replies
- 4.1k views
-
- 3 replies
- 1.1k views
-
- 0 replies
- 639 views
-
- 4 replies
- 4.5k views
-
- 7 replies
- 4.7k views
-
- 5 replies
- 3.2k views
-
Posts
-
I would look at the manual for the switch, because there are switches where the contacts NC/NO operate at different times. For most ESTOP buttons, they should actuate at the same time. But yeah, it makes sense to use all the same contact types. And I would monitor the safety PLC output, not the ESTOP directly. Only when the safety controller says it is OK to run should the PLC be given a go signal. -
-
Hello, I would like to share a personal experience regarding the use of NO (normally open) contacts to signal an emergency stop to the PLC. During a machine installation, the emergency stop button was placed in a location where the operator would occasionally bump into it by accident. These buttons have a certain travel distance before they actually change state. So, when the operator accidentally brushed against the emergency stop, the NC (normally closed) contact would open, but since the button wasn’t fully pressed, the NO contact never closed. As a result, the machine would stop for safety reasons, but the system wouldn’t indicate which emergency button had been triggered—because it would return to its normal state right after the bump. After that experience, I started using an NC contact as well to signal the PLC when an emergency stop is activated. This way, even a brief activation is properly detected and logged. -
I have searched but either the videos are out of date or the Analogue version is different to the Digital version. What entries are needed in Crimson to get the PM50D to show up in Crimson using a WiFi connection when configured as a client? I have got a bit of experience in Koyo and Maple. I am able to connect to these either from my PC or laptop via a serial / USB connection. I am looking to use the PM50D in cut to length machines as the Durants 57602 and old Red Lions fail. -
By Chris Elston · Posted
I thought you might have been the developer. It's not too hard to pick up or there are some youtube videos of course. If this is something you aren't comfortable with, it's probably best to reach out to an integrator in your area. -
By Chris Elston · Posted
The PLC-5 stores its channel configurations in battery-backed RAM. It could be the battery is starting to get low. When is the last time you changed this battery? Go online with RSLogix5 or similar and check the battery status bits in processor status, see it's low enough to trigger a bit. But maybe proactively change the battery. Make sure you measure the voltage of the replacement battery as online vendors tend to have these on the shelf for a long, long time and they are dead when you get them... -
Start by checking the "actual pulses" shown on the display of the drive. According to your explanation it should be roughly on the same value, since the axis is not moving. Depending on the response level of the servo drive/motor you will the pulses jump up- and down in the area of current position. This is normal. De PLC is sending only pulses towards the servo drive in most cases and not reading actual positions back. Try to detect where the current position is comming from. Maybe an external encoder is connected to the main PLC and you can find a problem there. -
Hi, I work at a plant that uses mostly PLC5/80E's - Series F with remote IO racks using the 1771-ASB Series B. The PLC processor is powered by a UPS that maintains power to it during an outage but the RIOs lose power, at times long outages occur where the UPS runs out of battery causing processor power loss. Recently an issue has been occurring where if the PLC processor loses power it is losing configuration on Channel 1B and not communicating with the RIO's, I've discussed this with previous engineers at the plant and we don't have a history of this happening until recently. Channel 1B is setup as a Remote I/O Scanner for the 1771-ASB. When the PLC cycles power it will come back online with no apparent code loss, but each of the RIOs lights are indicating it is not connected to the processor, and we are getting rack fault alarms on our Citect. We are able to fix this typically by putting the PLC into Program mode and pushing "Auto-Config" on Channel 1B. The issue with this is we want to know why this is occurring now and not previously, additionally we run 24 hours and those with PLC access aren't there outside of hours, meaning every time it occurs someone has to come in late at night. Any assistance with this issue would be appreciated. Attached a screenshot of Channel 1B. -
Good afternoon all, Hello All, I am currently experiencing an issue with TouchWin software that was used in the past to program TH and TG series HMIs. As of two weeks ago, upon attempting to upload an existing program from any of the HMIs, I am encountering a runtime error that is causing the upload to fail, and force closes the software. I have tried reinstalling the software and have attempted to reach out to the MFG but they have not returned any correspondence. No updates have been installed on the programming computer. Any thoughts? Thank you all for your time. -
It is not weird, it is just old way of doing things by using Pulse Train Output, and event today it is prevalent, usually in China and other price sensitive locations. There is encoder, mounted on servo motor, and there signal that is information when it is in initial position (some sensor). Your motor shaft is most likely rotating the encoder because there is change of encoder value, but the signal for initial position is not happening. You need to read the manual, and there are a lot of pages.
-