Part Number: PGA460-Q1
We have the PGA460-Q1 Eval module and everything works perfectly for our application. We are trying to watch the RX and TX serial data that the PC sends and receives to the Eval board. We can clearly see the 55 and all RX and TX waveforms on the scope. We use a simple 3.3V to RS-232 converter to watch the hex data on a serial monitors. The data is random 00 FF 0C.... but we cannot determine the baud rate that the EVM is using.
I know that it autobauds on the 55 but our serial monitor cannot auto baud.
What is the Baud rate when the EVM does all of the register transfers and Commands? 115k, 9.6K... do not seem to work.
In reply to peter mccormick:
In reply to Pradeep Kumar R:
In reply to Akeem Whitehead:
Hello akeem whitehead
i just continued further testing with two transducers on default thresholds of case 0 as in sample program.
good news is i found right for the object at 2.22 meters
not so good news is am also finding stray values as in screenshot and the sequence continuesly repeats until anther stray value of 10.84 after which i do not either 2.22 or other stray values. In fact it remains 10.84 need guidance on what i may be doing wrong.
I am able to run the EEPROM bulk read command without the initial six-byte error. Here is a screen shot showing what the respond should look like when running the command via the GUI. Notice that the first byte should read out as 0x40, which represents the diagnostic byte with no errors reported from the last UART transaction. Do you also receive 0x40 as your first response byte when running the bulk EEPROM read command, and after (subsequent command)?
How are you writing the first six bytes of the user EEPROM space? Are you using the bulk EEPROM write command? If so, send me the master transmitted sequence you are sending for the bulk write.
When using a bi-static transducer configuration, the threshold does not need to consider the decay profile or time, and can be set more linearly.
The "stray" values could be a result of the echo barely being strong enough to trigger an object detection capture, you are not clearing the serial buffer between commands, the serial read is too fast and corrupting the time-of-flight data, or you are not allowing enough time to pass between burst+listen commands. If not already, please refer to the latest version (1.0.2) of the PGA460 Energia library which helps to improve the ultrasonic measurement result stability by adding additional margin to the serial read time.
We tried using 2 transducers hoping that there we could have objects much closer than about 30mm. The second transducer seems to "hear" the transmitting transducer so you really don't save much. We had much better success by finding a transducer that has low ringing time instead of using 2 transducers. I obviously don't know your application and am not a TI employee expert but thought this might be helpful.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.