I could not see the combination of idVendor and idProduct on an internet search, and so it has me thinking perhaps some very recent software release might know the combination, while anything slightly older does not.
Normally, when a USB device is plugged in, the USB will announce the idVendor and idProduct, and any driver which can handle that combination can take ownership of the device. If for example this is a common chip, then it won’t matter who used that chip in their product, the driver will just work without anything special.
On the other hand, the manufacturer can use their own idVendor and idProduct. If it turns out that this custom vendor/product uses the same driver (which is highly likely), then one needs a udev rule to associate the new vendor/product to the old vendor/product. Once that association exists, then the driver can bind to the device. The same udev rule might be used to provide a new device special file name to distinguish this particular implementation from someone else’s implementation.
So far as I can tell from your udev rule this never mentioned a driver to associate with, all it did was set permission to the device special file. When looking up common vendor/product IDs I never found the combination vendor 0x2ca3 and product 0x001f. Seems this is new (the registries I looked at are probably at least 6 months old). On your systems which were able to use this it leads me to believe the USB registry and udev combination were newer than on the system not recognizing the device. The device vendor (apparently DJI) could probably help with this (or it might be a hardware failure…the fact that you saw DJI in dmesg tells me this is not a hardware failure) by providing a more complete udev rule. Or if by coincidence you install some newer software which is already aware of this vendor/product combination, then this too would work. I just don’t know which version that is.
Btw, you can check for USB ACM serial deice support via:
zcat /proc/config.gz | grep 'USB_ACM'
=m” or “
=y” means it is supported so long as the driver is associated with that vendor/product ID.