Part Number: BOOSTXL-PGA460
I have developed a pcb with a pga460 and all the stuff needed to generate a burst. I have got the datapath from this new pcb and I want to customize the threshold levels. I have tried to load my datapath to the memory dump screen to see it on my threshold window but I can't.
Is this possible?
In reply to Akeem Whitehead:
Thank you Akeem.
I do have EVM. but we want to deploy a large batch of units on field and we would want to ask those units the datapath so we can adjust at any time the threshold and tvg (through wifi/lora/zigbe...). It would be great if you could modify the GUI to allow us to do that. We are not in a hurry right now, so next week sounds amazing.
In reply to Pablo Martinez80:
Hello Akeem, have you had the time to check the GUI's improvements?
I have a couple of questions related to the PGA460 but I couldn't find an email to write to yo directly nor a private message on the forum.
I wonder if there is a double transducer version of the evaluation board. We have tested the BOOSTXL-PGA460 board and it works great but now we need to measure lower distances and because of the decay time we have with the one transducer solution we are unable to detect distance lower than 25 cm (give or take).
We want to test https://e2e.ti.com/support/sensor/ultrasonic/f/991/t/595974
2 sealed due to the nature of our device. Is this possible? anything we should keep in mind while designing pcb or software?
Hi Pablo, The latest version of the GUI (184.108.40.206) will be available on the web tomorrow since TI.com refreshes overnight. To load the echo data dump generated by the GUI onto the threshold or TVG pages, navigate to either of the pages, and click on the new "Load Chart" button in the bottom right corner of the page. If you do not need the TVG or threshold, you can always use the already available Echo Data Dump plotter from the menu bar (File --> Echo Data Dump Plotter) to load previous echo data dump recordings. Both the echo data dump plotter and load chart features require the data format to match what is typically exported from the GUI. Regarding the dual transducer configuration, you can use the EVM to test this feature. We typically refer to a dual transducer configuration as bi-static, whereby a single PGA460 device uses a separate transducer to transmit and another transducer to receive. To modify the PGA460-Q1 EVM's daughter card for bi-static mode, follow the instructions from FAQ #4.4.5 "How do I enable the daughtercard to use a bi-static transducer pair (a separate transmitter and receiver)?"at: www.ti.com/.../slaa733 The software is not impacted by mono-static or bi-static operation. Only the hardware must be altered. A single Murata MA58MF14-7N can detect as low as 10cm in transformer drive mode. You'll need to update daughtercard's R38 from 2.7kOhm to 10.0kOhm, and C15 from 1500pF to 680pF. If you need less than 10cm, then a bi-static solution may be required. If you do not need a long range (1-2m), you can also use a single high-frequency transducer (180-450kHz), which can detect down to 3-5cm.
Thank you Akeen, I will test the new GUI as soon as it is available.
Do you know any 480Khz sensor we could test? I have been looking for a part number to buy some but I couldn't find anything good.
We will make the modifications in EVM to test dual transducer.
I just tested the new version. But I am not able to display any of my saved memory dump. I try creating new ones (files contains data) but when I try to display them, I see a black chart. Could you check this? I unninstalled previous GUI version.
I see you added ambient temperatue. Could you tell me how to get that? Is there a formula? Just an offset? It would be great for us to have that, we could remove our temperature sensor in that case
I see where we went wrong with datadump. We are trying to introduce inside the GUI the values we get from the uart command "get echo datadump". It returns values in hex format and we created a file like the one you get when you hit datadump memory on the GUI. We load that file onto the board connected to the gui and nothing happens. We have the same problem when we load our file on the button you added. Because it is not the same kind of file structure.
This is what we want to add:
;GRID_DATADUMP_MEMSPACE80 (DATA_MEM_0),EC81 (DATA_MEM_1),FF82 (DATA_MEM_2),FF83 (DATA_MEM_3),FF84 (DATA_MEM_4),FF85 (DATA_MEM_5),FF86 (DATA_MEM_6),FD87 (DATA_MEM_7),FF88 (DATA_MEM_8),FF89 (DATA_MEM_9),FF8A (DATA_MEM_10),FF8B (DATA_MEM_11),FF8C (DATA_MEM_12),FF8D (DATA_MEM_13),FF8E (DATA_MEM_14),FF8F (DATA_MEM_15),E990 (DATA_MEM_16),B491 (DATA_MEM_17),FA92 (DATA_MEM_18),FE93 (DATA_MEM_19),E394 (DATA_MEM_20),5695 (DATA_MEM_21),3996 (DATA_MEM_22),5497 (DATA_MEM_23),5498 (DATA_MEM_24),3C99 (DATA_MEM_25),189A (DATA_MEM_26),199B (DATA_MEM_27),1D9C (DATA_MEM_28),1D9D (DATA_MEM_29),1B9E (DATA_MEM_30),129F (DATA_MEM_31),0AA0 (DATA_MEM_32),07A1 (DATA_MEM_33),06A2 (DATA_MEM_34),05A3 (DATA_MEM_35),04A4 (DATA_MEM_36),02A5 (DATA_MEM_37),02A6 (DATA_MEM_38),02A7 (DATA_MEM_39),02A8 (DATA_MEM_40),02A9 (DATA_MEM_41),01AA (DATA_MEM_42),02AB (DATA_MEM_43),02AC (DATA_MEM_44),02AD (DATA_MEM_45),02AE (DATA_MEM_46),03AF (DATA_MEM_47),03B0 (DATA_MEM_48),03B1 (DATA_MEM_49),06B2 (DATA_MEM_50),07B3 (DATA_MEM_51),06B4 (DATA_MEM_52),08B5 (DATA_MEM_53),09B6 (DATA_MEM_54),09B7 (DATA_MEM_55),08B8 (DATA_MEM_56),07B9 (DATA_MEM_57),06BA (DATA_MEM_58),05BB (DATA_MEM_59),04BC (DATA_MEM_60),03BD (DATA_MEM_61),03BE (DATA_MEM_62),02BF (DATA_MEM_63),02C0 (DATA_MEM_64),03C1 (DATA_MEM_65),08C2 (DATA_MEM_66),11C3 (DATA_MEM_67),13C4 (DATA_MEM_68),12C5 (DATA_MEM_69),0CC6 (DATA_MEM_70),09C7 (DATA_MEM_71),06C8 (DATA_MEM_72),06C9 (DATA_MEM_73),06CA (DATA_MEM_74),06CB (DATA_MEM_75),03CC (DATA_MEM_76),02CD (DATA_MEM_77),02CE (DATA_MEM_78),01CF (DATA_MEM_79),02D0 (DATA_MEM_80),02D1 (DATA_MEM_81),02D2 (DATA_MEM_82),02D3 (DATA_MEM_83),02D4 (DATA_MEM_84),02D5 (DATA_MEM_85),01D6 (DATA_MEM_86),02D7 (DATA_MEM_87),02D8 (DATA_MEM_88),02D9 (DATA_MEM_89),02DA (DATA_MEM_90),02DB (DATA_MEM_91),03DC (DATA_MEM_92),03DD (DATA_MEM_93),03DE (DATA_MEM_94),02DF (DATA_MEM_95),01E0 (DATA_MEM_96),01E1 (DATA_MEM_97),01E2 (DATA_MEM_98),02E3 (DATA_MEM_99),02E4 (DATA_MEM_100),02E5 (DATA_MEM_101),02E6 (DATA_MEM_102),01E7 (DATA_MEM_103),01E8 (DATA_MEM_104),01E9 (DATA_MEM_105),20EA (DATA_MEM_106),50EB (DATA_MEM_107),51EC (DATA_MEM_108),43ED (DATA_MEM_109),2BEE (DATA_MEM_110),26EF (DATA_MEM_111),23F0 (DATA_MEM_112),1BF1 (DATA_MEM_113),10F2 (DATA_MEM_114),0DF3 (DATA_MEM_115),19F4 (DATA_MEM_116),20F5 (DATA_MEM_117),26F6 (DATA_MEM_118),25F7 (DATA_MEM_119),22F8 (DATA_MEM_120),38F9 (DATA_MEM_121),37FA (DATA_MEM_122),23FB (DATA_MEM_123),18FC (DATA_MEM_124),0EFD (DATA_MEM_125),0DFE (DATA_MEM_126),0DFF (DATA_MEM_127),12EOF
Could be possible to add this as it is? Or your file with values in hex format? That would be enough. In other case we should have to change every value before adding it to the file. Besides that, your file has only 127 measures instead of the 128 the datadump returns. Is this ok?
I update with a comment. Would be possible to display the chart as a line instead as bars? It is easier to see the line with thresholds and time varying gain
We have done further tests. We think we have a problem with the burst number. We have tested the configuration you suggested with the R38 10K and C15 680pF with the murata sensor and the closest we get is 19cm. Could you please give us the configuration you used to get 10cm?
On the other hand, we have a strange issue.We have configured the device to fire 10 bursts. We have connected an oscilloscope to the test pin (analog front end output) and what we see is:
*Channel1 x 1. AFE Voltage.
*Channel2 x 10. Transducer voltage.
Why do we have longer oscillation between burst and decay time?
I think this is our problem with sorter distances. Our datapath have a very long blind area:
Besides that, I attach you our current configuration for the murata sensor so you can test it and tell us what we are doing wrong.
;GRID_USER_MEMSPACE00 (USER_DATA1),0001 (USER_DATA2),0002 (USER_DATA3),0003 (USER_DATA4),0004 (USER_DATA5),0005 (USER_DATA6),0006 (USER_DATA7),0007 (USER_DATA8),0008 (USER_DATA9),0009 (USER_DATA10),000A (USER_DATA11),000B (USER_DATA12),000C (USER_DATA13),000D (USER_DATA14),000E (USER_DATA15),000F (USER_DATA16),0010 (USER_DATA17),0011 (USER_DATA18),0012 (USER_DATA19),0013 (USER_DATA20),0014 (TVGAIN0),BA15 (TVGAIN1),9916 (TVGAIN2),9917 (TVGAIN3),1018 (TVGAIN4),E819 (TVGAIN5),361A (TVGAIN6),FC1B (INIT_GAIN),C01C (FREQUENCY),8C1D (DEADTIME),001E (PULSE_P1),0A1F (PULSE_P2),0120 (CURR_LIM_P1),6A21 (CURR_LIM_P2),FF22 (REC_LENGTH),3223 (FREQ_DIAG),0024 (SAT_FDIAG_TH),EE25 (FVOLT_DEC),7C26 (DECPL_TEMP),8F27 (DSP_SCALE),0028 (TEMP_TRIM),0029 (P1_GAIN_CTRL),012A (P2_GAIN_CTRL),012B (EE_CRC),8340 (EE_CNTRL),0041 (BPF_A2_MSB),8B42 (BPF_A2_LSB),4D43 (BPF_A3_MSB),F344 (BPF_A3_LSB),7245 (BPF_B1_MSB),0646 (BPF_B1_LSB),4747 (LPF_A2_MSB),7C48 (LPF_A2_LSB),D349 (LPF_B1_MSB),014A (LPF_B1_LSB),974B (TEST_MUX),204C (DEV_STAT0),804D (DEV_STAT1),005F (P1_THR_0),3760 (P1_THR_1),5461 (P1_THR_2),6862 (P1_THR_3),9963 (P1_THR_4),9964 (P1_THR_5),9965 (P1_THR_6),FF66 (P1_THR_7),D067 (P1_THR_8),2068 (P1_THR_9),0069 (P1_THR_10),026A (P1_THR_11),246B (P1_THR_12),2C6C (P1_THR_13),2D6D (P1_THR_14),2D6E (P1_THR_15),076F (P2_THR_0),8870 (P2_THR_1),8871 (P2_THR_2),8872 (P2_THR_3),8873 (P2_THR_4),8874 (P2_THR_5),8875 (P2_THR_6),8476 (P2_THR_7),2177 (P2_THR_8),0878 (P2_THR_9),4279 (P2_THR_10),107A (P2_THR_11),807B (P2_THR_12),807C (P2_THR_13),807D (P2_THR_14),807E (P2_THR_15),007F (THR_CRC),F5EOF
I can update the GUI to display the Load Chart values as lines, rather than bars. The format you're requesting could be accommodated, but the short term fix may be for you to develop a converter, which accepts the text file as you've generated, and creates a new text file in the format required by the Load Chart feature. The problem with the hex only amplitude is that there is no time reference, so it would be impossible to align the echo data dump to the threshold and TVG profiles without knowing the preset record time length. The next GUI update/release won't be for another few weeks, so the text convert workaround is recommended. You are correct in that the echo data dump should have 128 bytes, but the GUI and load chart feature always expect 127.
Regarding 10cm detection using the Murata MA58MF14-7N, I reviewed your configurtion, and have a few recommendations.
Note, 10cm detection occurs in the decay profile. Use of the ultrasonic measurement results with proper threshold mapping is required to detect 10cm.
•Set your Digital Gain SR Gain to x1. It is currently x2, which is why the echo data dump shows a saturated decay.
•Set Preset 1 Burst Pulses =4 and Driver Current Limit = 100mA. For comparison, set Preset 2 Burst Pulses = 16 and Driver Current Limit = 400mA.
•You may need to further reduce the AFE Gain Range to 32-64.
•Tighten the Band-Pass Filter Bandwidth to 2 or 4 kHz.
I'll need to dig up the full register configuration, but your results should appear as follows:
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.