MMWAVEPOEEVM: Sensor is not working after 'sensorStart' command is send

Hi,

Can you confirm that you have gone through the steps listed in the MMWAVEPOEEVM user's guide, as there are some specific hardware settings that must be done in order to work with the MMWAVEPOEEVM.

Best Regards,
Alec

Hello,

Yes. The shunt jumpers in POE and MMWAVEICBOOST are placed as per instructions. The connection is made and cfg is able to send. But the sensor didn't start.

Thanks and regards,

Aleena N A

Hi,

Understood. I will try this out on my end to see if I can replicate your issue. Please allow me some time as I will have to locate a POE evm. I will provide an update no later than Tuesday

Best Regards,
Alec

Hello,

Is there any demo for interfacing with MMWAVEPOEVM similar to the 3D people counting demo using UART? There is a 'Wi-Fi Communication Setup for 3D People Counting User's Guide'. Similar to that is there any MMWAVEPOEEVM interfacing demo?

Thanks and regards,

Aleena N A

Hai,

The problem was resolved. Now the issue is 'TLV Header Parsing Failure' and 'Point Cloud TLV Parser Failed''. Why this is happening?

Thanks and regards,

Aleena N A

Hi,

Can you confirm what demo + visualizer you are running?

Best Regards,
Alec

Hai,

We are using 3D people counting demo(Industrial toolbox 4_9_0) and python visualizer.

Could you please tell me how you have interfaced MMWAVEPOEEVM. We edited tcpecho code and it was flashed into MMWAVEPOEEVM.

Thanks and regards,

Aleena N A

Hi,

Have you modified the people counting visualizer to take in data over ethernet rather than UART? The visualizer is configured for serial ports rather than ethernet, so I imagine some significant changes would be needed there. If you have any issues with the output from the POEEVM itself, you may need to make a forum post for the MSP432 forums as well.

Best Regards,
Alec

Hai,

We have made changes in the python code for visualizing. We receive data in some frames. But most of the frames have missing data. We sometimes get the target data. But most of the frames have missing data. After going through the code and doing debug prints we found that it corresponds to sizes.

We added debug prints in the warnings. According to that, we got, 

Point Cloud TLV Parser Failed : index 12 is out of bounds for axis 2 with size 12

TLV Header Parsing Failure : unpack requires a bytes object of length 8

Target TLV parse Failed : unpack requires a bytes object of length 112

The above is the original warning : obtained debug prints. From this, we infer that the received data from the sensor via POE is not complete. The connections are correct and sometimes we get the target data. 

Please look into it.

Also how to interface using MMWAVEPOEEVM in any of the existing demos??? Please help me.

Thanks and regards,

Aleena N A

Hi,

If you are losing data between the demo and the visualizer, you will need to do a bit of debugging here to determine where the data is lost. 

Things you can check:

1. In the python script, can you look at the raw block of data to see if you get the entire frame with a slightly longer delay? I imagine the rate at which you get data may be a bit different since it is now ethernet rather than UART.
2. Can you debug on the MSP432 to ensure the UART stream coming from the mmWave device is good?

In terms of interfacing using the POE EVM, the assistance we can offer here is a bit limited since all visualizers created for the mmWave devices rely on the UART connection, and would all need to be converted to ethernet. If the UART stream coming from the mmWave device is incomplete, we can happily debug that further, but if the issue is related to the conversion from UART to Ethernet on the POE EVM, I would again suggest you open another ticket which can be directed to the MSP432 team.

Best Regards,
Alec

Hai,

We have checked the incoming data. We found that the data from the sensor is not fully received via POE. The size of data received using UART is 4666bytes. But when we give a buffer size of 4666bytes in the UART of POE it didn't work. Please help us to solve this.

Thanks and regards,

Aleena N A

Hi,

Can you confirm that the baudrate of the POE/MSP432 is set to 921600 to match the data rate of the IWR6843? Additionally, the volume of data will likely fluctuate per frame, so you may want your buffer to be a bit larger than the size of a single frame to allow for fluctuations over time.

Best Regards,
Alec