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
Pages: 1 ... 24 25 26 [27] 28 29 30 ... 78
391
« on: October 19, 2019, 12:41:52 PM »
FYI, in case it is of any help, the offsets for multi-switches are hardcoded in the TCB firmware. They are done as you would expect, by dividing the range from 1000uS to 2000uS into however many positions we want.
For a 6-position switch the positions come to:
1000 uS (Pos 1)
1200 uS (Pos 2)
1400 uS (Pos 3)
1600 uS (Pos 4)
1800 uS (Pos 5)
2000 uS (Pos 6)
(Where the positions are reversed if you reverse the channel in OP Config)
Your radio doesn't have to hit those positions exactly. The firmware will read the current channel value and will assign it to whatever position it is closest to. So if for example your channel is at 1480 uS the TCB will read it as Pos 3.
If your channel is at exactly 1500 uS then that is not good, with jitter the TCB will be oscillating back and forth between position 3 and 4. So it is not important that you hit the targets exactly, but that you keep away from the edge cases. Anyway this should be easy to do in your transmitter programming. Most transmitters use percentage offsets so in this case you'd probably define your positions as 0%, 20%, 40%, 60%, 80% and 100% and make sure your endpoints are set to the default 100%.
392
« on: October 19, 2019, 12:34:20 PM »
Hi Rad, to me this sounds more like a transmitter programming issue. But let me see if I understand correctly what you are doing.
In OP Config you have defined two 6-position channels. Presumably each of these positions will trigger a "User Sound X - Play Once" function (for user sounds from 1 through 12).
On your radio you have only a single 6-position switch, but when mixed with your RUD and ELE channels you can actually output 6 positions on two different radio channels (radio channels 14 and 15, assigned to Aux 10 and 11 in OP Config).
I imagine that RUD and ELE are defined as logical switches on the transmitter and don't themselves actually connect to any output channel to the receiver.
Your physical RUD switch is a 3-position switch but you only need it to perform as a 2-position switch (a 2-position momentary would probably be the ideal). What it sounds like to me is that if the unused middle position of the RUD switch is actually triggering a sound, that is an issue in your transmitter programming because your transmitter should actually be ignoring the RUD middle position and only be mixed with your 6-position switch when it gets to the down position.
I would think that the Read Radio function in OP Config should be useful for helping you troubleshoot this. Turning your 6-position switch on the radio should theoretically have no effect on the visual display of Aux 10 and 11 in OP Config. Only when you move the RUD switch down should one of those channels move to a new position (which Aux channel moves will depend on the position of your ELE channel). Does all that seem to work correctly? Are you able to access all 6 positions of both Aux 10 and 11 (confirming that your mix offset amounts are defined correctly)? What happens when you move the RUD channel to the unused middle position - does Aux 10/11 move to an undesired slot?
To answer your other question, whether it is related to your problem or not, OP Config only knows "positions." If you want some position to be "off" or do nothing, then the way to accomplish that is simply don't assign any function to that position. You could remove the function trigger for the sound 5 that you don't want. Of course now you lose that sound 5.
You could also set one of the Aux channels to 7 positions with one of the 7 being the unwanted position that gets triggered when RUD switch is in the middle, leaving you 6 others. But this will require you to modify the mix offsets in your transmitter and I don't really think it gets to the bottom of the problem.
I'd review your transmitter programming and use Read Radio to confirm that your mixes are working correctly.
393
« on: October 19, 2019, 11:12:17 AM »
Yes you can flash the firmware from the Arduino IDE, but you don't use a Hex file, you download all the source code from GitHub and then open the project in the IDE. However before you try all that try this first. Go to https://zadig.akeo.ie/ and download the Zadig 2.4 program. It's just a single EXE, it doesn't need to install anything. Run the EXE. Plug in your Arduino to the computer. In Zadig go to the Options menu and select "List All Devices." Then in the main drop-down box try to find your Arduino device. It may be listed as "FT232R USB UART" or who knows what else. If you can't identify it let me know what devices it does find and I'll see if I recognize one. One you select your Arduino device, on the left side of the form it will show what driver is currently installed, and on the right side of the form it will give you an option to replace that driver. I would be interested to know what driver it says is currently installed, but after you make a note of that, select "libusb-win32 (version xxx)" from the list on the right and then click the Replace Driver button. Now reboot, then try flashing again and see it if works.
394
« on: October 15, 2019, 02:48:24 PM »
I dont know if the feature is already there, but can we control the smoke with a pot? I mean in a proportional way, the more the more you turn the pot, the more the smoke. Yes, this is possible if you set the Control to "Manual (with function triggers)" in the Smoker section on the Motors tab of OP Config. Then assign the "Smoker - Manual Speed" function to your pot channel. Of course as the name implies, you will have to adjust the speed manually - the smoker will not respond to throttle commands, it will only respond to you turning the pot. But I think this must be the same method as when you use a speed control.
395
« on: October 15, 2019, 02:44:39 PM »
I'm glad you got it working again! It's always the simple things which trip us up.
396
« on: October 10, 2019, 04:36:17 PM »
Obviously I've never bought from them so I have no idea, but you can try and find out. I mentioned to you earlier the PJRC Official Distributor List, there are multiple sellers in Germany on that list as well as others elsewhere in the EU. I don't know why you wouldn't just use one of those but as we say in America, it's a free country and you can do what you want.
397
« on: October 10, 2019, 11:49:22 AM »
I would not suggest buying a counterfeit Teensy from China, there are many reports that they do not work. It also doesn't seem like they cost much less, and there is a good possibility you will just be throwing money away. For the second part you are correct - just plug it into your computer and flash the Open Panzer Sound Card firmware using OP Config, that's all you need to do.
398
« on: October 09, 2019, 03:47:33 PM »
There are really no user-replaceable components on the Teensy board. It doesn't have an amplifier on it, most likely what was fried was the DAC output on the processor ("digital-to-analog converter," which it uses to create sound waveforms).
Possibly that is the only portion of the processor that was damaged, but even if so it would render the sound card fairly useless. Your further test where it fails to connect to the computer would seem to indicate that the processor is basically dead.
For this application the Teensy 3.2 is required, a 3.1 will not work.
399
« on: October 09, 2019, 03:44:13 PM »
Ok, as I've delved further into this I realized that exceeding 9 positions will be problematic, because I didn't reserve more than 1 digit for them back in the early days when I started writing the firmware. It is possible to expand them but it would be more work than I have time for now. But up to 9 positions should now work and you can test that if you like. Also as you point, day by day better and newer radios are popping out. Have you seen the new Jumper T16? Looks like an amazing piece of technology, and has 6 push buttons in the front, so they can be used for triggering those user sounds. If for some disaster my 9xtreme radio dies, that will be my replacement. I saw the T16 earlier this year and was initially quite interested, but my enthusiasm was tempered when I discovered that Jumper is not using the official OpenTX firmware but their own fork of it, which we can assume will not be updated as often or maintained as rigorously. Even worse, the er9x developers have decided not to work with them at all, and that is actually the transmitter firmware I prefer (this was several months ago and things could have changed since, but I don't think so). It is kind of pathetic, but after almost 15 years a modded 9x transmitter remains the best tank radio in my opinion; unfortunately the best upgrade for it (the 9XTreme board) is no longer available. You'd think some manufacturer would make a suitable replacement for it but while there are new transmitters released all the time, nothing has quite come close to replacing it for the value and features in my view. Regarding the turret rotation speed, well, to be honest my (freak obsesive) idea was even a bit more deep than I stated.
If I had the knowledge and the skills, what I would do is a proportional turret sound, so the more further you move the stick, the faster the turret sound loops. It has some sense, in real life the faster you hand crank the turret, the faster it will turn. And yep, being able to limit the manual turret speed is also cool. For me, the more features and customization, the better! Proportional turret sound would be nice, but as you know the Open Panzer sound card doesn't have the ability to change sound pitch or speed, so what we'd have to do is create something like what we do for drive sounds, where we end up with something like 10 turret samples, each one played at a different speed of rotation. So now the burden is on the sound designer to find multiple turret sound samples which I imagine would be difficult, and it's hard to say how good the transitions between each one would sound. Everything has a cost in time and effort and even when those are reasonable every new addition adds complexity and setup work for the end user. I was told many times by people that they thought the Open Panzer project looked interesting but "too complicated" and they didn't have the time to figure it all out. On the other hand, others want more and more features, options, tabs in the setup program, pages in the Wiki, things to remember, etc, etc... So it is impossible to please everyone. As a designer I have increasingly become convinced of the need to keep things as simple as possible for a multitude of reasons, but of course the perspective is often the opposite for the client. The hope really was that developers would be attracted to the project and invest time in creating some of these new features, for that matter much like Jumper did it is entirely possible for anyone to fork the TCB code and take the project in a whole new direction. But it would seem that software developers are as rare as hens teeth in the RC tank modeling community. Anyway, those are my random thoughts. For now I'm going to leave the turret sounds as they are.
400
« on: October 08, 2019, 09:30:29 PM »
Hi Rad, although I haven't fried anything your experience with the 22 cent Chinese amp is similar to mine - horrible sound quality. Electrical interference is always a problem, even on a properly-designed board with very careful trace layout the challenge remains, once you start adding external wires and such the problems only compound. I'm sure you had the wiring correct but it would appear that the input impedance (or some other fancy-sounding word) of the Chinese amp was not compatible with the output of the OP Sound Card. This is probably why Benedini posts all kinds of cautions and warnings when using external amplifiers with his device. As mentioned in a different thread I have tried a few different cheap Chinese amps and haven't fried anything, but neither has the sound been any better. I have not done extensive testing of the line-out capability and you'll notice I removed it on subsequent revisions of the sound card. The question here is whether you actually fried the Teensy, since the onboard amplifier chip is bypassed when using the line out. If so, you could buy a new Teensy 3.2 and just swap it out since it's on a socket, and most likely that will restore the functionality. You can buy one directly from PJRC in the States but I'm sure there are some EU sellers that have them too, for example it appears the Mouser EU has them. I would try that first and see if it fixes it. As for the sound card entering production there is nothing in the works at the moment. If there ever is to be any future Open Panzer production I don't expect it to happen until late 2020 at the earliest. Even then that is a long way off and I can't predict if it will come to fruition or not. .
401
« on: October 08, 2019, 12:13:18 PM »
Ok thanks, I knew I would miss something without testing. That is an easy fix and there are a few other changes I need to make anyway so I will release another update to OP Config in the next couple days. Thanks for letting me know.
402
« on: October 07, 2019, 03:37:47 PM »
I will be curious to see your progress! At least the gun appears to be stationary...
403
« on: October 07, 2019, 03:36:01 PM »
Hi, this is not an idea but a (hopefully) very easy request.
In the open config I would like to be able to select a 12 pos switch too.
Yes, I know I will be the only soul in the earth using it, but it is very handy for me, for triggering the user sounds.
I programmed the radio in a way that having a 6 pos switch, with some software tweaking it feels and behaves like an 12 pos switch.
So with the rotating switch I select the desired user sound, and with some logic switches and programming, when flicking another switch or pressing a push button I trigger it.
This is the same system I am using for triggering the user sounds in the Benedini´s Mini and Micro.
Well as you know I don't accept all feature requests but this one seems reasonable as the number of functions has increased and people with advanced radios can now create these kinds of multi-position switches. I've added support for all positions up to 12 positions, but I have not tested it! It should work fine since we are just increasing certain parameters rather than creating new functionality but let me know how it works for you. (You will need to upgrade to v0.93.63 for both OP Config and your TCB firmware.) Another idea, (not request but an idea)
It would be nice to have two different "Max turret toration speed" one with the motor on, and another with the motor off. This has some sense, and means hand cranking the turret makes it turn slower than with the motor. That is an interesting idea, which I personally would file under the "more complication than is warranted" category. The same effect can be created with your thumb! It is not a bad idea but complication has a cost even for good ideas and I try to only add complication when there is a compelling need.
404
« on: October 07, 2019, 03:30:31 PM »
Yes let us know, I will be interested to hear how/if it works.
405
« on: October 07, 2019, 01:34:17 PM »
The paint job looks very good to me! I think you should be proud of it. You have used quite a collection of sounds and it is a good showcase for what the OP sound card can do (I notice for example you have subtle things like the stop sound played when the turret ceases movement, they are very small details but really help the realism). For anyone wanting to download Rad's King Tiger sound set or any other OP sounds sets others have made, you can find them at this link: Open Panzer Sound Sets on GitHub.
Pages: 1 ... 24 25 26 [27] 28 29 30 ... 78
|
Show Posts