ES9018 I2C controller

[necplusultra]

isolator is only required between I2C bus and dac.


not required for other I2C devices.

[CeeVee]

That is exactly what i want

Originally Posted by Corpius

If there is enough interrest I might do so or sell it through my website. First priority is to finish the design and make a prototype.

I could do with some input for the design. I'm thinking of adding some function to put the entire DAC into standby, except for the control unit. When it's in standby it could show the day time, month and year with the backlight turned off. This could be achieved with a little add-on board that houses a logic controlled relais that switches the power to the transformers.

[gwikse]

I went through some ideas with you earlier. From what I understand now you will link several atmei chips together if there is need for more programming space?

Anyways, each add on board could possibly have its own Atmega328?

Here are some of the things I am thinking of:

1. Networking in order to control the dac from a iphone / android possibly with the same gui as on the 20x4 display but with buttons along the edges to select inputs and the side-buttons on the android/iphone controls volume.

2. IR-learn and blast ability. In order to just use the apple remote for every component on a secondary function on the remote (f. ins pressing center + menu to control the source for the selected input).

3. I2c extender in order to link with other components? (i2c to cat5).

4. 20x4 LCD size PCB with screw holes so that it can be mounted to the rear of the LCD.

5. 12V trigger functionality. I am running the surround reciever through the dac and switch with relays. If the dac had a 12V trigger functionality this could be automated so that when the surround reciever is turned on the relays switch to the reciever.

The functionality you have listed is very good, I can see this being the controller in all my Buffalo/Opus builds.

Edit: more ideas

[Corpius]

Originally Posted by necplusultra

isolator is only required between I2C bus and dac.

not required for other I2C devices.

I can understand that it is not needed for the display and the other ICs that are going to be used within the controller, but using it for the outbreaks seems a good idea to me. Maybe you have a good reason to disagree. If so than please share it with me.

[Corpius]

Originally Posted by gwikse

I went through some ideas with you earlier. From what I understand now you will link several atmei chips together if there is need for more programming space?

Anyways, each add on board could possibly have its own Atmega328?

Here are some of the things I am thinking of:

1. Networking in order to control the dac from a iphone / android possibly with the same gui as on the 20x4 display but with buttons along the edges to select inputs and the side-buttons on the android/iphone controls volume.

2. IR-learn and blast ability. In order to just use the apple remote for every component on a secondary function on the remote (f. ins pressing center + menu to control the source for the selected input).

3. I2c extender in order to link with other components? (i2c to cat5).

4. 20x4 LCD size PCB with screw holes so that it can be mounted to the rear of the LCD.

5. 12V trigger functionality. I am running the surround reciever through the dac and switch with relays. If the dac had a 12V trigger functionality this could be automated so that when the surround reciever is turned on the relays switch to the reciever.

The functionality you have listed is very good, I can see this being the controller in all my Buffalo/Opus builds.

Edit: more ideas

1. We have discussed this before and it is also high on my whish list. There is a W5100 Ethernet module on its way to me. I`m not sure if it will make it into my first prototype. I have still not found any time yet to learn how to write an app for Android. I do not own a Iphone.
2. In my opinion way to complicated to control all sources. I`d rather use a logitech harmony or similar. I have thought of using such a remote for easy access to all functions I`m planning to add, but now I`m using the apple remote and still manage to access all functions. A IR learn function to teach the control how to use any remote would be nice. No idea how difficult this is. When in teaching mode the IR codes could be written to the EEPROM so the controller would reconise them again. I`ll try to find some info on this.
3. Would you like to control anything outside the chassis with it? There is no real need for an extender as long as all slaves are inside the chassis.
4. The holes already correspond with the ones of the 20x4 LCD
5. Isn`t this normally used to switch on a power amp?

[glt]

Originally Posted by Corpius

If there is enough interrest I might do so or sell it through my website. First priority is to finish the design and make a prototype.

I could do with some input for the design. I'm thinking of adding some function to put the entire DAC into standby, except for the control unit. When it's in standby it could show the day time, month and year with the backlight turned off. This could be achieved with a little add-on board that houses a logic controlled relais that switches the power to the transformers.

That is mostly s/w. You could have two cases in the main loop: Active case and Standby case: Active case: power the transformers, program and monitor the DAC; Standby: power off the transformers, skip the DAC code and do the RTC stuff.

[gwikse]

Originally Posted by Corpius

1. We have discussed this before and it is also high on my whish list. There is a W5100 Ethernet module on its way to me. I`m not sure if it will make it into my first prototype. I have still not found any time yet to learn how to write an app for Android. I do not own a Iphone.
2. In my opinion way to complicated to control all sources. I`d rather use a logitech harmony or similar. I have thought of using such a remote for easy access to all functions I`m planning to add, but now I`m using the apple remote and still manage to access all functions. A IR learn function to teach the control how to use any remote would be nice. No idea how difficult this is. When in teaching mode the IR codes could be written to the EEPROM so the controller would reconise them again. I`ll try to find some info on this.
3. Would you like to control anything outside the chassis with it? There is no real need for an extender as long as all slaves are inside the chassis.
4. The holes already correspond with the ones of the 20x4 LCD
5. Isn`t this normally used to switch on a power amp?

1. Yes I know, I am hoping that others may be interrested in this as well and possibly someone with the knowledge to make apps and what would be nessesary in the dac for it to work. I have seen an app for iphone that control the pins on an arduino controller. Very basic control but perhaps it could be used as a starting point for a more elaborate control system.

2. AMB audio`s lcduino system has this function so perhaps we could use that code as a start point for the ir learn function. Then it would be a matter of adding the ir blast code to each input. But I also use a universal remote atm and it works flawlessly. The only thing is that it is a little complicated for some users. A simpler remote is requested from others here in the household

3. It would be nice to be able to only use one display in the dac chassis and still have a Beta22headphone amp + Alpha20 linestage with delta1+2 input/volume system in a second chassis. It would proborably be easier to have a second controller (LCDuino) to control this, but it would be cool to control both from the same controller. Other uses might be f.ins. light control, doorbell control (when the doorbell rings the dac is muted) etc. Many things you can do with an arduino.

4. Great
5. Yes, power amps can be switched on/off by that sort of system. But also other uses like turning on a projector and lowering a motorized projection screen.

[Corpius]

I

Originally Posted by glt

That is mostly s/w. You could have two cases in the main loop: Active case and Standby case: Active case: power the transformers, program and monitor the DAC; Standby: power off the transformers, skip the DAC code and do the RTC stuff.

That is indeed the easiest way to accomplish it. There will also be access to the RTC stuff while the DAC is active.


EDIT:
@ gwikse:
Thanks for pointing me to the lcduino. Perhaps I will add some function to control your curtains too

[glt]

Originally Posted by gwikse

...

2. AMB audio`s lcduino system has this function so perhaps we could use that code as a start point for the ir learn function. Then it would be a matter of adding the ir blast code to each input. But I also use a universal remote atm and it works flawlessly. The only thing is that it is a little complicated for some users. A simpler remote is requested from others here in the household

...

Do you have a link to the code?

[gwikse]

Originally Posted by glt

Do you have a link to the code?

I have the code. I will ask linux-works if it is ok to use/share his code.

Edit: the code is made for this project but he has used it in many systems. http://www.amb.org/audio/lcduino1/ http://www.netstuff.org/audio/