Follow the reported evidence

1. For “Wrong parity”, compare the tested settings with the field-device configuration. Try the documented parity and verify a clean read. A CRC-valid response can still have UART parity/framing errors.
2. For “Conflict”, check whether two devices share the address. The scanner observes repeated corrupted replies; wrong baud/parity or other faults can look similar.
3. During an appropriate maintenance window, isolate one suspected device and repeat the same request. If each device works alone at the same address, change the addresses to unique values using the devices' documented procedure.
4. For “Garbled”, check serial settings and the possibility of noise, a late response, or competing traffic. Compare with an isolated device and known wiring.
5. If results differ only in stop bits, use the manufacturer's setting. A response does not reliably identify its stop-bit count.
6. After a clean scan, apply the required normal port settings, exit commissioning, and verify the external integration.

If listen-before-transmitting reports a busy bus, identify the active master before proceeding. Disabling that check is not the default fix for a live installation.

Expected result

Each intended device has a unique address on its bus and consistently returns a clean response at the configured settings. Include scan results and isolation-test outcomes if the fault persists.