• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 30 subscribers
  • Views 974 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

IWRL6432: How to save motion-detected processed data when using L6432 Visualizer

IWRL6432BOOST: Saving XYZ coordinates using the Visualizer dedicated to IWRL6432BOOST

Aimane
Prodigy 10 points
Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: IWRL6432

Hello TI Support,

I've seen in a locked thread entitled " IWRL6432: How to save motion-detected processed data when using L6432 Visualizer " that saving the Visualizer's data was expected to be available this month (March) for IWRL6432. I didn't find any further informations about it.

If it's available, could you please tell me how to save XYZ coordinates ? Otherwise, when will it be available ?

Thank you in advance.

Best Regards,

Aimane

  • 0
    TI__Mastermind 20651 points

    Hello Aimane, 

    The toolbox release has been delayed slightly, we expect the release to happen in the coming weeks. Other than that, I'm afraid we don't have any examples for saving data with the IWRL6432. 

    The closest example that I could point you towards would be the parsing scripts in SDK 3 (for previous generation devices). The scripts allow you to provide a raw UART log then the data is parsed and saved to a CSV file. Note, these scripts will not work for the IWRL6432 without some modifications due to differences in UART output. Let me know if this is something you would be interested in.

    Best Regards,

    Josh 

  • 0 in reply to Josh Dye
    Prodigy 10 points
    Josh Dye said:
    Let

    Hello Josh,

    I've already started checking the parsing scripts of SDK 3. I've also managed in parellel to retrieve UART output but I've encountred some difficulties to analyze the frames when I compare them to the Frame Header and TLV schemes. I'm interested in working on this before the Toolbox release.

    Best Regards,

    Aimane

  • 0 in reply to Aimane
    TI__Mastermind 20651 points

    Hi Aimane,

    Understood. I think it would help you to look at the additional documentation in the demo implementation guide (MMWAVE_SDK_05_01_xx_xx/docs/MotionPresenceDetectionDemo_documentation.pdf). Section 12 contains information regarding UART output. 

    What difficulties are you facing currently? 

    Best Regards,

    Josh

  • 0 in reply to Josh Dye
    Prodigy 10 points

    Hello Josh,

    Most frames that I've retrieved from UART output have a size between 6 and 8 bytes but I should get more bytes for each frame normally. Do you have any idea about it ?

    Best Regards,

    Aimane

  • 0 in reply to Aimane
    TI__Mastermind 20651 points

    Hi Aimane,

    The size of the UART output each frame will depend on the output TLVs which are enabled, 6-8 bytes does seem low.

    I have a couple of questions.

    1. Have you made any modifications to the example demo code?

    2. What configuration are you using? By this I mean, are you using one of the default configurations from the SDK visualizer (Motion Detect or Presence Detect) or are you sending some custom configuration?
      1. If you are sending a custom configuration file, please let me know your setting for the guiMonitor command.

    Best Regards,

    Josh

  • 0 in reply to Josh Dye
    Prodigy 10 points

    Hi Josh,

    Sorry for the delay, I didn't made any modifications to the example demo code. I'm using the default configuration " Presence Detect ".

    Best Regards,

    Aimane

  • 0 in reply to Aimane
    TI__Mastermind 20651 points

    Hi Aimane, 

    No problem. I understand you have not made any modifications to the demo code. I will try to replicate this on my end. 

    Also can you please clarify on this:

    Aimane said:
    Most frames that I've retrieved from UART output have a size between 6 and 8 bytes

    Is this just the size of individual TLVs or is this the entire output for each frame? The frame header should be 40 bytes alone including the magic word which should be the first 8 bytes. Are you able to see the magic word?

    Best Regards,

    Josh