Firmware rev 1.23 is the newest and the one to enable the 2nd I2S port. Verify after upgrading that bith the uManager and FPGA revision is 1.23.
If it was ever up as 1.23 for 1 second with wrong content, then one should release 1.24 when corrected. Thats version handling ABC.
//
Soekris do you maybe have a updated driver from thesycon that supports DSD48khz i remember reading that they implemented support from it in some revisions higher than the one currently on your webpage, hopefully the driver just needs to be updated, and not the dsd filters.
Last edited:
I am still im the process of burning it...which becomes a bit frustrating as the DAC looses its lock over USB after some time (like every 30min).
As my source is the same for many years and as I had never any issues (its a sorm isb card, which played sofar into a waveio-card, so xmos as well): I suspect there is an issue on the DAC side...amyone else has faced the same issues ?
.....
By the way: Are those Wimas in the signal path ?
As my source is the same for many years and as I had never any issues (its a sorm isb card, which played sofar into a waveio-card, so xmos as well): I suspect there is an issue on the DAC side...amyone else has faced the same issues ?
.....
By the way: Are those Wimas in the signal path ?
Sorry to hear about this. Do you have the option to connect the waveio or a Rpi through the i2s input? Just to make sure that it is indeed the xmos.
The caps are shunting the output, so yes, very much in the signal path. Don't know about you, but I wouldn't want Wimas anywhere close 🙂
The caps are shunting the output, so yes, very much in the signal path. Don't know about you, but I wouldn't want Wimas anywhere close 🙂
Yes, i can test this...giving USB input over Waveiocard, noprob.
Is there a schematic to see what the wima caps do ? If they are for hf filtering and signal to geound, I would not be too concerned. If they play into NF or even worse are coupling caps in series with the signal, I would be very concerned. Jupiter copper in wax is what I can stand as coupling caps...if I have to...
Is there a schematic to see what the wima caps do ? If they are for hf filtering and signal to geound, I would not be too concerned. If they play into NF or even worse are coupling caps in series with the signal, I would be very concerned. Jupiter copper in wax is what I can stand as coupling caps...if I have to...
The schematics of this "diy" project are a heavily guarded secret 🙂 In the 1021 the output filter involves the output impedance as the series resistor and a shunting ceramic cap to ground. It seems the 1941 has been upgraded to Wima.
In my 1021 replacing the ceramic with a polystyrene was an upgrade, yet i much prefer it with no filtering cap. I have an active transformer coupled pre, which effectively filters above 100kHz, so maybe removing the cap is not a blanket recommendation.
In my 1021 replacing the ceramic with a polystyrene was an upgrade, yet i much prefer it with no filtering cap. I have an active transformer coupled pre, which effectively filters above 100kHz, so maybe removing the cap is not a blanket recommendation.
Good point. I have built at least ten DACs over the last 15 years and I always preferred without the typical Hf filter as well...could be that this is what is reducing the life-like experien in the upper mods/treble, will test this...I got a transformer-coupled tubeoitput stage as well and the ll1692am starts to filter stuff from 40khz om anyhow.
Any insides on on-board regs ? I still try to understand if I could feed the 1941 with pure LiIon battery power...which would result in either 3.3V or 6.6V input voltage...
Last question: Any documentation on the display board switches ? I understand one is for Digital inpit, but can I switch digital filters with it instead of using umanager ?
Any insides on on-board regs ? I still try to understand if I could feed the 1941 with pure LiIon battery power...which would result in either 3.3V or 6.6V input voltage...
Last question: Any documentation on the display board switches ? I understand one is for Digital inpit, but can I switch digital filters with it instead of using umanager ?
The 1941 manual says
Buttons:
S5: Input SelectS3: Filter SelectS8: CrossFeed SelectS4: Output Select
So, no, you don't need the umanager to change filters
Buttons:
S5: Input SelectS3: Filter SelectS8: CrossFeed SelectS4: Output Select
So, no, you don't need the umanager to change filters
Since the firmware now supports the second input I2S, the question arises how to switch to this input. Is it detected automatically when a signal is present? Can you manually switch to this input with the switch 3 and how could you indicate that with an LED like the other inputs? If I push the switch 3 is there a state where all LEDs are off, then is the I2S input active? Unfortunately, I have not yet imported the firmware update, so I can not give it a try ...😎
best, Peter
best, Peter
Hi Peter,
the first led is the I2S input (I5)
no led is auto input (I7)
one easy way to switch to this input or change the filters is via serial commands.
what kind of source device do you have?
the first led is the I2S input (I5)
no led is auto input (I7)
one easy way to switch to this input or change the filters is via serial commands.
what kind of source device do you have?
... not possible to edit the posting after 30 minutes ... so here more information...
Q: how to switch to this input (I2S)?
A: Switch to the first LED (input = I5)
Q: Is it detected automatically when a signal is present?
A: Switch to the position that all LEDs are off (input = I7). Now you are in the AUTO mode. If a valid signal from any input is present, the DAM swithes to the input wih the signal and the LED is on. If you disconnect the input the LED will remain on the input but the AUTO mode is still active. If you put a signal to another input the DAM will switch to it. There is some priority (TOSLINK has priority over I2S).
Q: Can you manually switch to this input with the switch 3 and how could you indicate that with an LED like the other inputs?
A: See Attachement. You can print it, glue it on some cardboard and punch some holes for the LEDs and switches. This helps for debugging.
Another easy way to switch to this input or change the filters is via serial commands. what kind of source device do you have?
Q: how to switch to this input (I2S)?
A: Switch to the first LED (input = I5)
Q: Is it detected automatically when a signal is present?
A: Switch to the position that all LEDs are off (input = I7). Now you are in the AUTO mode. If a valid signal from any input is present, the DAM swithes to the input wih the signal and the LED is on. If you disconnect the input the LED will remain on the input but the AUTO mode is still active. If you put a signal to another input the DAM will switch to it. There is some priority (TOSLINK has priority over I2S).
Q: Can you manually switch to this input with the switch 3 and how could you indicate that with an LED like the other inputs?
A: See Attachement. You can print it, glue it on some cardboard and punch some holes for the LEDs and switches. This helps for debugging.
Another easy way to switch to this input or change the filters is via serial commands. what kind of source device do you have?
Wima polypropylene caps
The Wima polypropylene capacitors on the dam 19x1 do not appear to be present on the dam 1541. What type and value are the output capacitors on the dam 1541?
The Wima polypropylene capacitors on the dam 19x1 do not appear to be present on the dam 1541. What type and value are the output capacitors on the dam 1541?
Hello to all...
somehow I am not clear with the instructions for the firmware update. The connection between the computer and the dam works, if I turn on the encoder or switch the input, I get something displayed in the terminal program z.b. V-10 for volume followed by 2 cryptic characters (there probably is something wrong with the setting). Even switching to the uManager works. But how to continue? How can I enter a "1K Xmodem protocol"?From where does the dam1941 get the file? Somehow...I do not see the forest, but so many trees ...
Help...please...😕
@tonno, thanks for your helpfull explanation
! My surce is a raspberry pi with I2S, if it works someday...
somehow I am not clear with the instructions for the firmware update. The connection between the computer and the dam works, if I turn on the encoder or switch the input, I get something displayed in the terminal program z.b. V-10 for volume followed by 2 cryptic characters (there probably is something wrong with the setting). Even switching to the uManager works. But how to continue? How can I enter a "1K Xmodem protocol"?From where does the dam1941 get the file? Somehow...I do not see the forest, but so many trees ...
Help...please...😕
@tonno, thanks for your helpfull explanation
! My surce is a raspberry pi with I2S, if it works someday...
In uManager (after +++) you do:
Download
DAM responds with: CCCCC.. (for 30 seconds - then it times out so... hurry 😉 )
You do, in your terminal program menues, something like: File, Send File, (point to .skr file) - SEND.
Now the file transfer goes on between the terminal program and the DAM.
You will understand when it is finished.
//
Download
DAM responds with: CCCCC.. (for 30 seconds - then it times out so... hurry 😉 )
You do, in your terminal program menues, something like: File, Send File, (point to .skr file) - SEND.
Now the file transfer goes on between the terminal program and the DAM.
You will understand when it is finished.
//
I do not have any response from the dam like cccccc. When I download and then send the file, I get in the receive data window many cryptic characters. After the send process is finished, I wait a moment, but nothing happens. When I turn off and on, is still the old (1.21) firmware on it ...