Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

dpkingston / arcom-interface Public

Notifications You must be signed in to change notification settings
Fork 1
Star 0

Code
Issues 7
Pull requests
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Breadcrumbs

arcom-interface

/

arcom.conf.sample

Latest commit

History

8 lines (8 loc) · 364 Bytes

Breadcrumbs

arcom-interface

/

arcom.conf.sample

File metadata and controls

8 lines (8 loc) · 364 Bytes

1

2

3

4

5

6

7

8

; Config file for arcom.py (typically in $HOME/.arcom.conf or $PWD/.arcom.conf)

; call should be your FCC call sign

; location can be any short descriptive string to be included in the weblog entry.

; Grid location is a good choice. Or it could be descriptive like 'Home' depending

; on how you plan to use the weblog data.

[arcom]

call = N1LXA

location = FN34ld

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.