• These commercial threads are for private transactions. diyAudio.com provides these forums for the convenience of our members, but makes no warranty nor assumes any responsibility. We do not vet any members, use of this facility is at your own risk. Customers can post any issues in those threads as long as it is done in a civil manner. All diyAudio rules about conduct apply and will be enforced.

Reference DAC Module - Discrete R-2R Sign Magnitude 24 bit 384 KHz

The plan is to daisy chain the serial ports, the echo of all commands should make it possible. Then use volume pot and input selector on the first one in the chain....

Paralleling the I2S and Toslink inputs are easy, SPDIF might require buffering....

This means pre-programming each board mono left and mono right before daisy chaining?
 
Some random thoughts.

On the volume control;
When I connect the DAM directly to the power amp I usually end up with volume settings V-15 to V-20. In view of
The -01 used a mix of 0.01%, 0.02%, 0.05% and 0.1% resistors in the R-2R network, while the -02 used 0.02%, 0.05% and 0.1% resistors, both with the most precise resistors on the msb bits and least precise on the lsb bits.

On the new -12 I moved around the different resistors, so the -12 have fewer 0.01% parts and more of the 0.02% parts.
the realization of the volume control in the DAC ladder is convenient but a waste of resources. The expensive MSB resistors are never used, and the specs are thus (theoretically) worse than if you attenuate after the ladder (for the volume only, no precision resistors are needed) or lower Vreff.
Perhaps a future revision could realize the coarse part of the volume control outside the ladder.

On crossover/momo:
I would prefer to keep the paths of the analog signals short. So ideally something like aktive speakers with digital input. For that the DAM would need
1.) to have the crossover for one channel on one board (with the current approach, one board handle a dedicated frequency range for both channels).
2.) that two DAM boards can run synchronous and communicate controls over some meters distance.
 
The plan is to daisy chain the serial ports, the echo of all commands should make it possible. Then use volume pot and input selector on the first one in the chain....
That could work to some extent if only a physical input switch and volume pot are used for dam1021 control, assuming DAM ignores all irrelevant chatter on serial line, like R and L messages.

For driving it with a microcontroller it gets hairy. With the current firmware we have to go into umanager to obtain the filter list. With daisy chained setup the downstream devices would have to echo the umanager output from the first device without acting on it. It gets ugly pretty fast...
And to change default settings or load new filters and firmware updates the completed device would have to be physically taken apart...

I'm getting more inclined towards using dedicated serial host ports for each dam board.

SPDIF might require buffering....
Any official recommendations?
 
When I connect the DAM directly to the power amp I usually end up with volume settings V-15 to V-20.
To get the best out of the complete system the adjustment of the amplifier's gain would help - is necessary?

In view of the realization of the volume control in the DAC ladder is convenient but a waste of resources. ... Perhaps a future revision could realize the coarse part of the volume control outside the ladder.
That's an additional amplification stage - trust it or not :cool:
 
Some random thoughts.

On the volume control;
When I connect the DAM directly to the power amp I usually end up with volume settings V-15 to V-20. In view of

the realization of the volume control in the DAC ladder is convenient but a waste of resources. The expensive MSB resistors are never used, and the specs are thus (theoretically) worse than if you attenuate after the ladder (for the volume only, no precision resistors are needed) or lower Vreff.
Perhaps a future revision could realize the coarse part of the volume control outside the ladder.

As stated long time ago, the dam1021 resistor network direct out is a voltage source with 625 ohm in series. If you want to lower the output level you simply just shunt the output with a suitable resistor....

On crossover/momo:
I would prefer to keep the paths of the analog signals short. So ideally something like aktive speakers with digital input. For that the DAM would need
1.) to have the crossover for one channel on one board (with the current approach, one board handle a dedicated frequency range for both channels).
2.) that two DAM boards can run synchronous and communicate controls over some meters distance.

Now you want to push beyond what the dam1021 was designed for, it can't be everything to everybody and still be simple and low cost....
 
I notice that sometimes changing songs a bit fast the dac suddenly looses track and I have to powercycle. It happens with 16bit - 48khz material. Doesnt help changing tracks.
FW 0.99, sorens filter.
rpi2 - i2s - dam

I was not in the umanager when this happens.
A follow up here. This happens from time to time. Quite annoying
Did a check in umanager today and this is what it says when it becomes silent.

Seems as it loads a "silent" filter or something (L000). I am unable to make it sing again. Have to turn power off and on again.
 

Attachments

  • l0.PNG
    l0.PNG
    2.4 KB · Views: 644
A follow up here. This happens from time to time. Quite annoying
Did a check in umanager today and this is what it says when it becomes silent.

Seems as it loads a "silent" filter or something (L000). I am unable to make it sing again. Have to turn power off and on again.

I have never observed anything like that. L000 could be caused by unstable clock. Are you sure it's the dam1021, not your player or your raspberry pi ??
 
Here is a trace with Vref.
CH3 (magenta) is -4V ref
CH4 (blue) is -12V input power

This is with unmodified DAM hardware, only the 27k resistor is added.
Input power is +/-12V from simple LM317/337 regulators with 2x2200 uF filter caps per side.
Another strange thing is that the poweron output pulse amplitude is so high - well above 10Vpp, on one occasion I saw 20Vpp. How can those voltages appear on unbuffered output? Perhaps the output opamps are wreaking havoc?

I have uploaded updated firmware, still 0.99 but dated 20150826. Can you please check to see if the problem you observed is still there ?
 
That could work to some extent if only a physical input switch and volume pot are used for dam1021 control, assuming DAM ignores all irrelevant chatter on serial line, like R and L messages.

For driving it with a microcontroller it gets hairy. With the current firmware we have to go into umanager to obtain the filter list. With daisy chained setup the downstream devices would have to echo the umanager output from the first device without acting on it. It gets ugly pretty fast...
And to change default settings or load new filters and firmware updates the completed device would have to be physically taken apart...
An easy solution could be to give each board an individual id-number as parameter to be set in uManager once.
Then make two variants of the commands, e.g.
"set2" would only affect DAM no 2, whereas "set" would affect all DAMs.
For settings where it makes no sense to send a command to all DAMs the unnumbered command should be disabled if the DAM has an id number.

The only problem is , that I have the impression the DAM does not always react on commands (but perhaps I only typed something wrong ... hard to say if you get no echo of what you typed in play mode). If this happens with daisy chained DAMs they end up in different states.
 
Lets face it, there is no elegant way to control multiple devices over a single RS232 line. The second set of commands will not help if there are more than two dacs for crossover use. And it would not be that trivial to make it work reliably. It is going to take a bit of extra hardware to make multi-dam setup fully functional.
 
An easy solution could be to give each board an individual id-number as parameter to be set in uManager once.
Then make two variants of the commands, e.g.
"set2" would only affect DAM no 2, whereas "set" would affect all DAMs.
For settings where it makes no sense to send a command to all DAMs the unnumbered command should be disabled if the DAM has an id number.

The only problem is , that I have the impression the DAM does not always react on commands (but perhaps I only typed something wrong ... hard to say if you get no echo of what you typed in play mode). If this happens with daisy chained DAMs they end up in different states.

I think that daisy chain needs other hardware (e.g. RS485) or two RS232 on the DAM: One for input and one for output and the implementation of a type of token protocol.