Progress with installation and H bridge as a smoker.
Nothing goes to plan. The photos will follow. I installed the board; it ran for a while, and when I applied the power for the third time, I got the dreaded grey smoke. That sort of thing is a nightmare because one does not know why the fault happened. It was working and I didn't touch anything sir.
You have to guess, unless you are certain of having made a mistake. I don't believe in failures due to bad luck. So I made some improvements which I will detail later, and also added a switch so as to turn things on with all inputs active and set. I learned a few things about low current H bridges.
Simple Sailor reminded me earlier about logic level MOSFETs. I was tempted and I fell. But it turns out that all the usual precautions on H bridges are required. You don't really save anything, because logic chips do not have enough Oomph to drive the FETs at a reasonable speed. You really have to add a buffer amplifier. And most switching circuits have a tendency to self destruction which must be resisted. I discerned a design rule to share.
If designing an H bridge with only one drive point on each side, the sum of the Vgs of the top and bottom FET when conducting the nominal load current must be less than the rail voltage. That is generally true for logic level FETs with single battery cell devices, but for 2 cells, or anything above 5V or so, a single point drive of an H bridge with logic level devices is liable to have problems, grey smoke being one of them. You should really use the old, bigger higher Vgs rated devices. Especially when you're a modeller rather than a speed merchant.
You have to drive the top and bottom transistors of one 'leg" of an H bridge so that there is a "dead band" when both are nominally off, or at least nearly off. This goes against nature and what FETs want to do, which is to both stay on together in an embrace to destruction. Normally, that means a driver chip is required but I am far too mean for those and found a workaround. I think a 3 cell 12V device would certainly need a driver chip, which all add their own problems, especially as many do not handle flat out full speed. At a future point I will cover H bridges and their foibles and differences. At no time may any transistor gate be uncontrolled, especially at turn on. The normal ESC is a bargain....
Surprisingly, I rethought my ideas on old fashioned Bipolar devices, and provided the current is no more than 5A they probably work out cheaper and simpler than MOSFETs especially at higher voltages. And low voltages below 2V is possible, where a MOSFET will start to struggle. They can be made more tolerant of abuse and the driving of them is actually quite easy.
Anyway, after a few hours soldering and retest....
Success! At least until it goes in the water. I added some LEDs which tell me if a prop is going forward or back, and the brightness indicates the speed. The circuit seems to be behaving properly; all functions work. Whether its all in the right direction only a trip to some water will tell. And to some extent, its a matter of preference or even practicalities.
I examined the Tug electronics and it's a little more non standard than I expected.
The rudder servo pulse is 1to 2 msec, but occurs at a rate of about 8.6 msec, over twice as fast as usual. Servos don't care about this but I do; cue some value changes to readjust gain.
The motor throttle pulses also come at every 8.6 msec. Full speed is seen, but the minimum starts at 2 msec or just under 1/4 speed. I feel that is excessive for a Tug. In time I will add an adjustment for that. When throttle is stopped and I move the rudders, as designed the motors turn in opposite directions for a spot turn. I can make the motors turn very slowly indeed, albeit in air. So it looks like the 2 msec they have used corresponds to a maximum servo pulse.
Provided it works OK in the water I will start to document the circuit in sections and use each section to illustrate the use of common and inexpensive electronic parts.
This has ended at a slightly higher cost than originally envisaged, but still very light for the functionality. It's the bits at the edges that cost.... I have realised from other blogs that every expert among us accumulates numbers of small tools, methods and knick knacks that help us to practise our expertise. When you come to help someone else get started, the real cost suddenly stares you in the eye. What is cheap and easy for me turns into something expensive for another to duplicate because of such start up costs.