Show Posts

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] 2 3 4 ... 38
Open Panzer Help / Re: Airsoft switch position detection issue solved
« on: October 18, 2018, 04:42:53 PM »
I might not remember exactly all the details of the original problem or of your setup. When the "Trigger with Cannon" option is checked it means that the airsoft action will automatically occur when you trigger the Cannon Fire function. So yes, in that sense a trigger is still required, but the Cannon Fire function basically does a half-dozen things with a single function (sound, light, servo recoil, airsoft, IR, track recoil, etc, etc...). If you un-check that option, you can still trigger the airsoft but you will have to use the Fire Airsoft / Mechanical Recoil Unit function and it will only run the airsoft action but none of the other components of cannon fire.

I guess it is a little confusing, and almost everyone will want to leave that option checked, but by unchecking it you have the ability to create your own cannon fire effect by using half a dozen functions instead of the single Cannon Fire function.

Anyway, that explains that option. I'm assuming you are using the Cannon Fire function rather than a bunch of individual functions. And that ironically, when you uncheck the option to include airsoft with Cannon Fire, meaning it should no longer be active at all, you are able to re-activate it with the airsoft enable/disable functions. But when you leave the option checked, it tends to "overwrite" the initial setting of your enable/disable switch such that it always starts up enabled.

Do I have that correct? If so it might be something I can correct, it sounds like just an issue with the order in which settings are applied at startup.

For now let's ignore the 1 of 6 exceptional case because that is just going to muddy the waters. As for the cannon sound, what sound cards are you using? The Taigen sound card will not play the cannon sound unless the engine is running, that is a limitation of the Taigen and nothing to do with the TCB. All other sound cards should play the cannon sound at any time, engine running or not.

Open Panzer Help / Re: New to OP TCB and need some troubleshooting
« on: October 18, 2018, 04:13:29 PM »
No, you do not need any Y-cable. I think the only mention of any Y-cable in the Wiki is in the section describing the use of two serial controllers at once, but since you are using standard hobby ESCs that does not apply to you.

The ESCs plug into the RC outputs and you have it correct, left track goes to output 1 and right track goes to output 2.

Your description of the behavior you're seeing is not entirely clear. It almost sounds like you might have the wrong selection under the Vehicle Type option on the Motors tab. Double check and make sure you select "Tank (Dual drive motors)"

Hi Baeng, I recommend anybody who is not already experienced with reflow soldering to not attempt to assemble these boards. There is too much that can go wrong and I can't support hardware that others built.

Yes that is exactly correct. There is a little triangle cut-out on the bottom pad of the chip, on my chips there is also a little cross on the top of the chip at this same corner, these align with the dot on the board on the lower-right side as you mention.

The main thing is not to get too much paste on that footprint before you reflow. You want good coverage, but the layer of paste should be very thin.

Open Panzer Help / Re: Heng Long IR upper Hull to TCB
« on: October 05, 2018, 02:54:51 PM »
Paul, see the Wiki page on mechanical recoil units such as those used in IR turrets, there are photos and even an instructional video on how to wire these so they are compatible with the TCB. The standard Heng Long/Asiatam/Taigen design does use two micro switches, but only one is needed for the TCB as is explained in the video. If you have some kind of different unit than is show there then I don't know about it, perhaps you can post some more information.

As for Motor B it depends on what you are trying to use it for. If you are trying to use it for barrel elevation, just select "Built in Driver (Motor B)" for the Barrel Elevation motor selection on the Motors tab of OP Config. Then you can control it with whatever stick on your radio is assigned to barrel elevation.

If you want to use it independently for some other purpose, then you need to assign something else to the barrel elevation motor, and then several Motor B functions will appear in the Function list, to which you can assign aux channel triggers or any other suitable trigger.

Show and Tell / Re: "Painbot" Battle Unit - combined IR apple
« on: October 05, 2018, 02:27:35 PM »
Interesting as always. Looks like you have created the slots for 4 IR receivers, though in your photo only one is installed. I suppose a fully-equipped unit with 4 receivers and 4 notification LEDs would end up with quite a few pins coming out the bottom, >20? Could be kind of unwieldy.

You might be able to design a small PCB to slot into the case where you could solder all the components and tie the receivers and hit LEDs together, thus reducing the pin count considerably...

Good job on the Scout, and I'm sure it's rewarding to have something work that you assembled with your own hands.

The serial labels on the Scout and sound card are relative to the TCB - so TCB TX-O (transmit out) will always go to the Scout/Sound Card RX-I (receive in) for example. I suppose you're right, the labels may look a bit odd from the sound card to the Scout, but the Sound Card is designed so you can connect the TCB to either one of the connectors, it doesn't matter which, so both labels on the Sound Card are relative to the TCB. But yes you are correct, the signal is simply passed straight through from one connector to the next.

From your description it appears your sound card is functioning more or less correctly, but you probably have an issue with the amplifier chip. Typically you will see the orange LED on the Teensy lit up when it is playing a sound file, that is another thing you can check.

I don't think you can change the firmware on the USBASP itself, probably you are experiencing a Windows driver issue. Try using the Zadig libusb driver installer, see this page for more. Anyway this is what I have always used.

There is no point trying to flash firmware to your Scout until you have the bootloader installed, so the fact you got errors in OP Config is to be expected.

I don't think you will see any LEDs or activity on the Scout before the bootloader is installed. After the bootloader, you will see the red LED blink slowly. Also - you should apply battery power to the Scout board while trying to flash the bootloader, the USB is not always enough to get the job done.

Open Panzer Help / Re: IR Doesnt seem to be working
« on: October 02, 2018, 02:20:14 PM »
Always tricky troubleshooting things when there are multiple problems going on at once, but you got it figured out. Glad to know the TCB was not the cause.

On a side note, On this latest version of OP config, I cannot seem to just connect to my tank with the connect button. I now have to go to 'firmware' and snoop, then hit connect. Is this a bug?
Yes, this is a known issue for some people. For others it is intermittent, for others it never happens. It is listed in the Troubleshooting section of the Wiki and elsewhere. It's definitely an inconvenience and I apologize for those who must deal with it. I've tackled it several times and so far have not come up with a consistent solution.

I do have a few questions/suggestions but it would probably be better if I did a seperate post for those?
Yeah a separate thread would be a good idea so this one remains on the topic of IR.

Open Panzer Help / Re: IR Doesnt seem to be working
« on: October 01, 2018, 12:41:08 PM »
This sounds like something very simple that was overlooked.

The most obvious thing this sounds like is that you are testing with USB power alone, but the IR functions require a battery to be connected. Something I have done many times... but an easy fix if so.

Another simple mistake is that you could have made the changes in OP Config (setting the IR to Taigen), but forgot to write those changes to the TCB.

Also ensure the Fight<->Repair switch is set to "Fight."

I would perform the test with the TCB connected to the computer in Snoop mode. This will let you confirm that your fire trigger is actually working.

To see if an IR signal is being transmitted it can help to look at the IR LED using the screen on a digital camera. The human eye can't see IR but a camera lens will see it as light. Using the voltmeter isn't going to help because the signal is so short it will not register on your meter. You would need an oscilloscope to capture it.

You can also use the camera to check if the Taigen board is sending an IR signal as well. On the receiving end once again it will help to connect the TCB to OP Config in Snoop mode to see what messages it may give you. In Snoop confirm also at the beginning that your settings have been correctly saved by the TCB.

Of course be sure the polarity of the IR LED is correct, as it sounds like you have. If you have a second LED, test with that one.

See if any of this helps, and report back if not.

Yeah, the amplifier IC on that board is about the only component susceptible to shorting, but it would not be hard to do.

  • Please use the attach image functionality of the forum to post pictures, rather than putting them in Word documents
  • It looks like you are trying to play the sound using the Test feature with a jumper on RC input 1, is that correct?
  • When you are viewing debug information from the sound card (or any other OP device), do not use the Connect button - instead use Snoop.
  • Make sure your sound file is encoded as 16 bit 44,100 Hz. Open it in Audacity or some other audio program to confirm or convert it if need be.

Possibly. Read through the Wiki for the sound card to be sure you have not missed anything. Note the procedure for using it in RC mode is different then when controlled by serial via the TCB. In RC mode you must place all your settings in an INI file on the memory card, and there is a separate utility provided to help create this file. Again, there is documentation in the Wiki.

The behavior you describe with the LED sounds exactly like what is expected. I'm not sure what is wrong or what you need help with?

Show and Tell / Re: IR battle without apple
« on: September 28, 2018, 09:11:29 PM »
Hi Kees, that's a very ambitious project! You clearly are comfortable with electronics, hacking and modding, and I always like to hear about unique projects like yours. You basically built your own ESC from scratch so that is impressive.

Pages: [1] 2 3 4 ... 38