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 ... 21 22 23 [24] 25 26 27 ... 78
346
« on: December 19, 2019, 01:34:11 PM »
The boards arrived, it remains to wait for the arrival of the necessary radio elements and nodes.
I like the black! And we will be waiting patiently to see your experiment progress.
347
« on: December 19, 2019, 01:33:04 PM »
From all your previous screen shots it looks to me like you had the cannon sound assigned to position 1 of the 2nd Coder column in TBS Flash, which is correct. What it almost looks to me like is that the change that fixed it is was this earlier suggestion: Hi Wibbly, you have the Prop2 Type set to "2nd Coder 2-Key" but it should be "Function 1/2". I know, they look similar, but do very different things. Only in your most recent screen shot do I see this now assigned correctly. The incorrect setting there certainly could have caused your machine gun sound to repeat incessantly. The gun sound will only operate if the left stick is about 1mm to the left of centre at the top, otherwise i just get the flash and recoil. I don't know if this is due to the Prop settings in diagnostics, it seemed to work ok when I tested the mini. The v1 won't allow uploads of settings, the v3+ allows Luke's files to be uploaded. This sounds strange, theoretically if the flash and recoil are going then the signal is also being sent to the Micro, moving the stick over a bit won't change that signal at all. So no in this case it is not an issue with the Benedini Prop settings and anyway those settings are mostly for Prop3 which we aren't using on the Micro anyway. You could try moving those various cannon fire functions off the turret stick and assigning them to a switch on your transmitter and seeing if the problem goes away. Although the behavior you describe shouldn't happen, I also don't think the turret stick is really an ideal trigger source if you can avoid it.
348
« on: December 18, 2019, 04:37:25 AM »
Hi Wibbly, I'm glad you persevered. Yes, the Micro will work with Flash v1 (as will even the Mini), you just don't get as many features.
It's funny, but from your most recent screenshots I don't see how you've done anything different than what was in the Wiki, or for that matter, what you appeared to have been doing earlier this week. You mention the "engine startup sound glitch" but I'm not sure if I know what that was or if you resolved it.
Do you know what it was exactly that was preventing the Micro from working before, that you have since changed? It would be good to know.
349
« on: December 16, 2019, 05:42:54 AM »
Yes, if you can get either Flash v3 or v4 then you should be able to use your Mini.
350
« on: December 14, 2019, 11:46:58 AM »
Ok, if the flash and servo recoil are working on left stick up then we know the function trigger is working (you could have used Snoop also as suggested).
The other thing you could try is putting a regular hobby servo on the Prop 2 output that normally goes to the Micro. We are just sending regular servo signals to the Micro so its fine to replace it with a servo instead.
When used with the Micro the Prop 2 output has three positions - servo center which tells the Micro to "do nothing." Cannon fire is one extreme, and machine gun is the other extreme. When you fire the cannon the servo should blip over to one side if the signal is being sent correctly to the Micro. The blip won't last very long and your servo will probably not have time to travel all the way to one end because the signal is rather short, but you should still see the servo blip.
If you assign a "Machine Gun - Fire" and "Machine Gun - Stop" function to some other control on your radio you should see the servo move the other direction. This one is easier to see visually because when the machine gun is turned on the signal is sent and held until the machine gun is turned off, whereas the cannon fire is just a single quick pulse.
If that works then we can assume the issue is with your Micro somewhere.
351
« on: December 14, 2019, 08:55:10 AM »
Good grief! The Wiki really needed some changing, my apologies. The whole bit about using a switch to toggle the engine should have gone under the Mini page on the Wiki, and not the Micro page. In fact on the Micro there is only one engine-start option that is supported, and that is Auto Start (set in TBS Flash). Under this method the Micro will auto start the engine with the first blip of throttle (which the TCB automatically sends when you start the engine using a TCB function). The Micro will also auto-turn off the engine when idle for 20 seconds. I have updated the Wiki on these topics.
You still need a function when using the Micro to start the engine, and technically this can still be a switch, but there will be no way for the switch to turn off the engine, only on. With the Micro the only way to stop the engine is for the Micro to detect idle for 20 seconds. So in this case it probably actually does make most sense to for the function to start the engine on the TCB to be the built-in function that is selected with the "Auto Start Engine with Throttle" checkbox on the Driving tab of OP Config. In that case you don't need to create any other function triggers for engine stuff, just check that option and blip the throttle.
So ignore most of what I said about engine stuff above and I will go back and edit it.
However it sounds like your main issue has been the cannon fire sound which I hope we can still resolve.
352
« on: December 14, 2019, 08:22:30 AM »
Hi Wibbly, if I'm sitting in front of the computer anyway I don't mind responding.  For the engine settings, the Wiki in its current state is confusing and I need to update it. EDIT: this message was a bodge. Here is an edited version: For the Micro the Engine Type in TBS Flash should be set to "Autostart." In this case the Micro will start the engine sounds as soon as the throttle is advanced and it will stop the engine when idle for 20 seconds. You still need a function on the TCB to start the engine, and the TCB will conveniently blip the throttle signal to the Micro when that function is called. But since there is no way to tell the Micro to turn off the engine the best method is to make the TCB match the Micro settings. In that case, go to the Driving tab of OP Config and check the option to "Auto Start Engine with Throttle." Then also tell OP Config to "Auto Stop Engine when idle for: " and select 0.3 minutes (approximately 20 seconds). The transmission is automatically engaged by the TCB as a convenience to the user whenever you start the engine (subject to a user-defined delay that you can set in OP Config). So that is why you are seeing that message in Snoop. I didn't see in Snoop that you tried to fire the cannon. While Snooping try moving your turret stick up and see if Snoop shows cannon fired.
353
« on: December 14, 2019, 07:06:10 AM »
In my experience when things are going this crazy something very simple has been overlooked. You mention that your transmitter switch engages/disengages the transmission. That is not correct if what you assigned the switch to is "Engine - Toggle On/Off." Are you possibly using a mis-matched version of firmware on the TCB with software in OP Config? Update both to the latest to make sure they are compatible with each other.
Then forgetting the Benedini for the moment, verify that your transmitter is triggering the correct functions that you expect with the correct stick/switch movements using Snoop. For example you should be able to see the cannon fire displayed in Snoop when you move your turret stick up. If not, get those things resolved, either by running through Radio Setup again, or double-checking your function-trigger assignments, etc...
As for the Benedini, are you remembering to write the parameters to the device when you change them in TBS Flash? You may also want to re-write your sounds to the Benedini just to be safe.
Re Amiens, I only just moved here a couple weeks ago from the USA. I'll be here for the next several months. Where are you located in England? I may be heading over there later next year.
354
« on: December 13, 2019, 09:55:23 AM »
Also, thank for the snoop file but my thought there was to try firing the cannon and see what Snoop says, just to make sure it is reading your transmitter correctly. One other thing - I see you have the engine set to auto-start with throttle. I haven't tested this with the Micro but it might not work very well in keeping synchronization. The Micro has some limitations when it comes to the engine starting and stopping. You can read here the recommended way to control the engine with the Micro, which involves a 2-position switch on your transmitter. I also see a bug in OP Config in that when you select the Micro on the Sounds tab the turret and elevation sound checkboxes should be hidden since they don't do anything with the Micro. This is just a visual error and isn't related to the issues you're having with the cannon fire function, but it's good you helped me notice it.
355
« on: December 13, 2019, 09:48:10 AM »
I've got these two, but can't see the *.tbp file, even a search doesn't throw anything up? Yeah, in TBS Flash go to the File menu and select "Save Parameter" and select a location on your hard-drive.
356
« on: December 13, 2019, 08:24:55 AM »
Can you post your OPZ file for me to look at, and also your parameter file from TBS Flash (.tbp file)?
You might also check Snoop to see if it shows anything useful.
357
« on: December 12, 2019, 10:21:48 AM »
Hi Wibbly, you have the Prop2 Type set to "2nd Coder 2-Key" but it should be "Function 1/2". I know, they look similar, but do very different things. Leave Prop3 disconnected, it isn't used with the Micro and will only confuse it.
358
« on: December 10, 2019, 11:53:56 AM »
I really don't think you will get it to work with your version of Flash because the Mini won't know what values to expect on the Prop 3 input which for the Mini is what we use to play all the sounds (except engine sounds and the repair sound, which go on Prop 2). When using the Micro we don't use Prop 3 at all and cannon and machine gun get set to Prop 2, the positions of which are hard-coded in the Micro so that is easy.
But with the Mini it needs to know in advance all the various positions of Prop 3 (there are 16 positions) and Thomas Benedini was kind enough to create a utility on the Diagnostic tab of Flash v3 and v4 where you can import a PropSettings file to tell the Mini what these positions will be. But Flash v1 has no such ability.
If you are getting some cannon fire sounds on engine start or odd positions of your turret stick then probably what is happening is that the Mini is using some default assumptions about the 16 positions which do not match what your TCB is actually sending, so instead of playing the cannon sound when it is supposed to it is playing it at some other time under some other conditions.
I know all this is frustrating, but what the Chinese cloners don't make very clear is that their products only work with Thomas's software and Thomas is only giving out his software to people who have actually bought a product from him. One of the very reasons why he has continued to release new versions of TBS Flash is precisely so he can stay ahead of the clone game and hopefully add features that will not work with the bootlegged software.
What I can say is that the Open Panzer firmware, even on a DIY Mega board will absolutely work with Thomas's sound card, but I can only guarantee it when the official products and software from Thomas are utilized. I don't personally mind people trying other things, it's not costing me money either way, but I think most of the time it's not going to work.
359
« on: December 10, 2019, 06:07:47 AM »
I am wondering whether the TBS needs the correct values in Prop settings so that it knows when to play the sounds when it gets a signal from the TCB. The engine sounds work ok, so it must just be Prop 2 that isn't seeing what it should. Yes I think that is the case. To use the Mini with the TCB (whether it be Benedini's or the DasMikro) you will need TBS Flash v3 or v4. Flash v1 will only work with the Micro sound cards and even then with more limited options.
360
« on: December 09, 2019, 05:35:32 PM »
Ok my apologies, I had gotten it into my head you were using the Micro clone. I forgot that only recently they have cloned the Mini, but it is not helped by the fact they call themselves DasMikro! Ok, so you do need to select Benedini - Mini as the sound device on the Sound tab of OP Config. Then you need to refer to the Mini Wiki page. Note that we have to put sounds in a different location on the Parameter tab of TBS Flash when using the Mini (also you may have to use a new version of TBS Flash depending). Note that now your cannon fire sound (your Sound #2 in TBS Flash) will need to be assigned to slot 3 of the first coder column. Please also read the entirety of that Wiki page to make sure the rest of your Mini settings are specified correctly for compatibility with the Open Panzer device. That should finally correct your problem, but let me know!
Pages: 1 ... 21 22 23 [24] 25 26 27 ... 78
|
Show Posts