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.

IWR6843ISK: "nul" after each command

Part Number: IWR6843ISK
Other Parts Discussed in Thread: MMWAVEICBOOST,

Hi Team, seeking for assistance from a customer.

Using IWR6843ISK together with MMWAVEICBOOST. What I want to do is modify the existing 3D People Counting example so that instead of sending data to the existing visualizer, we send it through an ESP device (using AT commands) and then over MQTT protocol. So I need to use UART for that, and more specifically UART_writePolling, because I need to send command by command. However, whenever I try to send a command with that, it sends something additional, on Realterm tool it shows a "nul" after each command, how do I work around it?

Also, one of the biggest problems we have is that the sensors just stop working sometimes for some reason, we cant use it in either functional nor flashing mode. We double check everything, but this issue keeps repeating. And then after a while they function, it sounds silly but thats how it happens.

Thank you.

-Mark

  • Hi Mark,

    However, whenever I try to send a command with that, it sends something additional, on Realterm tool it shows a "nul" after each command, how do I work around it?

    This sounds like a problem with the serial port application you're using. Can you probe with a logic analyzer to see what's on the line.

    Also, one of the biggest problems we have is that the sensors just stop working sometimes for some reason, we cant use it in either functional nor flashing mode. We double check everything, but this issue keeps repeating. And then after a while they function, it sounds silly but thats how it happens.

    Does the sensor stop working? Or does the visualizer stop working? Additionally, what code are you running and have you made any modifications to it?

    Best,

    Nate

  • Hi Nate, seeking for further response.

    The problem with 'nul' was actually related to the fact that the UART was configured to send a carriage return (0d) whenever a line feed (0a) was detected. When sending AT commands it is necessary to send \r\n after each one to signify the end of the command and this is what caused all the nuls. 
    We solved the problem temporarily by going to the driver implementation itself and commenting out the part where additional characters are sent and rebuilding the library, but could you please provide an example of how that could be handled in the code itself?

    Does the sensor stop working? Or does the visualizer stop working? Additionally, what code are you running and have you made any modifications to it?
    Well, both. When we flashed the prebuilt binary, the visualizer would sometimes work and sometimes would not (the latter was the majority of the cases). We made sure we used a fully powered computer, and if I remember correctly, it is said in the guide for the example (People Counting) that the visualizer does require a stronger machine to work more smoothly but that it should, nevertheless, still be functioning with possible lagging if the machine is not.
    We changed the existing demo to send the data through the AT commands, and we harded the CLI commands needed for the radar subsystem, pretty much that is it. But the problem was occurring even before that. 
    As I said, it would sometimes not let us neither run the existing firmware nor flash the new (or the same) one.
    Thank you.
    -Mark
  • Hi,

    Please run the demo without the AT commands to be sure that it is working. Most laptops should work fine. Once you can get the prebuilt binary working without the ESP device, then I would move on to trying to interface with the ESP device. If you cannot get the prebuilt binary working, please let us know the error you're receiving so we can help debug.

    Best,

    Nate