I have configured a serial bridge and verified that data is correctly arriving via the cat /dev/ttyAMA1 command in the terminal. However, I am unable to see or receive this data on my PC.
and I have confirmed that serial data is successfully reaching Node-RED (via debug node), but I cannot receive it on my PC. I would like to know if there is a way to verify that the data is being correctly transmitted out from BlueOS to the network.
To ensure there are no residual configuration conflicts, I have performed a full system reflash (firmware flushing) and am currently testing on a completely clean setup. Despite this fresh start, the ‘Connection Refused’ issue persists when trying to access the data externally.
My situation and symptoms are very similar to the issue linked/described below.
This shows you have set up a server in BlueOS, which waits for a client to establish a connection and then forwards the serial data to it. The client needs to connect first (for the server to know which port to talk to), and needs to regularly communicate to the server (at least once every 10 seconds) or the connection will be dropped.
Am I understanding correctly that this is running as an Extension in BlueOS, not on your control station computer (PC)?
If so, were you trying to replace the serial bridges functionality? I don’t believe both a serial bridge and NodeRED can connect to a serial device at the same time without conflicts.
This seems to be using TCP as the transport protocol, whereas the BlueOS serial bridges functionality creates UDP bridges (which is a different protocol).
