element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
RoadTests & Reviews
  • Products
  • More
RoadTests & Reviews
RoadTest Forum Feedback regarding a companies comments on user expectations
  • Blog
  • RoadTest Forum
  • Documents
  • RoadTests
  • Reviews
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join RoadTests & Reviews to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 21 replies
  • Subscribers 2563 subscribers
  • Views 1560 views
  • Users 0 members are here
  • RoadTest
  • feedback
  • s12zvml-minikit
Related

Feedback regarding a companies comments on user expectations

kas.lewis
kas.lewis over 5 years ago

Hello All,

 

I was looking to get some connect regarding feedback I received from NXP regarding my review of their motor control eval platform. As I do not wish to sway sentiment one way or the other I will leave my comments for after receiving some feedback from the community. I would very much appreciate you open honest comments on both my review as well as the response to this review.

 

Thanks

Kas

 

The review can be found here, the company response/commnet can be found below.

 

 

Hello,

I'm really glad that there is some feedback on the product. I'm not going to comment on the documentation, but I'd like to give you some comments on the technical matter.

Just a general introduction: personally, I have studied electric drives at the university, I have done my PhD in related field and I have intensively worked with sensorless motor control for 4 years now. Even after that I cannot say that I fully understand AC electric drives. And the same you can hear even from established professors - the more you know, the less you understand (or the more you realize how much you don't understand).

Just to clarify, the S12ZVML-MINIKIT is a tool, which helps educated people to start with a very basic application, which is based on widely known field-oriented control (PMSM) or six-step/block commutation (BLDC). If one doesn't understand how FOC works, I agree it would be very difficult to understand the application. On the other hand, 10 minutes of reading some quick start guide cannot replace 2 semesters and more of electric drives course. I agree that there are gaps in linking the documentation, which is already available, even dedicated to another product, but using the same approach. Normally (if a link is provided correctly) you would follow this document: https://www.nxp.com/docs/en/application-note/AN4912.pdf  or this one https://www.nxp.com/docs/en/application-note/AN4642.pdf. The AN5327 https://www.nxp.com/docs/en/application-note/AN5327.pdf  is providing information on the FOC control implementation, however, it's worth to look for more info, even a basic one at 3-Phase PMSM Control Workshop with NXP's Model-Based Design Toolbox or some external sources.

My feeling is, that customers expect to have a mobile flight simulator game experience and with that background, to fly a real aircraft with the same results. Maybe an exaggerated statement, but many times not so far from the real expectations.

 

Why this product is not so easy to use? The application itself has to be open enough to be used by professionals and that has been successful so far. Our experience is, that even if there are some generic use cases, many electric drives have to be threaten case by case. Making a super-generic application can do a good job with a specific demo motor, but especially in automotive applications, more fine-tuning and maybe some additional algorithms need to be added. EDIT: Therefore, any "smart feature" simplifying the user experience would make it hard or even impossible to add these advanced features.

For a new-bee, a motor is just spinning, slow or fast, left or right and that is good enough. For a professional, low acoustic noise, high efficiency or high dynamics make the difference.

 

Ad SOFTWARE

From your testing, I can see that you are not familiar with the open-loop start-up sequence of sensorless drives. Why? Your sensorless settings are using 200 RPM as the Mergin speed 1 and the same setting for Merging speed 2. In the default settings, these are set to 150 RPM and 300 RPM. There are also some other settings changed especially in the speed loop control, which may cause an unexpected behavior. If this was the test case, then it was an example of misused settings. It would be fair to mention that random tuning of random values and expecting the application to run perfectly fine is just not the approach an engineer would do with such a development platform.

Testing the application at 100 RPM indicates that you are forcing the application to run in the region it was not designed for. In model-based sensorless operation, the field-oriented control works with BEMF observer roughly from 10% of the base (nominal) speed. In the MCAT, sensorless operation starts from the Merging speed 2, which is 200 RPM by your setting. Below this speed, the motor is designed just to speed up, not to operate continuously. And I would be very careful about saying that 200 RPM is perfect - based on my personal experience with the Linix motor, it would be at least 250 RPM, but it depends on the current limit, load and speed ramp. Errors thrown during the tests within the open-loop to sensorless transition are most likely connected to wrong settings of the open-loop start-up and the BEMF observer itself. There are many articles at IEEE Xplore covering this topic, in summary: even after years of research, there is no generic solution that works for all the motors. If certain setting works for one, it most likely will not work for other motors. And we are working on a solution which covers as many cases as possible.

 

Ad HARDWARE

It's worth to say that S12ZVML-MINIKIT is dedicated to automotive low-cost applications. It demonstrates how an application would look like in terms of almost minimal configuration for up-to 10 Amps of current (for sure, the on-board debugger is not intended to be part of the final application). There is also S12ZVM EVB or the devkit (MTRCKTSPNZVM128|Development Kit S12 MagniV | NXP ), which is probably the one you would be looking for, if more I/O pins and features are needed.

 

Thank you for the review, I believe it will rise some action items on our side.

  • Sign in to reply
  • Cancel

Top Replies

  • DAB
    DAB over 5 years ago +3
    Hi Kas, I agree with Shabaz, you did a very good review and the response from NXP did not dispute your findings. The response did correctly point out some of the science and engineering issues with the…
  • colporteur
    colporteur over 5 years ago +3
    The companies response doesn't make a good first impression. It reminds me of an instructor chastising students for doing poorly on an exam. It not the instructors fault they did poorly. The students had…
  • neuromodulator
    neuromodulator over 5 years ago +3
    Communicating with the product company is always a good idea. I've so far roadtested 2 products. One company didn't respond my email but the other did and was quite helpful. They even gave me access to…
  • Jan Cumps
    Jan Cumps over 5 years ago in reply to neuromodulator

    Yes - in that case I say that an NDA is needed to work with the device. It makes a difference.

     

    edit: and in that case I don't blog about the device. I don't write about a device where I had to sign an NDA for.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • neuromodulator
    neuromodulator over 5 years ago in reply to Jan Cumps

    Unless its an "open" device, there is always going to be info that's missing...

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • Jan Cumps
    Jan Cumps over 5 years ago in reply to neuromodulator

    That is true.

    I talk about closed devices if I can use them without NDA.

    Once I have to sign an NDA to get something working that does not work without that info, I stop talking about it in public. No issue using it for private/company designs.

    It's a choice.

     

    edit: that's the reason why I never blogged about two TI CC3xxx WiFi microcontrollers that they sent me.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • neuromodulator
    neuromodulator over 5 years ago in reply to Jan Cumps

    Well most of the released stuff can be used with readily available info, otherwise the product is a failure. No point on releasing a product that nobody can figure out how to use. Was that TI micro a prerelease?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Jan Cumps
    Jan Cumps over 5 years ago in reply to neuromodulator

    Yes, it was a pre-release. But I only got informed I needed an NDA when trying to use it. Not when they asked me to review it.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • neuromodulator
    neuromodulator over 5 years ago in reply to Jan Cumps

    It's a common practice to provide pre-releases under NDA. They probably don't want competitors to get an edge on unreleased products

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Gough Lui
    Gough Lui over 5 years ago

    I have read your review and the response comprehensively. It seems that your review did raise a number of issues, all of which I would think are valid observations especially for those who have never used this particular kit or combination before.

     

    From my point of view, the response you received while perhaps a bit unpolished, is the exact kind of candid response that I often appreciate. It pays to look beyond the way the thoughts are expressed and see what is trying to be conveyed. From my reading, I feel that the response:

    • acknowledges that it can be difficult to understand motor control theory (and that's one reason I haven't dived into such RoadTests myself).
    • acknowledges that their documentation is perhaps not as complete as it could be, while also providing a counterpoint that it is not intended to teach the user the fine art of motor control as it is something of a "dark art".
    • provides some hints as to other documentation which might be relevant (but I didn't assess whether it is helpful or not).
    • explains that the item is perhaps more targeted towards professionals that might have a better idea as to what all the parameters may mean.
    • provides a counterpoint that having the additional parameters is a feature especially in the case of professionals with demanding motor drive requirements.
    • attempts to explain some of the unexpected behaviour and possible remedies.
    • provides a justification as to product positioning, with an alternative product in case of greater needs.
    • acknowledges that some changes may be necessary.

     

    I do think the expression may be slightly poor or be misinterpreted as defensive/blaming the user, but this is something I've come to worry about less and less as many may not have English as their first language and really intend to be helpful rather than confrontational. But it's also quite likely that this particular contact within the company may also be willing to have a more rapid back-and-forth communication into the future as things change or new questions arise.

     

    This is contrasted to cases where I may have a RoadTest with technical issues and end up contacting them via their marketing team playing "gatekeeper", such that every single problem report takes two weeks to turnaround as an official investigation is launched, a report is written, solutions are discussed and then someone has to draft an e-mail back to me with the absolute minimum of details in the hopes they won't accidentally admit fault. Incidentally, those companies that have this kind of workflow often can "lose" the clarity of the reports and replies as they pass through many hands and are "corrupted" by careful ass-covering. Just my 2c.

     

    - Gough

    • Cancel
    • Vote Up +3 Vote Down
    • Sign in to reply
    • Cancel
  • colporteur
    colporteur over 5 years ago in reply to Gough Lui

    Your benevolent perspective of the vendors response is one way to placate the reader. There are two points in your response that raise my ire.

     

    P1: "It seems that your review did raise a number of issues, all of which I would think are valid observations especially for those who have never used this particular kit or combination before."

    P2: "It pays to look beyond the way the thoughts are expressed and see what is trying to be conveyed."

     

    Why does P1 entitle the vendor a pass? My investigation didn't uncover any knowledge limits or expectations that could be used by the reader. I didn't find the disclaimer that indicated "If you find this information is incomplete or inconsistent you must be a novice and don't have sufficient knowledge to be using it". Other than understanding acronyms, how would higher learning have changed the inconsistencies of QUICK Start Guide references?

     

    I am reluctant to condone the approach you suggested in P2 because it requires a subjective approach.  What effective protocol standard permits the transmitter to send what ever they feel like and leave it up to the receiver to interpret what is received?

     

    Justin Halpern wrote a book called Shi#! My Dad Says using quotations made by Halpern's father, Sam, regarding various subjects. After I read the book, I thought, this is stuff I would like to say but something in my understanding of social order tells me it is not appropriate. Something in the message motivated kas.lewis  to ask for feedback from the group. I speculate he perceived a tone in the message that didn't align with what he felt was appropriate. I read the review before reading the vendor comments. I then read the vendors comments and felt something I labelled as dismissive.

     

    Now I could use your P2 suggestion and try and find the good in the message. Unfortunately my teeth are long in technology careers and find the suggestion demeaning and requires me to feel contrite. It is formula for acceptance or acquiesce. The alternate interpretation offered by the vendor, I find is not appropriate and I am not willing to give them a pass.

     

    I believe the RoadTest review program offers great value to vendors for minimal investment on there part. I believe my perspective is standing up for the program. I respect your commentary but remain with a dissenting opinion. 

     

    Sean

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • Jan Cumps
    Jan Cumps over 5 years ago in reply to colporteur

    For me, as non-native English speaker it sounds dismissive too. Talking down.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • Gough Lui
    Gough Lui over 5 years ago in reply to colporteur

    colporteur  wrote:

    Why does P1 entitle the vendor a pass?

    To be fair, I never said it did. I always provide feedback to manufacturers in my RoadTests which even include itemised lists of errors in documentation. Poor documentation can cause safety issues, can destroy products and can waste time - I would agree that quality documentation and support is very important for development-type products.

     

    I had only expressed it in the way I did to make clear that some of the perceived issues (e.g. with the number of bewildering parameters and options) would not in itself necessarily be a problem for someone who may be a professional in motor drives. It was not meant to be understood as giving a vendor a free pass to leave things in its status quo.

     

    If you go and buy yourself a Porsche, you won't expect the manual to include a complete guide to high-performance driving ... likewise, there are reasonable limits to be expected for some of these things, and from my perspective, this will vary depending on the purchaser's existing level of familiarity with the class of products and the field. This kit is not targeted at people like myself who know absolutely nothing about motor drives - but as to whom it actually targets, this is more "implied", hence I acknowledged the validity of the observations up-front.

     

    colporteur  wrote:

    I am reluctant to condone the approach you suggested in P2 because it requires a subjective approach.

    In my younger days, I would have said the same. In an ideal world, communication would be precise and concise with no room for ambiguity, but unfortunately, that's often not the case. I was blind to this before, but I guess, the more I take to reading other people's work and writing my own, the more I begin to appreciate the greys and try to ensure that I don't write something that would be too easily misinterpreted. After all, to be human is to embrace the subjectivity of life, even though it is something that (as an engineer) I find difficult at times.

     

    But sometimes, it's all about making sure you have some thick skin and sleep well at night. There are more important things than the polish on a few words. I've met some Chinese vendors in the past who had a very terse, confrontational response, but this was because they were not able to communicate effectively in English, relying on phrase-books and online translators. Without any non-verbal cues, intent can be quite hard to judge, but I'm defaulting to presume the best rather than the worst.

     

    Instead, I find that every communication is a chance to open a dialogue (for better or for worse) - in fact, the regime we live in is basically what you have described just there. I can write whatever I feel like I mean, but depending on your command of the language (and even the ever-changing definition of the language), your interpretation may well differ. This is often why there are so many lawsuits and legal loopholes, as the spirit of the law and the letter of the law often differ. I think even in that case, the legal precedent is often to respect the spirit of the law as intended. That's why dialogue is important as it offers an opportunity to elaborate and clarify the communication. It's part of the reason why comments can be so valuable to any posting.

     

    It pays to remember that sometimes the conflicts that happen are not intended - merely by a misunderstanding in communication. But to wage war would be an unproductive effort for both sides.

     

    colporteur  wrote:

    Unfortunately my teeth are long in technology careers and find the suggestion demeaning and requires me to feel contrite.

    [...]

    I respect your commentary but remain with a dissenting opinion. 

    Very much in the same vein, I completely understand your feelings and respect your opinion, as this was one that I myself have had in the past. Sometimes, to be contradicted so directly could be considered a wound to your pride. I know if it was directed to myself rather than someone else, I might have had that immediate reaction on the first read. Often, I will sit on things for a while, as the first knee-jerk reaction may not always be the right one. But I found that it was ultimately unproductive in terms of my own sanity and health, and put up a barrier between myself and the other party involved, so I often acquiesce and compromise. I have been accused of being a push-over ... so I guess that's just part of my character.

     

    As an academic researcher, I've come to realise how insignificant I am in the grand scheme of things. I can only do my best effort - but from there, what is taken and what is "left behind" is not up to my choosing. But then again, it's not my prerogative to influence - merely provide my opinion, whatever it is worth. At the end of the day, perhaps even this response might not be useful to anyone ... but I felt that I would be remiss if I didn't at least take the opportunity to explain the philosophy behind my benevolent character is for my own benefit as well. Life has enough worries already ... no need to add more.

     

    - Gough

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Cancel
<>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube