This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - LukeZ
1
« on: July 05, 2026, 10:42:08 AM »
Glad to hear it, thanks for letting us know.
2
« on: June 29, 2026, 12:42:31 PM »
Hi Tom, the X8R has been used by quite a few other users on this forum with success, so we know it is possible. There are however as you have found discrepancies between the different firmware versions that FrSky uses and there are multiple posts of people having issues getting that all straightened out, which I suspect is the case here as well.
The first thing you should do when there are radio problems is to run through Radio Setup once again. It could be that channel orders have been changed under the new firmware, or something like that. But at any rate, Radio Setup will show you visually and immediately which channels are being read by the TCB and which are not. If it's simply a channel order problem, then you can re-arrange them.
If some channels are not appearing at all, then I think the issue is likely between the transmitter and the receiver, or with the setup on your transmitter, and that I can't help you with, but perhaps your contact at FrSky can (who I see is also a member on this forum, so perhaps he will chime in).
3
« on: June 11, 2026, 11:06:43 AM »
Hi Fox, you summary of the limitations (and inconsistencies) of the Motor Serial port is accurate, and you are discovering that certain pins were allocated a time long before I had a clear idea in mind of their ultimate potential uses. The current layout was arranged when my only idea was the connection of a single ESC (at the time the Scout hadn't even been considered, but I was thinking of the Sabertooth). Later I discovered that Pololu had a very small serial ESC that I thought might be useful for turret functions on larger models. Pololu later discontinued that, but that put the idea in mind that maybe it would be nice to control more than one ESC on the same port, regardless of brand. The sound card came much later, and was tacked on to the same port.
The only reason in those early days that I could see for communication from the ESC to the TCB, was perhaps to report telemetry information (current, temperature, etc) for passing on to a custom screen on the transmitter, but these ideas were never brought to completion. By the time I decided to add multiple devices to the same port, I had dropped the idea of bi-directional communication altogether, and so now as you find that Rx pin on the TCB is just floating there, without any use.
However your proposal would correct that oversight, and as you say, leave the path open to further possibilities - if someone has the will, time, and reason to develop them. But it is always good practice to leave room for such things, and then if a bright idea comes along, the hardware is there ready to serve. I think your suggestion is a good one.
4
« on: June 08, 2026, 03:02:08 PM »
That's fine, no apology needed. I'll just be a bit slower moving forward.
5
« on: June 08, 2026, 09:59:03 AM »
Tom, you will notice that I have made some changes to the location of your posts.
In the past six months you have created more new threads than any other user on this forum has managed to do in the last 10 years, including myself. You have posted almost daily, which is not a problem in itself, but almost every post has been a question, and that's a lot of questions. It has gotten to the point where the notifications I am getting from the forum on your behalf are coming in at the rate of a never-ending IM chat.
Understand that my time is limited and I can not afford a part time job devoted to one single user.
Here is what I have changed:
I have merged all of your threads since January of this year, into this single thread titled "Tom's Questions"
You had some other threads created way back in 2017, I have left those alone.
From now on please do not start any more new threads. When you have a question, you can post it in this one. Of course you are still free to post comments in other people's threads.
Finally, for my part, I will not be responding to this thread more than once per week.
6
« on: June 08, 2026, 09:39:37 AM »
You sent me a custom hex. to try and correct the firing of the cannon movement (non servo) the first time with no sound. Finally had a chance to try it.
I recently downloaded drivers on a new computer and all the tcb boards connect on various com ports. But when connected and after downloading
the custom hex. and try flash it.. the tcb disconnects with "flash operation failed. Make sure you select correct port" On this board the only option is com 1 and 4 and 4 is the one it connects to but on trying to update with latest version or the custom hex. it disconnects? Would another version of the drivers perhaps
fix this? Again, any changes can be made and downloaded after it connects, it's just the flash update.
Try uninstalling OP Config, reboot your computer, then re-install OP Config.
7
« on: June 07, 2026, 10:11:48 AM »
Hi Christian, my apologies, I thought you were asking about the firmware for the original Open Panzer sound card.
The sound card being discussed in this thread ("OPSC Lite") is a personal project that Foxhood is working on, but which as you can see is not complete; therefore there is nothing you can download or build at this time.
8
« on: June 07, 2026, 10:05:34 AM »
Perhaps you have the wrong COM port, it sounds like maybe you haven't attached that board to a computer in a long time, and it could have changed. The other thing you can try is to re-install the FTDI driver.
9
« on: June 07, 2026, 05:38:27 AM »
Hi Tom, no, I'm sorry, I'm not inclined to make this change.
10
« on: June 07, 2026, 05:31:47 AM »
The solution is almost always something simple like that. Glad you figured it out.
11
« on: May 29, 2026, 02:26:41 PM »
I personally don't have a Pershing sound set. You might have more luck asking in one of the more active tank forums if anyone has Pershing sounds, and not necessarily for the OP Sound card, because I doubt that exists, but in any format (.wav, .mp3, etc) that could be converted for your use.
12
« on: May 29, 2026, 09:59:15 AM »
Only one sound can play at a time from the 1st Coder column in TBS Flash. You can set a user sound to be triggered by vehicle speed, but since both the user sound and the squeak sounds are in the 1st Coder list, only one of them can play at a time. We can't predict in advance which one it will be, since the squeaks are random and the vehicle speed is constantly changing. It appears that most frequently in your case the squeak sounds predominate.
13
« 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!
14
« 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.
15
« on: May 08, 2026, 01:20:55 PM »
Thanks for reporting the resolution.
|
Show Posts