16

TCB Dev / Re: Re: Testing TCB Firmware with Stock Arduino Mega

« on: July 14, 2020, 03:02:34 AM »

Hello Kim! Your design is extremely impressive and interesting. Thank you for sharing! It is very educational to see the design choices you have made and the components you have chosen, I think a lot can be learned from this design. I see you have changed some of the pins in order to manage the onboard main motor drivers, it looks like you had to sacrifice PWM on the Hit Notify and Aux outputs? 

I may be willing to make some changes to OP Config on your behalf but it is something I will want to think about and I may not do it right away. Of course it would benefit you and your club but the extra options in the documentation will only confuse all the hundreds of other people who already have a TCB, so I have to weigh these things carefully.

In the meantime it would be great if you could make your project open source, including the firmware for the Arduino Mega, and board files and bill of materials for your shield. This could be hosted on GitHub. If you are able you can make a fork of the TCB firmware with your changes on your own GitHub, or if you prefer you can provide me the source code and I can fork it myself and host it on the Open Panzer GitHub page.

You may be interested to know that in fact all the functions could be simplified onto the Teensy 3.2 alone, eliminating the need for the 2560 altogether. In other words, we can combine both the sound card ability and all the rest of the TCB functions onto just the Teensy, including onboard main motor drivers as you have done, so that in the end we have a complete single board product. The 3.2 has barely just enough pins if we use some shift registers! I have started writing code for this but it is not yet complete and I don't know when I will have the time to finish it. I haven't even started on a board design. I am not spending much time in development this year due to other commitments, but if the project were to be revived someday I think that would be the way to do it. But for now it is just an idea.

Thank you for the praise  Yes I needed an extra timer for the motor C and D PWM, not really sacrificed as such, they can still be PWM controlled they are just running at a different frequency XD.

Yes this should perhaps be an entire new branch of OP, to differentiate it. I do not intent to make things harder for the rest of the OP userbase. I will work on putting my designs on GitHub and make a fork on the firmware (I should probably comment a bit more in my code "gulp") I think i prefer it to be on the Open Panzer GitHub page, I think it will reach more people this way.

Yeah in my research I also considered going with Teensy alone (4.0 specifically) but due to time constraints before my exam, I stuck to the current setup. As an after thought, I considered the teensy 4.1 because of the plethora of outputs. STM32 F4 and F7 series would also be interesting. Many posibilities, a lot of coding required
I would be delighted to help you with the board design if you want on that teensy branch

In my Frankenstein Leopard 2 I went to exam with I used the teensy 4.0 and an external DAC for the sound card (16bit sound is awesome!) that's what the EXT_DAC port on my design is for, a PCM5102 based module

Cheers Kim

17

TCB Dev / Re: Re: Testing TCB Firmware with Stock Arduino Mega

« on: July 10, 2020, 02:42:55 AM »

I could however use some help making some additions to the OP config, to implement some of the changes I have made, a little better.
In order to use 2 sets of onboard motor drivers I have had to "hi-jack" the code of one of the selectable ESC's, I chose the Sabertooth, but it would be neat to have an actual parameter that was called "Build-in driver (Motor C)" and "Build-in driver (Motor D)" or something like that.

I have also made some exspansions to the Forces of Valor IR library, defining ammo types with different armor penetration, and on the receiving end definitions of armor thickness (I'm also working on a directional IR receiver, making side and rear shots a possibility, with a higher chance to penetrate as a result). This is also something I wish to have implemented in the menues.

I know I am asking a lot, but I really wish to keep this project alive and we are a 1/16 rc tank club with about 20 members testing my creations out and the enthusiasm is high.

Best regards Kim Olsen Panzer Club Denmark.

18

TCB Dev / Heclo TCB Shield for Mega2560 Boards

« on: July 09, 2020, 07:38:56 AM »

Hello everyone!

I have been following the Open Panzer project for a while and in my education as a electronics technician I made a "shield" that fit on an arduino mega 2560 R3 board, with most of the functions of the Open Panzer TCB and the Open Panzer sound card onboard, plus some extras.

Instead of the L298 motor driver as the onboard drivers I have opted for 2 x VNH5050 chips which are similar to those found on the OP Scout ESC, but in a smaller package. They can draw 30A each and therefore should be adaquete to most aplications. I have also added 2 additional H-bridges to power the turret elevation and traverse motors, they can draw 3A each.

The high-current drivers have current monitoring which I have implemented into the TCB code so that throttle commands corrosponds to engine wattage instead of a PWM setting, this makes simulating a models scale power a lot easier, resulting in realistic slow down when going uphill or through rough terrain.

All in all this makes Open Panzer a stand-alone board with all the necessary components onboard (except for a radio recaiver I suppose).

It has been tested in so far 6 different tanks with great results.
 
I have attached the schematics and a pinout rendering for those interested.