can't connect Current Ranger to a pc

[rufsiany_sr]

First of all, I have been using CR for a year and I am very pleased. I bought it together with the display and it was enough for me so far. Recently however, I decided to use additional possibilities such as data logging via BT. But before connecting the HC-05 (or 06), I wanted to upgrade CR to the latest version. (the display shows version 1.0.0 and the board is R3Mk4). Unfortunately, when I connect the CR via a USB cable to my laptop, the laptop does not see it. I'm using Ubuntu 20.04 and after plugging in the CR, no new device in /dev/ttyUSBx shows up. (Of course, the CR is on.)

Interestingly, after connecting the cable, 'lsusb' shows 1 new device:
'Bus 003 Device 011: ID 04d8: ee4c Microchip Technology, Inc.', which gives some hope, still without the proper ttyUSB I can't even connect the console.

What may be the problem?

[rufsiany_sr]

some further information. After browsing the log files I found this:
(latest entry on top)
3-13.1: Process '/usr/lib/snapd/snap-device-helper bind snap_arduino_arduino /devices/pci0000:00/0000:00:14.0/usb3/3-13/3-13.1 189:274' failed with exit code 1.
bus: 3, device: 11 was not an MTP device
checking bus 3, device 11: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-13/3-13.1"

[Felix]

Probably some driver issue.
The CR enumerates as a generic communication class serial port.
So it should have no problem being recognized on major OS-es.
Can you try on W10?

[rufsiany_sr]

I tried on Windows 7 (which I had to revitalize, after bringing it from the attic  . After installing the driver, the console worked and after booting into the bootloader mode, I was able to copy version R3 1.1.2 and upgrade the CR. So far so good...
Unfortunately, the problem with the lack of a console on Linux remained, because I use Linux on a daily basis. However, I hope that after connecting the HC-06 (ordered it today), I will be able to connect to Linux, so the problem will solve itself. In addition, BT does not pose any problems with the ground loops.

[Felix]

Ok good to hear.
The BT will be significantly slower though.
It's merely for the wireless ability, but otherwise for higher speed of logging I would just use a USB isolator, if you can find a way to use USB serial.

[topor]

I have a similar problem, Windows detect it as Standard Com X but there is nothing back when I type "?" on Arduino (1.8.19 & 1.8.9) or Hercules , However Putty works fine.

I tried differents cables, and two computers (win 10 & win 11) same behavior.

I tried to turn on the usb logging with "u" in Putty and it start to output the log as it should , I close putty,  open the COM with Arduino Serial, Arduino Plotter or Hercules and I get nothing, I open the COM again with Putty and the usb logging is still there outputing data. Any ideas? Is there any w10/11 signed drivers to try it out?



Thanks

[Felix]

There is nothing special about this virtual com port, no signed driver required.
Something's odd on your system. Putty as well as any serial terminal app should open this up. Maybe something's holding it up on your Windows instance.

[topor]

too unlikely that 2 different systems would fail in the same way, don't you think? On the second computer with windows 10 that I have tested is a clean install with office and little else, I have downloaded Arduino for the first time to test it.


On the main PC (w11) I am continuously using arduino and reading COM ports, any suggestions for testing something else?

[Felix]

I agree, do you happen to have another CR to try?

[topor]

Solved at least on my PC, it turns out that if you have selected a third party board is not working.  I had selected an ESP32 board so it was as simple as selecting an random Arduino board (Arduino Yun) and start working.

Thanks for your support as always 

[johnevans88]

it seems the USB driver is not loading properly, as 'lsusb' sees the device but no /dev/ttyUSBx. You might want to try reinstalling the CH340 or FTDI drivers for Ubuntu. Sometimes a reboot helps in recognizing the port.

Also try switching USB cables because sometimes the issue lies with the cable, which might only support charging and not data transfer  😊