Is it possible in IRC5 rw6 to make digital outputs (fi communication on Profinet with plc) and virtual outputs remanent for power down-up?
Now I see the value goes always to 0 after power up-down or restart. I should want to keep my value (0 or 1) that was active before the restart.
IRC5 rw6 : making digital and virtual outputs remanent after power down-up
-
Plc_User -
February 18, 2019 at 4:32 PM -
Thread is marked as Resolved.
-
-
To make the robot remember the signal state at power off and automatically restore it at power on you have to change the signal safe level type.
You can do this manually through the MOC, Example:-Name "doR1_Home" -SignalType "DO" -Device "IO_Internal_Device"\
-DeviceMap "33" -Category "machine" -Access "DEFAULT"\
-SafeLevel "SafetySafeLevel"Or you can use the "new" io configurator in robot studio.
-
Reviving an old thread. RW 6.12.
Just checking, but it looks like the Signal Safe Level is only meaningful for outputs, not inputs, correct?
I'd like to retain the states of my various Clear signals when a power outage happens. Right now, all my various DOs and GOs are using the Default Safe Level:
And it seems like the easiest way to get what I want would be to change the Startup setting to "Set Last Value". I've been trying to think of conditions in my application where that could cause issues for me, but I think it'll be okay.
Does anyone know of any issues or items of concern that might apply if I do this?
-
Since we know that the best practice is to hold the signal high when clear and drop to low when not clear, a not clear low would still be low when restarting, as it would be while power is off. Should be no problem restoring clear signals when rebooting, unless some numbskull manages to move the robot while power is off.
-
Should be no problem restoring clear signals when rebooting, unless some numbskull manages to move the robot while power is off.
About what I thought. And if someone manages to move the robot while the power is off, I've got much bigger problems.
-
It can be done easily with the smaller robots, you can overpower the brakes. Did you know about the hack to use three-nine volt batteries in series to operate the brake release with power off?
-
It can be done easily with the smaller robots, you can overpower the brakes. Did you know about the hack to use three-nine volt batteries in series to operate the brake release with power off?
Well, this is a 400kg payload robot, so I don't think I need to worry about anybody without a winch or forklift.
No, I did not know of this hack. Pray tell me more, you interest me strangely.
-
Well, a wrinkle: I can't change the Default. So I made a copy, changed the Startup setting for the copy, and then reassigned all my Clear-Of signals to the new Safe Level.
-
Additional note: I tried adding my WZDO signals to the new "retain last value" Safe Level. Didn't work. The IRC5 didn't give me any faults, but a reboot test showed that even with this setting, the WZDO did not retain its True value during reboot, even with the robot located physically inside the WZ before, during, and after the reboot process.
-
Additional note: I tried adding my WZDO signals to the new "retain last value" Safe Level. Didn't work. The IRC5 didn't give me any faults, but a reboot test showed that even with this setting, the WZDO did not retain its True value during reboot, even with the robot located physically inside the WZ before, during, and after the reboot process.
Adding another Signal Safe Level to a WZDO signal will not work. To update a WZDO signal to its correct state requires motors on state.
-
Adding another Signal Safe Level to a WZDO signal will not work. To update a WZDO signal to its correct state requires motors on state.
So I discovered. I was hoping otherwise, but... it is what it is.