No. Like it is stuck in USB mode (mode 15) even though I confirmed by pressing the MODE button that it is on mode 5 (standard serial).
The software also says it is in standard or simple serial mode.

In the manual is says...

RoboClaw includes 3 LEDs to indicate status. Two green status LEDs labeled STAT1 and STAT2
and one red error LED labeled ERR. When the motor controller is first powered on all 3 LEDs
should blink briefly to indicate all LEDs are functional.

STAT1 lights up when connected to USB. Only STAT2 lights up when not connected to USB.

Forgot to add..,.

The LEDs will behave differently depending on the mode. During normal operation the status 1
LED will remain on continuously or blink when data is received in RC Mode or Serial Modes. The
status 2 LED will light when either drive stage is active.

Now I have STAT1 lit when not connected to USB. It's hard to see the problem.

Further testing. Works without vendor software connection but with USB connected. Disconnect USB, then it doesn't work.
So the only thing it gets from the USB connection is more 5v power. Curious!

What would happen if I connected the Roboclaw's USB to its own S5 5v power supply? Risky or not?

I tried this experiment and it worked. I connected one end of a USB cable to the Roboclaw's USB connector and the other end to its own 5v power on the S5 pin. So why is this necessary is the big question?

Quote:

I tried this experiment and it worked. I connected one end of a USB cable to the Roboclaw's USB connector and the other end to its own 5v power on the S5 pin. So why is this necessary is the big question?

Honestly, I think something got damaged when you had it mis-wired originally.  From what I have seen in the documentation this should not be needed, but if that is the only problem I would consider myself lucky that there is such a simple solution.

Alan

Perhaps. The vendor's software put me on the wrong track as it kept indicating the logic battery was around 2v. And it never indicated the 5.5v that I expected - even now.