You are completely right, I wired the AudioIN to the wrong pin! Now, I soldered it to DAC0 and I can hear sound! Thank you to have spotted this!
Thank you also to have spotted the mistake in the config file. As I tried many things to debug I modified the file at some point and forgot to put it back to the initial state (with 144 LEDs).
I still have some issues with sound and LEDs. When I plug the battery, I can hear a sound, then if I click on the button, the sound of ignition and hum start (most of the time). Sometimes it doesn't work. I just here a small noise and nothing is working until I disconnect the battery. By the way I have a kill switch that I did not wired, maybe I should add it... Sometimes it is working and then stop working as soon as I click on the button. Finally sometimes it is working even when I move the Prop Shield (sound of clash etc...), but at some point it stops working and I can't do anything except remove and reconnect the battery.
I put 3 different files + 2 pictures and 1 video in a new folder (160420) from the drive (Teensysaber V1 with Teensy 3.5 - Google Drive
), to explain in more details the remaining problems.
- the 2 pictures correspond to the WS2812B when the saber is ON or OFF (nothing is turning ON, should I wire things
- the video shows the sound that is stopping at some point when I touch the Prop Shield
- the 3 files contain information from the monitor that I gathered from different scenario:
--> first scenario: "sound_stay_constant_no_more_output_on_the_monitor.txt" this scenario happens sometimes when I
try to touch the Prop Shield to get sound. At the last line, sound stopped (I can hear a constant noise), and
nothing is responding anymore. I have to disconnect the battery.
--> second scenario: "sound_stop_because_too_much_solicited.txt" in this scenario, I am touching a lot the Prop
Shield and very rapidly sound stops. But as you can see it is different from the first scenario because in this
case the program is not able to find the .wav files and the monitor does not freeze. I still have to disconnect
battery to make it work again.
--> third scenario: "sound_stop_wav_file_not_found.txt" this scenario is similar to the second one (probably same
problem) but in this case I am not soliciting too much the Prop Shield and it stops working randomly after some
time. Sometimes it happened without doing anything.
You are giving me great hope to have a working lightsaber =), thanks again for your help.