Part Number:TIDM-1019
I recently purchased an eval board for the MSP430FR6047 Low Cost Water Meter. This board has the MSP430 marked with a REV B sticker. This leads me to believe that this eval board has the REV B silicon. Additionally, the eval board came pre-loaded with firmware (unknown version) that when used with the Ultrasonic Sensing Design Center (version 02_20_00_15) worked amazing well. I was able to change the USS configuration on the eval board and was able to achieve roughly 0.5% accuracy on our customer spool piece from 0.2 to 33 GPM using 2Mhz transducers. The USS is truly a well made product.
Unfortunately, at some point when we were trying some changes to the parameters of the USS on the eval board, the eval board started reporting error code 255, which the Design Center Software said was an unknown error. At this point we tried to recovered by programming in a saved configuration which we knew was working, but it would no longer function.
So, I then went out to the TI website and downloaded the firmware project for the eval board (version 02_20_00_04 as found in main.c with USSlib_02_20_00_15 found in ussSwLib.h)
I imported the project into CCS verison 8.3.0.00009 and was able to successfully compile, program, and debug/run the firmware.
At this point the eval board was working again (although the settings were incorrect so the display, but I again needed to change some of the values in my USS settings, so I opened up the Design Center tools and began to tweak settings to get the ultrasonic interface to work.
Now, with the above mentioned versions of PC-GUI and eval board firmware, I get an error message and the TX/RX stops running.
The error message is as follows:
SAPH, Error Code 7, Turn on ADC Count value is invalid or less than 40uSec.
According to the Eval boards quick start guide, a valid value is 5,000 ns, i.e. 5 uSec. So this message doesn't make sense to me.
So my question is why did this just start happening when I downloaded and programmed firmware into the eval board?
And why does the eval appear to function at a 'gap between pulse start and ADC capture' of 27uS (Turn on ADC Count Value of 5,000) and then not work when set to 26uS (again Turn on ADC Count VAlue of 5,000)?
Our target for the 'gap' is 15uS