My Arduino class library for the ES9028/38 chip is now available here at Github

If you want to configure the ES9028/38 in dual mono, quadrophonic, implement a 2, 3, or 4 way digital x-over, or control multiple DACs, then this is for you - and of course, the Arduino allows you to easily add remote control, LCDs, etc to your project.

Example code snippet for quadraphonic configuration (see the example programs for a more complete overview of programming with the library):

// map DAC channels 1-4 to inputs 1 & 2 (first I2S right/left data input),
//and DAC channels 5-8 to inputs 3 & 4 (second I2S right/left data input)
dac.mapInputs(ES9028::Input_1, ES9028::Input_2, ES9028::Input_1, ES9028::Input_2, ES9028::Input_3, ES9028::Input_4, ES9028::Input_3, ES9028::Input_4);

Note that the code example above will not work with stereo boards such as the BIII SE PRO but works a treat for chips transplanted onto the old BIII 8-channel board

(There is also a completely rewritten version of my ES9018 library there as well)

Enjoy!

Poss

Edited by user Tuesday, June 12, 2018 1:17:30 AM(UTC)  | Reason: Not specified

I started playing around with Arduino control a few years back when I wanted to play with the bandwidth register setting on a BII. Now I do all of my builds with Arduino as it opens up heaps more build possibilities - e.g.: ir/bluetooth/wifi control - and is easy to debug issues real-time using a PC and the Serial Monitor interface (applying updates is easy too).

I managed to learn the requisites based on DimDim's Arduino code (as well as from Russ's on-board firmware code) - however, it was still a heap of work transforming those solutions into something custom when you're dealing with registry bits 'n bytes - even for an IT pro like myself.

DimDim's Arduino projects combined user interface code for the LCD and remote control with the DAC control code into one large code base - fine if you want to build a similar project, but not so great if you had to unravel the code because, for example, you didn't want to use an LCD, or had a different number of DACs (or even a mixture of ES9018/28/38s!). So I decided to write an object-oriented library that separates and encapsulates all the DAC-specific behaviour - thus completely abstracting the user from all those pesky registry addressing and bitwise settings, and separating that code from the UI-specific code.

Hopefully the library makes it easy enough for even a novice programmer to use.

Another big advantage of this coding approach is that it is easy to create user interface libraries that interact with the DAC classes - such as DAC remote control, LCD, and indicator light libraries - so anyone with basic programming skills can quickly program a custom build by plugging together the various DAC user interface libraries they need for their build (you can tell I have an OO software background :-) )

Here's an example of the main code to control 3 different DACs in a 3-way xover, add support for a power button, lock, power, and input indicator LED, motorised volume control pot, and infra-red remote control:

#define NO_OF_ES9018_DACS 1
#define NO_OF_ES9028_DACS 2
ES9018 lowDAC = ES9018("Front Right Low", ES9018::Clock100Mhz, ES9018::MonoRight, ES9018::InPhase, 0x48);
ES9028 midDAC = ES9028("Front Right Mid", ES9028::MonoRight, 0x49);
ES9028 hiDAC = ES9028("Front Right High", ES9028::MonoRight, 0x47);

DACControl dacCtrl = DACControl(es9018dacs, NO_OF_ES9018_DACS, es9028dacs, NO_OF_ES9028_DACS);
DACPowerButton powerButton = DACPowerButton(&dacCtrl, DigitalPins::POWER_BTN);
LightControl indicatorLight = LightControl();
DACVolumeControl dacVolCtrl = DACVolumeControl(&dacCtrl, AnalogPins::POT_INPUT, DigitalPins::POT_MOTOR1, DigitalPins::POT_MOTOR2);
IRrecv irrecv(DigitalPins::IR_RECV);
DACRemoteControl dacRemoteCtrl = DACRemoteControl(&dacCtrl, &dacVolCtrl, &irrecv);

A lot of work went into this. Hope you find it useful!

Edited by user Tuesday, June 12, 2018 12:58:32 AM(UTC)  | Reason: Not specified

Your ready to go - All the functions are already there! (not tested tho)

SPDIF functions and switching between modes:

bool setInputSelect(InputSelect val); // Configures the SABRE DAC to use a particular input decoder if auto_select is disabled.
bool setSPDIFUserBits(SPDIFUserBits val); // Setting user_bits will present the SPDIF user bits on the read-only register interface instead of the default channel status bits.
bool setSPDIFDataFlag(SPDIFDataFlag val); // Configures the SPDIF decoder to ignore the ‘data’ flag in the channel status bits.
bool setSPDIFValidFlag(SPDIFValidFlag val); // Configures the SPDIF decoder to ignore the ‘valid’ flag in the SPDIF stream.
bool setAutoSelect(AutoSelect val); // Allows the SABRE DAC to automatically select between either serial, SPDIF or DSD input formats
bool setSPDIFInput(SPDIFInput val); // Selects which input to use when decoding SPDIF data. Note: If using a GPIO the GPIO configuration must be set to an input.


Sync/async functions:

bool enableMasterMode(); // Enables master mode which causes the SABRE DAC to derive the DATA_CLK and DATA1 signals when in I2S mode
bool disableMasterMode(); // Disables master mode
bool setMasterDiv(MasterDiv val); // Sets the frame clock (DATA1) and DATA_CLK frequencies when in master mode.
bool enable128fsMode(); // Enables operation of the DAC while in synchronous mode with a 128*FSR MCLK in PCM normal or OSF bypass mode only.
bool disable128fsMode(); // Disables operation of the DAC while in synchronous mode with a 128*FSR MCLK in PCM normal or OSF bypass mode only.
bool setLockSpeed(LockSpeed val); // Sets the number of audio samples required before the DPLL and jitter eliminator lock to the incoming signal.
bool setSPDIFInput(SPDIFInput val); // Selects which input to use when decoding SPDIF data. Note: If using a GPIO the GPIO configuration must be set to an input.

I use a 2nd arduino running as an I2C slave to test isolator. Lets u see whts going on. Can send u tbe sketch if u want

The I2C connections to BIIIpro are the same as for BIIIse - and you need to use an I2C isolator like on DimDims shield

However, in addition you will need to pull the DAC reset pin high to enable it. I use an optocoupler to do this (don't know if DimDims board has something similar). Please read the description on my githuib page here: https://github.com/possum64/BuffaloDAC

The I2S connections are also the same as on the BIIIse - however, you can configure the DAC to use any of 13 possible SPDIF inputs via the setSPDIFInput() func (eg: dac.setSPDIFInput(ES9028::DATA8) makes data input 8 the SPDIF input). You can even use GPIO pins. So its possible to simultaneously have I2S connected and also have multiple SPDIF inputs connected to the unused data and GPIO pins and use the setSPDIFInput() func to switch between them via the Arduino (no Sidecar needed).

I will have to check Russ's firmware code to see which input the BIIISEpro board is using for the SPDIF in (I never use SPDIF so I don't know off the top of my head..).

You can switch input select via the setInputSelect() function - e.g.: switch to SPDIF input by calling dac.setInputSelect(ES9028::InputSelect_SPDIF) or select I2S via dac.setInputSelect(ES9028::InputSelect_Serial)

I have not included the sampleRate() function in the ES9028 library yet but can do so if you need it.

The code to initialise the DAC in stereo I2S is straightforward:

#include <ES9028.h>

ES9028 dac = ES9028("My Stereo DAC", ES9028::Stereo);

void setup() {
// initialize digital pin LED_BUILTIN as the DAC lock light.
pinMode(LED_BUILTIN, OUTPUT);
// wait for SR trident regulators to ramp up to full voltage
delay(1500);
// put code here to pull DAC Reset Pin high to enable the DAC
//...
if (dac.initialise())
{
dac.mute();
// default to I2S input
dac.setInputSelect(ES9028::InputSelect_Serial);
// init GPIOs 1 and 4 to same as BIII
dac.setGPIO1(ES9028::GPIO_Automute);
dac.setGPIO4(ES9028::GPIO_Lock);
//play with settings
dac.setSerialBits(ES9028::Bits_24); // set 24 bit I2S source
dac.setDpllBandwidthSerial(ES9028::DPLL_Lowest);
dac.setFilterShape(ES9028::Filter_Hybrid);
dac.setAutoMute(ES9028::AutoMute_MuteAndRampToGnd);
dac.setAutomuteTime(100);
dac.unmute();
}
}


void loop() {
if (dac.getInitialised())
digitalWrite(LED_BUILTIN, dac.locked()); // turn the LED on if both DACs locked
delay(100);
}

Edited by user Thursday, January 17, 2019 5:21:32 AM(UTC)  | Reason: Not specified

2 I2S inputs is easy - a TPA OttoII board will do the job. You can control it from Arduino via another optocoupler.

From the ES9028 manual:

"An SPDIF source multiplexer allows for up to 13 SPDIF sources to be connected to the data and GPIO pins selectable via
Register 11: SPDIF Mux and GPIO Inversion. SPDIF input mode can be manually selected by input_select in Register 1:
Input selection or automatically selected if auto_select in Register 1: Input selection is set to a mode allowing automatic
SPDIF selection."

Selecting the standard SPDIF is also easy - as per the BIIISE pro manual it is connected to DATA3:

"The SPDIF input accepts consumer level or CMOS level SPDIF - the SPDIF signal is level shifted to CMOS and sent to the DATA_3 pin on the DAC Controllers switching between Serial and SPDIF should select DATA_3 as the SPDIF source."

Please note consumer level SPDIF is shifted to CMOS. The BIIISE pro board does not expose DATA 4-8, so you will have to use one of the GPIO pins exposed on the new header for your second SPDIF input and you will need to build/buy a similar consumer level-to-CMOS circuit for it.

I have companion libraries for pushbutton and remote control interfaces you can use/adapt

I'd suggest you use DimDim's isolator board as I believe it includes a flash rom you can use to save your settings to (you will need some kind of a user interface to select, change, and save settings of course)

Is the Arduino communicating with the DAC ok? (check the serial monitor window)

Plug your PC into the Arduino board via USB and open up the Arduino IDE - go to Tools->Serial Monitor

It will show detailed diagnostic trace of comms between Arduino and DAC (built into the code library)

I want to see if the Arduino is properly communicating via I2C

Ok, I reloaded the code above, and ran it, but the serial monitor is not showing anything?

The scanner sees the dac, but the codes could not??

Alex

- that's

PUT the following line as the first line in setup():

Serial.begin(115200)

You can set the baud rate to 9600 but my library has very verbose diagnostics and the higher speed is recommended - change your I2C network sniffer to use the higher baud rate

BTW What Arduino are you using?


Clearly you have I2C comms with the DAC (its address is 48) - so there's no reason why we cant get this puppy to behave :-)