smanet: Thank you for your response. I agree that clear communication is essential, especially when doing this kind of remote troubleshooting. I have tried to be very specific, giving specific reference designators (i.e PQ809) and the pin numbers. I don't think the problem is clarity in this particular case. Please let me explain.
What I believe has happened to some degree here is that we are talking two different languages. By that, I am not referring to English versus Spanish or anything like that. What I mean is when someone who is just starting out with electronics, or anything else technical for that mater (I believe you said this is the first time you have done this), is communicating with a design engineer, they are often speaking a different language. This is NOT the fault of anybody, it is just design engineers, and probably most engineers, kind of have their own language. I think some examples will help to explain.
Lets take the measurements you took on VREG5 & VREG3. These are the names inside the IC (PU9) assigned by the chip manufactures. Design engineers never, or almost never, use these names. Unfortunately, this caused me to incorrectly associate these with 5VSTBY & 3.3VSTBY instead of LDO5 & LDO3, and resulted, I am sure, in comments I made that did not make sense. Again, this is no ones fault, or if someone is to blame it is ME. I realized this at some point, but much later than I should have. I apologize for that.
Design engineers refer to net names, or signal names if you prefer, and not the names inside the IC. You will notice in the schematic that almost no net name is the same as the name inside the IC. This is because the engineer assigns his/her own net names that make the most sense to them. Often, the names inside the IC do not make sense to the engineer for what they are using it for, and sometimes it has multiple functions, 4 or 5 or more with a long name inside the IC with / in between each name for each function, such as GPIO10/ICS1/AD2 and so on.
So, it helps if you use the net/signal name (net name and signal name are the same thing). So for example, you measured VREG5 (which is connected on PU9, pin 17) you would say "I measured LDO5 across cap PC60". Because the designer here used their nomenclature for naming components, it helps to say what kind of component it is, cap, resistor, diode, etc. Most Engineering places have their own nomenclature, so this just helps to be clearer. A sudo-standard, quite often not followed, is this - U for digital IC, C for cap, R for resistor, D for diode, etc. Here they use PQ for FETs, PU for ICs, PC for caps, etc. If you are measuring across a 2 pin component, then you can simply say "I measured 1.8V across PC60". This is clear enough for the other person to find it if they have the schematic. If not, it helps to give the signal name as designers are often familiar with those, or can figure them out, and what the component is, cap, resistor, IC, etc.
Please let me stress that this is NOT critical of anyone. It is just an explanation of a little of the language engineers speak, or things they are used to hearing. I will also be as specific as I can, but sometimes too much information can be confusing, such as saying "I measured LDO5, VREF5, PU9 pin 17 across PC60, pin 1 to 2". Just saying "I measured LDO5 across PC60", provides all the information needed.
Let me know if you have any questions or something I can help you with. I suspect you will be a while checking all the FETs on page 43, so you probably don't need any more suggestions right now.
Good luck as always.
Omegaman