Took delivery of 2 pcs. Small board 🙂 - now wait for the rest of the needed stuff.
Please share your impressions when everything is ready (esp. dam1021 comparisons).
Thanks.
Just received and open box.
Surprise.
The problem is ? I actually had to reverse that power protection diode as the contract manufacturer made a mistake on the first batch.
The first board there might be a piece of solder left, just take a small brush and remove it. Anything else just looks like a little flux residue, don't do any harm.
The problem is ? I actually had to reverse that power protection diode as the contract manufacturer made a mistake on the first batch.
The first board there might be a piece of solder left, just take a small brush and remove it. Anything else just looks like a little flux residue, don't do any harm.
The second one have scratch on PCB case by retouch.
I don't know why the factory accept the the pcb have scratch have retouch.
And the QA accept the piece of solder left on the PCBA.
The second one have scratch on PCB case by retouch.
I don't know why the factory accept the the pcb have scratch have retouch.
I can't see any problem with the PCB.... And they're all fully electrical tested anyway. Or at least specified to be, you never know with these far east PCB manufacturers....
And the QA accept the piece of solder left on the PCBA.
Maybe because the rework QA (In this case me....) missed it ??
Sören - as I understand it this board introduce re-clocking (U8/U11?) after the FPGA. You should have moved the clock close to the re-clocking flip-flops - 8mm traces and make the long traces back to the FPGA etc.
//
//
Sören - as I understand it this board introduce re-clocking (U8/U11?) after the FPGA. You should have moved the clock close to the re-clocking flip-flops - 8mm traces and make the long traces back to the FPGA etc.
//
Eeeh, LVDS signaling with controlled impedance traces and termination.... Trust me, clocking is optimal.
Hmmmnnnjjjjvvsss....
OK, I do 🙂
Still, a short optimized path is better than a longer optimized path - or?
//
OK, I do 🙂
Still, a short optimized path is better than a longer optimized path - or?
//
Last edited:
Config 3..1:
0xx: 0dB output attenuation
1xx: -40dB attenuation
Please? My budget for woofers are exhausted 😉
//
0xx: 0dB output attenuation
1xx: -40dB attenuation
Please? My budget for woofers are exhausted 😉
//
Last edited:
Config 3..1:
0xx: 0dB output attenuation
1xx: -40dB attenuation
Please? My budget for woofers are exhausted 😉
//
Enter uManager and do "set volume = -40". Anyway, the dam1121 is supposed to be controlled by a processor, I'm not going to waste the few hardware straps by something unnecessary....
Hmmmnnnjjjjvvsss....
OK, I do 🙂
Still, a short optimized path is better than a longer optimized path - or?
//
No, not when you have other considerations. LVDS signaling allows short stubs, like when the onboard oscillator need to drive an external buffer, that's why the oscillator is located that close to the connector.
Eeeh, LVDS signaling with controlled impedance traces and termination.... Trust me, clocking is optimal.
Søren
Can you provide any report about using si570 between the local clock?
thanks
No, not when you have other considerations. LVDS signaling allows short stubs, like when the onboard oscillator need to drive an external buffer, that's why the oscillator is located that close to the connector.
OK I see. Maybe you should have made the sync on frame level instead of bit clock. You had lost DSD there but I don't think that had mattered. But, lets enjoy the important improvement on this new fine product.
How about the volume control from pot - can we anticipate this or do one need to seek an other solution.
Bluetooth <-> RS232 a' 3USD? How about 2 when the channels are physically separated? A small script to to duplicate the orders over air?
//
Enter uManager and do "set volume = -40". Anyway, the dam1121 is supposed to be controlled by a processor, I'm not going to waste the few hardware straps by something unnecessary....
Go it!!!

//
Søren
Can you provide any report about using si570 between the local clock?
thanks
I have no clue what you're asking about....
OK I see. Maybe you should have made the sync on frame level instead of bit clock. You had lost DSD there but I don't think that had mattered. But, lets enjoy the important improvement on this new fine product.
How about the volume control from pot - can we anticipate this or do one need to seek an other solution.
Bluetooth <-> RS232 a' 3USD? How about 2 when the channels are physically separated? A small script to to duplicate the orders over air?
//
No volume by analog potmeter, wouldn't be possible to track over multiple boards.
As I said a couple of times, the dam1121 is supposed to be controlled by a uC, like the STM32F030 I'm already using.
I have no clue what you're asking about....
Søren
I want to know the preformance different between Si570 and Si514
Thanks
Søren
I want to know the preformance different between Si570 and Si514
Thanks
I don't have equipment to measure it, and can't hear any difference myself.... Take a look at the two datasheets.
- Home
- Source & Line
- Digital Line Level
- Building with the Soekris dam1121