-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Excitations, data and simulation over 500 kHz? #71
Comments
Thank you for your interest one more time GuilleMaese. |
Dear Diego Serrano,
Thank you very much for the clarification. I think that is a strong reason. Nevertheless, please keep us posted in case you decide in the future to modify the setup so that higher frequency characterisation can be performed. It will definitely be a great improvement given the constraints that it carries along with this.
Best regards,
----
Guillermo Salinas López
Power Electronics Designer
Engineering & Technologies - TSPIE
Airbus Crisa
C/ Torres Quevedo, 9
28760 – Tres Cantos (Madrid)
España
De: Diego Serrano ***@***.***
Enviado el: martes, 5 de abril de 2022 16:47
Para: PrincetonUniversity/magnet ***@***.***>
CC: SALINAS LOPEZ, Guillermo ***@***.***>; Author ***@***.***>
Asunto: Re: [PrincetonUniversity/magnet] Excitations, data and simulation over 500 kHz? (Issue #71)
Thank you for your interest one more time GuilleMaese.
We are aware that 500 kHz might be too low for certain applications. However, with the measurement system that we are using, we cannot guarantee the accuracy of the data at very high frequencies, especially for materials with low losses. The problem is we calculate core losses based on direct voltage and current measurements, a technique highly sensitive to delays. Any delay between the voltage and current measurement would be interpreted as losses, and this effect has a larger impact at higher frequencies for any given time delay. We are not planning to change the setup for the measurements; this one does not require hardware changes when measuring different operation points, making it very well suited for automation.
To sum up, to ensure that the quality of the data is maintained, we do not plan to increase the frequency. We will update the FAQ section to clarify this limitation.
—
Reply to this email directly, view it on GitHub<#71 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYD5UOM466HEPOOM32FWGZDVDRG7RANCNFSM5RHOFHQQ>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
This Item has been reviewed and was determined as not listed under Spanish regulation, nor EU export controls, nor U.S. export controls. However, in the case of the item has to be resold, transferred, or otherwise disposed of to an embargoed country, to an end user of concern or in support of a prohibited end use, you may be required to obtain an export license.
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
|
Dear team,
I can see now that all the database, as well as the options you provide, only allows a frequency range from 50 to 500 kHz.
Nevertheless, many applications require frequencies over 500 kHz.
Are you planning to extend your tool for frequencies over 500 kHz (for those materials that can operate over this frequency) ?
Thank you very much!! Keep up the good work.
The text was updated successfully, but these errors were encountered: