The GrubDAC
Jul 21, 2014 at 3:51 PM Post #1,066 of 1,079
I can't guarantee anything, but this has been a long standing issue with Win7. There is no difference with respect to 2707 or 2706 for this issue. The 'C' variant is supposed to address it.

As stated however, I can't guarantee anything about your personal setup. I just thought that maybe you could confirm it for all of us.

If you're afraid to mess with it, I can certainly understand.
 
Aug 1, 2014 at 11:08 AM Post #1,067 of 1,079
Well, this is a first. Never had any sort of problem with SMD soldering before.
The board looks fine, there are no shorts anywhere, I've tested every pn on the ICs and they are soldered properly. The electrolytic caps are soldered right. PC feeds 5.18V into the DAC. The LED lights up as it should.
 
Problem is, the 3.3V test point gives 0.25-0.30V. This would seem like a cold solder joint, but I've reflown every pin on the regulator, and every component besides it (the ferrite and the three capacitors, who give stability to the chip if I'm not wrong). I've even changed the regulator for another one, because I thought the first one was dead on arrival or killed by heat or something. But no.
 
What could it be? Pictures in the gallery.
 
http://imgur.com/a/KfUkh
 
EDIT: also removed the ferrite between the reg and the other ICs to check if there was a short somewhere along that way, and nothing. The circuit seems okay, it's jut the region of the regulator.
 
Aug 1, 2014 at 1:41 PM Post #1,068 of 1,079
Is there 5 volts at the input to U2?
If there is, remove C7, C8 and L3.
Is there a short under C7 or C8.
Is there 3v3 from U2 now?
If no, replace U2.
Is it working now?
If yes, re-install C7, C8 and L3
 
 
Aug 1, 2014 at 2:40 PM Post #1,069 of 1,079
1. Yes
2. No shorts
3. No, but I reflowed it (yet again) and now it gives me an oscillating value, between 2.8 and 3.4. Looking good.
4. Soldered the caps: voltage drops to 0.5 or so again. What the hell? I guess I have bad caps.
 
Is it possible that I have received a bad batch of regulators?
 
Aug 1, 2014 at 3:34 PM Post #1,071 of 1,079
C8 is the noise reduction cap for the regulators internal reference.
C7 is an input bypass cap in parallel with the electrolytic on the
other side of the board.
 
If either of these were to cause a problem, it would be C8.
 
What about C14...it is directly on the output of the regulator.
Have you removed and checked it?
 
Aug 31, 2014 at 11:58 AM Post #1,073 of 1,079
  I am confused about this issue though - I read the documents for the "C" revision of the PCM2706/7 and it seems like they only changed the behaviour of the volume control (i.e. how the volume changes with the win7 volume slider); the "C" variant doesn't seem to enable the volume control. 
 
The document is here: http://www.ti.com/lit/an/sbfa019/sbfa019.pdf
 
I'm trying to isolate the problem: is my non-functioning master volume control due to me using PCM2707 instead of PCM2706, or is it because I'm using the non-C revision?
 
Desoldering and resoldering the IC chip will be a nasty job...

 
I can't guarantee anything, but this has been a long standing issue with Win7. There is no difference with respect to 2707 or 2706 for this issue. The 'C' variant is supposed to address it.

As stated however, I can't guarantee anything about your personal setup. I just thought that maybe you could confirm it for all of us.

If you're afraid to mess with it, I can certainly understand.

 
Tragedy! I tried to desolder the PCM2707 chip and but burnt some solder pads off the board. Now the board is useless and I have wasted the other parts that are already soldered on :frowning2:
 
I then built a Pupdac with a PCM2707C after much effort (the pcm1794 is a tough job). Alas, the volume control in windows 7 is still not working.
 
I am now contemplating whether to order another grubdac and pupdac board to do a better job.
 
Thank you for your help Tom!
 
Dec 24, 2014 at 2:39 PM Post #1,074 of 1,079
So... I bought a new desktop PC with Windows 7 and it doesn't even detect my GrubDAC... this is sad. =(
 
I'm clueless when it comes to Windows. How do I go about debugging this?


edit: I booted on a fedora usb stick and dmesg floods me with this:


[ 209.924022] hub 6-0:1.0: connect-debounce failed, port 2 disabled
[ 212.126019] hub 6-0:1.0: connect-debounce failed, port 2 disabled
[ 214.330018] hub 6-0:1.0: connect-debounce failed, port 2 disabled
[ 216.535020] hub 6-0:1.0: connect-debounce failed, port 2 disabled


This project is getting sadder every time I try to make it work. I'm out of ideas here. =(
 
Dec 24, 2014 at 3:12 PM Post #1,075 of 1,079
It should have recognized it right away...even if just to give you an error.
It's as if it didn't see it at all.
I'm sure you tried a different cable and port...
 
Is the DAC getting power?
 
Dec 24, 2014 at 3:18 PM Post #1,076 of 1,079
The DAC powers fine...

I think the problem is with the Carrie, so I'll be moving this discussion over there. Here's why I think so:

I added a power switch between the carrie and the dac. When I plug the DAC in with the switch open, the DAC is recognized:

1460.483019] usb 6-2: new full-speed USB device number 52 using uhci_hcd
[ 1460.669007] usb 6-2: New USB device found, idVendor=08bb, idProduct=2707
[ 1460.669011] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1460.669014] usb 6-2: Product: USB Audio DAC
[ 1460.669017] usb 6-2: Manufacturer: Burr-Brown from TI
[ 1460.701071] input: Burr-Brown from TI USB Audio DAC as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.2/input/input19
[ 1460.701346] hid-generic 0003:08BB:2707.0009: input,hidraw5: USB HID v1.00 Device [Burr-Brown from TI USB Audio DAC ] on usb-0000:00:1d.0-2/input2

But the moment I close the switch to power the carrie...

[ 1528.953037] hub 6-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
[ 1528.953045] usb 6-2: USB disconnect, device number 52
[ 1531.042021] hub 6-0:1.0: connect-debounce failed, port 2 disabled
[ 1533.246020] hub 6-0:1.0: connect-debounce failed, port 2 disabled

I'm thinking my Carrie+GrubDAC combo is pulling too much power off the usb port.
 

Users who are viewing this thread

Back
Top