so is that it? the ADXL, the WT sound player, all gone? now its this new SD card based thing and the other accelerometer? MPU thing? and a slew of .h files?
wow. so this new sauce is Jake/Proto/Nesk 's baby!?
is these even a clash sensor now? its all just code?
billpealer:
so is that it? the ADXL, the WT sound player, all gone? now its this new SD card based thing and the other accelerometer? MPU thing? and a slew of .h files?
Oh, heck no! It's not "gone", don't be silly. This is just one more option. I'm planning to have my next build feature one of Canobi's sheet cake boards with the WT for sound. There are pros and conns to each design. I'm all about exploring, experimenting, and learning. One contributing factor to even starting my Mk. II project in the first place was because I was a little bored with seeing the same 3 sound boards in 80% of the DIY sabers I read about. I wanted something different, more open, and more flexible, so here we are.
billpealer:
wow. so this new sauce is Jake/Proto/Nesk 's baby!?
Thanks! And yes, this saber is the result of collaboration between the 3 of us.
billpealer:
is these even a clash sensor now? its all just code?
Yeah. Neskweek was able to figure out how to detect clashes with the MPU alone, so no clash sensor needed. It's something I still want to explore with the ADXLs, but I am only one man who does this for a hobby.
billpealer:
this is so transcended home brewing.
Well, sort of, but you can still build a board yourself that does exactly the same thing by buying the component parts. Like me, Protonerd has made no attempt to hide what his board is made out of. Everything is a tradeoff. In this case, time and effort vs. ease of use and money. It's the same for Canobi's boards or really just about anything that you buy but could build yourself.
Protonerd:
Also worth to check out (sorry for off topic): E11 arduino blaster
I'm working on blaster fx
I just did a test etch of it yesterday (measures just 25 x 22 mm). I used toner trasnfer, admittedly it came out a bit warped on one side and needs a little clean up so any subsequent boards will be made the using photo etch method (if it works out) but it'll suffice for a proto:
so, not only am i a complete noob with arduino, even after reading this thread.... i am still not quite understanding a few things so here goes with the questions.
i have built a saber staff with RGB leds that i currently use a 100mAh buck puck with. in each end of the saber i have a 7.4v 18650 lion battery, 1000mAh buck puck and cree xp-e2 red green royal blue LED.
what i would like is the ability for the color mixing like you show but i dont need/want the sound.
so first, would i need to use the buck puck at all with the mosfet setup? second, how do i wire the mosfet in line with the led. as i said ive never used/heard of such a thing.
third, i was planning on using the adafruit pro trinket board in the 5v version. will this complicate thingsa at all?
i enjoy building my own sabers and would love to make my own sound boards eventually, but for now i just want to be able to perfect the color changing aspects.
Canobi:
To make routing on a one sided PCB a little more straightforward I may have to shuffle the pin list a bit.
As a small precaution I'm going to stick to the power rail setup as it is so the WT's GND reference won't need accounting for in code as it could be a pitfall for the unwary adventurer.
Out of interst, is the accent LED you're term for the FoC LED? I couldn't see a reference to it in the diagram and only count 3 fets.
[Hello Jake.
In your project, if I will be using a ledstring, could report what would be necessary to change?/quote]
I might of had a breakthrough in clash detection with only the ADXL335 (no clash sensor). Still in the prototype phase, but it shows promise. Take a look and let me know what you folks think.
Lately, I've been pondering on how random selection was achived in code as it would be useful for clash file playback. So I had a look round just now and found this little gem written by Grumpy-Mike.
Admittedly it is for an SD card but I daresay could it be modified to work with audio modules too:
char toPlay[11]; // string array for file to play 00.WAV to 99999.WAV
// then pass this function a random in the range of the files you have
makeName(randNumber,0); // generate file name in global array toPlay
void makeName(int number, int depth){ // generates a file name 0.WAV to 9999.WAV suppressing leading zeros
if(number > 9) {
makeName(number / 10, ++depth); // recursion
depth--;
number = number % 10; // only have to deal with the next significant digit of the number
}
toPlay[indexToWrite] = (number & 0xf) | 0x30;
indexToWrite++;
if(depth > 0) return; // return if we have more levels of recursion to go
else { // finish off the string with the wave extesion
toPlay[indexToWrite] = '.';
toPlay[1+indexToWrite] = 'W';
toPlay[2+indexToWrite] = 'A';
toPlay[3+indexToWrite] = 'V';
toPlay[4+indexToWrite] = '\0'; // terminator
indexToWrite = 0; // reset pointer for next time we enter
}
}
// Then play the file name
musicPlayer.startPlayingFile(toPlay);
Canobi:
Lately, I've been pondering on how random selection was achived in code as it would be useful for clash file playback. So I had a look round just now and found this little gem written by Grumpy-Mike.
Admittedly it is for an SD card but I daresay could it be modified to work with audio modules too:
char toPlay[11]; // string array for file to play 00.WAV to 99999.WAV
// then pass this function a random in the range of the files you have
makeName(randNumber,0); // generate file name in global array toPlay
void makeName(int number, int depth){ // generates a file name 0.WAV to 9999.WAV suppressing leading zeros
if(number > 9) {
makeName(number / 10, ++depth); // recursion
depth--;
number = number % 10; // only have to deal with the next significant digit of the number
}
toPlay[indexToWrite] = (number & 0xf) | 0x30;
indexToWrite++;
if(depth > 0) return; // return if we have more levels of recursion to go
else { // finish off the string with the wave extesion
toPlay[indexToWrite] = '.';
toPlay[1+indexToWrite] = 'W';
toPlay[2+indexToWrite] = 'A';
toPlay[3+indexToWrite] = 'V';
toPlay[4+indexToWrite] = '\0'; // terminator
indexToWrite = 0; // reset pointer for next time we enter
}
}
// Then play the file name
musicPlayer.startPlayingFile(toPlay);
Here's a link to the thread:
http://forum.arduino.cc/index.php?topic=424522.0
Interesting, and I encourage any learning experience, but I'm wondering if you were aware this has already been solved in USaber for the WT588D and DFPlayer (DIYino) sound modules. The sound player API I defined already supports random playback of any sound type, clashes included.
JakeSoft:
Interesting, and I encourage any learning experience, but I'm wondering if you were aware this has already been solved in USaber for the WT588D and DFPlayer (DIYino) sound modules. The sound player API I defined already supports random playback of any sound type, clashes included.
That's just freaky, a new large drive model at work use similar wire/board to board connectors and I've been contemplating designing a similar system all this week after coming across them:
I've already found a source for these and was just working out my pin count when I thought I'd drop in to see how the thread was doing and saw the link you posted.
In much the same manner, I figured I could put all SMD on one board with the other reserved for anything that requires hand soldering.
I checked these guys out when doing my original research. Pretty good for space saving and overall it's a good system from what I can tell. As you said, it gets pricey though. I disregarded this option when the price of the DIY board started to approach the price of a commercial sound board.
The WT588D-U 32 and other similar modules must be picky. As per Jakes posts back on Sugarbomb's thread.
YOU HAVE TO MAKE A NEW PROJECT in the WT software and set it to 1 line mode. Do not save a project in Key mode,. and then save it again in 1 line mode. It for whatever reason does not work on some modules.
my first WT module that i used AND tested in Keymode, and then saved it in 1 line mode worked just fine,. no new projects required.
But my latest units,. ALL had this issue, and it snagged me for a good hour until i remembered.
billpealer:
The WT588D-U 32 and other similar modules must be picky. As per Jakes posts back on Sugarbomb's thread.
YOU HAVE TO MAKE A NEW PROJECT in the WT software and set it to 1 line mode. Do not save a project in Key mode,. and then save it again in 1 line mode. It for whatever reason does not work on some modules.
my first WT module that i used AND tested in Keymode, and then saved it in 1 line mode worked just fine,. no new projects required.
But my latest units,. ALL had this issue, and it snagged me for a good hour until i remembered.
I finally made it through all 72 pages of this thread. Wow, thanks so much to all the contributors. I've been going down the path of building some custom sabers for my daughter and I. I've been doing some hacking of toy hasbro boards with rebel LEDs and buckpucks but we want more.
Building arduino based sabers is right up my alley and I'll have some boards to play with soon. I just have to decide between 3.3v and 5v. I'll probably get some of each given the cost of the Chinese units.
BTW, I'm a software developer and can't wait to check out the code and get it working on a prototype. If there's room for contribution it'll probably happen.
My first question... Has anyone had any luck with the SSOP24 / MP3-flash-16p? Quotes below to jog your memory.
I took a look at the manual and the serial commands look pretty robust (after painfully running the command table through Google to translate from Chinese to English, of course).
I attached my translated serial commands. Not to get us too far off track, but I may pick one of these up for experimenting. It could be one more sound module to add to the USaber library. (I'm working on adding sound support, I swear!)
splinter182:
That is true, and with limited space its hard to make things easily removable!
I've found the site of the ebay vendor of the MP3-Flash-16p module, cheaper than ebay and free shipping.
RubberToe:
Building arduino based sabers is right up my alley and I'll have some boards to play with soon. I just have to decide between 3.3v and 5v. I'll probably get some of each given the cost of the Chinese units.
BTW, I'm a software developer and can't wait to check out the code and get it working on a prototype. If there's room for contribution it'll probably happen.
My first question... Has anyone had any luck with the SSOP24 / MP3-flash-16p? Quotes below to jog your memory.
Cheers!
Welcome!
Yeah, I did get the SSOP24 sound module working on my breadboard. I never tried it in an actual saber, though. There is Universal Saber Library support for it. In theory it should work with DIYinoSoundPlayer, but I also added a DFPlayerSoundPlayer class specifically for the SSOP24.