-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LCD and SSR questions #1
Comments
As I understand specs, fully safe (safe to board, chip etc.) current from IO pin is limited to 12mA, but it can get higher as 50mA - I wrote this to make information complete. Anyway, since I've already provided +5V (directly from power supply) to relay box for EMR relay, clean solution would be to use small transistor, to drive bigger current. I guess for example 2N3904 and some current limiting resistor would be enough. But, If you would need two separate SSRs - it's going to be extremely easy to do - just let me know. |
Ok, so I've tested mine SSR and it draws max 8,73mA (at least this is how much my multimeter can measure in MAX mode - I don't know it's frequency). I've looked also at some different specs for Fotek SSRs - and some says MAX 12mA, some says 7mA at 12V, and also I definitely don't have original Fotek :).
|
I have another idea - quite easy to implement :). You could use logic level converter module like this. This way you can have up to 8 SSRs - driven with single GPIO (with this chip/board). Just connect one side VA to 3,3V and ESP32 pin 19 to all A0-A8 gates. Then on the other side connect +5V to VB and B0-B8 pins to SSRs you have. This chip can (according to specs) provide up to 50mA of current on single pin. |
Thanks for putting this nice project up on github!
Question: as I understand the maximum gate current on an IO pin on the ESP32 is 12mA. Is that enough to drive the SSR? In my case I have two heating elements in my kiln and will have to drive them from separate pins because I don't think the ESP can source enough current to drive both from one pin.
The text was updated successfully, but these errors were encountered: