Rank: Member
Groups: Member
Joined: 6/3/2010(UTC) Posts: 53  Location: romania Thanks: 2 times
|
Ok I have connected the scope on b3se inputs as following yellow - mck cyan - D2 purple - D1 blue - DCK I am using also the counter function to see the frequency of the signals Here I am using the dac async. As you can see D1 is 384khz and the dac plays fine.  image1.JPG (112kb) downloaded 10 time(s).When using the dac in sync I noticed that the frequency on D1 is always double than the one of the file I stream(for all files from 44.1 - 384khz). In the photo I was streaming a 384khz file but to the b3 was arriving 768khz sample rate. DCK seems dead to me when streaming 384khz files image3.JPG (101kb) downloaded 15 time(s).Edited by user Wednesday, February 24, 2016 6:40:38 PM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 6/3/2010(UTC) Posts: 53 Location: romania Thanks: 2 times
|
in sync mode DCK comes double too until 192k sample rate. Above 192k it dies.
|
|
|
|
|
|
Rank: Administration
Groups: Administration, Customer
Joined: 10/24/2006(UTC)
Posts: 3,979
Location: Nashville, TN
Thanks: 25 times
Was thanked: 89 time(s) in 83 post(s)
|
Interesting, Compare the signals on the input side of the cronus to the output side.
Also check that the clock going out to the Amanero are 1:2 of the actual master clock.
|
|
|
|
|
|
Rank: Administration
Groups: Administration, Customer
Joined: 10/24/2006(UTC)
Posts: 3,979
Location: Nashville, TN
Thanks: 25 times
Was thanked: 89 time(s) in 83 post(s)
|
The cronus itself operates identically always - regardless of DAC being in sync mode or async mode
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 6/3/2010(UTC) Posts: 53 Location: romania Thanks: 2 times
|
In the first photo I connected the scope on amanero mck and fsclk. To be sure that amanero is in slave mode I powered only amanero and on the scope there was no wave present for the mck so it`s in slave mode  After that connected the dac in async and for a 384k file I get 24.576mhz on amanero mck input and fsclk is right too. image1.JPG (122kb) downloaded 7 time(s).Now when I connect the dac in sync mode the mck that arrives to amanero is a little bit strange. Watch the frequency for different trigger values, it`s almost double  image2.JPG (123kb) downloaded 7 time(s). image3.JPG (123kb) downloaded 5 time(s). image1.JPG (134kb) downloaded 9 time(s).. Later tonight I will do what you asked for also Thanks
|
|
|
|
|
|
Rank: Administration
Groups: Administration, Customer
Joined: 10/24/2006(UTC)
Posts: 3,979
Location: Nashville, TN
Thanks: 25 times
Was thanked: 89 time(s) in 83 post(s)
|
I looks as if the Mck on the DAC is still running when you run sync? Or you have some kind of a ground loop or compromised cable - you might try using single hookup wires GND,MCK,BCK,LRCK,Data to the DAC - no coax. One thing is for sure when you are connecting mck to the DAC something abnormal is happening to It. Also - just a Note - that 50Mhz DSO will not pick up the 40+Mhz signals very well. Probably passable - but just a warning that you will be operating at the limits which can make some interesting aliasing happen on a DSO. Edited by user Thursday, February 25, 2016 7:40:21 PM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 6/3/2010(UTC) Posts: 53 Location: romania Thanks: 2 times
|
The first two channels are the on cronus mck and fsclk the side that goes to the isolator The 3rd and 4th channels are on the dac side mck and fsclk This is when running the dac async so no master clock connection between cronus and dac image1.JPG (143kb) downloaded 5 time(s).In the second I run the dac async but I left amanero disconnected from pc image2.JPG (128kb) downloaded 8 time(s).And the last ones with amanero connected to pc and streaming a 384khz file. image5.JPG (129kb) downloaded 10 time(s). image4.JPG (130kb) downloaded 15 time(s).
|
|
|
|
|
|
Rank: Administration
Groups: Administration, Customer
Joined: 10/24/2006(UTC)
Posts: 3,979
Location: Nashville, TN
Thanks: 25 times
Was thanked: 89 time(s) in 83 post(s)
|
It looks like you have two clock signals superimposed on each other. Is the master clock on the DAC unpowered?
|
|
|
|
|
|
Rank: Administration
Groups: Administration, Customer
Joined: 10/24/2006(UTC)
Posts: 3,979
Location: Nashville, TN
Thanks: 25 times
Was thanked: 89 time(s) in 83 post(s)
|
Also when checking the amanero for being in slave mode - you must try to play music. Otherwise I think both clocks will be off.
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 6/3/2010(UTC) Posts: 53 Location: romania Thanks: 2 times
|
When I run the dac in sync mode I always remove the vdd_xo trident reg. The Dso has a licence on it for 100mhz so nothing to worry about. In the photo you can see b3 onboard 100mhz clock when running async. 9f74126fca30823cf29a2fa54eda14e41c0bc96fd19b2ceb81474f8caf478e08.jpg (114kb) downloaded 14 time(s).If I don`t power up cronus foobar will not start playback at any sample rate. To stream files I have to start first cronus/b3 combo which are powered toghether from the same battery and after that connect amanero to pc
|
|
|
|
|
|
Rank: Administration
Groups: Administration, Customer
Joined: 10/24/2006(UTC)
Posts: 3,979
Location: Nashville, TN
Thanks: 25 times
Was thanked: 89 time(s) in 83 post(s)
|
Just saying - it seems in your earlier pics it is quite clear there are two clocks present. I can only guess one is from the amanero?
Also try wiring as I indicated and see if that helps?
Connecting the clock to an input (as long as there is no loop etc) should have no effect at all on the clock. :) So there has to be something else going on.
|
|
|
|
|
|
Rank: Administration
Groups: Administration, Customer
Joined: 10/24/2006(UTC)
Posts: 3,979
Location: Nashville, TN
Thanks: 25 times
Was thanked: 89 time(s) in 83 post(s)
|
How much voltage are you supplying the Cronus via the battery?
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 6/3/2010(UTC) Posts: 53 Location: romania Thanks: 2 times
|
The battery is 11.1 nominal. After that I have two regs, one for cronus and another for b3.
Cronus is powered with 5.5v, b3 the same.
|
|
|
|
|
|
Rank: Administration
Groups: Administration, Customer
Joined: 10/24/2006(UTC)
Posts: 3,979
Location: Nashville, TN
Thanks: 25 times
Was thanked: 89 time(s) in 83 post(s)
|
So one thing I observed was that some of the master clock few on your scope seem to be a mix of the two time domain.
Try this, remove one of your master clocks on the Cronus - leaving only the 48Khz time domain. Worth a shot and easy to test. :)
|
 1 user thanked Russ White for this useful post.
|
|
|
|
Rank: Member
Groups: Member
Joined: 6/3/2010(UTC) Posts: 53 Location: romania Thanks: 2 times
|
They seem to be a mix only when I use the dac in sync mode 
|
|
|
|
|
|
Rank: Administration
Groups: Administration, Customer
Joined: 10/24/2006(UTC)
Posts: 3,979
Location: Nashville, TN
Thanks: 25 times
Was thanked: 89 time(s) in 83 post(s)
|
There must be something amiss in the wiring.... because it is not possible for a master clock signal to be coming from DAC if the master clock is not powered. The only thing I can think to suggest next is to make sure you only have one ground connection between your DAC and the Cronus. If they already share a common power supply ground do not route GND from the Cronus to the DAC and only wire MCK,DCK,LRCK,DATA via plain copper hookup wire - not coax. Edited by user Friday, February 26, 2016 5:51:42 PM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 6/3/2010(UTC) Posts: 53 Location: romania Thanks: 2 times
|
If I remove the 45mhz oscillator from cronus foobar won`t play nothing multiple of 44.1khz. Neither in sync or async The mck at both sides on cronus is dead. When I remove the 49mhz oscillator and connect the dac in sync mode on the scope I get this image1.JPG (122kb) downloaded 14 time(s).The fsclk for the above photo is in the 3mhz range 
|
|
|
|
|
|
Rank: Administration
Groups: Administration, Customer
Joined: 10/24/2006(UTC)
Posts: 3,979
Location: Nashville, TN
Thanks: 25 times
Was thanked: 89 time(s) in 83 post(s)
|
Originally Posted by: schultzsch  If I remove the 45mhz oscillator from cronus foobar won`t play nothing multiple of 44.1khz. Neither in sync or async The mck at both sides on cronus is dead. When I remove the 49mhz oscillator and connect the dac in sync mode on the scope I get this image1.JPG (122kb) downloaded 14 time(s).The fsclk for the above photo is in the 3mhz range Yeah just leave them both in - i don't think that is core of the problem. I wasn't even sure if the amanero would function correctly with some clock present for 44.1 time base.
|
|
|
|
|
|
Rank: Administration
Groups: Administration, Customer
Joined: 10/24/2006(UTC)
Posts: 3,979
Location: Nashville, TN
Thanks: 25 times
Was thanked: 89 time(s) in 83 post(s)
|
Just put both clocks in and wire as I described a post above your last and see what happens
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 6/3/2010(UTC) Posts: 53 Location: romania Thanks: 2 times
|
In both photos the dac is running in sync mode and as wiring I used straight wires for the signals with only one wire for the ground. In the first photo amanero is disconnected from the isolator and as you can see I have 77mhz on cronus 1:2 output image1.JPG (116kb) downloaded 13 time(s).When I connect amanero I get 60mhz on the same output image2.JPG (116kb) downloaded 12 time(s).Edit On the dac side I get the mck frequency exactly it`s right values 45... and 49... mhz Edited by user Friday, February 26, 2016 10:24:01 PM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
