I got asked my local theatre if I could make a couple of props for their stage shows.
Not going to be any pennies in it for me, but... its something to do.
Rather than the usual UNO/Mega hash with a PSU and some bits bolted on.... what do you guys think is a better way forward for a more rigid install?
They want some RGB leds and multiple sound effects. Maybe a small motor on a prop plane.
I was thinking either Mega (for flexibility) or a Teensy 4.1.
It's the sound that I think is the issue. I have used Teensy 4.1 (and the now dead 3.2) sound modules and they are great, but I kept on getting long term failures.
The main advantages of those was the ability to overlay the sounds.
The sound is getting output on a 1/4" jack to their sound system.
Is there anything already out there that covers this? I don't want to go Raspberry PI, as I am just not good enough at the coding.
Maybe a Din rail mounted something. It's the sound I am stumped on.
DMX would be handy too!
If you are not an experienced programmer, I wouldn't recommend to use a new boards such as Giga for which there are not yet sufficient resources on the network and there is no community that could help you.
Well I am totally happy to stick with a Mega or a Teensy 4.1
I am reasonably decent at coding.... I just don't do Raspberry Pi's.
Been doing this tinkering for 45 years.
Its the sound that looks to be the issue.
I need to overlay sound. Sound it's either Teensy 4.1 sound board (but like I said, I have had quite a few long term failures on those) or multiple single players.
The is the WavTrigger range of boards. I seem to remember they were pricey, but did work.
To me, this sounds more like a question about physical implementation than choice of controller boards etc. As argued above, if you're happy with a Teensy (or whatever), just keep using that. Focus on the physical build of the system; buy/build a housing that everything screws/fits into nicely so that it doesn't jostle and move around. Steer clear from dupont connectors etc. as they're a liability in the sort of environment you're going to work with. Use proper clamped, screwed or soldered connections. For a really slick outcome you could even consider making (or having made) an interface/backbone PCB that the modules of your choice can plug into.
Have you considered using a dedicated audio controller or sound card for the sound effects? They often have better audio quality and reliability than built-in solutions. Do you have any experience with these?
The sound I think would be best served with a Tsunami Super WAV Trigger.
Used them before and seem pretty decent.
My only issue is the SD card. Would have preferred some onboard Flash storage or something, but you can't have everything.
Ideally, I would have the ability to dial in remotely to check things etc, but I think that might be a step too far. Not sure.
I already have my own design opto-isolated DMX PCB here that I used for various projects.
I am thinking a Teensy 4.1, the DMX PCB and the above sound card would give me a lot of scope.
But... no WiFi ability there. An ESP32 would make more sense because of the WiFi and Bluetooth, but I am not friends with ESP32's. Also, nowhere near the pins or power of a Teensy.
I used to love the 3.2 Teensy. 5v tolerant etc. I made a PCB that had literally all the functions I could ever need a few years back, and then the chip got binned.
No laughing at the ropey soldering... didn't have a heated SMD plate back then
Are you kidding? That looks perfectly fine for a hand job (no pun...ah well, take it like whatever!)
I'm generally not a big fan of "let's throw some microcontrollers together", but when it comes to cheap & relatively easy access to WiFi, BLE etc., ESP is hard to beat. In your case, you could always use an ESP as a peripheral to your main core. That would broaden your options considerably.
9-40v Supply
5v 5A Bus
3.3v 1A Bus
Onboard JQ8400 mp3 module with flash (they are pretty good)
Onboard stereo amp with pre-amp out
Onboard HC06 Bluetooth
Onboard RTC and backup battery
16x digital Inputs
16x digital Outputs (optically isolated)
4x PWM out
8x Analogue in
IR out onboard and remote
IR Receiver onboard and remote
Extra EEPROM memory chips x2
4x Onboard DIP switches for any use
Onboard MicroSD card
Onboard connectors for 128x32 and 128x64 OLEDs.
Can't remember what else. That picture has some of the modules unplugged.
I made a second version that also had optically isolated DMX onboard.
Same project, slight deviation.. Going to put a Teensy 4.1 + ethernet board in a DIn rail enclosure. That sorts the processor.
WAV Trigger board for the sound effects.
Ethernet. Going to have a play with this, as I don't usually use it.
If I configure access to the Arduino Cloud (I'll start with a basic LED test on the free version), then all will be fine on my home WiFi network.
But, if I then place this 'receiver' in place at the threatre, is that going to need a static IP address to be able to communicate outside the building? I am guessing yes.
I just like the idea of being able to 'dial in' to update the software and alter settings (yes, I know I need a paid subscription for OTA).
Also, is the Arduino cloud the best one? From the tutorials it looks a bit clunky... wondered if there was anything that allowed slightly better dashboards
It depends, but I'd always recommend using a static IP address if it's feasible/permissible on the local network. It'll be easier/more dependable that way in case you need NAT so that outside devices (e.g. servers) can reach your device. However, I suspect that Arduino Cloud does not necessarily require NAT. There's also the general inconvenience of 'losing' your device because it gets assigned a different IP address, which would of course always occur right before a show (cf. Murphy's Law).
That confirms a firm 'yes' on the need for a static IP.
Can't comment on that; I never use it. I've never seen the need to go beyond a dynamic web page on an ESP and/or MySQL connection to a database server.
There's no way to negotiate with the local systems operator? Admittedly, they may be very hesitant especially if you explain you need it to gain access to the device from the outside world.
With 'dynamic' I refer to the content of the page itself, which can be generated by the ESP based on variables stored in its own memory (for instance).
In order to access a web page, it doesn't matter whether the IP on the host (or the client for that matter) is static or dynamic, as long as it's known at the moment that the request is made (i.e. the page is being viewed). Of course this might present problems if a DHCP lease expires and a new address is assigned (which often doesn't happen upon expiry, btw - but you can't be sure).
Neither the web page remark, nor the MySQL stuff helps in any way with the remote updates btw. For that to work, you'll have to make an opening in the firewall by telling the router to direct requests on a certain port towards a specific address on the local net. Network administrators will in generally be unwilling to do this, since every open port constitutes a security liability.
For sake of complexity mostly at the organizational level, you're probably better off just walking into the theater when you want/need to update the device and do it locally. People know you and nobody will object if you maintain your own stage equipment, I expect.
Wow, the scope of what I thought you wanted really grew!
For little things, I was thinking a stand-alone 328P with a sound board of some kind. And I wonder if a Pi Zero could do for that. You'd want to make a board, no doubt, but the cost could be low to where loss would not matter much.
I've started to look into low end Pi's for possible game units since they do video and sound. Somehow make a generalized sub-system for other devices to use.
