Come to think of it, why are you switching it at all? Is it possible to send the BLDC driver a disable command? That would make much more sense, than switching the power.
Usual reasons for switching the power:
* Prevention of rectified BEMF voltage (generated by the motor when manually turned un-powered) running into the battery/supply
* Extra safety layer
* Powering off drivers that do not have the enable feature at all, or consume too much power in disabled state, and can't be modified
Exactly
In any case, it's not obvious why you'd need two? (You might need a $2 SSR to control a bigger SSR; the larger ones seem to want higher "coil" voltages.)
Hi guys,
yep I suppose there has been a little bit of obfuscation.
The circuit in my original post was supplied to keep things easily digestible - the design below essentially uses two of the circuits from the original post and is coupled with an INA169 module for power monitoring, I understand the basics of what was going on, however like many of you I had a few questions to regarding design choices - before my initial post I had tried to simulate it it hope that would answer my questions but the simulation didn't work as I expected - which only led to more questions. I also asked the guys who designed the original circuit, but they didn't seem to know themselves.
The circuit in my original post was derived from the following designs:
https://github.com/HoverMower/Ardumower_PCBs which was derived from:
https://github.com/Starsurfer78/Ardumower_PCBs/blob/main/Charging_PCB/charge_pcb.pdfThe schematic above performs the following:
Turns on/off charging to ensure batteries do not get over charged via Q1 + Q2
Q3 + Q4 controls power to J4, J5, J6, J7, J9 - this could be used to turn off the device to prevent battery undercharge or just to turn off the device when required
Monitors charge current via an INA169 Module
Monitors Charge Voltage, Batt Voltage via Voltage dividers
J8 is a Normally open switch (momentary) used as a start button to turn on the robot
However the original schematic (
https://github.com/Starsurfer78/Ardumower_PCBs) above was designed for use with a 29.4V battery.
Initially I'll be using a 42V 4.4AH battery (10S2P) from a hoverboard - the battery has a built in BMS but it's pretty basic.
However there's a high chance I'll upgrade the battery at some point in the future to get longer run times (anywhere up to 55V 20Ah) although that all depends on how it performs with the battery I have.
Connected to this "Power PCB" via J4, J5, J6, J7, J9
Meanwell DDR-30L-5 30W 5V DC/DC converter (to power all 5V devices incl. Arduino Nano and Nvidia Jetson)
hacked hoverboard motor driver + BLDC motors (for driving robot)
Additional motor driver + BLDC motor (for cutting grass)
Arduino Nano @3.3v (controls Power PCB and some other peripherals)
Nvidia Jetson Nano 4GB B01 (main MCU - controls Arduino nano via USB cable)
Stereo depth camera
IMU
RTK GPS
I'll also have include an emergency stop so that it kills power to all motors but not the computers - that way it can resume what it was doing if the "emergency" has passed (like a pause button).
So yeah one of my main concerns I suppose was if the mosfet fails, I don't want it surging through the gate pin and frying everything via the connection to the Arduino GPIO however obviously that can be prevented via isolation such as by using an optocoupler, capacitive isolated gate driver, relay etc...