What might cause a CR3000 to be unable to connect with DevConfig?
Typical causes include the following:
- The version of DevConfig is too old.
- The CR3000 has power issues.
- The wrong COM1─COM4 port is selected in DevConfig.
- The device driver for the USB-to-serial adapter is not found.
- The CR3000 is damaged.
If the CR3000 display is working properly, it is likely that the communication issue is the software version or settings, or an issue with the connecting cable.