Tutorial: Connect Mini/Pro to other I2S DACs

After all you have done to solve it. I still suspect it is an I2S issue.

  1. Be sure that the cables are okay. I2S is very sensitive depending on good connection.

2.To show you what problem I had with the settings in APCWorkbanch. I uploaded these two pictures to make it clear. Take a close look at the setting of “PLL Clock1”. In the distorted picture “PLL Clock2” is active, but “PLL Clock1” is selected. So, be sure that you click with your mouse on “PLL Clock1”, EVEN if it seems to be selected.
distorted
not distorted

I really appreciate your help. I shortened the cable. It’s now 12cm long. And I check the settings.


But nothing helps, or changes something.

Hi @j.eeken1,

I’m designing a adapter board for a specific purpose using the ES9023P DAC as follows:

The bit that’s confusing me is the need to connect the Mini V3 0V to AGND to ensure the ES9023P AVCC gets 3.3V, yet I don’t want to pollute it with the Mini V3 GND as I suspect that is just a common AGND and DGND. I’ve now ended up with AGND, DGND, GND1 and Earth!

I’m aware I could easily use their own DAC, but this is how I like to learn.

Simon.

2 Likes

Maybe this could help you:
https://community.silabs.com/s/article/agnd-and-dgnd-connection?language=en_US

Wifi module (Linkplay A31) manual:

1 Like

Thanks @j.eeken1.

It seems I just connect GNDA and GNDD together in one place to avoid a loop.

I had sort of done that with the solder jumper as on RHS of the schematic.

The other adjustment I’ll make the ground plane of the board GNDA again, and just make sure its isolated from the Luxman recevier chassis and the Mini V3 as those would cause a ground loop.

By the way. Great looking receiver. Love these vintage stuff.

1 Like

Thanks. I’ll be posting the finished article on this forum when it’s done.

I ordered the Wondom »S/PDIF AND IIS/I2S AUDIO SIGNAL TRANSCEIVER« board. Bu I don’t know if this is a good idea. I don’t want an extra conversions in my signal chain and I don’t know if there will be one with this connection.

I have that board to. I use it for testing. if you mean that there will be quality loss. It won’t.
PCM will just be passed through.

A week ago Wondom released a video on youtube how to connect it with the Jab5

Cool. But one question back. Could this issue be a conflict between the Clock which expect the Wondom and the delivered from the Up2stream. For example: For Bluetooth and Analog there will be a 48Khz used and for WiFi 44kHz. If the JAB5 expect 48kHz and get 44kHz he will be confused. Normally this will be controlled via the Master/Slave switch, right? But I heard that the ADAU1701 standalone DSP-Board always works as Master.

The Up2stream boards all have an 16bit/44.1khz output. No matter what the input is. So you can configure the ADAU1701 boards with 16bit/44.1khz. The ADAU1701 dsp has 4 digital inputs and if you connect a second source to it that outputs 24bit/48khz, than you configure it to 24bit/48khz and it still accepts 16bit/44.1khz without distorsion.

The company “Analog Devices” that developed the ADAU1701 dsp chips has it’s own community. You may ask there to help you with your problem. They have way more knowledge then me.

Sorry, but I’m still talking about the JAB5 Amplifier board. I don’t have the ADAU1701 DSP-Board. But the JAB5 has the same chip on board as I know. Perhaps the DSP-board can have more inputs but I have to deal with the inputs that are available on the JAB5, and this is only one I2S Input.
I don’t know enough about the technical details, I’m just frustrated, and try to find the source of the problem. If the Up2stream only sends 44kHz/16Bit I don’t understand why streaming over Wifi is not working but via Bluetooth or analog.
The solution to use the SPDIF conversion board as a bridge is ok if I don’t have any loss of quality. It’s not the philosophy of integration which I would reach, but if it works…
I will write some more infos if I took a look in the System with Sigma Studio.

1 Like

Yes, I know you are talking about the Jab5. But, the onboard bluetooth of the Jab5 supports Aptx-HD 24bit/48khz. When you use that too or connect another source to the SPDIF board, you can leave the settings in Sigma Studio to 24bit/48khz. That was what I tried to tell.
I can really understand that you are frustrated by now. I was suggesting the Analog Devices community, because these are pros that may can identify your problem.

Finally I fixed it with Sigma Studio. I had some issues before it works – combinations of drivers, switches, what to power on first. But at the end I got it.
The reason was not the sampling rate, it was the LRCLK polarity. After switching it it works. Don’t know why, but it works, also with bluetooth and USB.
LRCLCK-switch

Now the fun part. I have the four potentiometer connected to the JAB5, but I want just a 2.0 system. So I don’t need the crossover potis and also I want just one volume controller. My idea is to have

  • one poti for volume
  • one poti for balance
  • one poti for treble
  • one poti for bass
    The only concern is the volume controller. The Up2stream has also a volume controller. I recalculates the digital values.
    Can I deactivate the volume controller from Up2Stream?
    How to realize a IR remote volume controller?
    Any experiences or ideas?

Currently no, will consider to make a new command to use static volume for up2stream board, as it’s not a problem for DIYers :grin:

1 Like

Hi I’m back. Now I build up my complete setup. And I have still the issue with the distorted signal. But know I recognized that’s only in the right channel. Left channel works fine. In my first test I had only one speaker connected. And this is the reason why the problem disappears as soon as I switched the LRCLK.
With speakers connected to both channels channels the distortion can be switched from one channel to the other if I switch LRCLK. I also tried an other Up2Stream Pro without any changes in the setup. Same issue.
Definitely the I2S signal over Network connection creates distortion on the right channel.

I will start a new discussion, because this is not related to your original topic: Up2Stream I2S distorted right channel only via network