• State TI Thinks Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 738 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

EVM430-FR6047: Water meter error increase as the test progress

Kim GyeoungHyun
Prodigy 80 points
Part Number: EVM430-FR6047


Hello.

I have some trouble measuring water with EVM430-FR6047.

Calibration, test overview, question are in the PDF file and test result is in Excel file.

Test overview.pdftest result.xlsx

Please, check the PDF file and reply the comment.

Thank you for your help,

Kim

  • 0
    TI__Mastermind 25435 points

    Hi Kim,

    I will forward your thread to USS expert and ask his comments on your requirement.

    B.R.

    Sal

  • 0
    TI__Mastermind 46765 points

    Hi Kim,

    There are some thoughts that causes the EVM #3 does not perform as expected. 

    The first thing need to check is the power supply. It is recommended to use external power supply for the EVM board to get the best performance. 

    You can supply the power from block 1. And turn the switch to EXT in block 2. Then remove the VCC jumpers in block 3. 

    For the temperature aspect, I do not think only a 2 degC change will cause this kind of effect. The ADC-based approach is insensitive to temperature. 

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 80 points

    Thanks for the reply.

    I changed the power of EVM #3 from ezFET to External, using 3.63V battery.

    I calibrate EVM #3 again with battery and test with EVM #1, #2. 

    (EVM #3 Configuration, Calibration parameters)

    Fullscreen 0285.USSConfig.xml Download 
    <?xml version="1.0" encoding="UTF-8"?>
<ussMspGui>
	<settings>
		<isLogging>true</isLogging>
		<logLocation>C:\Users\PNC\USS_02_40_00_00\USSWorkspace\USS_Project</logLocation>
	</settings>
	<configParams>
		<target>water</target>
		<board>EVM430-FR6047</board>
		<device>MSP430FR6047</device>
		<lph_gpm>lph</lph_gpm>
		<f1f2>1000.0 1060.0</f1f2>
		<patternSeq>0</patternSeq>
		<gapBetweenPulseAndCapture>50.0</gapBetweenPulseAndCapture>
		<numberOfPulses>25.0</numberOfPulses>
		<gapBetweenUpsAndDns>3000.0</gapBetweenUpsAndDns>
		<gapBetweenDnsAndUps>1000.0</gapBetweenDnsAndUps>
		<gainControl>-2.3</gainControl>
		<areaConstant>20275903.57</areaConstant>
		<xt2Freq>8000</xt2Freq>
		<sigSamplingFreq>4000.0</sigSamplingFreq>
		<adcSamplePulse>20</adcSamplePulse>
		<deltaTOFOffset>0.0</deltaTOFOffset>
		<absTOFAdditionDelay>0.0</absTOFAdditionDelay>
		<captureDuration>40.0</captureDuration>
		<intrplCorrTableSize>2</intrplCorrTableSize>
	</configParams>
	<devModeParams>
		<param1>0</param1>
		<param2>3.0</param2>
		<param3>10000.0</param3>
		<param4>5000.0</param4>
		<param5>0.0</param5>
		<param6>0.0</param6>
		<param7>120.0</param7>
		<param8>11.0</param8>
		<param9>3.0</param9>
		<param10>0.0</param10>
	</devModeParams>
	<configCalibParams>
		<maximumVFR>10000.00</maximumVFR>
		<calculateTemp>0</calculateTemp>
		<minTempLUT>5</minTempLUT>
		<maxTempLUT>60</maxTempLUT>
		<tempResLUT>1.000</tempResLUT>
		<transducerLen>9.432</transducerLen>
		<calibType>1</calibType>
	</configCalibParams>
</ussMspGui>
     
    Fullscreen 8637.USSVFRCalibFlowConfig.xml Download 
    <?xml version="1.0" encoding="UTF-8"?>
<ussCalibration>
	<version>1.00</version>
	<dataFlowUnit>L/h</dataFlowUnit>
	<calibrationRanges>7</calibrationRanges>
	<range>
		<id>1</id>
		<minFlow>0.000</minFlow>
		<errorThreshold>0.00</errorThreshold>
		<calibrationPoints>3</calibrationPoints>
		<data>
			<id>1</id>
			<expectedVFR>0.0000</expectedVFR>
			<meanVFR>-0.1153</meanVFR>
			<id>2</id>
			<expectedVFR>3.2440</expectedVFR>
			<meanVFR>4.3373</meanVFR>
			<id>3</id>
			<expectedVFR>6.5095</expectedVFR>
			<meanVFR>8.0017</meanVFR>
		</data>
	</range>
	<range>
		<id>2</id>
		<minFlow>7.000</minFlow>
		<errorThreshold>0.00</errorThreshold>
		<calibrationPoints>3</calibrationPoints>
		<data>
			<id>1</id>
			<expectedVFR>8.4189</expectedVFR>
			<meanVFR>10.1455</meanVFR>
			<id>2</id>
			<expectedVFR>10.2742</expectedVFR>
			<meanVFR>12.1565</meanVFR>
			<id>3</id>
			<expectedVFR>12.4007</expectedVFR>
			<meanVFR>14.3894</meanVFR>
		</data>
	</range>
	<range>
		<id>3</id>
		<minFlow>13.000</minFlow>
		<errorThreshold>0.00</errorThreshold>
		<calibrationPoints>3</calibrationPoints>
		<data>
			<id>1</id>
			<expectedVFR>14.4295</expectedVFR>
			<meanVFR>16.4033</meanVFR>
			<id>2</id>
			<expectedVFR>16.4800</expectedVFR>
			<meanVFR>18.4784</meanVFR>
			<id>3</id>
			<expectedVFR>19.3662</expectedVFR>
			<meanVFR>21.1548</meanVFR>
		</data>
	</range>
	<range>
		<id>4</id>
		<minFlow>20.000</minFlow>
		<errorThreshold>0.00</errorThreshold>
		<calibrationPoints>3</calibrationPoints>
		<data>
			<id>1</id>
			<expectedVFR>30.6394</expectedVFR>
			<meanVFR>31.8979</meanVFR>
			<id>2</id>
			<expectedVFR>75.7244</expectedVFR>
			<meanVFR>76.4399</meanVFR>
			<id>3</id>
			<expectedVFR>120.4258</expectedVFR>
			<meanVFR>122.0083</meanVFR>
		</data>
	</range>
	<range>
		<id>5</id>
		<minFlow>150.000</minFlow>
		<errorThreshold>0.00</errorThreshold>
		<calibrationPoints>3</calibrationPoints>
		<data>
			<id>1</id>
			<expectedVFR>200.1954</expectedVFR>
			<meanVFR>201.7119</meanVFR>
			<id>2</id>
			<expectedVFR>348.7140</expectedVFR>
			<meanVFR>346.5391</meanVFR>
			<id>3</id>
			<expectedVFR>498.3533</expectedVFR>
			<meanVFR>487.9363</meanVFR>
		</data>
	</range>
	<range>
		<id>6</id>
		<minFlow>630.000</minFlow>
		<errorThreshold>0.00</errorThreshold>
		<calibrationPoints>3</calibrationPoints>
		<data>
			<id>1</id>
			<expectedVFR>696.1972</expectedVFR>
			<meanVFR>677.9516</meanVFR>
			<id>2</id>
			<expectedVFR>825.3148</expectedVFR>
			<meanVFR>806.2225</meanVFR>
			<id>3</id>
			<expectedVFR>995.6155</expectedVFR>
			<meanVFR>974.1740</meanVFR>
		</data>
	</range>
	<range>
		<id>7</id>
		<minFlow>1030.000</minFlow>
		<errorThreshold>0.00</errorThreshold>
		<calibrationPoints>3</calibrationPoints>
		<data>
			<id>1</id>
			<expectedVFR>1494.8916</expectedVFR>
			<meanVFR>1450.7101</meanVFR>
			<id>2</id>
			<expectedVFR>2422.1926</expectedVFR>
			<meanVFR>2337.7398</meanVFR>
			<id>3</id>
			<expectedVFR>3045.0359</expectedVFR>
			<meanVFR>2887.3047</meanVFR>
		</data>
	</range>
</ussCalibration>

    EVM #1, #2 were tested in the same environment as before. (using ezFET power)

    This is the Test result.

    test result 2.xlsx

    Unlike EVM #1 and #2, EVM #3 looks unstable.

    Thank you for your help,

    Kim

  • 0 in reply to Kim GyeoungHyun
    TI__Mastermind 46765 points

    Hi Kim,

    The flowrate at 16LPH seems unstable on the #3 board. I would suggest to run some test to figure out if this issue is related to the EVM board or the pipe and transducer or the test position on the test bench. 

    First, only switch the EVM #2 and #3 board. It can role out if it is related to the board. 

    Then, switch the pipe position of the #2 and #3 pipe with transducer. It can tell if this issue is related to the position or the pipe. 

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 80 points

    Hello 

    Thanks for the reply.

    I switch only EVM #2 and #3, And I calibrate and test EVM with battery.

    test result 3.xlsx

    Despite calibration & testing EVM #2, #3 at the same time, EVM #2 (with pipe #3) test results were not good.

    There seems to be a problem with the #3 pipe or the position, so I will change the pipe or change the position in next test.

    But I have a question.

    Before I test iteration #1 10L/h VFR, EVM #2 (with pipe #3) Delta ToF was around -200 and 1L/h VFR, even thought zero flow rate.

    And it effected the iteration #1 test result.

    So I reconnected battery and 5pin(laptop), Delta ToF changed to around -50 and 0 VFR.

    As the Delta ToF and test results seems strange, Delta ToF offset might be changed during calibration.

    And when I remove VCC jumpers to use EVM with battery, I didn't remove GND jumper because EVM can't connect to USS GUI without it.

    Please check if I did anything wrong.

    And always, thank you for your help.

    Kim.

  • 0 in reply to Kim GyeoungHyun
    TI__Mastermind 46765 points

    Hi Kim,

    Okay. Try remove these four jumpers. If the noise is coming through the GND pin, then try with a different laptop, or a different USB port. 

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 80 points

    Hello

    Thanks for the reply.

    As your recommendation, I test without jumpers and test with different laptop, USB port.

    Test result is in here.

     

    Delta ToF Test.pdf

    Please, check the PDF file and reply the comment.

    Thank you for your help,

    Kim

  • 0 in reply to Kim GyeoungHyun
    TI__Mastermind 46765 points

    Hi Kim,

    The zero flow condition can effect the water measurement. If it is around 1LPH at zero flow, it will brings 10% error at 10LPH. 

    So, the issue is not solved by removing the jumpers and changing the laptop. And we have tested before that EVM#2 is normal with #2 pipe. This error only shows on #3 pipe now. I would assume this issue is caused by the transducer now.

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 80 points

    Hello, Thanks for the reply.

    I test with the other transducers. (different product)

    Please check this PDF file and reply.

    Change Transducers.pdf 

    test result 5.xlsx 

    Fullscreen 4718.USSConfig.xml Download 
    <?xml version="1.0" encoding="UTF-8"?>
<ussMspGui>
	<settings>
		<isLogging>true</isLogging>
		<logLocation>C:\Users\PNC\USS_02_40_00_00\USSWorkspace\USS_Project</logLocation>
	</settings>
	<configParams>
		<target>water</target>
		<board>EVM430-FR6047</board>
		<device>MSP430FR6047</device>
		<lph_gpm>lph</lph_gpm>
		<f1f2>1000.0 1060.0</f1f2>
		<patternSeq>0</patternSeq>
		<gapBetweenPulseAndCapture>50.0</gapBetweenPulseAndCapture>
		<numberOfPulses>25.0</numberOfPulses>
		<gapBetweenUpsAndDns>3000.0</gapBetweenUpsAndDns>
		<gapBetweenDnsAndUps>1000.0</gapBetweenDnsAndUps>
		<gainControl>0.1</gainControl>
		<areaConstant>20210199.10</areaConstant>
		<xt2Freq>8000</xt2Freq>
		<sigSamplingFreq>4000.0</sigSamplingFreq>
		<adcSamplePulse>20</adcSamplePulse>
		<deltaTOFOffset>0.0</deltaTOFOffset>
		<absTOFAdditionDelay>0.0</absTOFAdditionDelay>
		<captureDuration>40.0</captureDuration>
		<intrplCorrTableSize>2</intrplCorrTableSize>
	</configParams>
	<devModeParams>
		<param1>0</param1>
		<param2>3.0</param2>
		<param3>10000.0</param3>
		<param4>5000.0</param4>
		<param5>0.0</param5>
		<param6>0.0</param6>
		<param7>120.0</param7>
		<param8>11.0</param8>
		<param9>3.0</param9>
		<param10>0.0</param10>
	</devModeParams>
	<configCalibParams>
		<maximumVFR>10000.00</maximumVFR>
		<calculateTemp>0</calculateTemp>
		<minTempLUT>5</minTempLUT>
		<maxTempLUT>60</maxTempLUT>
		<tempResLUT>1.000</tempResLUT>
		<transducerLen>9.432</transducerLen>
		<calibType>1</calibType>
	</configCalibParams>
</ussMspGui>

    Thank you for your help

    Kim.

  • 0 in reply to Kim GyeoungHyun
    TI__Mastermind 46765 points

    Hi Kim,

    What is the ADC capture looks like? I do not remember if you have sent ADC captures before. 

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 80 points

    The ADC capture looks like this with the above parameters.

  • 0 in reply to Kim GyeoungHyun
    TI__Mastermind 46765 points

    Hi Kim,

    This ADC capture looks okay to me. But you can also try with set numberOfPulses as 12. and sigSamplingFreq at 3600. 

    Check if it will improve the result. 

    There is one more points we need to check is the position #3. All the issues data for know happens on the position #3. We need to check on this point. 

    Best regards,

    Cash Hao

**Attention** This is a public forum