💬 Livolo 3 buttons US/AU switch adapter
Awesome work dude !! And you did the pcb on eagle, you are my hero <3
That's will help me for develop EU version
Thx a lot
I love this! If you guys need any assistance with making the EU Version then please shout. Drop me a message and i will be more than willing to help/test/assist with eagle or anything.
@Samuel235 if you draw the outline of the board, put a rectangle where the connector is, circles where the sensors are, and give me the pins for VCC 3V/GND and to control the relays, I'm ok to manage the rest
But you will have to print outline on paper, cut it and make sure it fits in the box with connector perfectly aligned as I have no switch in this format so I can't control the shape.
I do not have one of these product to test the fitment with the connector in the correct placement. If i had one i would have got that eagle file to you asap
Do you have a link to the EU/UK version so i could take a look through. I've only ever read the US version but knew that they had a UK version and assumed it was the same but different mounting and voltage ratings.
The only thing that bothers me, and stops me purchasing these, is the fact they're WiFi, if RF i would have them everywhere already
@Samuel235 They are not wifi, they have a 433MHz receiver. Receiver only, that's the main problem.
With a MySensors board to replace the touch PCB, problem solved
@Nca78 - Indeed, this is why i said that i would have had them everywhere if they were not WiFi and hence why i'm interested in this development
I have designed the outline of the 2 buttons, 1 way board EU the last week
I need time for identifiy the function of each connector pin because they have changed.
I must do the same thing for the 1 buttons, 1 way EU version which i have.
But i would like to see if we can use a gate OR for command the relays by TTP Or Atmega. I want to keep the possiblity to command the light with button even if the atmega is out off service.
For doing this i'll need help because i'm newbie in electronic
Never seen that before without frying it with too high voltage, or bricking it with failed bootloader writing.
If it happens in the wall switch, the high voltage will also fry the TTP223 and you won't get any touch function to make a "or" with :P
It would also block you from doing any "advanced" use of the buttons, like long touch, double touch, ...
Personally, i don't think there is a need to have with working without the ATMega. If it was mine, i would like to have a pretty sure way of seeing there is a problem, not to be able to continue using the product even if it was 'broken' to an extent. I see why you would like that feature but i just don't see it being much use. If you have a specific case that you would like to put forward or i'm not seeing any serious use of this, please advise me as i would change my mind
Just my opinion about this case would be that if i knew it was broken but could still use it without an issue then i would be rather lazy and not change the atmega straight away. But that may just be me alone, everyone else may not be as busy/lazy as me. Maybe that is the engineer inside of me coming out though haha.
It would take 2 minutes to put back the original Livolo touch plate anyway, so IMHO not worth adding other components = more complexity = higher risk of failure.
Thanks you for your arguments, both of you.
You're right, if the atmega was broken, the best way is to stop use this node because some components could be broken too.
This feature can permit to use the command when a problem with the radio or the controler appear.
But with MY_TRANSPORT_WAIT_READY_MS , maybe we don't need this feature anymore ?
You convainced me to undo this feature and minimise the components mostly if Livolo will make many updates.
As you requested, if someone want to check the board, i have adapted it for LINOVO 2 gangs 1 way EU format.
You can find the files her https://github.com/tonnerre33/Linovo_EU_2Gang_1way/tree/develop/
Perfect, Thank You!
Nice work. I was very curious regarding on how did you made the pcb layout so I took a little time to inspect it and I noticed that you added a ceramic resonator but it's placed a little bit too far from the MCU pins. Now I know why you did that and this is the reason I didn't used a crystal/ceramic resonator in the first place - that's because of the limited space available. When I say limited is because of many reasons:
- it's not ok to have traces/components under and/or too close the touch pads
- didn't wanted to place components on the other side of the board because that's where the livolo glass panel comes and it may interfere from a mechanical point of view
That said I gave up on using a crystal/ceramic resonator and in most of the cases the internal 8MHz RC oscillator is more than enough(as far as I know it only matters when you have an environment where temperature variations are pretty significant so the MCU oscillator frequency can drift a lot).
Now getting back to your board and crystal/ceramic resonator placement: it's advisable to have it as close as possible to the MCU pins where it connects to and this is to reduce parasitic inductance/capacitance that long traces can and will create. Remember that 8MHz is pretty high frequency so even short traces matter so you don't want surprises in your circuit.
- filtering caps for MCU need to be placed also as close as possible to Vdd pins(and for Aref too).
- the big polarized capacitors(tantalum and/or electrolytic) need to have lower value ceramic capacitors around 100nF placed in parallel in order to reduce their high ESR
Oh and please stop using Eagle in the future ..I was a former user of Eagle and now I'm really glad I got rid of it trust me. Aside from the limitations that it has and now even more as it was acquired by Autodesk it doesn't have some VERY useful features like KiCAD has now when it comes to pcb routing( one of them is push and shove ). Now I know it's hard to gave up on a tool that you used for a very long time(it was for me too) but with a little effort and small steps it can be done. And I know that KiCAD it's not that stable as Eagle is but it's still very usable(even with nightly builds that I use because of the new and nifty features). It has a little different learning curve and it's a little bit hard in the beginning but after you master it then it's a kids play. Not to mention that you have a 3D viewer for your board(very useful for mechanical integration and inspection) and it supports step models(in the nightly builds for sure).
I'm making all of my designs using KiCAD for a long time now and I didn't had issues with the final PCB even if I use nightly builds. And on top of all of this: it's FREE and no limitations and great community support on https://forum.kicad.info.
I know that you're still working on it so the pcb layout might change but I just wanted to give my first impressions on it. Good luck with your design and keep up the good work.
thanks you for your feedback
Whatever the distance, i try to place all the time a ceramic resonator just for debug. Indeed, i have already brick my atmega with wrongs fuses and i had to add a resonator for change them again.
I did that on other project even if i use the 8Mhz internal oscillator.
For the distance, i didn't now the limit with 8Mhz.
I was thinking i have placed the caps for MCU like your project, isn't it ?
I didn't know the problem of the big tantalum capacitor (Is 100nF big ?) I'll place a 100nF ceramic capacitor in parrallel of the tantalum capacitor in a next rev.
I have tried kicad but when i have printed the PCB it was blurrier than the same maked with eagle. I was afraid with that, that's why i continu with eagle for the moment.
I'am glad that you looked this pcb, a big thx again.
Edit : on the linovo pcb, why they don't put a ceramic capacitors near the tantalum capacitor ?
I wasn't referring to the 100nF ones which are ceramic type usually. If I remember well I saw some 10uF or 100uF in parallel in your schematic (the polarized capacitors) so I was assuming that you use tantalum ones.