21

TCB Dev / Re: Potential OpenPanzer-DA

« Last post by LukeZ on May 24, 2026, 08:19:02 AM »

Hi Foxhood, I can see you've done a lot of work, but also still have a lot of work left. However once you have some hardware available to start experimenting with, I find that progress is much faster (or anyway, it feels like it moves faster).

All the TCB boards up to now have always been labelled as "Mk 1 (rev xx)." The current board sold by Torro is revision 24, but nevertheless the silkscreen still says "Mk 1." You mentioned calling your project a V2; I agree it's different enough to merit such a distinction, and I'd suggest you could label it "Mk 2." And that would probably mean more to the general public than the "AD" name.

Many of your changes won't really be noticeable to the end user, but the addition of sound on the same board will be a massive upgrade that I know many people will be overjoyed about. So your detour and testing on the OPSC Lite seems to have had a very positive result.

As always I'm impressed with your work as well as your perseverance. Bon courage and keep going, the outcome will be very impressive!

22

TCB Dev / Re: Potential OpenPanzer-DA

« Last post by Foxhood on May 21, 2026, 12:49:06 PM »

While most work is going into the OPSC. The TCB hasn’t sit idle that much either. Been slowly chipping away at it and ready to show some early info and images.

Board Changes:
    • Switch to 4-Layer setup (Improved EMI)
        ◦ 4-layer has proven economic at pretty much every fabricator. Only exception being OSH
    • Modified Layout for better EMI and Routing.
    • Embraced smaller Packages such as QFN
    • Switched primary Controller (AVR128DA64)
    • Switched USB Serial Bridge (CH340X)
        ◦ Switched USB Connector (USB-C)
        ◦ Added switch that reconfigures USB Bridge into SerialUPDI device for programming its controllers without external hardware (in case of bootloader absence/failure)
    • Added Sound Co-Processor (AVR64DD28 + MAX9768)
    • Switched motor Driver (DRV8434E)
    • Simplified Polarity inversion for S.BUS through Open-Collector Inverter IC
    • Rerouted unused UART-TX (serial3) to Receiver pad for ELRS (CRSF protocol) connection.
    • Additional High-Power Driver (For Smoke units with seperate pumps/fans)
    • Overhauled Power supply (PFET Polarity Protection + SMPS 5V Supply + Low ESR Cap)
        ◦ Added Power Supply EN connector for external shutoff
        ◦ Improved Battery Monitoring input protection.
    • Replaced individual NFET drivers with Arrays (ULN2003V12).
        ◦ Need to verify if IR-Output is not distorted by the filters within the arrays.
    • Improved Airsoft/recoil Input protection
    • Current limiting resistor networks on Servo/RC Outputs.
    • Replaced I2C connector by JST-SH connector (Stemma-QT compliant).
    • Added “Smoke+” Connector for connecting to external driver.

The board has been changed up significantly. To the point i’m tempted to just call it a V2. Most of the changes are kind of trades. Where as one part simplifies (e.g. Led output control and the AVR not requiring a external oscillator anymore) another gets slightly more complex (e.g. Power supply). Biggest change being the integration of the OPSC-Lite so that at the very least: Sound no longer requires a seperate board.
Images are very much WIP as stuff like the OPSC are not fully set up (need to modify stuff such as the switches to enable switching of UPDI target), some components lack values, may see substitution and I try to optimize layout based on routing attempts. Also realize i forgot to give some custom parts basics like their bloody name...

Just finished a Dev-board for the AVR128DA64 and a prototype of the OPSC-Lite. So work is now going into finishing the latter and getting the TCB V1 code to compile on the former before moving to add new features. Also gotta build a TankIR to help test IR and something of a CRSF dummy as it is rather hard to convince my wallet to open for a Radio+Receiver before the project is as good as guaranteed to succeed. <_<;

23

TCB Dev / Re: TCB Firmware with Stock Arduino Mega

« Last post by Tef2008 on May 17, 2026, 07:00:41 AM »

I have the escs set up as described and I’ve had good experience with them on other projects (rc ships).

Think you might be right with the battery though. I’m using a NiMH battery because discharge rates haven’t been so important to me. I’ve got a lipo on order and I’ll see if that improves things.

24

Open Panzer Help / Re: dasmikro mini connection problems

« Last post by Tom on May 16, 2026, 08:56:24 AM »

https://www.silabs.com/software-and-tools/usb-to-uart-bridge-vcp-drivers?tab=downloads

Finally found a driver that will connect Dasmikro mini.

25

TCB Dev / Re: TCB Firmware with Stock Arduino Mega

« Last post by LukeZ on May 16, 2026, 07:27:49 AM »

Hi Tef, what you describe is very strange and I can think of no reason why that should be happening, and especially why it would occur with both ESCsc but not with one.

There are a couple things which I do not think are the cause, but which would be good to verify. First, both ESCs should have their BEC (+5v) wire disconnected prior to connecting to the TCB, as described in the Wiki.

Secondly, I see these ESCs have multiple driving settings, selected by jumpers on the device. They should be set to "Forward/Backward" mode; in other words, there should be no jumper on position 1 or 2. This lets the TCB handle braking.

As for the behavior itself that you describe, I really have no idea. But one wild guess is that when both ESCs are commanded to perform the abrupt track recoil movement, they momentarily draw more current than your battery can provide, and this causes a brief voltage drop that disrupts the normal function of the TCB processor. One way to test this theory would be to use a battery with a larger capacity and C-rating.

Otherwise the other thing to try would be different ESCs, though that will require spending money.

26

TCB Dev / Re: TCB Firmware with Stock Arduino Mega

« Last post by Tef2008 on May 15, 2026, 02:34:42 PM »

Anyone able to help with a track recoil issue on an arduino mega build?

I’m using to radio link 9030 escs which work fine when driving. When I use track recoil I have no issues if only one esc is connected at a time. However, if I connect both then the entire system goes hay wire and the track recoil effect fires on a continuous loop until I reset the system. Any idea what could be causing this?

27

Open Panzer Help / Re: Sound 2

« Last post by LukeZ on May 08, 2026, 01:20:55 PM »

Thanks for reporting the resolution.

28

Open Panzer Help / Re: Sound 2

« Last post by Tom on May 08, 2026, 11:51:18 AM »

Solved:) It was one wrong number on prop setting on the TBS. 153 should have been 157!

29

Open Panzer Help / Re: Sound 2

« Last post by Tom on May 08, 2026, 07:09:50 AM »

Thanks Luke,

Yes more process of elimination lol.
I think it may be something in parameter settings.

30

Open Panzer Help / Re: Sound 2

« Last post by LukeZ on May 07, 2026, 02:24:21 PM »

To solve these kinds of problems you will have to do some troubleshooting, which requires experimentation with a view to narrowing down the possibilities - an experiment can prove that one part of the chain of events does work, which you can then cross off the list of potential issues; or the experiment can be designed to prove that one piece does not work, and then you know where to focus.

You know your other sounds work when triggered by something other than braking, but that doesn't tell you whether A) Sound 2 actually works, or B) whether braking actually works as a trigger. These are the two things you need to experiment with.

You tried to trigger Sound 2 with the Transmission switch, because you know the Transmission switch works. Sound 2 still didn't play. That would imply to me that the problem is with Sound 2.

What if you tried to trigger your Transmission sound with the braking trigger instead of the switch? We know the Transmission sound works, so in this test you are focused on whether the brake trigger works. Or you could set up a light to come on with the brake trigger, and if that works, then it would be further evidence pointing to a problem with Sound 2. There are lots of things you can try, but only you can try them.