Infineon 3-Phase Motor Drive EVB with FOC

Table of contents

image

 

{tabbedtable} Tab LabelTab Content
About

This roadtest will test drive a three-phase inverter power stage with half-bridge gate-driver IC based on CoolMOS™ PFD7, the latest Infineon’s SJ technology with fast body diode. It includes a debugger and a fan motor.

 

About the Evaluation Board

This is a complete evaluation board that includes IPN60R1K5PFD7S discrete Superjunction (SJ) MOSFET and 2ED28073J06F gate-driver ICs for motor drives application. Ready-to-use three-phase inverter power stage with 600V blocking voltage - up to 100W. In combination with iMOTION™ controller, the user can run a motor within one hour with a smooth start-up using inductive sensing.

 

The EVAL_DRIVE_3PH_PFD7 is designed to provide easy to use power stage based on Infineon's discrete CoolMOS™ Superjunction MOSFET. The board is equipped with all assembly groups for sensorless field oriented control (FOC). It provides a single-phase AC-connector, rectifier, and three-phase output for connecting the motor. The power stage also contains emitter shunts for current sensing and a voltage divider for DC-link voltage measurement.

gate drive evb

Features

  • Low BOM count due to the CoolMOS™ PFD7 and latest iMOTION™ algorithm
  • Smooth startup using inductive sensing
  • Best light-load efficiency solution
  • Sensorless field-oriented control (FOC)
  • Ease of use with graphical user interface (GUI)

 

Applications

  • Drives
  • Heating
  • Home appliances
  • Household
  • IoT
  • Motor control & drives
  • Power supply (SMPS)
  • Pumps

 

About Debug Probe

It is a functional Isolated Debug Probe, based on SEGGER J-Link Technology. XMC™ Link is an Isolated Debug Probe for all XMC™ Microcontrollers. The debug probe is based on SEGGER J-Link debug firmware, which enables use with DAVE™ and all common third-party compiler/IDEs (Altium Limited, Atollic, ARM/KEIL, IAR Systems, iSystem, Rowley Associates) known from the wide ARM® ecosystem.

debugger

Features

  • 1kV DC functional isolation
  • Debug protocols
  • JTAG
  • Serial Wire Debug (SWD)
  • Serial Wire Viewer/Output (SWV/SWO)
  • Infineon's Single Pin Debug (SPD)
  • Virtual COM Port (UART-to-USB Bridge)

 

About the Fan Motor

An ebm-pabst 3-phase axial fan motor with the following specs.

axial fan motor

image

Additional Information

Important Dates

Enrollment Begin: Apr 11 2021

Enrollment Ends: May 12 2021

RoadTesters Selected: May 26 2021 (estimated)

Product Shipped: May 28 2021

RoadTesting Begins: June 4 2021

Reminder/Update Email:July 5 2021

Submit Reviews By: Sept 20 2021

*The element14 RoadTest Staff will send this reminder/update email.

**If a RoadTester is unable to meet the deadline, please notify the RoadTest Program Lead, , as soon as possible before the deadline.

 

How to locate the official RoadTest review form:  How To Locate the Official RoadTest Review Form (duplicate)

RoadTesters

Terms and Conditions

Infineon 3-Phase Motor Drive EVB with FOC– RoadTest

Terms and Conditions

These are the terms and conditions which govern the Infineon 3-Phase Motor Drive EVB with FOC RoadTest contest. This Contest requires participants to submit an application indicating their previous experience with this type of equipment/component, information on what they would do to test the equipment/component, and the applicant’s desire to post a thorough review of their experience with images, photos, or other supplemental materials. Participants will be required to meet the Conditions for Participation.  The winners of this RoadTest will receive the item(s) listed below. RoadTest Reviews are due no later than 60 days after the receipt of the item(s). No other prizes are offered.

The Principal terms of the Competition:

The following words and phrases are used in these terms and conditions and have the meanings given to them below.

 

Key dates:

Applications Close: midnight (GMT) on May 12 2021

Announcement of Winner (estimated): May 15  2021

Prize: Infineon 3-Phase Motor Drive EVB with FOC

Additional Prizes: none

Competition Site: https://www.element14.com/community/groups/roadtest?ICID=menubar_resources_roadtest

Site or element14 Community: www.element14.com/community

Judges: members of the element14 community team chosen at the Organiser’s discretion.

Judging Criteria, All of the following which will have equal weighting:

· Demonstrated competence with the technologies including links or descriptions of past projects

· Qualifications as indicated by current job role and/or schooling/vocational training;

· A thorough description of how the prize would be tested;

· Likelihood that the Applicant will blog about the prize and provide a review on element14.com;

· Originality;

· Innovation.

Organiser: Premier Farnell plc (registered in England and Wales under company number 876412) whose registered office is at Farnell House, Forge Lane, Leeds, UK

Conditions for Qualification: in addition to meeting the requirements of these terms, all persons applying to take part in the Contest (each one an Applicant) must:

· Provide a RoadTest application describing what he/she would do if awarded the Prize including similar previous projects, product experience and qualifications

Terms: these terms and conditions which govern the Competition and to which the Organiser reserves the right to make changes from time to time and the latest version of these Terms from time to time will be posted to the Site.

  1. Eligibility
  2. Applications:
  3. Selecting Winners:
  4. Liability:
  5. General:

1.1 Save as set out in these Terms, the Contest is open to any natural or legal person, firm or company or group of natural persons or unincorporated body.

1.2 All Applicants must be aged at least 18 at the time of their application.

1.3 Applicants must not enter the RoadTest if doing so or taking part may:

1.3.1 cause the Organiser and/or themselves to be in breach of any agreement (including but not limited to any contract of employment) to which they are a party or in breach of any law, regulation or rule having the force of law to which the Organiser or the Applicant may be subject or any policy of the Organiser or the Sponsor;

1.3.2 Require the Organiser to obtain any licence, authorisation or permission to deal with the Applicant; or

1.3.3 Be in breach of any policy or practice of their employer. Some employers prohibit or restrict their employees from taking part in competitions such as these or receiving prizes under them and the Organiser respects those policies and practices.

The Organiser reserves the right to disqualify any Application made in breach of these Terms and to reject any Application which it reasonably believes may be or become in breach. The Organiser reserves the right to require evidence in such form as the Organiser may reasonably require of any Applicant’s compliance with any of these Terms and to disqualify any Applicant or Participant who cannot provide such evidence reasonably promptly.

1.4 Multiple applications are not permitted.

1.5 Applications may not be submitted by an agent whether acting on behalf of an undisclosed principal or otherwise.

1.6 The Contest is NOT open to:

1.6.1 Any person or entity who is a resident or national of any country which is subject to sanctions, embargoes or national trade restrictions of the United States of America, the European Union or the United Kingdom;

1.6.2 Any employee, director, member, shareholder (as appropriate) or any of their direct families (parents, siblings, spouse, partner, children) (“Direct Families”) of the Organiser and Sponsors; or

2.1 Each Applicant must fully complete and submit a RoadTest Application by the Application Close.

2.2 By submitting a Registration Form, each Applicant:

2.2.1 Authorises the Organiser to use his or her personal data (as defined in the Data Protection Act 1998) for the purposes of running and promoting the RoadTest;

2.2.2 Authorises the Organizer to copy, reproduce and publish their application should they be accepted as a Participant;

2.2.3 Will be deemed to have read, accepted and agree to be bound by these Terms. Applicants are advised to print and keep safe these Terms;

2.2.4 Authorises the Organiser to copy, reproduce and use the Application and/or Review for the purposes of the RoadTest and as otherwise contemplated by these Terms. The Organiser will not be responsible for any inaccuracy, error or omission contained in any reproduction or use of the Project Blogs.

2.2.5 Licenses the Organiser to use the intellectual property in the Project (IP) for the purposes of this Contest. As between the Applicant and the Organiser the IP remains owned by the Applicant.

2.2.6 Grants the Organiser the right to use his or her likeness, photographs, logos, trademarks, audio or video recordings without restriction for the purposes of Contest or the promotion of it or the Site;

2.2.7 Agrees to participate positively in all publicity surrounding the Contest;

2.2.8 Agrees to be responsible for all expenses and costs incurred by him or her in preparing for, entering and participating in the Contest (save for any expenses expressly agreed by the Organiser to be borne by it in these Terms);

2.2.9 Confirms that he or she owns all IP used in his or her application or Project or Blogs and indemnifies the Organiser from any claim by a third party that use of any material provided by an Applicant to the Organiser infringes the intellectual property rights of any third party;

2.2.10 Agrees not to act in any way or fail to act in any way or be associated with any cause or group which would have a negative impact on the reputation of the Organiser and/or the RoadTest.

2.3 All applications submitted to this RoadTest must meet the following criteria:

2.3.1 Applicants must be the author, creator and owner of the proposed review idea. Applicants must not submit someone else’s idea;

2.3.2 The proposed application must be reasonably achievable by the within the time constraints of the Contest;

2.3.3 Applications must not include or propose any of the following, the inclusion of which shall render any proposed application ineligible:

(a) Applications which relate to socially taboo topics, such as illicit drug use or sexual gratification;

(b) Applications that are or could reasonably be considered to be illegal, immoral, discriminatory or offensive as determined by the Organiser;

(c) Applications in relation to them which if accepted would infringe or breach any of the policies or terms of access or use of the Site.

2.4 No Application may contain any of the hazardous substances identified by Article 4 of Directive 2002/95/EC of the European Parliament on the Restrictions on the Use of Substances in Electronic and Electrical Equipment ("the Directive") or the use of such hazardous substances in the in any such Project must not exceed the maximum concentration values set out in the Directive.

3.1 Winners will be selected by the Organiser on the basis of the quality of his or her application and its adherence to these Terms.

3.2 The total number of Winners selected will be at least the minimum number set out above but the actual number is at the sole discretion of the Organizer and/or the Sponsor, if applicable.

3.3 The Organiser will use all reasonable efforts to announce the Winners via an update to the RoadTest page by the date listed above.

3.4 Winners agree to take part in all publicity which the Organiser or the Sponsor wishes to use to promote the RoadTest, the Products featured or other Contests with which the Organiser may be connected from time to time.

3.5 Details of the Winners may also be published in the media.

3.6 Winners are responsible for all applicable taxes, duties or other charges payable in relation to any prize.

3.7

4.1 The Organiser hereby excludes all and any Liability arising out of the Contest or the acceptance, use, quality, condition, suitability or performance of any Prize, even where that Liability may arise from the Organiser’s negligence.

4.2 Nothing in these Terms will affect any Liability of the Organiser for death or personal injury arising from its negligence, for breach of Part II of the Consumer Protection Act 1987 (in the event that any entrant is entitled to claim rights under the Consumer Protection Act 1987) or for any matter in relation to which it would be illegal for the Organiser to exclude or to attempt to exclude its Liability.

4.3 Subject to 4.2, neither the Organiser, any parent company nor any subsidiary of the Organiser or such parent company or any of their directors, officers and employees (together referred to in these terms and the ‘Associates’) makes any guarantee, warranty or representation of any kind, express or implied, with respect to this Competition or the Prizes potentially available under it. Neither the Organiser nor any of its Associates shall be responsible for any Liability that may arise out of or in connection with person’s participation in this Competition, the claiming, redemption or value of any prizes under it, the use or enjoyment of such prizes or any events or circumstances arising out of or in connection with any of them. Any implied warranties of condition, merchantability or suitability or fitness for purpose of any of them are hereby expressly excluded. Wherever used in these Terms, ‘Liability’ shall mean any and all costs, expenses, claims, damages, actions, proceedings, demands, losses and other liabilities (including legal fees and costs on a full indemnity basis) arising directly or indirectly out of or in connection with the matter concerned.

5.1 The RoadTest is organised and sponsored by the Organiser. The Organiser reserves the right to delegate all or any of its powers, rights and obligations arising in relation to the RoadTest to any Associate and certain such rights and powers are assumed by the Organiser on behalf of itself and each Associate. Reference to “Organiser” shall be deemed to include reference to each Associate.

5.2 The RoadTest may be terminated at any time if there are, in the sole opinion of the Organiser, an insufficient number of entries, or if the Applications are not of an appropriate standard for a competition of this nature. The Organiser has the right to cancel or suspend the RoadTest at any time due to circumstances outside its reasonable control.

5.3 The Organiser shall have the sole discretion to disqualify (without correspondence or right of appeal) any Applicant it considers to be adversely affecting the process or the operation of the RoadTest or to be in breach of these Terms or to be acting in a disruptive manner or with intent to annoy, abuse, threaten or harass any other Applicant or Participant.

5.4 The Organiser has the right to amend or add to these Terms from time to time. Revised Terms and Conditions will be posted on the Contest Site and it is a condition of entry to the RoadTest that Applicants agree to comply with these Terms and, if appropriate, such Terms as amended from time to time.

5.5 Headings are for convenience only and do not affect the interpretation or construction of these Terms and Conditions.

5.6 These Terms and the operation of the Contest shall be governed by and construed in accordance with English Law and any claim or matter arising under these Terms shall be subject to the exclusive jurisdiction of the English courts.

Comment List
Anonymous
  • Hi

    I registered the product on infineon website, the "special documentation" is the PCB file and gerber file.
    To register the product you have to use the name of the demoboard "EVAL_DRIVE_3PH_PFD7" and than se second code that you find on the evaluation board.

    I sent an email to the company that produces the fan to send me the parameters of the motor. now I'm waiting for an answer.

    Honestly I'm very disappointed with the kit, it's not userfriendly.

    I tested the motor in the star configuration with 220V AC. Obviously, it doesn't work.

    The motor is sinusoidal (PMSM), if you try to check the voltage on a phase with the oscilloscope and turn the fan by hand, you will see a sinusoidal waveform.
    as soon as I go to the office on Tuesday, share all the acquired data (Ls, Rs, pole pairs ...).

    Roberto

  • I've got around to having the fan on my stand, built the parameter file in MCEWizard from scratch for the IMC101T (with my measurements, and also another with the suggested figures where available in the quick-start), loaded it and I'm getting something similar to what you mentioned - audible noise, only a small "twitch" of the fan blade at the beginning of attempting to start the motor and no spinning. The controller definitely *thinks* the fan is spinning as does the traces from MCEDesigner, but it isn't. The configuration is definitely in hall-less mode. On the upside, it didn't trigger any faults. Measurement of the phases shows that there is a PWM-AC signal at around the intended speed and rather healthy voltage, but obviously the motor start-up sequence was perhaps too quick or didn't catch the rotor. I tried playing with the parking, open loop start-up and low speed thresholds but I still can't seem to get it started. I tried changing the Ref Speed to something slower or faster, but no change. Fan is connected in delta, as suggested by the quick start.

    image

    Did either of you or have any luck getting it spinning? Perhaps my parameter file is not right, or there is something I am missing, or perhaps I will need to dig into the depths of tuning the drive to get it to run. Just for fun, I tried the supplied parameters and didn't see any difference either ...

     

    I'm not sure if any of you tried to register the product on Infineon's website either - I'm getting error messages on registering the product, but it doesn't seem like there is any extra exclusive content for those who register the serial number ... or if there is, I can't seem to access it.

    image

     

    (In the meantime, I hooked it up using some old scrap appliance wire, but found it was copper-clad aluminium and it's falling apart on me ... time to savage another cord and replace it. Just my luck!)

     

    - Gough

  • Not sure if you saw my comment above with regards to the AMD USB controller causing issues - I managed to sort out my issue with changing over to an Intel-based machine.

     

    I was using the firmware you mentioned, and if you examine the parameter file, you'll see it does not match the specifications of the motor (and the parameters claimed in the quick-start). The shipped parameter files seems to be for an 8-pole motor with 0.40A rating, rated speed of 2730rpm and Ke of 36. I re-measured the parameters myself, as I wanted to be sure that the values were correct. Having the wrong values would often result in control issues.

     

    Good to hear you have measured the parameters yourself. I'm just finishing the build for my motor stand so I can safely run the motor without it potentially catching a wire or falling off a table ...

     

    - Gough

  • I used the firmware at this link.

    https://www.infineon.com/cms/en/product/power/motor-control-ics/digital-motor-controller-imotion/imc101t-t038/#!tools

     

    I saw the same things for the parameters. I measure in the lab with LCR meter the value of L and R (are the same on the Infineon datasheet).

    true...for the 230V just with delta connection it is possible to use the FAN.
    https://it.farnell.com/ebm-papst/a2d200-aa02-01/axial-fan-200mm-230vac-ball-bearing/dp/2502079

    I was thinking that the firmware for the EMC101 was already set for this FAN. They use this FAN in their datasheet

  • Just in case anyone else is experiencing failures programming the board firmware with the "Mode is not in application!" error, "Register accesses denied." error, "Error could not send trace request to the remote." and persistent mismatch in firmware versions, I've made a discovery which might be of help.

     

    When debugging using the XMC Link on my AMD Ryzen based system with an X370 chipset, it seems that when the debugger is connected to my USB 2.0 ports, it is "fast" but fails to load the firmware. Plugging it into the USB 3.0 port makes it a lot "slower" and firmware loading is possible, but debugging is very unreliable with timeouts.

     

    Swapping over to an Intel-based chipset machine (a Lenovo E431 from my Tektronix RSA306 RoadTest) running the same build of Windows 10 - everything just works and MCEDesigner throws no such crazy errors. I suspect the reason is because of a J-Link driver issue or hardware compatibility issue with the AMD USB chipset or drivers.

     

    - Gough

  • As I've got many things on my plate (including a parallel RoadTest), I can't say I have the answers, but my impression is that delta should be used given the voltage into the board is up to ~230V nominal. I would use star if the board was 405V 3-phase, but I could be wrong here ... I'm still a relative novice when it comes to motor drives.

     

    As for the motor model, my impression is that you're supposed to use MCEWizard to build the parameter file, answering the necessary questions to inform the controller of the right current limits, rotation rate, Ke, etc. Some of the values are not in the motor datasheet, so having an LCR Meter and oscilloscope should help with determining the right values. If you're really stuck here, I could share my values but I can't guarantee they are right - the default values seem wrong for this motor though.

     

    Could you share what files you used in the MCEDesigner Programmer window? I'm still getting version mismatches and hangs after the firmware programming step, so with that, I couldn't actually command the board because of the claimed mismatch. Admittedly, I've had all of an hour with the board, so troubleshooting hasn't begun in earnest, but I see some of the documentation referencing IMC101T but others referencing IMM101T which is also confusing me since these are two different controllers so software and parameter files are not always interchangeable. The board seems to have "per phase" shunts but some of the IMM101T parameter configurations are set for single-leg (perhaps because the corresponding board has this configuration) but the right selection for this particular board within MCEWizard is still unclear to me because the version I have seems to be newer and the selections do not correspond with the quick start guide.

     

    Thanks,

    Gough

  • The situation is not very clear to me. should the motor be connected in delta and not in star? and then I have to do the whole procedure or is the motor model already parameterized? From the datasheet they used the same engine, I expect it is already parameterized with the default configuration.

    I uploaded the firmware and now I can communicate with the microcontroller.

    I tried to start the motor and something has been happened (noisy sound) but the fan was at a standstill.

  • Let me know how it goes , as so far, I find the "Getting Started" guide to make a lot of incorrect assumptions about file locations/names, and I'm not having any luck getting past the second error despite trying to program firmware and parameters together -

    image

    Of course, then a hard reboot of the board and programmer are necessary to reprogram, but the link here suggests that repeatedly attempting to load the firmware could end up bricking the board - https://www.infineonforums.com/threads/11458-IMM101T046-programming

     

    It seems none of the applications have a "direct" choice to generate a config for this board in particular by name, so we have to wade through a lot of similar-looking model numbers ... I'll try and devote more time to this but I'm afraid that's all I have for today!

     

    - Gough

  • Ahhhh, now I understood the second problem...

    For a random combination I switched on the AC supply, and than I opened the MC Designer.

    But this procedure is not reported on the application note.

    Thanks for you help.

  • Dear ,

     

    I wasn't going to start on the board until I had fixed up the fan motor, but inspired by this posting, I tried to get the software side up and running.

     

    I too encountered this issue when I tried to communicate with the board initially - as I was trying under the expectation that the microcontroller would be powered by the debugger.

    image

    However, for this board, this is not the case. The power required by the controller is supplied from the AC input terminals. Thus you need to provide the AC power directly to the board before starting MCE Designer.

    image

    The communication worked, but a new error cropped up as it detected somehow I had mixed design versions. I haven't looked into it as I only have about 20 minutes before I have to go to work - but hope that you can overcome the communication issue just by providing AC power to the board.

     

    - Gough