Reporting a problem
Open a bug report on GitHub, one problem per issue, after a look at the open ones: yours may be there already. The knob's own report, and the list below, are what let us find it without a round of questions first.
The quickest way: from the knob
Its configuration page makes the report and opens the form with it. Make it right after the problem: the knob keeps its log in its memory, and a restart begins it again.
- 1
Hold a finger on the S-meter until the knob clicks: the address card shows the knob's address. Open it in a browser on the same network, and log in. A knob still on its first login asks for a password of its own first, 8 to 32 characters, and shows nothing else until it has one.
- 2
Scroll to Report a problem, at the bottom of the page, press Make a report, and read it. It holds the firmware and its version, how the knob last started (a crash, a watchdog, safe mode), its power, network and link, a crash it remembers, and its recent log, with the passwords the knob keeps starred out. An issue is public: take out a network's name, an address or a call sign you would rather keep to yourself.
- 3
Press Open it on GitHub: the bug form opens with the firmware and the report filled in. It takes a GitHub account, and a browser that reaches the internet. A report too long for a link carries the newest log lines and says so, and the whole report goes on the clipboard: paste it over the cut one in the form's log. Copy it copies it, for anywhere else.
A knob older than 1.21.2 has no Report a problem on its page. Update it first — the knob offers the update as it starts, or upgrade it over its cable — or run nc <the knob's address> 3333 on a computer: it prints the same log.
Bluetooth not working?
No Bluetooth headset or speaker on the knob's configuration page, or a note there that its second chip does not answer: that chip — the one that talks to headsets and speakers — has no firmware on it yet. Nothing to report: put it on from Chrome or Edge, over the knob's USB-C cable, a few minutes and once. From then on the knob keeps it up to date by itself. Still not working after that? Report it, with item 6 below.
Add Bluetooth to your knobPlease give
The form asks for each of these.
- 1
The firmware and its version
As the address card says it (hold a finger on the S-meter until the knob clicks): OpenX6X00 1.21.1.
- 2
The radio, receiver or reflector
With its own software: an IC-705 and its firmware, a FLEX-6600 and SmartSDR's version, AetherSDR's version and the computer it runs on, an X6100 and its OpenX6X00 version, a receiver's or a reflector's address. And how the knob reaches it: WiFi, the USB cable, or SmartLink.
- 3
What happened
What you did, what you expected and what you got. Give what the face says — NO LINK and the reason under it, a message in amber or red — and the frequency, the mode and the screen you were on. A photo of the knob's face helps.
- 4
The knob's report
Make a report on its configuration page, as above, right after the problem; Open it on GitHub puts it in the form. Read it before you send it. Without the page, nc <the knob's address> 3333 on a computer prints the same log.
- 5
WiFi
For a WiFi problem: the exact message on the face, the router's security (WPA2, WPA2/WPA3, WPA3 only), its 2.4 GHz channel, whether the network has more than one access point (a mesh, a repeater), and whether a phone's hotspot works.
- 6
Audio and Bluetooth
What you heard (the radio's audio, or your own transmission), the volume and the mic gain, and where: the jack, or a headset or speaker, by its make and model.
A template, to write it down first
Fill in what applies, then put each part in its place in the form, and drop a photo of the knob's face onto it.
Firmware and version (on the address card): Radio, receiver or reflector, and its software and version: How the knob reaches it: WiFi / the USB cable / SmartLink What I did: What I expected: What I got: What the face said (NO LINK and the reason under it, a message): Frequency, mode and screen: The knob's report (Make a report, on its configuration page): WiFi: the message, the router's security, its 2.4 GHz channel, one access point or several, a phone's hotspot: Audio and Bluetooth: what I heard, volume and mic gain, the jack or a headset or speaker (make and model):
Ideas and features
A new feature or an idea goes to a feature request, one feature per issue. Its title starts with Feature: and names it in a few words — Feature: CW from a SmartCW keyer on SVXConnect. Look at the open issues first, and add your use to one that is there.
- The firmware. The one it is for, or several, and the version you run.
- What you want to do. The operating it is for — portable, a contest, a remote station, a net on a reflector, listening on a web SDR — not only the feature.
- How you do it today. On the radio, with a program, a phone app or another control head, and what is missing or awkward.
- Where it would live. On the face, on the configuration page or in the API: what you would do and see. A sketch helps.
- What it depends on. A radio's protocol or command, a service or a device, with a link to its documentation.
- How you can help. Testing it on your radio, a pull request, the documentation.