It's important to clarify the positioning of this bot. There are already many mature logging software options available, but the challenge for HAM (amateur radio operators) has always been the ability to log data in remote locations with just a mobile phone. Therefore, it should be positioned as a solution specifically designed for outdoor use, where only a mobile phone is available and manual data entry is inconvenient. Given that QQ is popular among young people, it's recommended to focus on satellite communication features and optimize them accordingly.
Regarding data format, exporting in ADIF format (also known as "qrz format") is essential. Both shortwave and satellite users will definitely use this format. If it's not possible to export, then it won't be usable. There are existing libraries available, so you don't need to parse it yourself.
Regarding QSO parsing, since it's for outdoor use, the parsing of QSOs entered by users will inevitably become very complex. Users can enter in any format, so appropriate error handling is necessary. For example, if a user enters "439600", "144640", or "14270", it should be corrected to "439.600", "144.640", or "14.270". Similarly, entries like "2025/5/5", "2025.5.5", "2025-05-05", and "May 5th" should all be recognized. Ideally, the system could also function like a delivery service, where entering an address automatically identifies the province, city, district, and street.
It's important to specifically mention satellite communication here. Using satellite communication allows for short-term, multi-person communication, and the frequencies used are common satellite frequencies rather than specific frequency numbers, such as:ISS (satellite name) - Contacted multiple parties within minutes.
QSO AAA BBB CCCIn cases like this, if QTH is specified, it would typically be indicated using the Megen-Heide positioning method (OM86(and so on). If these data can be parsed, and if the bot adapts to user habits rather than requiring users to input data according to its own preferences, then this bot has a real chance of becoming truly successful.
The situation regarding uploading and exchanging QSL cards is very complex. The "exchange card" function on the HamCQ forum has a number of issues, so it's recommended to avoid using it for now.
There are also some specific technical details that need to be addressed:
- Don't reinvent the wheel with frequencies; instead, use existing libraries like HamCQ's repeater data.
- Signal reports should not be overly prescriptive in their format. For those using shortwave, other formats may appear, such as -12, +01 (of course, these signal reports would also be automatically recorded by a computer and not used with this bot), and 599.（CW）Do not enter the default value of 59.
- Deletion and unbinding require a secondary confirmation.
- Ensure that the association between satellites and their frequencies is properly maintained in the background. Do not allow users to manually enter frequencies during satellite communication.
- Satellite Communication can even automatically log data without any instructions, as long as you use the "@" symbol to refer to the robot and input the Satellite Communication record format.
- Some tedious tasks, such as certain parsing programs, can be demonstrated with examples and then given to AI to complete.
闽ICP备2021006864号-7
闽公网安备35020602002794号