rspro82
Utility for programming channels into RadioShack PRO-branded scanners manufactured by GRE.
Several other radios use the same programming protocol. I have only tested it with the PRO-82, but it may work with other radios including the PRO-64, PRO-76, PRO-79, PRO-89, PRO-2016, PRO-2017 and PRO-2041.
Installation
python3 -m pip install rspro82
Command-line interface
Prepare a CSV file that has at least these columns:
- Channel: The number of the channel you wish to program
- Frequency: Frequency in MHz, like
156.6 - Delay: Boolean value for the channel delay flag (should the scanner pause on the channel for 2 seconds after a transmission ends?)
- Priority: Boolean value for the channel priority flag (should the scanner check this channel at least every 2 seconds?)
Additional columns are ignored.
Activate programming mode on the scanner by holding down the ENT and 9 keys on the scanner as you turn it on.
Run the CLI like:
rspro82 <port path> <channel csv file path>
On a Mac, the port argument will probably look like /dev/cu.usbserial-<numbers>.
On Windows, the port argument will look like COM4.
Cable
The PRO-82 uses a very simple programming cable connecting a RS-232 serial port to the unit's TRS headphone jack.
The serial port's GND line (pin 5 on a DB-9 connector) is connected to the sheath.
The serial port's TXD line (pin 3 on a DB-9 connector) is connected to the ring.
These cables can be expensively purchased, or inexpensively made by sacrificing something with a 3.5mm jack, like old headphones or a patch cable. Solderless DB-9 connectors are available and convenient.
Most Prolific-style USB/RS-232 adapters should work fine. Devices targeting hobbyists that expose TTL-level outputs and skip the DB-9 interface may not work, since TTL signal voltage levels are lower than the RS-232 spec requires. If you try it, I'm curious how you make out!
License
rspro82 is made available subject to the Apache License 2.0; see LICENSE for details.
Metadata
Release files for rspro82 23.8.0.post0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rspro82-23.8.0.post0.tar.gz | 8.3 kB | Without provenance | Details for rspro82-23.8.0.post0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rspro82-23.8.0.post0-py3-none-any.whl | Python 3 | none | any | Details for rspro82-23.8.0.post0-py3-none-any.whl |
Total release size: 17.2 kB
Release files / rspro82-23.8.0.post0.tar.gz
| Download URL | rspro82-23.8.0.post0.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8b8b3a5b9e9bad82f2168f808faba620a068d070d3e77bdf244ef98b4fb1d11e
|
|
BLAKE2b-256 checksum How to use checksums |
185db56d41a846f11753303029913a32f24b94fabb6da0527639d4d524c15e2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Release files / rspro82-23.8.0.post0-py3-none-any.whl
| Download URL | rspro82-23.8.0.post0-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
400c084ba03be6aad770c4618ff734f7e5ca92cb3f06c989a237131e69aaa1d4
|
|
BLAKE2b-256 checksum How to use checksums |
7b5e9c58cd3232ac75d39b875328c0f699ed94f7e9eb0d075b03da6ad14a9e89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Security for rspro82 23.8.0.post0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.