@JakeSoft, is there a reason why you used a 3.3V Arduino instead a 5V version, since the WT588D is a 5V device? I am talking about the schematic in post #6. As far as I've learned by now, it is not recommended to mix 3.3V with 5V shields and vice versa... Am I missing something?This is what I mean: http://jeelabs.org/2010/12/16/voltage-3-3-vs-5/
Howdy, nother FNG question:The WT588D and -WT588DU all seem to come with pre soldered pins.The WT588D obviously needs the little green cpu clamp style programming box.Though I see there is a adapter cable module for the WT588DSo I figure the WT588DU does not need to be in the board because of the USB. But I see that all the modules come with the pins pre soldered in place, so what do you do? De solder the pins so you can then attach the wires? Or attach the wires tothe pins?Also should I get a 16M or 32M one. I want to order but If I have one doubt its a no go.
Hmm. Interesting read. I haven't had any problems so far, so I assume that the manufacturer of the sound board has designed the modules to handle VDD of 5V and 3.3V on VCC. Read back in this thread a bit and see the discussion BillPealer and I had about this exact topic. The summary is that if you are using the WT588D-u (with built-in USB) then you don't need a 3.3V supply in your project. If you use the 16-pin version then you do. I used the 16-pin version. Several people have built spin-off designs with 5V Minis, Nanos, etc. Feel free to use whatever you are conformable with or have on hand.
Because my software is magic! ;-)
Have you tried to eliminate the VCC on your WT and just send 5V direct to the WT's VDD via your 5v regulator, and skip a solder point, Jake?
Dude, what do you use the BusyPin for? it is not being called to do anything in the WTSendCommand.
I use it for a few things in my code. The most important is sound calibration. I never show it in my videos, but I have a routine that plays each sound and measures how long it took to play and then stores off that timing data. Notice how my blade ramp-up and ramp-down effects are closely synchronized with the power-up and power-down sounds? Notice how my clash sounds are never interrupted by a swing sound? I know how long each sound takes to play. Those values are not hard-coded, they are dynamically captured. This allows me to change sounds without having to recompile my code.
i thought you used it to get the 3axis to ground. but i think any pin set to input and LOW in Arduino is ground.
Did you quote the correct post? I was talking about the WT588D sound module but now you seem to be talking about the ADXL335 accelerometer. You are correct however that any pin set LOW then effectively becomes a ground. I did exploit that when I soldered the ADXL335 GND pin to an arduino I/O pin. I just set the I/O pin to ground and it works great.
I guess it would be quite a challenge to "motion detect" a blade lock-up...even when the blades collide, the opponents try to force they way past the guard of the other and they struggle, i.e. there is still constant motion. That is why usually a 2nd switch is used to trigger a lock-up (I use the same as the one used to trigger blaster block and used to step through the different sound fonts).
How about making a loop out of a length of force sensitive resistor strip to fit inside the rim of the blade seat/emitter neck? https://www.sparkfun.com/products/9674ok, so I'm only guessing at this point which means it's probably not quite as simple as I make out but could the coding go something like: If resistance drops below x threshold for y amount of time, you have a "trigger lockup sound" scenario?While I'm on that train of thought, could the resistance threshold setting could be made adjustable as well to give different sensitivity levels?
I'm not sure a ring of it would even be necessary. In theory, a lock up would be pressure from the front of the blade, meaning that the base of the blade would be pushing forward. So, if one were to countersink one of these on the front of the blade chassis, then I think one could detect a lockup based on duration of pressure. Theoretically, of course.