Announcement

Collapse
No announcement yet.

User Profile

Collapse

Profile Sidebar

Collapse
Grouickman
Grouickman
Member
Last Activity: 04-23-2025, 02:30 PM
Joined: 06-24-2024
Location: France
  •  
  • Filter
  • Time
  • Show
  • Source
Clear All
new posts

  • Zotac Gaming Geforce RTX 3060 AMP WHITE ED 12GB, any boardview (or schematic) ?

    I'm looking for boardview (or schematic, or even some hi-res board photos of the board) for a Zotac Gaming Geforce RTX 3060 AMP WHITE ED 12GB (P/N 9288-BN617-210Z8).

    Trying to fix one, but someone really messed up the board badly already and I don't know what is missing....
    [ATTACH=JSON]{"data-align":"none","data-size":"full","title":"image.png","data-attachmentid":3617590}[/ATTACH]​I'm looking for boardview (or schematic, or even some hi-res board photos of the board) for a Zotac Gaming Geforce RTX 3060 AMP...
    See more | Go to post

  • I think I made something...

    So first, my theory about serial number was wrong, not much surprise here.

    But, I did compare the original eeprom content to the eeprom content I get after reseting the machine.

    I ignored the first part of the eeprom, there are indeed few different bytes, but I assume that the "header" is where all the options are stored.

    then lower (arround @ 0630) I found a section of 144 bytes that is empty on the "reseted state" eeprom vs the orginal eeprom.
    I suppose that's enough data to store some calibration...
    See more | Go to post

    Leave a comment:


  • If I could keep the original eeprom content I think the factory calibration could have survived.

    Anyway I tried, copied the original content to the eeprom and the machine is back to the error : 3S-3L beeps, which means communication issue with : KBC/LCD/Motor/BRAKE.
    So... either it's looking for the optional brake that is indeed not present (was removed by the previous owner(s))?
    or.. I have a new theory : it's looking for the KBD/LCD board which also has his own eeprom, and this eeprom contains only 5 or 6 bytes of data, and (theory intensify) this is the serial number...
    See more | Go to post

    Leave a comment:


  • I mean... a 6 is an upside down 9.. almost the same...

    ok... I did not wait... because I can't see a valid reason why the CPU would be defective on only one of it's A/D input (well... there are reasons, and it could...) but... I need a justification here, because yeah... a few days would not matter but... reasons....

    So.... it works. Setting the proper model helps (a lot !) ! funny that with the same board they do not use the same A/D input for V.line...

    And finally all that work for nothing... well.. I least I have a pretty good idea of how the electronics...
    See more | Go to post

    Leave a comment:


  • Ok... I think you can call me stupid. Well, we still need to confirm my new theory, but you still can...

    Remember when i said after some poking around the eeprom was corrupted and it started showing an error and asked to reconfigure the model number ?

    yes... so.... I selected model 9300 (first option in the list) instead of 6300.
    Not sure it can explain the issue, but for sure it would probably not work properly.

    Now... should I wait few more days for the new cpu? If it is the cpu at least I will have a(hopefully) fully functional one and won't need...
    See more | Go to post

    Leave a comment:


  • The capacitor array is just for filtering (C in // with cpu input pin), it not a dc-block (series).
    Saying otherwise : the Vline signals goes trough the series resistor (10K) then directly to the CPU input pin, and the capacitor is in // for filtering the noise.
    See more | Go to post

    Leave a comment:


  • yes, Vline is on pin 18, but pin 14 (that I tought was the ripped pad) is "Line Freq", which I supposed the absence could be a reason why the firmware would not check VLine and report it as 0V.
    My assumption is that the firmware checks line frequency before line voltage, but it was just a guess from my side.

    Anyway, not the case as it's definitely pad 13 that is ripped, so no matter how the firmware behaves, that does not explain anything.

    I might be trying too hard to find an explanation to the CPU not being able to read VLine while it's definitely present...
    See more | Go to post

    Leave a comment:


  • I'm positive that's pin 13.

    Pin 1 is the round pin, all other pins are square. And the damaged pad is on the odd row.
    [ATTACH=JSON]{"data-align":"none","data-size":"full","title":"image.png","data-attachmentid":3609165}[/ATTACH]​I'm positive that's pin 13.

    Pin 1 is the round pin, all other pins are square. And the damaged pad is on the odd row.
    [ATTACH=JSON]{"data-align":"none","data-size":"full","title":"image.png","data-...
    See more | Go to post

    Leave a comment:


  • never mind I read it wrong it's X11 pin 13 not pin 14. It's a temperature measurement, so nothing to do with the line frequency...

    Still need to fix it, but I won't refit anything until I got the new CPU.
    See more | Go to post

    Leave a comment:


  • Ho crap... I just noticed the Line Freq input is missing a pad on the connector socket, it got ripped when I removed the connector from the board to put it on the hot plate.

    Could it be... the pad was already damaged, and the "line Freq" signal was missing before.... causing the Vline to not be detected (or software not checking Vline if Line Freq is out of range) ??
    There is a code (C93) to show line frequency, but it's not implemented on this model, I'm 100% sure I wanted to check this code and could not.

    I' know I did check line Freq signal before,...
    See more | Go to post

    Leave a comment:


  • I have the same reading before/after the resistor array, and on the AN15 pin of the cpu.
    At some point I was hoping for the cap array to be cracked/shorted, that would pull the voltage to 0, but no.

    I agree, cpu being faulty, on that input (maybe other ?) seems a bit odd. Especially because I have (apparently) correct readings on other A/D channels
    but since there is nothing else in-between the V.Line input and the cpu... must be the CPU...

    The only other explanation I would see is that some sort of software issue that would cause the reading to be 0, but...
    See more | Go to post

    Leave a comment:


  • So, I refitted everything and gave it another go.
    now the situation "back to normal" : ~3.8V on both side of the V.Line 10K res, so the "short" is gone, and there are no more shorts between A15 and AN6....


    but still input voltage (C55) read as 0.
    I should receive the spares CPUs in few days, I'll see then as for now I can't see anything else.
    See more | Go to post

    Leave a comment:


  • Ok, I gave it another try this morning,
    C110 show 5.24, right what my DMM says
    [ATTACH=JSON]{"data-align":"none","data-size":"full","title":"image.png","data-attachmentid":3608832}[/ATTACH]

    C55 still says 0
    [ATTACH=JSON]{"data-align":"none","data-size":"full","title":"image.png","data-attachmentid":3608833}[/ATTACH]​


    I did some measurements again, on X11 V.Line pin (18), I read 3.86V (slightly lower than...
    See more | Go to post

    Leave a comment:


  • yes indeed, there is some circuit driving an optocoupler (HCNR200, one led illuminating 2 photo-leds) which one of the output goes into some opamps for filtering and signal conditioning generating the V.line voltage. That's the voltage I measure @ around 3.89V.
    I'm working on making a schematic of the board, but here's a photo with some annotations.
    - the HCNR200 diode is driven by the LMC6001 opamp. One of the photodiode goes on secondary side for Vline and LineFreq measurements. one photodiode is in the loop gain of the opamp. The opamp input comes from the two resistors below the...
    See more | Go to post

    Leave a comment:


  • ok, so... I was wrong again !
    The Vline is present on the pin header, read ~3.89V. not sure whether or not it's a correct value for ~230VAC, so I tied forcing the voltage to 0V and to 4.5V (after the 10K series resistor, which sits between the header and the cpu AN13 pin) and in all cases the cpu reports error "line voltage low".
    4.5V is the VREF used by the A/D, so it's safe.
    I found a service code that will display the line voltage (C 55) and it always reads "0" no matter what, it's supposed to read the live voltage.

    i was suspecting the internal...
    See more | Go to post

    Leave a comment:


  • Ok, so I have some progress and the machine seems to work. There is still a fault, but should be an easy fix.


    First, yes this I²C waveform has been bothering me for some times and in fact it's thanks to a "mistake" I made while I was trying to understand why the I²C signal was so dirty that I "repaired" the board.

    So, I was poking around the board with a scope while plugin/unplugging the ribbon cables on which the I²C are going (one to the KBD/LCD, one to the main PSU board and one to the opto board) to see which board was causing this....
    See more | Go to post

    Leave a comment:


  • ok, so it seems that the I²C waveform could be a case of reduce de value of the "pull up resistors" according to several information I found here and there.

    I tried to change the value to 5K but nothing changed.
    Then 1K, but at 1K something strange happens: the Low level is not always at the right voltage. Sometime the signal goes down to 0V, sometimes it goes down to ~2V for a low level.
    It seems to me that 2x I²C devices are trrying to "talk" at the same time, and the signal gets jammed. Might be wrong, but I find the waveform suspicious.
    ...
    See more | Go to post

    Leave a comment:


  • Ok, so some progress :you were right about the first error code, it was the opto board.
    Well not the opto board itself, but the cabling.
    I did solder wire directly from the opto board to the cpu board and now the initial fault has gone... but I have a new fault.
    Anyway I carefully cleaned the connectores on both side and re-flown the connector pin header on both boards, the fault did not come back when I removed my wires.. not sure what was the issue here (dirty/corroded connectors or cracked solder joints ?), but I'll take it.

    Anyway there is some progress !!! Now...
    See more | Go to post

    Leave a comment:


  • I did already check the two boards connected to the cpu board which have some form of communication (I²C) :
    - the kbd/lcd has an eeprom, an lcd driver and an 8 bit I/O chip for the kbd, all on I²C bus
    - the opto board hasan I²C eeprom.
    I checked the signals (SDA and SCL) reaches both board. Cant' tell if the eeproms are read by the cpu, but I was able to extract their content, so I guess they're fine.
    I checked the LCD driver, but found no activity, which I believe is normal as the CPU board does not pass the initialization phase (halts on errors with beep codes)....
    See more | Go to post

    Leave a comment:


  • Just in case : I solved the issue, it was the PCH. There were some intermittent contacts with the PCB (cracked solder joints on some of the balls). Especially when the board was hot.

    of course stupid me cracked the PCH die after de-soledring it from the board by dropping it on the floor...
    Gave a shot at some sellers on Aliexpress, and I was lucky enough to receive a working PCH, re-balled it and soldered it, and it's a fix ! no more NVME disappearing for no reasons and no random shutdown when moving the laptop.

    So just in case you have a similar issue, check the...
    See more | Go to post

    Leave a comment:

No activity results to display
Show More
Working...
X