↧
DAC5652A: DAC5652A
↧
TIDEP-0091: Maximum range that can be achieved
Part Number:TIDEP-0091
Hello,
What is the maximum distance that can be detected with TIDEP-0091? I have used the default codes for both IWR1443 and MSP432. Standalone IWR1443 BOOST I have tested upto 80m and works nicely. I have designed a horn which filters the RF signals well.
Regards,
Prudhvi Sagar
↧
↧
CC1310: boot with application
Part Number:CC1310
if I want to connect 2 application into one binary build
1st part: the bootloader
2nd part: the empty project
How can I connect the 2 projects into one binary build?
Vitaly
↧
CCS/MSP-EXP432P401R: tirtos - how to start pwm on p2.0 with TIMERA0?
Part Number:MSP-EXP432P401R
Tool/software: Code Composer Studio
By modifying pwmled2_MSP_EXP432P401R_tirtos_ccs example, I have got the P2.0 on-board led dim. What I exactly did is add items in PWMName in MSP_EXP432P401R.h and MSP_EXP432P401R.c by imitating exist ones.
typedef enum MSP_EXP432P401R_PWMName {
MSP_EXP432P401R_PWM_TA1_1 = 0,
MSP_EXP432P401R_PWM_TA1_2,
MSP_EXP432P401R_PWM_TA1_3,
MSP_EXP432P401R_PWMCOUNT
} MSP_EXP432P401R_PWMName;const PWMTimerMSP432_HWAttrsV2 pwmTimerMSP432HWAttrs[MSP_EXP432P401R_PWMCOUNT] = {
{
.clockSource = TIMER_A_CLOCKSOURCE_SMCLK,
.pwmPin = PWMTimerMSP432_P2_1_TA1CCR1A
},
{
.clockSource = TIMER_A_CLOCKSOURCE_SMCLK,
.pwmPin = PWMTimerMSP432_P2_2_TA1CCR2A
},
{
.clockSource = TIMER_A_CLOCKSOURCE_SMCLK,
.pwmPin = PWMTimerMSP432_P2_0_TA1CCR4A
}
};
const PWM_Config PWM_config[MSP_EXP432P401R_PWMCOUNT] = {
{
.fxnTablePtr = &PWMTimerMSP432_fxnTable,
.object = &pwmTimerMSP432Objects[MSP_EXP432P401R_PWM_TA1_1],
.hwAttrs = &pwmTimerMSP432HWAttrs[MSP_EXP432P401R_PWM_TA1_1]
},
{
.fxnTablePtr = &PWMTimerMSP432_fxnTable,
.object = &pwmTimerMSP432Objects[MSP_EXP432P401R_PWM_TA1_2],
.hwAttrs = &pwmTimerMSP432HWAttrs[MSP_EXP432P401R_PWM_TA1_2]
},
{
.fxnTablePtr = &PWMTimerMSP432_fxnTable,
.object = &pwmTimerMSP432Objects[MSP_EXP432P401R_PWM_TA1_3],
.hwAttrs = &pwmTimerMSP432HWAttrs[MSP_EXP432P401R_PWM_TA1_3]
}
};Also, here is my version of pwmled2.c:
/*
* ======== pwmled2.c ========
*/
/* For usleep() */
#include <unistd.h>
#include <stddef.h>
/* Driver Header files */
#include <ti/drivers/PWM.h>
/* Example/Board Header files */
#include "Board.h"
/*
* ======== mainThread ========
* Task periodically increments the PWM duty for the on board LED.
*/
void *mainThread(void *arg0)
{
/* Period and duty in microseconds */
uint16_t pwmPeriod = 3000;
uint16_t duty = 0;
uint16_t dutyInc = 100;
/* Sleep time in microseconds */
uint32_t time = 50000;
PWM_Handle pwm1 = NULL;
PWM_Handle pwm2 = NULL;
PWM_Handle pwm3 = NULL;
PWM_Params params;
/* Call driver init functions. */
PWM_init();
PWM_Params_init(¶ms);
params.dutyUnits = PWM_DUTY_US;
params.dutyValue = 0;
params.periodUnits = PWM_PERIOD_US;
params.periodValue = pwmPeriod;
pwm1 = PWM_open(Board_PWM0, ¶ms);
if (pwm1 == NULL) {
/* Board_PWM0 did not open */
while (1);
}
PWM_start(pwm1);
pwm2 = PWM_open(Board_PWM1, ¶ms);
if (pwm2 == NULL) {
/* Board_PWM0 did not open */
while (1);
}
PWM_start(pwm2);
pwm3 = PWM_open(Board_PWM2, ¶ms);
if (pwm3 == NULL) {
/* Board_PWM0 did not open */
while (1);
}
PWM_start(pwm3);
/* Loop forever incrementing the PWM duty */
while (1) {
PWM_setDuty(pwm1, duty);
PWM_setDuty(pwm2, duty);
PWM_setDuty(pwm3, duty);
duty = (duty + dutyInc);
if (duty == pwmPeriod || (!duty)) {
dutyInc = - dutyInc;
}
usleep(time);
}
}Everything works well and then I wanted to try and dim the P2.0 led with another Timer, and by pressing F3 on PWMTimerMSP432_P2_0_TA1CCR4A, I found:
/*!
* @name Port 2, Pin 0 'pwmPin' setting variations
* @{
*/
#define PWMTimerMSP432_P2_0_TA0CCR1A (PWMTimerMSP432_TA0CCR1 | 0x20) /*!< @hideinitializer */
#define PWMTimerMSP432_P2_0_TA0CCR2A (PWMTimerMSP432_TA0CCR2 | 0x20) /*!< @hideinitializer */
#define PWMTimerMSP432_P2_0_TA0CCR3A (PWMTimerMSP432_TA0CCR3 | 0x20) /*!< @hideinitializer */
#define PWMTimerMSP432_P2_0_TA0CCR4A (PWMTimerMSP432_TA0CCR4 | 0x20) /*!< @hideinitializer */
#define PWMTimerMSP432_P2_0_TA1CCR1A (PWMTimerMSP432_TA1CCR1 | 0x20) /*!< @hideinitializer */
#define PWMTimerMSP432_P2_0_TA1CCR2A (PWMTimerMSP432_TA1CCR2 | 0x20) /*!< @hideinitializer */
#define PWMTimerMSP432_P2_0_TA1CCR3A (PWMTimerMSP432_TA1CCR3 | 0x20) /*!< @hideinitializer */
#define PWMTimerMSP432_P2_0_TA1CCR4A (PWMTimerMSP432_TA1CCR4 | 0x20) /*!< @hideinitializer */So I wondered if I can dim it with Timer0 i.e. with TA0CCR4A. But as long as I replaced this item PWMTimerMSP432_P2_0_TA1CCR4A with PWMTimerMSP432_P2_0_TA0CCR4A. The program will somehow went into the while (1) loop after pwm3 = PWM_open(Board_PWM2, ¶ms); Though I have found the TimerA0 seems not defined in this project and I tried to do that by adding entries in timerMSP432HWAttrs and Timer_config in the MSP-EXP432P401R.c file but things still not work for me. So, how can I generate PWM on the P2.0 pin with TIMERA0? Thanks
↧
CCS/PGA900: PGA900 EVM board have no output signal
Part Number:PGA900
Tool/software: Code Composer Studio
Hi :
I am using XDS200 to do firmware debug. PGA900 EVM board has voltage output on Vout pin.
But it has no output when I do firmware debug.
I can watch that PADC data and DAC_REG all changed with input voltage.(10mv)
But when I measure the Vout pin, it has no output.
here is source code and picture of debug page.
Could you help to check what may cause this problem?
(Please visit the site to view this file)
↧
↧
CCS/CC3220SF-LAUNCHXL: CCS/CC3220SF-LAUNCHXL:
Part Number:CC3220SF-LAUNCHXL
Tool/software: Code Composer Studio
I tried to debug project mqtt_client_CC3220SF_LAUNCHXL_freertos_ccs which is available in resource explorer. Upon debugging, following error message appears:
Error connecting to the target:
(Error -2131 @ 0x0)
Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 8.0.903.2)
Please help me out with this problem.
↧
CCS/TMDXIDK57X-LCD: failed to debug after Linux on microSD boot up
Part Number:TMDXIDK57X-LCD
Tool/software: Code Composer Studio
Hi
I've successfully used code composer studio on my windows PC to debug the board (without microSD) via JTAG. But after I put the microSD with Linux SDK, and let the boot finish, I can't debug with code composer studio anymore. This is the error I get when debugging:
Cortex_M4_IPU1_C0: GEL Output: --->>> AM572x Cortex M4 Startup Sequence In Progress... <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> AM572x Cortex M4 Startup Sequence DONE! <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> AM572x Cortex M4 Startup Sequence In Progress... <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> AM572x Cortex M4 Startup Sequence DONE! <<<---
C66xx_DSP1: GEL Output: --->>> AM572x C66x DSP Startup Sequence In Progress... <<<---
C66xx_DSP1: GEL Output: --->>> AM572x C66x DSP Startup Sequence DONE! <<<---
C66xx_DSP2: GEL Output: --->>> AM572x C66x DSP Startup Sequence In Progress... <<<---
C66xx_DSP2: GEL Output: --->>> AM572x C66x DSP Startup Sequence DONE! <<<---
CortexA15_0: GEL Output: --->>> AM572x Cortex A15 Startup Sequence In Progress... <<<---
CortexA15_0: GEL Output: --->>> AM572x Cortex A15 Startup Sequence DONE! <<<---
CortexA15_1: GEL Output: --->>> AM572x Cortex A15 Startup Sequence In Progress... <<<---
CortexA15_1: GEL Output: --->>> AM572x Cortex A15 Startup Sequence DONE! <<<---
IcePick_D: GEL Output: Ipu RTOS is released from Wait-In-Reset.
IcePick_D: GEL Output: Ipu SIMCOP is released from Wait-In-Reset.
IcePick_D: GEL Output: IVAHD C66 is released from Wait-In-Reset.
IcePick_D: GEL Output: IVAHD ICONT1 is released from Wait-In-Reset.
IcePick_D: GEL Output: IVAHD ICONT2 is released from Wait-In-Reset.
CS_DAP_DebugSS: GEL Output: --->>> CONFIGURE DEBUG DPLL settings to 1.9 GHZs <<<---
CS_DAP_DebugSS: GEL: Error while executing OnTargetConnect(): Target failed to read 0x80031804@APB_View
at (*((unsigned int *) 0x80031804@data)&0x2) [AM572x_dap_startup.gel:244]
at dpll_dbgss_config_board() [AM572x_dap_startup.gel:185]
at OnTargetConnect()
CortexA15_0: Failed to retrieve the Wait in Reset Mode: (Error -6311) PRSC module failed to write to a register. (Emulation package 8.0.903.2)
CortexA15_1: Failed to retrieve the Wait in Reset Mode: (Error -6311) PRSC module failed to write to a register. (Emulation package 8.0.903.2)
CS_DAP_PC: GEL Output: Cortex-A15 1 is not in WIR mode so nothing to do.
CortexA15_0: Error connecting to the target: (Error -6311) PRSC module failed to write to a register. (Emulation package 8.0.903.2)
What should I do?
↧
IWR6843: IWR6843 EDMA
Part Number:IWR6843
Hi,
I would like to understand how EDMA works.
I look at Figure 12-6 pp.1179 of Technical Reference Manual SWRU522C.
I look at code from lab0015_pplcount_68xx dss_data_path.c line 443
EDMAutil_configType1 configured EDMA with following parameters
aCount = 512
bCount = 2
cCount = 1
sourceBindex = 1024
destinationBindex = 0
sourceCindex = 0
destinationCindex = 0
The EDMA is programmed as an "A-Synchronized transfer"
There are two transfers of 512 bytes because bCount is 2.
Is second transfer of 512 bytes have same destination addres as first one because destinationBindex is zero?
Regards,
Gennadii
↧
CC2538: RF designs under TELEC with CC2592
Part Number:CC2538
Our customers are limited by the system and assume the use of both CC2592 and CC2538.
We think that the transmission output as close as possible to 10 dbm is possible by combining the settings.
As a matter of fact, CC2592 is necessary to raise 7db to 10db (in order to cover 3db).
Of course there are also issues such as spurious and noise..
Have you experienced any of the above configurations that meet the RF characteristics defined by the Japanese Radio Law?
We are afraid of vague questions, but we would like advice if there are points that require consideration or attention.
Best regards,
↧
↧
TINA/Spice/CC1310: Non- TI interfacing
Part Number:CC1310
Tool/software:TINA-TI or Spice Models
Since the mentioned TI component is unavailable on simulating device how do we find out which non TI components would go with it?
We wish to interface MQ4, SIM 900A, GPS 6mv2, MPX5050, ACK- Sensor- collision- crash, ADXL345.
Can anyone help us with interfacing?
↧
LAUNCHXL-CC1310: Sending broadcast messages using the TI 802.15.4 stack
Part Number:LAUNCHXL-CC1310
Hi,
I am developing a 802.15.4 network based on the CC1310 MCU and the collector/sensor examples from the resource explorer. I have modified the code so every time a node triggers an alarm, it sends an alarm message to the collector.
This is working fine, but now I want the collector to notify all the other nodes when it receives an alarm notification. Is there some kind of broadcast message that the collector can send to notify all the other nodes?
Can you share any example code about this?
Thanks,
Javi
↧
TUSB9261: TUSB9261 SPI flash
Part Number:TUSB9261
Hi,
I have build up an USB-SATA Interface with SPI flash of Mircochip: SST25VF512A . It will be flashed by the TI Windows Flash Burner tool. But the firmware doesn't start. The TUSB9261 is still in bootloader mode. Does it depend on the internal unchangeable bootloader software inside the TUSB9261 or depends it on the Firmware 1.05 or 1.06?
Br
Bjoern
↧
CCS/MSP-EXP430FR5994: If attempt to step over a MSP430 "CALLA &abs20" function call in CCS 8.3, the debugger seems to free-run rather than stepping over
Part Number:MSP-EXP430FR5994
Tool/software: Code Composer Studio
The TI compiler MSP430 run-time-library contains _lock and _unlock function pointers to be able to insert mutual exclusion. The compiler generates a "CALLA &abs20" instruction to call these function pointers.
Using CCS 8.3.0.00009 with TI MSP430 tool-chain 9.0.1 found that trying to step over calls to such function pointers seems to cause the debugger to free-run until the next breakpoint, rather than stepping over the function call.
Using the attached example which can run on a MSP-EXP430FR5994:
1. Start a debugging session, and set a breakpoint on the line following the first malloc() call:
2. Step into the malloc() call.
3. Step until get to the _lock() call in malloc:
4. Use Step Over, which is expected to step to the text statement in malloc(). However, the Step Over causes the program to run to next breakpoint which was set in the main function:
Is this a bug, or the expected behaviour?
(Please visit the site to view this file)
↧
↧
Linux/TDA2EVM5777: Linking problem
Part Number:TDA2EVM5777
Tool/software: Linux
‘/home/hancan/PROCESSOR_SDK_VISION_03_04_00_00/vision_sdk/binaries/sample_app/tda2xx_evm_linux_all/obj/vision_sdk/tda2xx-evm/ipu2/release/vision_sdk_configuro/osa_mem_map.h’ -> ‘/home/hancan/PROCESSOR_SDK_VISION_03_04_00_00/vision_sdk/links_fw/src/hlos/osa/include/osa_mem_map.h’
# links_a15_algorithm: tda2xx-evm: Compiling algorithmLink_cfg.c
# system: tda2xx-evm: Compiling system_common.c
# system: tda2xx-evm: Compiling system_ipc.c
# links_a15_algorithm: tda2xx-evm: Creating archive links_a15_algorithm.a
# osa: tda2xx-evm: Compiling osa_mem.c
# osa: tda2xx-evm: Compiling osa_remote_log_client.c
# osa: tda2xx-evm: Compiling osa_remote_log_server.c
# system: tda2xx-evm: Creating archive system.a
# osa: tda2xx-evm: Creating archive osa.a
# sample_app: tda2xx-evm: Linking
/home/hancan/PROCESSOR_SDK_VISION_03_04_00_00/ti_components/os_tools/linux/linaro/gcc-linaro-5.4.1-2017.05-x86_64_arm-linux-gnueabihf/bin/../arm-linux-gnueabihf/libc/usr/lib/crt1.o: In function `_start':
/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-linux-gnueabihf/snapshots/glibc.git~linaro~2.21~master/csu/../sysdeps/arm/start.S:119: undefined reference to `main'
collect2: error: ld returned 1 exit status
thank
Shuai
↧
CCS/AWR1642BOOST-ODS: #35 #error directive: "Error: Check the compiler flags: SOC_XWR14XX or SOC_XWR16XX is not defined"
Part Number:AWR1642BOOST-ODS
Tool/software: Code Composer Studio
Hello everyone. I am using an AWR1642BOOST. I want to toggle a GPIO00 using ccs (I haven't bought AWR1642BOOST to toggle gpios, just for getting familiar with arm core). When I add the header:
#include <ti/drivers/gpio/gpio.h>
the error below appears:
Description Resource Path Location Type
#35 #error directive: "Error: Check the compiler flags: SOC_XWR14XX or SOC_XWR16XX is not defined" .ccsproject /AWR1642_EM_test1 line 534, external location: F:\ti\mmwave_sdk_02_01_00_04\packages\ti\drivers\gpio\include\reg_gio.h C/C++ Problem
How can I resolve the problem?
Thanks.
↧
TMS320F28379D: SCI TX / RS-485 Transceiver
Part Number:TMS320F28379D
I am configuring a RS485 two wire multidrop interface using the SCI port. My issue is control of the transceiver. There are no lines from the SCI to control the transceiver so I am wondering how other people solve this issue.
Currently I am using a GPIO to control the transceiver, but it is the disable of the transceiver that is the issue. When using the FIFO, the interrupt is based on the FIFO empty, but there is still a character being clocked out. So you cannot disable the transmitter in the FIFO interrupt when there are no more characters in the FIFO or to be transmitted, but there is still one character to go. The only way to know that the last character has been transmitted is to check SCICTL2.bit.TXEMPTY and I do not see anyway that I can redirect this to a GPIO pin. Obviously this has been solved before, but I cannot find it in the threads.
Thanks John
↧
ADC / DAC at 384k with microprocessor for fft and data management
We are designing an ADC and DAC pair that will allow us to record sound pressures as wav files with a sampling rate around 384k, (16, 32 or 64bits). Linear phase accuracy is important. The ADC is intended as the front end of an embedded system that will process the data in real-time. These systems have a market range betweeen 10k units and 80k units according to several studies. What components (ADC, DAC, microprocessor and literature) would TI engineers suggest we review? Many thanks for your help, Sooch
↧
↧
BQ40Z50-R2: Learning Cycle
Part Number:BQ40Z50-R2
Hi,
I'm having trouble with the learning cycle for some LiFePO4 packs I am working on.
I get up to 4.2.4 of SLUA848, but although RDIS clears, VOK remains set and LStatus at 4, even if I wait 48 hours.
Is this potentially related to the OCVFR flag that is set and if so, what is the 'cost' of bypassing this test to get a rapid QMAX - is it in terms of accuracy?
Any advice on this matter welcomed.
Thank you,
Jeremy.
↧
PMP20497: PMP20497: transformer Pulse PA4826NL datasheets.
↧
CCS/IWR6843ISK-ODS: Overhead People Counting Demo for detected target message
Part Number:IWR6843ISK-ODS
Tool/software: Code Composer Studio
I traced Overhead People Counting Demo souce code, and found something strange for below cases:
1. target info about accX/accY/accZ are assigned with dimension info (ex:targetList->target[n].accX = targetDescr[n].dim[0];)
2. No elements in MmwDemo_output_message_target struct to store dimensions info:depth, width, [height], doppler
3. However, TLV still have the output data for dimx/dimy/dimz
1. target info about accX/accY/accZ are assigned with dimension info (ex:targetList->target[n].accX = targetDescr[n].dim[0];)
2. No elements in MmwDemo_output_message_target struct to store dimensions info:depth, width, [height], doppler
3. However, TLV still have the output data for dimx/dimy/dimz
Task_app.c
MmwDemo_appTask()
{
for(n=0; n<tNum; n++) {
targetList->target[n].tid = (uint32_t)targetDescr[n].uid;
MmwDemo_appTask()
{
for(n=0; n<tNum; n++) {
targetList->target[n].tid = (uint32_t)targetDescr[n].uid;
targetList->target[n].posX = targetDescr[n].S[0];
targetList->target[n].posY = targetDescr[n].S[1];
targetList->target[n].posZ = targetDescr[n].S[2];
targetList->target[n].velX = targetDescr[n].S[3];
targetList->target[n].velY = targetDescr[n].S[4];
targetList->target[n].velZ = targetDescr[n].S[5];
targetList->target[n].accX = targetDescr[n].dim[0]; //refer to Gtrack.h & Mmw.output.h
targetList->target[n].accY = targetDescr[n].dim[1]; //refer to Gtrack.h & Mmw.output.h
targetList->target[n].accZ = targetDescr[n].dim[2]; //refer to Gtrack.h & Mmw.output.h
#ifndef ShortTarget
memcpy(targetList->target[n].ec, targetDescr[n].EC, sizeof(targetDescr[n].EC));
targetList->target[n].posY = targetDescr[n].S[1];
targetList->target[n].posZ = targetDescr[n].S[2];
targetList->target[n].velX = targetDescr[n].S[3];
targetList->target[n].velY = targetDescr[n].S[4];
targetList->target[n].velZ = targetDescr[n].S[5];
targetList->target[n].accX = targetDescr[n].dim[0]; //refer to Gtrack.h & Mmw.output.h
targetList->target[n].accY = targetDescr[n].dim[1]; //refer to Gtrack.h & Mmw.output.h
targetList->target[n].accZ = targetDescr[n].dim[2]; //refer to Gtrack.h & Mmw.output.h
#ifndef ShortTarget
memcpy(targetList->target[n].ec, targetDescr[n].EC, sizeof(targetDescr[n].EC));
targetList->target[n].g = targetDescr[n].G;
#endif
}
}
#endif
}
}
Gtrack.h
typedef struct
{
/** @brief Tracking Unit Identifier */
uint8_t uid;
/** @brief Target Identifier */
uint32_t tid;
/** @brief State vector */
float S[GTRACK_STATE_VECTOR_SIZE];
/** @brief Group covariance matrix */
float EC[GTRACK_MEASUREMENT_VECTOR_SIZE*GTRACK_MEASUREMENT_VECTOR_SIZE];
/** @brief Gain factor */
float G;
/** @brief Estimated target dimensions: depth, width, [height], doppler */
float dim[GTRACK_MEASUREMENT_VECTOR_SIZE];
typedef struct
{
/** @brief Tracking Unit Identifier */
uint8_t uid;
/** @brief Target Identifier */
uint32_t tid;
/** @brief State vector */
float S[GTRACK_STATE_VECTOR_SIZE];
/** @brief Group covariance matrix */
float EC[GTRACK_MEASUREMENT_VECTOR_SIZE*GTRACK_MEASUREMENT_VECTOR_SIZE];
/** @brief Gain factor */
float G;
/** @brief Estimated target dimensions: depth, width, [height], doppler */
float dim[GTRACK_MEASUREMENT_VECTOR_SIZE];
} GTRACK_targetDesc;
Mmw.output.h
typedef struct MmwDemo_output_message_target_t
{
/*! @brief tracking ID */
uint32_t tid;
/*! @brief Detected target X coordinate, in m */
float posX;
/*! @brief Detected target Y coordinate, in m */
float posY;
float posZ;
/*! @brief Detected target X velocity, in m/s */
float velX;
/*! @brief Detected target Y velocity, in m/s */
float velY;
float velZ;
/*! @brief Detected target X acceleration, in m/s2 */
float accX;
/*! @brief Detected target Y acceleration, in m/s2 */
float accY;
float accZ;
#ifndef ShortTarget
/*! @brief Target Error covarience matrix, [3x3 float], in row major order, range, azimuth, doppler */
float ec[16];
float g;
#endif
} MmwDemo_output_message_target;
typedef struct MmwDemo_output_message_target_t
{
/*! @brief tracking ID */
uint32_t tid;
/*! @brief Detected target X coordinate, in m */
float posX;
/*! @brief Detected target Y coordinate, in m */
float posY;
float posZ;
/*! @brief Detected target X velocity, in m/s */
float velX;
/*! @brief Detected target Y velocity, in m/s */
float velY;
float velZ;
/*! @brief Detected target X acceleration, in m/s2 */
float accX;
/*! @brief Detected target Y acceleration, in m/s2 */
float accY;
float accZ;
#ifndef ShortTarget
/*! @brief Target Error covarience matrix, [3x3 float], in row major order, range, azimuth, doppler */
float ec[16];
float g;
#endif
} MmwDemo_output_message_target;
For the document -Overhead_People_Tracking_and_Stance_Detection_users_guide.pdf, it says dimx/dimy/dimz are the target size in x/y/z dimension.
Seems need to update overhead People Counting Demo sample code for such issue..
↧