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 ... 13 14 15 [16] 17 18 19 ... 78
226
« on: November 08, 2020, 01:27:31 PM »
Hi CodeWarrior, my apologies for the slow reply. Yes, the firmware has been tested with a 1/35 Tamiya model, I used the Sherman but they should all be the same. One thing you mentioned is that you compiled the code on an Arduino Mega2560 board, however the standalone TankIR firmware is designed for use on an Arduino Uno/Nano/328-compatible board. I don't know if that is part of your problem or if you just made a typo when describing your setup. You can easily verify that your circuit is at least sending a signal by watching the IR emitter with a digital camera, or your phone, or by hooking up a standard LED with human-visible light to the output instead of an IR LED. This will at least tell you if the firmware is trying to do what you think it should. Beyond that there are many troubleshooting avenues to take, and where to start depends on where you think the issue probably resides. I do believe the firmware works, so be sure to double-check your wiring and such. Keep me posted on what you find and I'm sure we can figure out the problem eventually.
227
« on: November 01, 2020, 09:05:41 AM »
Thanks guys for the kind comments, I'm glad there are people still finding the site useful. I hope someday the board will become available again, but things move very slowly, and the global situation has not helped, so I have nothing to announce for the moment. But do not worry, the site is not going anywhere!
228
« on: October 27, 2020, 12:09:53 PM »
Very glad to hear it! What happens differently (or nothing) to the recoil
3 pin out puts as labeled on the bottom of the TCB (pos neg and signal) when switched from
Mechanical recoil to Airsoft?
The difference between the two is the order in which things are performed. You will not get the correct behavior if you set OP Config to airsoft when you have mechanical recoil or vice versa, but it will not break the board.
229
« on: October 27, 2020, 07:22:49 AM »
Ok, I guess I had not seen that before. You can see the mechanical recoil page for instructions on how to wire those. Your unit looks different from the one in my example, but anyway, the principle is basically the same between all these recoil/airsoft units. There is a motor that requires two wires, and a switch with two contacts, one side of the switch is attached to the negative motor terminal, the other side of the switch goes to the "trigger/signal" terminal on the TCB. If you can wire it correctly, and then select "Mechanical Recoil" in OP Config, it should work. Let us know your results.
230
« on: October 26, 2020, 11:26:08 AM »
I have not seen that kind of airsoft unit before but assuming it operates like all the others it should not be difficult to wire it correctly. Jurgen is right, the diagram on the page he linked to makes it about as simple as it can, I have re-posted the relevant part here.
Now it's true, in your picture the switch at the rear of the unit is different from normal in that it appears to have 3 contacts instead of two. I'm assuming the third contact at the very back is used to trigger a flash or something. Just ignore that third contact and let the TCB take care of the flash. Try getting the airsoft to work first, then we can deal with the flash if that is still an issue.
231
« on: October 21, 2020, 05:56:38 AM »
I think you have the correct MOSFETs! Enjoy the new board.
232
« on: October 19, 2020, 07:41:54 PM »
If the board has the wrong MOSFETs, none of the light outputs will work (Aux output, L1, L2, Brake, MG), the IR transmitter will not work, the IR notification LEDs will not work (these are the LEDs inside a Tamiya apple), and the mechanical recoil/airsoft output will not work. That is a total of 8 outputs that will not function.
Ironically, the high-intensity flash will work (it uses a different component).
233
« on: October 17, 2020, 04:05:04 PM »
Hi Osika, just a quick glance at the board will not tell us much, you need a closeup view of certain MOSFETS, and a magnifying glass can help. Here is a post that shows exactly which components need to be examined. If you can read "23EG" on the MOSFETs, then they are the wrong ones! Hobby King claimed to have fixed the issue but in fact some people received faulty boards up until the very end. You won't know till you get the board in your hands, but let's hope it's a good one!
234
« on: October 16, 2020, 03:35:59 AM »
There is an option as you already know to have a "manual gearbox" where you must select forward, reverse or neutral using a switch on the transmitter, and then the throttle stick simply controls the speed within the selected. However I do not have multiple forward or reverse gears, just the one. Rad was able to create a multiple gear effect using some programming on his 9X transmitter, you might find it interesting to read about what he did which is discussed in this thread.
235
« on: October 15, 2020, 10:48:16 AM »
I have ordered a servo and elevation recoil unit to use and just tested recoil using another servo I had using the output for gun fire.
It works each time with recoil set on cannon fire which is great. (Have not tried setting to mechanical
trigger or see need to?) I assume what you mean to say is that you have left the "Trigger with Cannon" checkbox checked, so that when you active the cannon fire function, the recoil action occurs. That is the way most people will want to do it, the other options are for unusual setups. One thing though and not a big deal..upon turning power on... Servo does some fast movements then upon triggering cannon does the proper fast/slow recoil return movement. I have not adjusted end points or anything yet. Yes, I think this is not a problem. The behavior of some output can be erratic on boot depending on the position of your servo, the status of your receiver, etc... As long as it ends up in the correct position when boot is complete, and as long as it works when you trigger the function from your transmitter, then I think everything is fine.
236
« on: October 08, 2020, 12:23:09 PM »
The version 0.93.70 is what's posted on the website now, so yeah we have a copy of it. After you feel like you have a stable version on your end with your various changes, you can send me a new hex and I will post that, but at that point you do want to be sure to update the version number. Go ahead and take your time on it, it is of course better to wait and be sure you have everything added that you want, than to post a whole bunch of versions...
237
« on: October 08, 2020, 05:43:17 AM »
No, that will not work. The device you are looking at only accepts RC signals for input. RC signals are 20Hz PWM pulses from 1-2mS. The device you are looking at converts an RC signal into a simple on/off.
The General Purpose I/O ports can not output an RC signal, so your device will not recognize it. However, the General Purpose I/O ports can turn on and off. And that is all you want.
The General Purpose I/O ports however are not strong enough to power a heater or fan. That is why you still need to use a relay. See the link I provided above.
238
« on: October 07, 2020, 05:01:55 PM »
The RC switch takes an RC signal so it would have to be plugged into one of the RC outputs, which would be mapped to a channel on your transmitter and set to type "analog" in OP Config, even though you will obviously actually use a switch on your transmitter. That is one option, but depending on your setup you might not have a lot (or any) RC outputs free. The easier way is just to get a relay module that can be controlled directly from the General Purpose I/O ports. There are several mentioned on the wiki page. Note there are built-in options for controlling the smoker fan and heating element separately already. If you choose to go that route, the fan is driven from Aux output (but it only delivers 5 volts) and the heating element is driven from the smoker output (at full battery voltage, as usual). You can control the level of the element and the fan separately with options in OP Config on the Motors tab.
239
« on: October 07, 2020, 03:02:43 PM »
Hi Osika, my apologies for the slow response. I see you are not using the functions to enable/disable the mechanical recoil, so that is not the problem. Your switch setup is fine too, that is the same way that I use cannon and machine gun on a 3 position switch too.
So that's good, but I am not sure what the problem could be. The fact that it does work sometimes tells me that the TCB is not broken, and it makes me suspect a mechanical issue with the recoil unit itself. The main thing to check is the little limit switch, possibly it is loose, or maybe it is not being closed completely at the end of the cycle. Also check your soldering job to make sure there are no loose wires, the wires on those units are very thin and flimsy.
This may not help anything but for the moment it is all I can think of. I don't have a unit on hand to test right now, but again I don't think it is a firmware issue because your recoil does work occasionally.
240
« on: October 07, 2020, 01:02:09 PM »
Ok, now for OP Config. You have created a spin box where the user will enter some number. We need to get that to the TCB.
We need to create a variable to hold this value in OP Config. This will be done in the file "op_devicedata_struct.h" (under the Headers section in Qt Creator). Similar to what we did with the TCB, we need to add a variable here, you would add it like this:
... etc ...
uint8_t HotStartTimeout_Sec;
// Heclo variables
uint8_t engine_max_watt;
// Driving adjustments
boolean AccelRampEnabled_1;
... etc ...
Now we have two files, the first one will handle copying the value from the spin box to the variable, and the other way around, copying the value from the variable back to the spin box. This file is called "mainwindow_varcontrols.cpp" (under the Sources section in Qt Creator). The first function in this file is called Variables_to_Controls(). Find the Motor tab section and add something like this:
ui->spinMotorWattage->setValue(DeviceData.engine_max_watt);
Keep scrolling down that same file and you will find a second function called Controls_to_Variables(). Again find the Motors tab section and add something like this:
DeviceData.engine_max_watt = ui->spinMotorWattage->value();
Now let's go to the second file, which will handle copying the variable to the array that gets sent to the TCB when writing, as well as the other way around to copy the value from the array back to the variable (for when the TCB writes to OP Config). The first function is called VarArray_to_Variables(). Scroll down to where section 22xx ends and before 24xx begins, and add this (I am assuming you gave your variable the ID 2311 in the Excel at the beginning):
DeviceData.engine_max_watt = VarArray.value(2311).toUInt();
Keep scrolling down that same file and you will see a second function called Variables_to_VarArray(). Again find the correct section, and add this:
VarArray.insert(2311, QByteArray::number(DeviceData.engine_max_watt));
I think that should be all. Sometimes we need to add user interface handling if we need to show/hide the spin box based on other selections, but in your case I don't think that is necessary.
You will want to change the version number of OP Config as well, this is done in version.h. It needs to be updated in about 5 places in that file, including VER_MINTCB_STR
which you should set to whatever version you set your TCB firmware to.
To make sure the version number gets applied whenever I change it, in Qt Creator I do the following three steps from the Build menu:
1. Clean All
2. Run qmake
3. Rebuild all
Ok, now you can test everything out! It's possible I have forgotten a step somewhere so if you have issues let me know, but I hope this information gets you further along anyway.
Pages: 1 ... 13 14 15 [16] 17 18 19 ... 78
|
Show Posts