jlpoole/microReticulumTbeam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add USB_Naming

jlpoole 2026-02-19 08:59:12 -08:00
commit f63d8f7196
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
USB_Naming.md Normal file

@ -0,0 +1,16 @@
Give your **devices permanent and meaningful names** so your commands are self-documenting which device you are working with. I decided to have names of /dev/tty + t (for T-Beam) + Device Name in all caps, e.g. /dev/ttytAMY. This is accomplished in Gentoo running Open RC with a rules page which is uploaded to this project. With my rules:
```
rnsenv) jlpoole@jp /usr/local/src/microreticulum/microReticulumTbeam/exercises/12_FiveTalk $ ls -l /dev/ttyt*
lrwxrwxrwx 1 root root 7 Feb 19 08:43 /dev/ttytAMY -> ttyACM0
lrwxrwxrwx 1 root root 7 Feb 19 08:43 /dev/ttytBOB -> ttyACM1
lrwxrwxrwx 1 root root 7 Feb 19 08:44 /dev/ttytCY -> ttyACM2
lrwxrwxrwx 1 root root 7 Feb 19 08:44 /dev/ttytDAN -> ttyACM3
lrwxrwxrwx 1 root root 7 Feb 19 08:44 /dev/ttytED -> ttyACM4
(rnsenv) jlpoole@jp /usr/local/src/microreticulum/microReticulumTbeam/exercises/12_FiveTalk $
```
It no longer matters when and in what order I activate/deactivate devices, I can always relay on udev to assign the correct name to the device I intend. That makes loading up the code self-evident with:
`pio run -e amy -t upload --upload-port /dev/ttytAMY`
At age 69 with devices having acronyms assigned by the kernel in numerical order, i.e. `/dev/ttyACM0`, it's like herding cats and makes for ambiguous documentation thereafter: how do I know AMY was at `/dev/ttyACM0` when I ran the upload script? Answer: I don't. Now I do using its soft-linked name: `/dev/ttytAMY`