Sensors Forum Discussions

I saw in the data sheet documentation that there are three modes of data flow in FIFO. Does each ADC correspond to an RX antenna? If so, is it necessary to restore the data sequence in ADC number order when receiving the 3ADC data stream.

For example: receiving ADC1, ADC2, ADC3, ADC1, ADC2... do you need to revert to ADC1, ADC1,... , ADC2, ADC2,... , ADC3,...

smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/%E9%9B%B7%E8%BE%BE%E4%BC%A0%E6%84%9F%E5%99%A8/BGT60TR13C-FIFO%E6%95%B0%E6%8D%AE%E6%B5%81%E4%B8%AD%E7%9A%84%E6%95%B0%E6%8D%AE%E7%BB%84%E7%BB%87%E9%97%AE%E9%A2%98/td-p/676032

Show Less

Hello everyone, I'm currently working with the SP40 chip for pressure sensors and I'm seeking information regarding its programming. I'm aware that the SP4x_ProgAdapter is widely recommended for programming the sensor. However, I'd like to inquire if anyone has knowledge about the possibility of using third-party programmers for this task. Is there a viable alternative to the SP4x_ProgAdapter for programming the SP40 chip? If so, what other programmers or methods can be used effectively and safely? I would greatly appreciate any shared information or experiences on this matter. Thank you in advance! Show Less

I hope this message finds you well. I'm currently working with the SP40+ chip and exploring its capabilities for a project. I have a query regarding the software functionalities and RF transmission capabilities. Specifically, I'm interested in knowing if the SP40+ chip, through its software interface, supports the transmission of customized strings via RF. Is it possible to send personalized strings such as "location of the tire" and "type of truck" via low-frequency RF transmission? Furthermore, could you provide guidance on whether these strings can be assigned and transmitted via the sensor's microcontroller through software configurations or if there's a specific procedure for transmitting such information via low-frequency RF? Any insights or documentation references regarding these capabilities would be immensely helpful for the project I'm currently working on. Thank you in advance for your assistance and support. Best regards. Show Less

I'm using SP49 example code Low Power Monitoring Code. 

The main function in the code int main(void) does repeat every time we call the library function Lib_State_Low_Power(); and also all global variable values are also automatically set to zero.

What's the reason behind this and please provide solution for it.

Show Less

the original driver writes values to undocumented registers 0x0E, 0x0F & 0x62 (neither in the datasheet for the DPS368 nor DPS310).

See function _xensiv_dps3xx_correct_temperature in xensiv_dps3xx.c (below)

Can anyone tell me anything about this function?

Thank you very much
Thomas

 

 

static cy_rslt_t _xensiv_dps3xx_correct_temperature(xensiv_dps3xx_t* dev)
{
    uint8_t write_data = 0xA5;
    cy_rslt_t rc = _xensiv_dps3xx_reg_write(dev, 0x0E, &write_data, 1);
 
    if (rc == CY_RSLT_SUCCESS)
    {
        write_data = 0x96;
        rc = _xensiv_dps3xx_reg_write(dev, 0x0F, &write_data, 1);
    }
 
    if (rc == CY_RSLT_SUCCESS)
    {
        write_data = 0x02;
        rc = _xensiv_dps3xx_reg_write(dev, 0x62, &write_data, 1);
    }
 
    if (rc == CY_RSLT_SUCCESS)
    {
        write_data = 0x00;
        rc = _xensiv_dps3xx_reg_write(dev, 0x0E, &write_data, 1);
    }
 
    if (rc == CY_RSLT_SUCCESS)
    {
        write_data = 0x00;
        rc = _xensiv_dps3xx_reg_write(dev, 0x0F, &write_data, 1);
    }
 
    return rc;
}

 

 

 

Show Less

I'd like to know how to upload and update the S/W of SP40.

From the Datasheet, it seems that PP0 and PP1 are used to make I2C.

Do I need an MCU to upload and update the S/W to SP40 in this way?

If you need MCU, do you upload and update S/W via Keil C51 and ST-Link?

Is there a way to do it without MCU?(Is there any SP40 S/W upload tool that Infineon provides separately?)

Show Less

 

Show Less

We are excited to announce the release of Radar Development Kit 3.5.1, which is now available for download from the Infineon Developer Center.

 This release introduces a range of new features, improvements, and fixes, and includes the following components:

• Radar SDK v3.5.0
• Radar Fusion GUI v3.5.4
• ifxdaq v4.0.0
• RBB Firmware v2.6.0

Please see below for details on the new features and changes in this release.

New Features:

 

Radar SDK v3.5.0

• General API for Controlling FMCW Radar Devices
  Radar SDK 3.5 introduces a new and versatile general API for controlling FMCW radar devices. The API can accommodate all FMCW-based radar sensors, and it includes a new configuration structure that supports multiple chirp configurations within a single frame.
• Revised Continuous Wave API
  The Continuous Wave API has been revised and is now structured similarly to the FMCW API. To create a Continuous Wave instance, it is no longer necessary to create a device instance and pass it as a parameter. The function call of ifx_cw_create returns a Continuous Wave instance, and the configurations for the ADC and baseband have also been restructured. The previous configuration (ifx_Avian_Config_t) no longer exists.

Radar Fusion GUI v3.5.4

• Support for BGT60UTR11AIP FMCW 60GHz Sensor
  Radar Fusion GUI now supports the BGT66UTR11AIP FMCW 60GHz sensor. This includes sensor configuration, raw ADC data acquisition, and presence sensing application.
• Expert Mode
  An Expert Mode has been introduced for 60GHz FMCW sensors in the Radar Fusion GUI. This mode includes a Timing Model view for the given frame configuration, multiple chirp configurations within a frame, a Difference Deviation plot designed to characterize inter-chirp performance, and a power consumption value display at the status bar for Avian sensors.
• Dummy Sensor Support
  Dummy sensor support is now available for compatible sensors. Users can experiment with sensor configurations and import/export these configurations to the register file, and visualization of timing and power modes for configured chirps.
• Recording of Raw ADC Data
  The recording of raw ADC data format now standardizes to the ifxdaq recording format for FMCW 60GHz Sensors. Raw data is stored in standard .npy format, and meta-data and sensor configs are stored in a separate JSON format. The GUI offers playback of legacy recordings, but any recording from the GUI will be in the new format. A converter in the Recording menu is available to convert legacy recordings to the new format.
• Register Export and Import
  Register export and import options have been included for FMCW devices.
• Presence Sensing App Upgrade
  The presence sensing app has undergone an upgrade with a more robust algorithm. New additions include a separate visualization dedicated to presence sensing, and display of the range of strongest targets alongside presence information.
• Range Spectrogram and Doppler Spectrogram Plots
  New range spectrogram and Doppler spectrogram plots have been added.
• Clipping Detection
  A display indicating clipping detection has been integrated into the status bar. This alert will trigger if the ADC time domain signal exceeds the limits of [-1, +1].

Changes:

• The convention for displaying approaching targets on the positive side of the velocity axis of the range Doppler map has been aligned.
• The range and angle measurement algorithm has been enhanced to achieve detection ranges of over 10 meters.
• Simultaneous visualization of multiple Rx antennas has been added to the Range Doppler Map plot.
• Fix the import of registers in a dummy device mode (reported in v3.5.3)
• Fix the allowed RF frequency range for supported FMCW sensors (reported in v3.5.3)

Thank you for choosing Radar Development Kit!

Show Less

Hi to all, 

I am looking for some reference code or examples that can help me understand how to make the SP49 sensor act as an I2C Slave. Additionally, I am need to know how we can read the SP49 sensor value using an external I2C master controller.

Anyone give me the solution for my issues

Show Less