QRP Labs ProgRock2, Руководство пользователя, Страница: 10 / 19

5 Connecting terminal emulator
Drivers
No additional drivers are required for operation with most Linux distributions, Apple Mac or MS
Windows 10 or Windows 11.
For older versions of MS Windows, it may be necessary to install a driver for the serial port
because this driver is not on your computer already by default. This driver is available from the ST
Semiconductor website at
https://www.st.com/en/development-tools/stsw-stm32102.html and is
applicable to 98SE, 2000, XP, Vista®, 7, and 8.x Operating Systems. There is a description for
installation on Windows 7/8 on the QRP Labs QLG2 page
http://qrp-labs.com/qlg2 so if in doubt,
please check this.
Linux special note
On Linux systems, a particular problem can occur. When the ProgRock2 (Serial) connection is
detected, the PC thinks that a modem has been connected and starts trying to send it Hayes AT-
commands dating back to 1981, implemented on Hayes’ 300-baud modem. Yes! 40 years ago…
The Operating System attempting to send AT commands to your ProgRock2 will certainly mess
everything up. Not least because when ProgRock2 receives a carriage return character, it will
enter Terminal Applications mode; this will send all sorts of characters back to the PC (as
ProgRock2 thinks it is now talking to a terminal emulator) and it will disable CAT command
processing, so your PC digi modes software will not be able to talk to ProgRock2. Disaster.
To fix this you need to issue the following commands to disable ModemManager:
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
sudo systemctl mask ModemManager
This will permanently stop ModemManager. If for some reason, you actually DO need
ModemManager operational, for some other reason… well there IS a way to stop it just for
ProgRock2… but Google will be your elmer on this!
Additional information from Greg Majewski:
There is another Linux service, BRITTY, that does the same. BRITTY is a Braille service for
access by sight impaired people. I have encountered the problem with the G90 and Ubuntu on a
laptop (Ubuntu full version), Raspberry Pi 3 with Raspberry OS and the Orange PI 800. Here are
commands that remove BRITTY:
sudo systemctl stop brltty-udev.service
sudo systemctl mask brltty-udev.service
note output: Created symlink /etc/systemd/system/brltty-udev.service
→ /dev/null.
sudo systemctl stop brltty.service
sudo systemctl disable brltty.service
ProgRock2 manual 1.00b
10