Whitestar is indeed more or less like DataEast without separate sound board. One could in fact use the adapter pinsound is selling, it should work with LOTR, it will be handled like DE. But I haven't designed a PCB for that, its just address decoding pulled from the CPU directly. Any volunteers?
Performance is better with Pi3. Faster bootup time, can hold all sound in main memory, avoid some (rare) delays on first load of a sample.
Quoted from BENETNATH:
- Booting time wise, what's the best setup and Linux distrib ? What is the current timing to have sound on cold boot ?
The actual image has a minimal arch linux bundled with it. Start time is (on Pi3) <20 sec.
Quoted from BENETNATH:
- did you explain somewhere the relay for a shaker ? I would like to have my tommy linked not only to propellers, but also to some sounds.
- Would it be possible to add 3 channels for additional toy triggering, like the shaker? That we could call based on sound ? A chimebox in the tommy would be easy that way.
Thanks
The wiring for the shaker is: the TX-Pin is controlling the shaker motor (either active high or low, configurable). You need to add a small driver circuit or relay in between, like one of these amazon.com link » They are completely decoupled by an opto and can directly driven from the Pi.
The general expansion idea to have more than just a shaker is indeed the UART interface that is exposed on the adapter board. I will simply output the sample ID when a sound is played, so that a secondary board (or many of these) can listen and control additional toys. But this is not ready yet / no tested, just as idea.
Of course one could also simply add control of more GPIO pins instead of just TX for controlling a shaker.
Thx Steve