The WM8741 in the OPUS can be configured with up to two device addresses (Sabre32 also with up to two addresses). That is the limitation of the chip.

Arduino can control any number of devices as long as they have different addresses.

More than two devices can be accommodated with some tricks: either h/w address multiplexer or s/w by implementing multiple i2c buses as LeonvB said. I think the Arduino library for I2S only supports one bus. There maybe other libraries available, but I don't have experience in that area.

BTW, I am a fan of the OPUS/WM8741. At least the documentation (eg datasheet) is much better...

In daisy chain all devices are progammed with the same value. With two wire (i2c) you can progam them independently for example one device mono right and the other device mono left

washout,

I am glad you are learning some s/w. Just copy and paste as many times as you wish (there is a limit of the non-volatile memory at 10,000 times or 100,000 times -I forgot, but practically you will never reach that limit).

The "notations" are "comments" which are ignored.

When you reset, the program restarts from the beginning.
When you load a new program, there is an automatic reset and new code is copied into the microprocessor.

Keep in mind that you should power Buffalo and the controller at the same time. If you power Buffalo first without the controller, Buffalo will start with the default settings which is FULL volume.

Hi glt and others

Very interested in the project. I've made a cart on amazon with the items needed for this to work.

Now, i have a small question about expanding the functionality of the arduino. I've seen it can be used for PWM, so i was thinking about using it as a failsafe if the temperature inside an amp or dac was too high. I have not checked it myself, but does the arduino have enough terminals to work both as a remote interface and fan controller using perhaps a thermistor? And can i wire a second display to the arduino and have a small display showing temperature?

Like this here: http://www.coolerguys.com/840556090885.html

There is still a few pins left after connecting everything. Connecting a separate display will not work because you will need another 6 pins and modify the library. You can support multiple LCDs if you go the I2C route but that means changing "everything". You can display the temperature in the existing display. You'll just have to find some empty space...

Best solution is what Brian said or open more holes in the case :-)

Did you install and adjust the contrast adjustment pot?

Did you remove the microprocessor from the Buffalo?
The code should not get stuck anywhere...
You can press the reset button in the Arduino to restart the program.

>> I should mention I am plugging in the Arduino and turning on the dac, I think, at the same time

Can you explain some more?

Edited by user Thursday, January 20, 2011 10:23:01 PM(UTC)  | Reason: Not specified

Switch the A and B connectors in the rotary encoder

Hi glt,

I put together my hifiduino control for my buffalo 2 over the weekend. So far so good. I changed the UI a bit, added mute, and made all selections available via the remote as well but I took the i2c settings for the DAC from your code.

Everything works pretty much as expected but I suspect your settings are not the same that Russ is using with his microcontroller. The difference becomes very apparent for me when I play material with a sample rate of 192Khz. There is a lot of noise on the speakers as soon as the DAC locks onto this sample rate when using the HIFIduino initialization code. I do not have access to the NDA data other than what is published in the help file for the Sabre GUI tool and embedded in your code. I have been thinking about letting the MCU on the initialize the DAC and then read everything back but maybe this post will help clear things up.

There is no noise when switching back the i2c connection to the volumite.


The relevant code for a fixed i2s connection from you web site is:

writeSabreReg(0x0E,0xF9); // Reg 14: BuffII I2S wiring, normal IIR BW and Fast rolloff
writeSabreReg(0x0A,0xCE); // Reg 10: 32 bit I2S, jitter reduction ON
writeSabreReg(0x11,0x04); // Reg 17: Auto spdif detection OFF
writeSabreReg(0x08,0x68); // Reg 8: Enable I2S/DSD input
writeSabreReg(0x19,0x02); // Reg 25: Use best DPLL settings
writeSabreReg(0x12,0x10); // Reg 18: Reroute SPDIf (to see if it improves i2S dropouts)

Maybe Russ can enlighten us to what is missing here without violating his NDA.

Cheers

Thomas

P.S.: The other obvious problem could be the i2c connection from my Arduino board. I did not add a 3.3V voltage converter.

Edited by user Sunday, January 23, 2011 10:45:36 PM(UTC)  | Reason: Not specified

I took the selection of Brightness because i ran out of real state in the display :-) but the code is in the previous version... I'll add it back later...