You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This concerns a system that's been in production since 2016. My client recently asked for some new features. To do that, I needed to upgrade from Debian Jessie to Buster and from Python 2 to 3.
The problem
The system uses /dev/ttyO0 and /dev/ttyO1 for ModBus serial control at 19200 baud. Since the upgrade, these ports can be opened and written to but they return no response.
Jessie serial configuration
Under Jessie, the ports were initialized in /etc/rc.local with:
and /dev/ttyO0 was released from use as a login console by commenting out the following lines in /etc/init/serial.conf
#respawn
#exec /sbin/getty 115200 ttyO0
Buster serial configuration
Under Buster, the overlay system is changed and /etc/rc.local and /etc/init/serial.conf are obsoleted in favor of systemd, so I'm enabling UART's with:
This concerns a system that's been in production since 2016. My client recently asked for some new features. To do that, I needed to upgrade from Debian Jessie to Buster and from Python 2 to 3.
The problem
The system uses
/dev/ttyO0
and/dev/ttyO1
for ModBus serial control at 19200 baud. Since the upgrade, these ports can be opened and written to but they return no response.Jessie serial configuration
Under Jessie, the ports were initialized in
/etc/rc.local
with:and /dev/ttyO0 was released from use as a login console by commenting out the following lines in
/etc/init/serial.conf
Buster serial configuration
Under Buster, the overlay system is changed and
/etc/rc.local
and/etc/init/serial.conf
are obsoleted in favor ofsystemd
, so I'm enabling UART's with:and disabling the login console mapping with:
Buster system report from /opt/scripts/tools/version.sh
The text was updated successfully, but these errors were encountered: