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: Connecting multiple IWR6843ISK's and running multiple people counting UART streams.

Part Number: IWR6843ISK

I would like to run two IWR6843ISK's REV D's running the People Counting Binary from Industrial Toolbox Version 4.8.0 at the same time.

However, whenever I plug the second IWR6843ISK into the computer while running the mmWave People Counting demo, I immediately get the following error:

Traceback (most recent call last):
  File "gui_threads.py", line 26, in run
  File "oob_parser.py", line 801, in readAndParseUart
  File "serial\serialwin32.py", line 275, in read
serial.serialutil.SerialException: ClearCommError failed (PermissionError(13, 'Access is denied.', None, 5))

If I try to start either unit while both are plugged in, I also get the same error.

Should it be feasible to gather both IWR6843ISK's streams at the same time?

Here is a picture of the device manager with everything plugged in

  • Hi,

    Yes, this is certainly possible. This is done in our Robotics Safety Bubble demo's. In order to accomplish this, you will typically need to modify the desired visualizer in order to support the reading of multiple devices, since most of our visualizers are not designed with this usecase in mind. I would recommend that you take a look at the source code for the visualizer in order to add the second device.

    Best Regards,
    Alec

  • Thanks for the feedback.

    Thanks for the lead and the confidence. Just perplexed why the uartParserSDK() python class from the People Counting GUI would fail, when simply another IWR is plugged in. I do my own backend on the People Counting IWR6843ISK People Counting Binary and use the uartParserSDK() python class to ingest my data.

    I'll go down that path.

  • Hi,

    I would imagine it has something to do with how we implemented the serial handler in the GUI, since it was not a use-case we were concerned with at the time, it likely was never tested. Let me know if you have any questions while making the modifications.

    Best Regards,
    Alec

  • I don't know if it is the python GUI handler.

    Why I think this:

    If I open a CLI and attempt to manually configure either one while plugged both are plugged in I can't.

    If I have one configured and actively sending UART 2 Position data, if I simply plug the other one in, the active one resets.

    If I have them both plugged in and I attempt to configure either using CLI commands, upon issuing sensorStart, I lose communication with the one I'm trying to configure.

    Normally, I'd get a "Debug: Init Calibration Status = 0xffe Done "

    back on the CLI when I just have one plugged in and I'd start to receive data on the other UART. Instead I get an error USB from RealTerm and the CLI is no longer responsive until I open/close the connection in RealTerm. I have never got a single stream of position data going when both are plugged in. Either the active one resets, or I can't get past sensorStart when attempting to configure either one.

    I see the Robotics Safety Bubble is using the Out of Box Demo. Maybe this would work, I can certainly test my same procedure (trying to configured two ISK's plugged in at the same time to data transfer through Real Term using the OOB Binary instead of the People Counting One)

    If anyone else has had success having two People Counting Binaries active at the same time, I'd be interested.

  • Darn. Almost same thing with the 3.5 Out of Box demo. Running the 68xx_mmwave_sdk_dsp binary.

    However, I can keep one stream going when both are plugged in if I set up a single one up without the other plugged in.

    If I attempt to issue sensorStart with both plugged in I always disconnect in error.

    If there is already one streaming and I issue sensorStart to the other, that setup one resets and the stream is lost.

    Now I'm wondering how the Robotics Safety Bubble Demo is issuing sensorStart to multiple sensors.

    Maybe they are hard coding the configs to get around sensorStart?

  • Hi,

    Are you plugging these into USB-hub, or directly into a PC? Plugging in a 2nd device should have NO impact on the 1st device if you are just connected via a terminal such as teraterm. I suspect something on your PC is affecting the behavior here such as a USB driver or something similar. If you are using a USB hub, that is likely the issue, if not then I would try another computer and see if you still see the same behavior.

    Best Regards,
    Alec