Trigger/file kills Wav-trigger

Hi!
We are a non-profit model railway club which have been using Wav-trigger since 5 years and it works very well. We have 3 of them, working in different areas at the moment.

We have an issue that we do not understand why it occurs and when we solve it, we do not know what the root cause was.

So i try to give some background:

We activate different sounds with the Wav-trigger internal ground-triggering functionality. Some triggers are connected to physical buttons while others are connected to other micro processors however physically isolated with relay or opto coupler. (So the other micro processer activates a relay or OC and that creates a closure at the Wav-Trigger end.

We use external amps and power through barrell with 9 or 12 v. Different power sources for amp vs. the WT.

This setup works fine but occasionally we have hade issues with distrubing sounds. I do not think the issue is related to trigger functionality.

All mixdowns are made in Auda City. SD card are FAT 32. San Disk 8-16 GB.

We run the player max. 8 hours per day during 36 days. We shut of power every day.

First issue
For example we have one wav-file that is a mixdown from AudaCity with multiple tracks. That is how most of our sounds are. The project file was correct according to requirements. What happened then was that everything worked from the beginning. Within a undefined period of time the sound track did play but some individual tracks in the mix down sounded like gibberish/deformed. It started suddenly.

I see that even tough the mix down is 1411 kbit/s (44.1 kHz), stereo and 16 bit individual tracks in the mix down has a rate of 48 or 96 kHz etcetera.

Could that be the root cause?

We solved this by loading the wav-file onto the SD-card again. It will work until further…

Issue 2
A similiar issue is this:
We have another Wav-trigger. Same setup as described above.

One trigger sometimes kills the board. Of course a ground issue then creates a disturbing sound in the speakers. But why does it kill the board?

I did today the same as above. I replaced the mix down on the SD card with the one I have in my computer. Now it works. It is almost as the file gets corrupted.

This mixdown only has 1 track and it is 44.1. This player has also multiple tracks, but they never creates issues. And in those mix downs all tracks are 44.1!. Strange isn’t it?

Project files
Here are a video showing Issue 2, some pictures of the version of board.
(When you hear the chicken sound, that is the track triggered that shuts down the board) https://www.dropbox.com/scl/fo/ma1d0jxyjuephk4sehegy/AJp7oR3saeve8vJ4OofRY3c?rlkey=qbqs033bl9x00hhdkd8gvvygg&dl=0

What to do?

I have read lots of topics here, and user guides and other communitys but I have not found anyone with those particular issues.

I look forward to your ideas.
If needed I can send project files and mix downs.

Best Regards Johan from Sweden

Wow - a lot to unpack here. Some questions:

You imply that you’ve had three WAV Triggers running for 5 years. Have you always had these problems, or did they start recently?

Have you tried using a new microSD card? Consumer grade cards do go bad. When you replace files on a card, they likely end up on different sectors which can start out good but then fail when the card starts having issues. Best to swap out with a whole new card.

It’s important to try and determine whether the problems follow the microSD card or are specific to the WAV Trigger itself. The vast majority of issues can be traced to the microSD card.

1 Like