why no one uses latching relays ?
-
If you drop me a message I can tell you what kind of bistable relays we are using in the Crownstones (http://crownstone.rocks). We switch 16A using a relays from Panasonic. It's one of the most expensive parts of our BOM.
-
OMRON G5Q consume 0.2W : https://www.omron.com/ecb/products/pdf/en-g5q.pdf (125mW for 5V version). Very small packaging
@Fabien just for completeness, that's specced for 10A. The Panasonic ones are not much bigger, http://eu.mouser.com/Electromechanical/Relays/General-Purpose-Relays/_/N-5g36?P=1z0z1s3, e.g. http://eu.mouser.com/ProductDetail/Panasonic-Industrial-Devices/ADW1212HLW/?qs=sGAEpiMZZMtSzCF3XBhmW2w01ZqnWsnJ%2FIRuNGt%252bt2Q%3D are specced for 16A.
-
I hear people's arguments that you do not know the last state of a latching relay on a power failure, but what if you stored the last state in the eeprom? I mean you store the node ID and other things that get remembered on a power failure, why not the relay state? Every time you change the state of the relay, store it. Doesn't seem that challenging.
Vera Plus running UI7 with MySensors, Sonoffs and 1-Wire devices
Visit my website for more Bits, Bytes and Ramblings from me: http://dan.bemowski.info/ -
I hear people's arguments that you do not know the last state of a latching relay on a power failure, but what if you stored the last state in the eeprom? I mean you store the node ID and other things that get remembered on a power failure, why not the relay state? Every time you change the state of the relay, store it. Doesn't seem that challenging.
-
There is a very minor edge case where you switch the relay and lose power before writing the state. Probably would never happen in reality. I think a bigger problem, which should be solvable) is if you lose power to your whole house, some relays would latched on and you could have surges or other problems. Hopefully latching relays are robust enough to handle it.
Another solution to the state problem is to have a power up routine that set all relays to a predefined state, then you know. That may be annoying if you reboot the system while someone is reading and the lights go off. This could happen with the more common relays also. The state problem is a lesser worry. The bigger worry is what happens when power comes back, do the relays leave things in a safe state while things initialize.
It comes down to trade offs, save some power and maybe have some imperfect behavior, or use a bit more and have fewer oddities. I think you almost have to decide for each relay.
-
I believe that with latching relay there is also a way to make the relay go into specific state during power outage - with a capacitor that stores some energy, that energy may be used to switch the relay into this specifi state. So I think that latching relays can do all the things non-laching relays can and also more :) and they are much more energy efficient. So my biggest issue is why there is so little of them on the market and hardly no ready made modules with required circuitry to handle them. And they are sooooo expensive ... :(
-
You can store the state in FLASH indeed, and have a rotating scheme to reduce wear. However, in practice it should also go fine if you store the information outside your system.
Suppose you have a phone that remotely SETs the relay. Now the relay gets powered off and on through some fluke. The next time it is powered on and its state is the same as that on the phone, because that device is oblivious to this entire sequence of events.
Next time the phone remotely does a RESET and the relay will toggle as expected.
If (1) someone else does change the state of the relay and (2) the chip is recycled, then you will be out of sync with the actual state for one cycle. After sending a SET or RESET it is synchronized again.
-
I believe that with latching relay there is also a way to make the relay go into specific state during power outage - with a capacitor that stores some energy, that energy may be used to switch the relay into this specifi state. So I think that latching relays can do all the things non-laching relays can and also more :) and they are much more energy efficient. So my biggest issue is why there is so little of them on the market and hardly no ready made modules with required circuitry to handle them. And they are sooooo expensive ... :(
@rozpruwacz i think your answer is "sooooo expensive", i suspect they are more complicated to build, so even if they were popular they would still cost more. As for the power cost, to put it in perspective, if you use 14w led bulbs, and your automation saves you 1 hour of bulb use, that will run your relay for 28hours at .5w. Now that doesn't help much if you are trying to run the relay on batteries/solar.
-
@gohan yes, they only consume power when making the switch. They don't consume any power to maintain state.
-
Apart from 12V supply voltage, this seems interesting:
http://www.ebay.com/itm/Latching-Bistable-Relay-module-12V-Relay-board-for-AVR-PIC-Arduino-from-EU-/181276052335 -
@Yveaux
I am talking about something like these https://it.aliexpress.com/popular/solid-state-relay-arduino.html . I heven't looked much into them since they have limitations, but I like the fact they are not mechanical.@gohan said in why no one uses latching relays ?:
@Yveaux
I am talking about something like these https://it.aliexpress.com/popular/solid-state-relay-arduino.html . I heven't looked much into them since they have limitations, but I like the fact they are not mechanical.Sorry, I misread your question, as this thread is about latching relays, not solid state.
Solid state relays do consume power, but in general less than mechanical relays.
-
@rozpruwacz i think your answer is "sooooo expensive", i suspect they are more complicated to build, so even if they were popular they would still cost more. As for the power cost, to put it in perspective, if you use 14w led bulbs, and your automation saves you 1 hour of bulb use, that will run your relay for 28hours at .5w. Now that doesn't help much if you are trying to run the relay on batteries/solar.
@wallyllama I agree that there are cases where normal relays are completely fine, but if you want to control some low power device that draws 0.5W then it makes sense to use latching relay, especially if it will be turned on half the time and you have 20 of them.
-
No problem, I brought up the solid state because the opening post was about power consumption of standard relays compared to the latching ones, so I was wondering where they fit in between. That's it. :)
@gohan ssr's require less power to drive them but on the load side they have about 1V drop so this produses power loses, and ssr's that can handle large currents are quite big. But the have other features, like zero crossing switching (they can switch on/off when the voltage sine wave is near 0V).
-
@gohan said in why no one uses latching relays ?:
@Yveaux
I am talking about something like these https://it.aliexpress.com/popular/solid-state-relay-arduino.html . I heven't looked much into them since they have limitations, but I like the fact they are not mechanical.Sorry, I misread your question, as this thread is about latching relays, not solid state.
Solid state relays do consume power, but in general less than mechanical relays.
Why are you all saying they are expensive ? If you take the 12V versions they are just a bit more expensive than normal relays.
@Yveaux said in why no one uses latching relays ?:
Solid state relays do consume power, but in general less than mechanical relays.
I'm sorry but I don't agree with this statement ;)
They consume nearly nothing from the "command" side, but they have a voltage drop. I think it's about 1V on those small Omron (on original one, not the copies sold on Aliexpress which could be worse) so the power loss is up to 2 watts for the 2A they are rated for. On the bigger models visible from the link above you need a (huge) radiator over 4A. -
@rozpruwacz We were talking relay modules (like this one) which normally only take supply and a single control signal.
Having to control the latching of the relay using an H-Bridge I find 'a bit harder' compared to just toggling an IO, regarding both software and hardware.For reference, this is the schematic I use to control a latching relay:
It uses a MAX2226/4427/4428 or compatible MOSFET driver to drive the relay.
And a function to switch it:
#define RELAY_INA_PIN (A0) #define RELAY_INB_PIN (A1) #define RELAY_SET_TIME_MS (30) static void switchRelay( const bool on ) { digitalWrite(RELAY_INA_PIN, on ? LOW : HIGH); digitalWrite(RELAY_INB_PIN, on ? HIGH : LOW); delay(RELAY_SET_TIME_MS); digitalWrite(RELAY_INA_PIN, LOW); digitalWrite(RELAY_INB_PIN, LOW); }You don't necessary need to use an H-Bridge, you can use: (Don't forget the flyback diodes!)
That above schematic is for an intermediate switch in a multi way switching circuit. This way has a high W.A.F (Wife Acceptance Factor). Doing it this way, you can keep the conventional light switches operational. As its part of a multiway light switch circuit, you only need to toggle it to turn the light on or off. You do of course need to detect if the light is on though!
And unless you're mass producing these for sale, what does the extra cost matter?
-
HAHA, You can always get a new wife with lower W.A.T (Wife Acceptance Treshold) :D
