Part Number: MSP430FR50431
Hello,
I'm using this thread as a way to reach anybody tied to the USS library development, who could help our team finally make our product reliable in long-term.
In the last year we have manufactured several hundreds of water flowmeters based on MSP430FR50431 and provided USS library. At the beginning we had quite massive issues with its algorithm not being able to lock onto proper lobe in UPS or DNS and therefore providing wrong flowrate values. After many weeks of trial-and-error development we came up with somewhat reliable way to calibrate our flowmeters, however we still have to hand-tune about 25% of them, because all our processes and assumptions are empiric and not supported by any hard evidence that the USS library in fact works the way we assume.
During our work we constantly tried our best to understand the logic behind USS library operation, this was however made very difficult due to ambiguous or completely missing documentation of important configurable parameters and overall lack of logical connection between datasheets (which describe principles) and source codes. Our latest attempt to understand the principle of dTOF calculation using correlation ended in statement that this part is confidental, see following:
We've based our project on MSP430FR50431 and provided USS library, because they seemed an ideal solution, unfortunately in our current situation we're losing large amounts of development time trying to estimate, what might work. If the core functional principle of USS library is proprietary and also acts erratically in certain situations without any further indications, it becomes a problem for us to the point we're starting to consider solutions based on completely different software/hardware despite the obvious loss of all previous development time.
At this point we would really like to acquire full source codes for the USS library to finally find solution to our problems. Me and my CEO/project manager have made several attempts to get in touch with TI employees, who might have the answer for us, unfortunately it never got through. We're very well aware that it would also probably void any further technical support, but we're willing to try this way.
Thanks in advance for any message that would assist us.
Best regards
Antonin Stepan
