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 ... 27 28 29 [30] 31 32 33 ... 78
436
« on: August 27, 2019, 03:57:38 PM »
Hi Adam, I am not too surprised. There is no published specification for the Taigen sound protocol. I did my best to decipher it using a logic analyzer, but the unit I had to work with was the PzIII sound card. It could be there are differences between the models.
I will try to obtain an IS-2 sound card (it did not exist when I wrote the firmware) and do some testing.
In the meantime, try this experimental firmware where I have taken a guess as to what might be the issue, but I can't really be sure. Let me know what it does. It might prevent the idle sound from playing during startup, but it also might prevent the idle sound from playing at all.
Download the hex, then in OP Config flash it to your TCB, but instead of downloading the latest hex from the web click the button that says "Use your own Hex" and select this file.
437
« on: August 23, 2019, 02:11:57 PM »
PS : Sorry Luke, but after your explanations, I2c connector was sacrified ! Yes, it's unnecessary. If I were producing the TCB today I would remove it.
438
« on: August 23, 2019, 07:45:20 AM »
I have seen that Luke add some possibilities for DIY boards, and I would like to clarify some details :
- Machine Gun mosfet drive was driven with PE2, non available on Mega board
Now connected to PD1 (Pin 20 SDA of I2c port)
Correct ?
- Recoil switch was connected to PE6, non available on Mega board
Now connected to PD0 (Pin 21 SCL of I2c port)
Correct ?
So, I2c connector can be removed That is all precisely correct. It requires us to give up the I2C port but we are not using that port in the TCB firmware anyway. I will be interested to see the results of your DIY experiment and I'm sure they will be useful to others as well.
439
« on: August 21, 2019, 01:44:36 PM »
Great, thanks for reporting back. I'm glad everything is working.
The timeout settings was actually a different issue which I don't think you had, but I discovered it while doing testing on this. It only happened with a unique combination of functions and only with iBus, which is why I originally thought it might be related, but in the end it wasn't. The issue with the Benedini was actually a bug in that code specifically. Of course it had worked at one time, but what happens is that changes are made later and these always have unintended consequences in other places so later we find something that used to work but does no longer and we have to change something yet again.
When I mentioned exponential I actually had in mind the settings you can adjust on your transmitter, and your i6X does have it. It's true the Sabertooth has an exponential setting as well but I don't think it's very useful because there is no adjustment for it, it's either on or off. I would leave that off. On the transmitter you can adjust the expo curve from 0-100% so you have the ability to finetune it. But if the end-point adjustment works for you then no need to do anything else.
I am subscribed to your thread over at RCTW and I will definitely be following along closely as you complete this beautiful model!
440
« on: August 20, 2019, 10:18:02 PM »
Ram, I've posted a firmware update (version 0.93.52). I believe it will fix your Benedini engine problem, but let me know your results.
441
« on: August 20, 2019, 02:04:42 PM »
Good, sounds like we've solved the gearbox issue. I had forgotten I'd written a section on the 2x12 RC in the wiki. I actually updated it just now because I think it wasn't entirely correct before, and I've linked to this thread for anyone else with the same problems.
Yes I agree with you the PDSGB gearbox has very sensitive steering, I think it is simply due to the way that it is designed. What we need is an "inertia" setting for the steering channel but that isn't really practical. Rather than modifying the endpoints on your radio, you might want to try using exponential instead. This will make steering less sensitive around center stick, but you will still have full travel at the ends so you don't lose any steering ability if you need it.
As for the Benidini issue - I have been able to reproduce it on my end which is good because it means I can solve it. I have not gotten very far into it quite yet. As I have time this week or possibly this weekend I will get to the bottom of it and let you know what I find.
Can I ask what radio you are using? I am guessing a FlySky iBus system but I can't be sure.
442
« on: August 19, 2019, 02:20:22 PM »
Ok, that explains it. When using serial control, when we tell the Sabertooth to stop the motors, we say "stop" and there is no ambiguity or possibility of miscommunication. When we use RC, it is sort of as if I said "I'm going to move my hand up and down, when it gets to about the level of my waist then stop." It is not precise at all and therefore what the TCB thinks is "stop" is not necessarily the same thing as what the Sabertooth thinks is stop. I have not tested the RC versions of the Sabertooths before. But I have just taken a look at the manual for the 2x12 RC from here. There does appear to be a calibration routine that may solve your issue. The first thing you can try is to set Dipswitch #5 on the Sabertooth (not the TCB) to the down position. This tells the Sabertooth to use the saved calibration settings which by default should be correct. However if you still have unwanted movement, you will need to move to the next approach: - With the Sabertooth off, put dipswitch #5 on the Sabertooth in the up position, and dipswitch #6 in the down position. All the others should be as shown in the Wiki (in other words, 1 and 2 down, 3, 4 up). - Leave the servo cables from the TCB to the Sabertooth disconnected. Power on the Sabertooth and power on the TCB. Make sure the Engine is off on the TCB. - Now connect the two servo cables. They will be transmitting the "off" signal and the Sabertooth should memorize this. - Now turn on the engine from the TCB and move your controls to their maximum (both throttle and steering). The Sabertooth should memorize the maximum travel. - Now turn Dipswitch #6 on the Sabertooth back to the up position. - Now disconnect power. - Now turn Dipswitch #5 on the Sabertooth to the down position and leave it there. This will be the final setting. 1, 2 and 5 will be down, 3, 4, and 6 will be up. Now you can operate the tank normally and it should theoretically work. Let me know the results. Sadly if there are still problems I'm afraid you might have to trade in your 2x12 RC for the full-featured 2x12. I wonder if moving your receiver helped at all with the Benedini issue?
443
« on: August 18, 2019, 01:27:27 PM »
Hi Ram, that's a beautiful model and I love how tidy you've kept the interior! I have a PDSGB gearbox as well and I think it's the bees knees, I will be happy to try to see if I can reproduce the issue on my end. I've have no problems with mine so I'm sure we can sort it out.
Can you post your OPZ file here so I can take a look?
I'm curious how you are driving the Sabertooth. In your photos I see two RC leads attached to RC outputs 1 and 2 which are for the left and right tank treads. It is in fact possible to drive the Sabertooth using RC, but I would recommend using the MOTOR SERIAL output instead. I also don't see any servo leads on RC outputs 3-5 which I you will need for your three turret servo motors (but maybe you have just disconnected them to take off the upper hull for pictures).
As for the Benedini (and possibly also your PDSGB issue) it almost sounds like possibly the radio setup is a bit off. You may want to perform that task once again.
The other thing I would do is move your receiver antennas away from the TCB and route them back over the side by the battery. It looks to me like you're using one of the 2-way FlySky receivers, which has 2 antennas. In addition to receiving these receivers actually also transmit information back to the transmitter, and those transmissions can definitely cause interference.
444
« on: August 09, 2019, 02:55:27 PM »
See also this thread by Sergey from Russia who I think was the first to make a DIY version. His Russian-language thread is also definitely worth checking out, it has more detail (he provides a link to it).
445
« on: August 09, 2019, 02:43:32 PM »
Hi Jerry, First, I've merged your posts with the Arduino Mega thread as you can see, to keep all the discussion in one place Having no experience with arduino's, could you suggest:
1) a vendor/manufacturer of preferred board with as many components which would make the transition minimal hassle?
All the commercially available Arduino Mega boards are functionally the same, they differ only in size/form factor. None of them will have any of the components that will make the transition hassle free, indeed all of them aren't really circuits so much as they are just "breakout boards" which simply bring the teensy-tiny pins of the processor out to headers where you can more easily access them. 2) a complete wiring diagram, which includes lights, sabertooth, etc. which the DIY firmware will work with? The latest one you posted is great, but missing the LED side, I think?
3) any other components which are needed IE: transistors/etc. for inverting the Sbus signal....I assume we need to make a small board to interface this? or any other components needed to emulate the TCB.
See this post earlier in this thread for a pinout document (updated to show the alternate DIY pins, of which there are only two). Of course a complete schematic as well as bill of materials is available on the Downloads page. The pins in the schematic refer to ATmega pin numbers, whereas your mega board will use Arduino pin numbers, which are not the same. However the document in the post I just linked will provide the crosswalk. 4) anyone to contact with success, willing to share pictures, etc?
This is the thread to be in! Start from the beginning and read through. Making a DIY version is not entirely an easy process but start with the simple things (radio in and servo outputs), then go from there. Don't connect or bother with any functionality you won't be using to simplify the final result. Comprehensive support for this undertaking is beyond the scope of the project but feel free to ask specific questions and I will try to assist.
446
« on: August 02, 2019, 09:24:39 PM »
That's true dedication! I hope they work well in your models, let us know.
447
« on: July 27, 2019, 12:59:51 AM »
There is a lot of forum spam going on (as I know from here), but hopefully they will respond to your message and allow you in.
May I ask what country are you located in? I am interested to know all the countries that Open Panzer users are from.
448
« on: July 26, 2019, 10:56:43 PM »
I have not personally designed a DIY Teensy board myself, so I can't speak from experience. But looking at the schematic I see no reason why separating the bootloader chip onto its own board wouldn't work (in other words, I think it should work fine). The only way to know will be to test. Of course you can also get some very good advice at the PJRC forum. They have a whole section called "Project Guidance" where you can describe your project and ask for input. There have been several threads in the past about people designing their own Teensy-compatible boards and the usual response is that it's not worth the effort especially for low production numbers. But everyone has their own idea about what efforts are worth making. If you have the time and the ability, as it seems you do, then it could be a rewarding experience.
449
« on: July 23, 2019, 11:12:33 PM »
Thanks. I see now the forum would not allow posting .ini files, I have changed that for anyone in the future who needs to attach one.
Anyway, here again we have another bug which I have fixed, and you will need to flash new firmware (v0.93.51).
Very few people in the world have even tested one of these sound cards, and I think even of those few people they are all using it with with the TCB - in other words, not in RC mode as you are. Therefore I am not surprised you are finding some bugs. I do appreciate your testing which is helping me perfect the firmware.
Let me know if you notice anything else strange!
450
« on: July 23, 2019, 01:23:37 PM »
Can you describe in more detail the issue with Switch 5? Is it a problem specifying the switch function in INI Creator? Or does that part work but the function doesn't trigger correctly on the sound card itself?
Can you also post your INI file?
I will think about the engine speed request. All that sort of thing is possible with the TCB but the configuration framework on this device is much more simple as you can see (no dynamic allocation of functions with triggers). In the meantime, if you are using a programmable transmitter you can accomplish what you propose with a transmitter mix. But it depends on your transmitter, it is true that most pistol-grip car radios do not have that level of programmability.
Pages: 1 ... 27 28 29 [30] 31 32 33 ... 78
|
Show Posts