• The Vendor's Bazaar forum is for commercial offers and transactions. Only unmoderated members can post here.

    diyAudio provides this forum 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.

dam1941 - Next Gen Discrete R-2R Sign Magnitude 24 bit 384 kHz DAC module

Well. I know that 99% of the people around prefer to talk about HW, LDOs, silver micas, cables, asf... 😉

How about a little SW talk? 😉

However. At least I would like to make sure beforehand that I get this DAC properly integrated into
my RPI/squeezelite environment without having the need for any further onboard controls.

Does anybody know if the python library dam1021 is compatible to the 1941?

Has anybody used that library to upload e.g. custom filters to the 1941?

Has anybody been using that Alsa dummy driver for volume control on the 1941?
Why actually doesn't offer the 1941 VC through the generic Linux USB driver?

And than I'm wondering what advantage I'd have to use onDAC volume control,
if any app supplies me with a 32 bit SW VC!?!?
That would leads to following question:
Is there any option to bypass all the Soekris internal filters and SW volume control and
do the related tasks externally on the transport?

I guess running DSD and DOP prevents from using volume control at all. Right??
ESS Sabre is the only one offering it afaik.
 
Had a quick look at the python library. Resisting the urge to vomit at the sight of Python..

That library simply operates by automating the umaanger serial terminal commands to the dam umanager. If the commands in the manuals are identical then it will work without a problem - there may be some parameter value differences though.

The change you need to be careful of the version of firmware that you would use for uploading to the dam itself (the "download" command). The Spartan6 fgpa firmware would work differently (both in the sign magnitude) but also operating the pinouts for the 4 R2R ladders - using the wrong version of the firmware could cause damage to the dam.
So use the wrong firmware uploaded means you could cause permanent damage.
 
Just looking:

Code:
VOLUME_INF=-80
VOLUME_SUP=10
VOLUME_POT=-99
INPUT_SRC_SET=range(4)

FSET_EXT_STR_TO_INT_D = dict(linear=4,mixed=5,minimum=6,soft=7)
FSET_EXT_NUM_TO_INT_D = {'1':4,'2':5,'3':6,'4':7 }

Rx.xx uManager firmware version
Mx Configuration mode.
Ix Input select mode, 7 = Auto, 0 = USB, 1 = AES/EBU, 2 = BNC, 3 = RCA, 4 =
Toslink, 5 = I2S.
Fx Filter Type, 4 = linear, 5 = mixed, 6 = minimum, 7 = soft
Lxxx Link Speed, 000 = unlocked, 044-384 PCM speed, 02M, 05M & 11M DSD speed Vxxx Volume, -90 to +10, default set to 0
Px Phase, N = Normal, I = Inverted, default is Normal
Xx Crossfeed Mode 0..3, 0 = off, 3 = max, only valid when headphones are selected
Command Messages
Ix Input select mode, 7 = Auto, 0 = USB, 1 = AES/EBU, 2 = BNC, 3 = RCA, 4 = Toslink, 5 = I2S.
Fx Filter Type, 4 = linear, 5 = mixed, 6 = minimum, 7 = soft
Vxxx Volume, -90 to +10
Px Phase, N = Normal, I = Inverted
Xx Crossfeed Mode 0..3, 0 = off, 3 = max, only valid when headphones are selected
The dam19x1 will acknowledge all command messages as status messages.

It looks like range(4) (ie 1-4) for the source validation may prevent 5 "i2s" and 7 "auto" being used.

There's also no crossfeed and phase mode support for the new feature - this would be relatively simple to add new support.
 
The DAM has minimal format/syntax check so be sure you do what you should or things may go wrong. This is experience talking. But hey, you use a computer - what could go wrong 😉

//

Yep - they don't even have a set of tests as part of that library. Been bitten by that many moons ago (20+) hence developing a slight clueso-eqsue twitch.
 
When I think of all of the things I did to my first SOEKRIS board I am amazed that I was able to mess it up with the removal of the ceramic capacitors. Everything now is about half the size; the first board was much easier to play around with due to the larger components.

I did not use heat - sharp dykes in the middle of the cap and then carefully squeeze. Seemed to go uneventfully … I cleaned two of the pads (left channel) and they cleaned up easily but it did not seem worth the trouble. The pads are there and undamaged.

The left channel plays music but there is something very wrong.

Everything looks fine on he board.

The right channel seems to be fine. Did not listen to it long so I have no idea what the removal did for the sound.

There is this noise, in the 120 hz region, not LOUD - you can hear the music on top of it easily but no one would want to listen to it like this.

Any ideas or is this now a mono DAC?

Not that I was not warned not to take things off of the board by the manufacturer. Wish I had left it alone. Never thought of myself as a cat but I must have something in common with them. Luckily, I just killed the board.

Yet I know if I had it to do over again I would have done it, again. Got worried Peter and analog_sa would think there was some veiled "blaming" them. They certainly did not recommend clipping them out and I suspect, too late, that, like most shortcuts, has its pitfalls. Get out the soldering irons!
 
When I think of all of the things I did to my first SOEKRIS board I am amazed that I was able to mess it up with the removal of the ceramic capacitors. Everything now is about half the size; the first board was much easier to play around with due to the larger components.

I did not use heat - sharp dykes in the middle of the cap and then carefully squeeze. Seemed to go uneventfully … I cleaned two of the pads (left channel) and they cleaned up easily but it did not seem worth the trouble. The pads are there and undamaged.

The left channel plays music but there is something very wrong.

Everything looks fine on he board.

The right channel seems to be fine. Did not listen to it long so I have no idea what the removal did for the sound.

There is this noise, in the 120 hz region, not LOUD - you can hear the music on top of it easily but no one would want to listen to it like this.

Sounds like only signal tracing with an oscilloscope is going to be able to answer that. 🙁
 
Yep - they don't even have a set of tests as part of that library. Been bitten by that many moons ago (20+) hence developing a slight clueso-eqsue twitch.

At least somebody did that library job (FOC). 😉

A job that could (should?) have been done by the manufacturer. 😛
There are $50 RPi DAC HATs out there that come with full blown drivers.
Volume control, mute, changing filters, changing outputs all these basic operational tasks I'd prefer to run via USB.


Anyhow.
Thx for pointing into potentially critical areas. I hope that the DAC is well documented. That should make it rather easy to get the library adapted.
And for me most important to know: As is, that python toolbox is not compatible.
And that could put quite some extra load on my shoulders. 🙄

A pity, as you mention, that the DAC allows to load firmware that might harm the device. That I'd consider a really weak spot.

Thx.
 
Just learning about bypass and ringing - this is the same as the oscillations for AC snubbing I assume, but given the square wave on the levels at 3MHz does the output have ringing and need a number of values of bypass capacitors - how is this tacked on the switches as I think I can only see one cap.

Does the slew rate allow a lower rate?
 
The "ringing" talked about re: DAC is not the same as the one a snubber is curing. DAC ringing is (mostly) due to it's digital filter and is a consequence of software calculations while a snubber cures an oscillation in a group of electrical components. The cap on the output is not a bypasss cap (i.e. a cap in series) but a decoupling cap, or a low pass filter if you like. This cap position could indeed remove "ringings" if it was set in low enough. But it is there to filter out high frequency energy way above the audible range.

Your second question does not make sense.

It seems that you are not skilled enough yet to phrase the correct questions. I kindly suggest that you read up on your used concepts on e.g, wiki etc.

//
 
Last edited:
The "ringing" talked about re: DAC is not the same as the one a snubber is curing. DAC ringing is (mostly) due to it's digital filter and is a consequence of software calculations while a snubber cures an oscillation in a group of electrical components.

Your second question does not make sense.

It seems that you are not skilled enough yet to phrase the correct questions. I kindly suggest that you read up on your used concepts on e.g, wiki etc.

So the power going to the LVC switches is a digital pulse at a frequency of 3MHz so the leading edges of the switching has ringing. Only a single is required? Does the speed of the LVC slew to switch reduce ringing?

I'm happy with the digital software based ringing from approximating a square wave with a limited set of frequencies, and FIR/IIR for realtime image processing. I never shoot my staff for asking a question.
 
Soundcheck, just a short remark:

In the DAM the +/-5v gets regulated down to +/-4v by the opamps in order to feed the shift registers, but the exact voltage is not particularly critical. Using Lipo batteries some users have had good results at 3.3 - 3.6v and there is no particular reason this voltage cannot be taken down to 2.7v. Obviously the 0db level will then be reduced and the required additional amplification will affect to a degree the S/N.

Should you decide to take this path, the opamp regulators on the boards can be removed/bypassed and external power applied directly to the shift registers.

In earlier posts (re 1021) there is a lot of mention of improving ''vref'', im not quite clear if this +/-4V supply is the same vref on dam1121/1941?
I assume it has to be because there is not much else in the analogue supply area aside from the op amp regs.
In that case I seen soekris mention the tolerance between positive and negative vref from the regs, small imbalances caused increases in distortion.
How would you keep +/- voltages closely matched and also sustained with battery supply?
 
Last edited:
An excellent point and one i believe has been raised before, perhaps even by Søren. Only, not having a personal interest in batteries i have forgotten all about it. Indeed, without a common reference this cannot possibly work well.

Thank you for correcting me.
 
An excellent point and one i believe has been raised before, perhaps even by Søren. Only, not having a personal interest in batteries i have forgotten all about it. Indeed, without a common reference this cannot possibly work well.

Thank you for correcting me.

Agreed, seems odd when you look at the varying power levels of batteries, the non-linear discharge vs time.
The switches (https://assets.nexperia.com/documents/data-sheet/74LVC595A.pdf) they do state variations in transition times based on voltage.. however I strongly doubt that someone could hear that and if they do it's more likely to some other aberration or absence of aberration such as noise from a PSU.

Also adding caps in the supply only provides filtering and ripple-countering pool - with the speed of switching over 3Mhz you're starting to need to think about high frequency circuit design (bypass caps to protect against ringing etc). Although I suspect there's more issues that would cause more noticeable aberrations.

Sorry but I'm a numbers guy - so if it shows on the oscilloscope then there's a difference. I want the dam to give a precise and accurate representation, I can then choose components to add aberrations such as tube amps etc.