Print

[YoloThuna]

I just built my diy Astro EQ based on the PCB and ICs i ordere from this site. The power LED does light up but the others dont when connected to PC. I checked all connections on the board for shorts and all polarities are also right. I havent connected the motors because i only found 1 suiting cable but i dont think this should be a problem.

[TCWORLD]

You'll need to be more specific I'm afraid.

The ICs and PCBs do function correctly - it is a long tried and tested design.

Could you post a couple of pictures of your board. That will help identify potential issues.

1. What order did you make connections? The 12V power cable must be plugged in before the USB cable.
2. Does anything show up in device manager (windows) or lsusb (linux)?
3. Have you checked the USB cable is functional?

[YoloThuna]

Wierd. Just as i was about to send the reply with further details but then i thought i test it another time and suddenly it worked but windows didnt recognize the driver so i unplugged it and installed the driver and now it wont recognize it again. No reaction at all. I attached the pictures maybe you can find a mistake, i will check it another time tomorrow.

Update: now the board gets recongized most of the time but only after ca. 30 sec and then it is a unknown USB device and the LED on the board is solid.

[TCWORLD]

Hmm.

If it is getting recognised but then dropping out, it suggests a few possibilities:
1. The crystal is not oscillating reliably causing it to lose sync (make sure the capacitors are te correct value, and maybe try taking the PIC out of the socket and putting it back in again).
2. The power supply is not stable (could be a dodgy conenction or usb cable)
3. There is a short somewhere on the board causing issues (have a quick check of C5 and C6 - there looks to be a near short on the picture, but its hard to tell)

I've attached a picture of a few points I'd double check on the board soldering wise (its hard to tell as some of what looks like metal in the picture may just be a blob of flux).

[YoloThuna]

The power source is stable, i used 2 different one, same problem with both.
I havent found any shorts and i double and triple checked the problem zones you found.
For some reason i cant measure my capacitors, i get BS reading if any. It changes every second or every milimeter i move my probe, the resistors are all good i could check them just not the capacitors.

Here i have an error code from the program "usbtreeview". Maybe this can help

   =========================== USB Port2 ===========================

Connection Status        : 0x02 (Device failed enumeration)
Port Chain               : 2-2
Properties               : 0x01
 IsUserConnectable       : yes
 PortIsDebugCapable      : no
 PortHasMultiCompanions  : no
 PortConnectorIsTypeC    : no
ConnectionIndex          : 2
CompanionIndex           : 0
 CompanionHubSymLnk      : USB#ROOT_HUB30#4&d584ab0&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
 CompanionPortNumber     : 17

      ======================== USB Device ========================

        +++++++++++++++++ Device Information ++++++++++++++++++
Device Description       : Unbekanntes USB-Gerät (Fehler beim Anfordern einer Gerätebeschreibung.) comment: this is german for: Unknown USB device (error requesting device description.)
Device ID                : USB\VID_0000&PID_0002\5&2EFFDC72&0&2
Hardware IDs             : USB\DEVICE_DESCRIPTOR_FAILURE
Driver KeyName           : {36fc9e60-c465-11cf-8056-444553540000}\0037 (GUID_DEVCLASS_USB)
Driver Inf               : C:\Windows\inf\usb.inf
Legacy BusType           : PNPBus
Class                    : USB
Class GUID               : {36fc9e60-c465-11cf-8056-444553540000} (GUID_DEVCLASS_USB)
Enumerator               : USB
Location Info            : Port_#0002.Hub_#0004
Manufacturer Info        : (Standard-USB-Hostcontroller)
Capabilities             : 0x64 (Removable, SilentInstall, RawDeviceOK)
Status                   : 0x01806400 (DN_HAS_PROBLEM, DN_DISABLEABLE, DN_REMOVABLE, DN_NT_ENUMERATOR, DN_NT_DRIVER)
Problem Code             : 43 (CM_PROB_FAILED_POST_START)
Address                  : 2
Power State              : D3 (supported: D0, D3, wake from D0)

        ---------------- Connection Information ---------------
Connection Index         : 0x02 (2)
Connection Status        : 0x02 (DeviceFailedEnumeration)
Current Config Value     : 0x00
Device Address           : 0x00 (0)
Is Hub                   : 0x00 (no)
Device Bus Speed         : 0x01 (Full-Speed)
Number Of Open Pipes     : 0x00 (0 pipes to data endpoints)
Data (HexDump)           : 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
                           00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 02   ................
                           00 00 00                                          ...

        --------------- Connection Information V2 -------------
Connection Index         : 0x02 (2)
Length                   : 0x10 (16 bytes)
SupportedUsbProtocols    : 0x03
 Usb110                  : 1 (yes)
 Usb200                  : 1 (yes)
 Usb300                  : 0 (no)
 ReservedMBZ             : 0x00
Flags                    : 0x00
 DevIsOpAtSsOrHigher     : 0 (Is not operating at SuperSpeed or higher)
 DevIsSsCapOrHigher      : 0 (Is not SuperSpeed capable or higher)
 DevIsOpAtSsPlusOrHigher : 0 (Is not operating at SuperSpeedPlus or higher)
 DevIsSsPlusCapOrHigher  : 0 (Is not SuperSpeedPlus capable or higher)
 ReservedMBZ             : 0x00
Data (HexDump)           : 02 00 00 00 10 00 00 00 03 00 00 00 00 00 00 00   ................

    ---------------------- Device Descriptor ----------------------
bLength                  : 0x00 (0 bytes)

      -------------------- String Descriptors -------------------
String descriptors are not available  (because the device has problem code CM_PROB_FAILED_POST_START)

[TCWORLD]

Do you have another PC or USB cable you can try with? I've seen in the past that some skinny or long USB cables can cause enumeration issues.


In the mean time, I've plugged ten or so of the current batch of PICs onto the programmer again to double check them and they all pass verification with the correct firmware, so it is unlikely that the one you received is bad (I checked the whole batch when they were programmed).

I'll build up a controller from the current batch of PCBs to make sure there are no issues with the PCB itself (shouldn't be any issues as the same design for the last three years, and the boards are electrically checked by the manufacturer). That will have to wait until the weekend as I'll need to order parts.


Kind Regards,
Tom.

[YoloThuna]

First of all thank you for your effort and testing all you pcb and ic.

I have already tried on my laptop and also bought a new cable, but still same thing. Now it just gets recognized a little faster but still unkown USB device. But i have noticed a strange behaviour: Most of time it only gets recognized when i press onto the PIC. I removed it and it looked fine. I also noticed that somtimes the status LED is solid and before that if flashes (sometimes dont remember, now it just did it), even when there is no usb cable attached. Maybe its always on, i made a terrible job with the LED soldering.

[TCWORLD]

Hmm, if its detected when pressing on the PIC, that suggests that there is either a loose connection (e.g. dry solder joint), or the socket itself is damaged.

It might be worth trying to carefully bend the pins of the PIC out slightly (only ~1degree or so), then putting it back in the socket to see if you get better contact.

I'd also reheat the solder joints for the socket just to make sure they have all taken. Pins 1 and 20 in particular (+5V and GND respectively).

[YoloThuna]

IT WORKED! I just reheated the solder joints on the PIC and added a bit of solder on a few on them and now it gets recognized and i can configure it. Thank you for you help!

[TCWORLD]

Perfect. Glad that sorted it.

Tom.