​Please note this issue is automatically detected and catered for in UPDD 6.0.717. Build 717 checks if libusb_get_port_numbers() returns zero (as is the case on the M1 systems) then the driver uses a different device identification method automatically.

The driver builds a list of connected device, supported by the installed driver software and lists them in the UPDD Console to be configured, calibrated, assigned etc as required.

On M1 systems it has been reported that in some cases multiple USB touch devices residing on the same USB hub are only seen as one device by the driver.

In cases where there are identical USB vendor and product ids the driver uses additional USB port information to distinguish between the touch devices. In Intel systems, the port identification data always results in a unique port ID, as seen in our debug trace log "USB location bus:0014-port:0003-0001"

In M1 systems in many cases the port data is identical for each device so the driver only discovers one device.

This issue is typically reported thus:

When using the software on a new M1 Mac Mini, we observed the following with two identical touch screens, with these configurations.
When both Touch Screens have USB connected to onboard HUB, System Info showed both devices, but the UPDD Console only showed 1 device.
When both Touch Screens have USB connected to an external hub, which is connected to a USB 2.0 port on the MacMini, the System Info still shows 2 devices, but the UPDD Software still shows 1 device.
When both Touch Screens have USB connected to an external USB-C hub, connected to a Thunderbolt port on the MacMini, the System Info still shows 2 devices, but the UPDD Console only shows 1.
Then when we split the load, and have a Touch Screen connected via the Mac Mini USB2.0 on-board port, and another Touch Screen connected via the USB-C hub, connected via the Thunderbolt port, we can see and configure both Touch Screens.

Whilst we try and identify a better method of retrieving USB port information on M1 systems that results in unique port identifiers you can instruct the driver to use a different device identification method and list them in the order that they are discovered by the system. This does rely on the system always finding the devices in the same order at each boot.

To enable this you need to set a bindmode setting for each of the device types listed in the Console, in most cases this will just be one device.

In a Terminal window run the command "upddutils setall bindmode 16384' and reboot the system.