MSP430FR6047: inaccuracy in negativ flow direction with template_example

Hello Jace,

thank you for the reply.

Which values would they need? I expect that just examples of my measured flow are not too helpful and I already sent Leo the value list of all intern parameters. I do not really have more data that I can tell you. I am just a bit confused because A A8 realized the same problem.

Did you test the template_example software with the calibration headers that are generated by the GUI? In this configuration I get problems. The uncalibrated template_example gives the same results in both directions.

Thanks for your help
BR, Kathrin

Hello,

The flow data is what was requested. 

Hi Jace,

ok. So would you be so kind to look at my code to find the error? It is certainly no hardware problem because with the Water_Demo project everything works fine and also with the uncalibrated template_example (headers are originally from TI, not from my values in the GUI).

I now compared the two versions of the USS_UserConfig.h, the original one and the one I got from the GUI. The huge difference is that the original one works in USS_PULSE_MODE_MULTI_TONE and mine in USS_PULSE_MODE_SINGLE_TONE. Therefore I have different values at USS_F1_FREQ, USS_NUM_OF_TRILL_PULSES and probably some other values.  What are the effects of these differences?
Of corse I have more flow ranges in USS_meterVFRCalibFlow.h.

Would you give me a place where I can upload the headers without sending it to everyone? Then you could test the code again with my headers and see if they are working in both directions.

BR,

Kathrin

I now tried to adapt my header that it also works with mode_multi_tone. I got an error message that this mode would not be available for devices without SAPH_A module. Obviousely the MSP430FR6047 is able to work in multi_tone. So what do I have to adapt for the SAPH-module? Is there a data sheet that explains steps like this? I found something in the family_guide but it does not tell me where I can find all these values.

On the other side it would be helpful to have an overview over the meaning of all defines of the USS_UserConfig.h. Is there a file that gives me these informations?

I also realized that the values in USS_UserConfig.h sometimes  are given with an f at the end of the number in the original version. What does it stand for? In my header versions I only have normal numbers or with an exponent at the end.

BR, Kathrin

Kathrin Honermann said:

I also realized that the values in USS_UserConfig.h sometimes  are given with an f at the end of the number in the original version. What does it stand for?

Floating point literals with a f suffix are single precision, whereas floating point literals without the suffix are double precision. The difference can affect the precision used for floating point calculations; on a MSP430 double precision calculations take more code and more time than single precision calculations.

Without checking how the floating point literals in USS_UserConfig.h get used not sure on the effect of single .vs. double precision floating point literals.

Thank you, this was the answer I needed

Hi Jace,

Thanks, I will search for the defines and parameters in the API Guide. Still there are not all mentioned in it. I will ask for them separately when I need to.

I have got a MSP430FR6047 which seems to only have SAPH registers. So why does the original code work in multi-tone mode? I sent you the link to my headers in a private chat. I expect that someone will soon find time to look at it and compare it to your working code.

Best regards,
Kathrin

Hi Jace,

thank you for the feedback. Of corse this is not satisfying for me. Especially because I am not the only person with this problem.
I will do my best in debugging it myself.

I wish you a nice Christmas time.

Best regards,
Kathrin