The Unified Theory Of Electrical Machines By C.v. Jones Pdf 'link' -
The Unified Theory of Electrical Machines C.V. Jones represents a landmark in electrical engineering pedagogy by providing a single mathematical framework for analyzing diverse machine types. First published in 1967, it refined and popularized the Generalized Machine Theory originally pioneered by Gabriel Kron. Open Library Core Principles of the Unified Theory
Extension of Gabriel Kron: Jones’s work is an extension of Gabriel Kron's non-Riemannian dynamics, which used tensor notation to write voltage and current equations for a wide class of machines.
- Primitive machine voltage equations:
v = Ri + L di/dt + ω_r G i - Torque equation:
T_e = ½ i^T (∂L/∂θ_r) i + i^T G i(simplifies toT_e = i^T G ifor constant L) - Park’s transform (3-phase to dq0):
f_dq0 = K f_abcwhere K = 2/3 * rotation matrix - Power invariance condition:
P_abc = P_dq0requires proper scaling of K (Jones uses power-invariant form)
Disclaimer: This article does not host or link to copyrighted PDFs. Always respect intellectual property. The Unified Theory Of Electrical Machines By C.v. Jones Pdf
4. Alternative Modern Books Covering the Same Unified Theory
If you cannot find Jones’s book, these cover the same unified theory (often better):
3. How to Study This Book Effectively (Without Getting Lost)
This is a dense, math-heavy text. Do not read it like a novel. The Unified Theory of Electrical Machines C
For the modern power engineer, renewable energy specialist, or PhD candidate: C.V. Jones’s unified theory is your Rosetta Stone. Find the PDF, work through the matrices, and unlock the singular elegance of the rotating field.
The Core Philosophy: One Machine, Many Masks
The defining feature of Jones’ work is right there in the title: Unification. Primitive machine voltage equations: v = Ri +
Modern Relevance: While written decades ago, this theory remains the mathematical backbone for modern Finite Element Analysis (FEA) and digital simulations of complex drive systems used today. Structure of the Text
Hi!
thanks for the detailed post. I’m facing an issue that isn’T listed here and wonder if you would have an idea.
When signing in the wizard, I get :
a managed service account with name “” could not be set up due to the following error, unexpected error while searching for MSA: specified directory service attribute or value does not exist.
in the log, it looks like this.
ODJ Connector UI Error: 2 : ERROR: Enrollment failed. Detailed message is: Microsoft.Management.Services.ConnectorCommon.Exceptions.ConnectorConfigurationException: Unexpected error while searching for MSA: The specified directory service attribute or value does not exist.
I believe I have all the requirements check… I tried to pre-create a gMSA account, set it to the service, no luck. On different servers as well, with or without the OU specified in the XML…. nothing budge…
Any idea is more than welcomed!
thanks
Jonathan – SystemCenterDudes
Hi Jonathan – great question, and you’re definitely not alone on this one.
That specific error is a bit misleading, but the key part is “error while searching for MSA” rather than creating it. In the cases I’ve seen, this usually points to an Active Directory lookup issue, not a missing requirement in Intune itself.
A few things that are not the root cause (even though they feel like they should be):
Pre-creating a gMSA (unfortunately unsupported by the connector at the moment)
The OU specified (or not specified) in the XML
Setting the service to run under a manually created account
The most common things I’d double-check instead:
Managed Service Accounts container
Make sure the “Managed Service Accounts” container exists at the domain root and is readable. The connector explicitly queries this container, and if it’s missing, hidden, or permissions are restricted, you’ll get exactly this error.
Schema visibility
Verify that the AD schema attributes for managed service accounts (for example msDS-ManagedServiceAccount) exist and are fully replicated. I’ve seen this break in domains that were upgraded in-place or restored at some point.
Domain controller selection / replication
The connector doesn’t let you choose a DC. If it’s hitting a DC where schema or container replication hasn’t completed yet (or a different site), the MSA lookup can fail even though “everything looks correct”.
Permissions beyond create
Even if the installing admin can create MSAs, make sure they also have read permissions on the Managed Service Accounts container and schema objects. Hardened AD environments sometimes block this unintentionally.
One important note: right now, the connector expects to create and manage the MSA itself. Pre-creating a gMSA or assigning it manually tends to make things worse rather than better.
If you check those areas and still hit the issue, I strongly suspect this is an edge-case bug in the new MSA discovery logic introduced with the updated connector. Hopefully we’ll see clearer documentation or a fix in an upcoming build.
Hope this helps – let me know what you find