Test monitoring host

Stability monitoring or integration "verification" testing benefits from having a non-intrusive FTDI monitoring cable attached and then logging all the routine operations of the device under test.

A simple version of this can use an available Raspberry Pi (rPi) with spare Type USB port and networking cable.
a) Standard rPi 3 or 4 which has USB and Networking ports
b) rPi Zero with USB and Ethernet expansion .....

I like to record all the output to the file system - I use minicom - and also to make the file system accessible from the network with samba. Though I've also found that the free version of Bitvise Client two panel "Remote Files" is pretty good.
Logging/SSH (Bitvise into the rPi say its called rpi3mon ;
$ sudo apt update
$ sudo apt-get install minicom
$ mkdir share # put all minicom log files
$ sudo apt install samba
?Modify smb.conf to use WINS settings from DHCP? No

$ sudo nano /etc/samba/smb.conf
[share]
workgroup = YOURWORKGROUP
# This share allows anonymous (guest)
# Read-Only access without authentication!
comment = Raspberry Pi File Server
path = /home/pi/share
read only = yes
guest ok = yes
guest only = yes

#save
$ sudo systemctl restart smbd

Plugin FTDI
$ ls /dev/ttyUSB0
$ minicom -b 115200 -o -D /dev/ttyUSB0 -C
Verifies that you see output from device, and that it also records to filename

$ nano .bash_alias
alias now='date "+%y%m%d%H%M”'
alias ttu0='minicom -b 115200 -o -D /dev/ttyUSB0 -C ~/share/ttylog$(date "+%y%m%d%H%M").txt'

$ sudo reboot now
on logging back in try

$ ttu0

Then from another network access - eg Win PC, step to that location, and see if the ModularSensors output is being recorded ....
\rpi3mon\share