Serial port will not work with cable already plugged in

General
21

The serial node is configured as /dev/ttyUSB0:115200-8N1

22

And the rest of the serial node config?

23

Input:

Split input    on the character    \n
and deliver    ascii strings
24

Do you know what is USB/serial chip is in your device?

25

Chip: FT232R (see: https://www.sossolutions.nl/slimme-meter-kabel)

26

Ok,
is it possible to try with cp2102 or ch340g chip?

27

No sorry, this is my only serial device...

28

My idea is to try some other usb/serial chip.
Cp2012 and ch340g are about 1-2 USD/each.
You need just connect tx to rx on the module. On the node-red take inject node and set to send anything every few second to the usb port.

29

Try it with a fixed number of characters instead, in order to see whether anything at all is being received. Perhaps it is not syncing correctly on startup or something.

When you run cu does the node-red log show anything (in both working and non-working cases)?

30

this is still very odd - I have several FTDI based devices - GPS, cable to Arduino etc... and so far I can't provoke this behaviour at all.

31

Starting today, I will be on vacation for a couple of weeks, so I cannot perform more tests now. I have my Pi connected to a UPS, so I hope it will keep running during my absence...
When I return I will continue to investigate this problem.
Thanks everyone for your help so far!

32

This has been reported on the Raspi boards here https://www.raspberrypi.org/forums/viewtopic.php?f=31&t=213230&hilit=ftdi

1 Like
33

That is not the same problem is it? That is describing a situation where the port is not recognised at all on boot. In the case here it works fine using cu but not in node-red. If it were the linked problem then cu would not work either would it?

34

I don't know what cu is, but FTDI devices are unstable. I have many clone arduino nanos that are now useless as they aren't recognised at boot. cu might talk to them, but that's irrelevant if NR can't