Back

Comments 20

  • Giant Animatronics Lego Minfig Operation Game 4 months ago

    your 3 touch sensos are configured as OUTPUTS in setup() rather than INPUTS. Seems wrong. Is that by design?
    Also, I in my build my inputs keep getting triggered randomly - I think my grabbers and their wire are acting as an antenna and finding random signals from the air. did you encounter this? if so, how did you deal with it?

  • Monster in a Box about 2 years ago

    FYI, I just update the code on this page. you will find it to be much cleaner than previous versions.

  • Monster in a Box about 2 years ago

    First, unless you grabbed my code from GitHub, you should redownload the code from this page: I JUST updated this page with the latest code.

    Put all 3 files into a folder named Monster_In_A_Box in your Arduino projects folder. Then double click Monster_In_A_Box.ino to open it with the Arduino IDE. When the IDE opens you should have 3 tabs "Monster_In_A_Box", "MonsterSounds.h" and "MonsterSounds".

    At this point, you should be able to compile and upload it to your Arduino.

    Remember: you need a Wave Shield for the sounds to work

  • Monster in a Box about 2 years ago

    Guys, You may have figured this out already but I found that Action_2 was causing false triggers and messing with the PIR on my box. If you are not going to use a switch/button to trigger the wake cycle and just use the PIR I would just remove Action_2 from the code completely.

    Even better, grab my lastest release from GitHub (v4.0). The code is more clearly written and the PIR works better. Pay attention to my note about the relays though - you have to change how you wire the devices to them.

  • Monster in a Box about 2 years ago

    Sorry for the slow response. Yes, I connected all of those.

    Also, if you are still working on this grab the V4.0 of my code from GitHub it is much better/cleaner and easier to understand IMHO

  • Monster in a Box about 2 years ago

    It only takes a few. Plus the Wave Shield uses almost half of the pins on the Arduino which means they are not available to drive external devices. ;/ I am actually working on another design that will use a different sound device and will be able to use MP3s rather than waves.

  • Monster in a Box about 2 years ago

    I recently did a complete rewrite of the code for this project. See the summary of the changes above. The new code has a bit less 'timer madness' to it. I completely removed the use of "Frames" and the delay() at the end of the loop() method. This significantly reduced the number of 'port busy' errors i get when trying to connect with the Arduino IDE. I labeled this at V4.0 on github.

  • Monster in a Box over 3 years ago

    An ATX PC power supply has multiple voltage outputs. If yours is following the standards (most do) the Blacks wires are Ground, the Red Wires are 5volts and the Yellow wires are 12 volts. You should have several 4 pin Molex connectors (like this https://tinyurl.com/ydggtwsl) You want to connect your Motor to the Yellow and a Black on one of these connects - and dont forget to include the relay in the circuit so the arduino can activate it.

    Also, you may not be aware that you need to make sure that your ATX Power supply is ON.
    Just look for the green wire in the cable from the PSU and follow it to the 20 or 24pin ATX plug.
    Then use a piece of wire to jump this Green wire to any of the Blacks on the same connector.
    Then just tape it in place now the power supply will always be ON when plugged in (remember that and be careful) I like to tape off all of the connectors that I am not using just to be extra safe.

    Good Luck!

  • Monster in a Box over 3 years ago

    Nicely done. Thanks for sharing!

  • Monster in a Box almost 4 years ago

    Did you get it to work ?

  • Monster in a Box almost 4 years ago

    How is your build coming along?

  • Monster in a Box almost 4 years ago

    I am using the Arduino IDE. You are correct to change the ".c" files to ".ino" (not sure why this site is adding the .C extension) The '.h' file should be a '.h' file, don't change this one to '.ino'
    your filenames should be: "Monster_In_A_Box_V03.ino", "MonsterSounds.h" and "MonsterSounds.ino" they should be in a folder named "Monster_In_A_Box_V03"

    I was using 1.6.11. so to be sure I just updated to 1.8.5 and recompiled: I got no errors, just the memory warning. I am, however, working on Windows 10, not Ubuntu. I wonder if that might be contributing to your problem?

    I agree, dont build any hardware until you get the micro controller working, even then I originally had a breadboard on my desk that used buttons and LEDs to emulate the IO of my prop. that way you can test and adjust everything from the comfort of your desk rather than stooping over a wooden crate :)

  • Monster in a Box almost 4 years ago

    It looks like you are mostly having trouble with the sounds. did you install the latest library version for the wave shield library? You need this for MonsterSounds.ino to compile.

    The memory error is 'normal' the wave shield eats up a lot of memory.

    fyi, I am planning to upgrade my setup this year and replace the wave shield with a DFPlay mini mp3 player. These tiny mp3 modules are very powerful and will completely free the arduino from sound processing. I will probably do this this summer.

  • Monster in a Box almost 4 years ago

    all of the files are attached. have you downloaded the wave shields libraries? you need to get these.

  • Monster in a Box almost 4 years ago

    You should only need 1 arduino and a wave shield for this. that is all.

  • Monster in a Box over 4 years ago

    I have not worked with the MP3 shield so i cannot say for sure, but I did try my best to isolate all of the sound management logic in the MonsterSounds code files. You SHOULD be able to replace the logic in this file with code that works with the MP3 shield. You should not have to modify the main Monster_In_A_Box file

  • Monster in a Box over 4 years ago

    Hmmm you may have wired something incorrectly -

    First, I would verify that your PAUSE button is properly setup - I think the behavior you are describing could occur if the you are inadvertently in pause mode

    it is also very possibly the input from the sensor is not being detected - check this connection

    I would suggest is that you add a Manual Trigger (momentary on pin A3) and the Debug (toggle on pin A5) switch. These are NOT in the diagram but the code supports them.

    The Debug "switch" could just be a simple wire jumper. This reduces the delay between "awake" events to zero so that you can trigger it as frequently as you want while problem solving.

    The Manual Trigger (called ACTION_2_BUTTON) in the code will manually trigger the "awake" logic. You can use this to trigger the "awake" logic without the motion sensor.

    Also, if you are not already doing so, troubleshoot with your board connected to a pc that is running the serial monitor. You will be able to see the output of the print statements in the code which should help you figure out what part of the code is running when. If needed add some additional print statements to figure out where things are going wrong

  • Monster in a Box over 4 years ago

    Hmmmm I thought I included them, but I could not find them here.
    So I have added them (again?) you will find them in a zip archive in the "Custom parts and enclosures" section

  • Monster in a Box over 4 years ago

    Cool! Please post some photos and/or video when you are done!

  • Monster in a Box over 4 years ago

    Did you download all 3 files? (note the tabs on the left of the file browser above)

Add projectSign up / Login