开云体育

Is anyone aware of a recipe for the from this past weekend? I tried creating a recipe, placing in the Documents/CCContents folder, but it's not being recognized by the program. Hoping someone has already correctly created the recipe....

Thanks in advance,

Jack
NG2E

Here's my attempted recipe .

I'm sorry I didn't get a chance to look at this last night. I'll take a look tonight after work.

I'd like to remind everybody that there is a write-up on how to create recipes in the documentation folder of CabConverter. At first glance, I think the problem with this one is in the QSO portion where we're using an unknown tag. It should have been something like STX or SRX for the sent text and received text fields.

Also, if you run CabConverter from the command line it will show error messages for what when wrong during the recipe's parsing.

More tonight. 73!

-- Scott (NE1RD and author of CabConverter)

Scott

Much appreciated. I used your instructions, examples (ARRL-VHF and Field Day), but I just didn't know where elements such as my grid, their grid, and serial numbers ought to go. I looked up teh and articles on . Still couldn't determine if grids and serial numbers ought to go in STX/SRX or use another element. Also didn't know how much of the header was "mandatory" or not.

Latest version attached.

Thanks in advance,

Jack

MacLogger DX provides two input places for received exchange data: the SRX and SRXn. The first (SRX) is used for capturing a text exchange. The second (SRXn) is used to capture a number (typically a serial number). We don't capture exchange data into GRID or STATE or other fields. It would be better if we could, but that isn't how the UI was set up when we began in 2013.

If we're capturing, say, a GRID, then we tell the user to configure the contest panel in MacLoggerDX to present the text fields (SRX and STX) to the user, then we lay out those values in the QSO record using <SRX> and <STX> XML tags. (If users also want to put that information in the GRID field of MacLoggerDX, they can either copy it later from the SRX field, or use the mapping that newer versions of the logger provide).

In short: all we have for received exchange information is one of two fields: TEXT or NUMERIC, SRX or SRXn. Those are the only two exchange fields that can appear in the QSO record for received data.

From the document:

The following keywords are available for the QSO section:

?

????????????? TheirCallsign????? ~ The call sign of the station contacted in this QSO

????????????? MyCallsign??????????????????????? ~ The call sign of the user (obtained from the personal data section)

????????????? Date?????????????????????????????????? ~ The date of the QSO in the form YYYY-MM-DD

????????????? Time????????????????????????????????? ~ The time of the QSO in the form HHMM

????????????? Frequency??????????????????????? ~ The frequency of the QSO in the form NNNNN (in KHz)

????????????????????????????????????????????????????????? ? unless the inMhz="true" which formats it in MHz NN or NNN

????????????? Mode??????????????????????????????? ~ The mode used in the contact (see note below)

????????????? RSTs?????????????????????????????????? ~ The RST sent

????????????? RSTr?????????????????????????????????? ~ The RST received

????????????? STXn????????????????????????????????? ~ The serial number (numeric field) sent

????????????? SRXn????????????????????????????????? ~ The serial number (numeric field) received

????????????? STX???????????????????????????????????? ~ The exchange string sent

????????????? SRX???????????????????????????????????? ~ The exchange string received

In this case I believe we need to have the exchange information in the SRX/STX fields (even if it means going back through the log and copying stuff into those fields from elsewhere), and then using those fields in the recipe. I should note that I've fixed lots of logs from folks that worked a contest without first reading the contest-specific instructions for CabConverter, and they put stuff in the wrong place. Fixing it was just a tedious bit of copy-paste so the SRX and STX fields were populated, so it isn't a disaster, but it does take some time. It is better to just have a contest-specific instruction file available and to think ahead about how the recipe must fill in the log when we're done.

I hope this helps. I'll still give it a look tonight. Thanks and 73!

-- Scott (NE1RD and author of CabConverter)

Scott,

Thanks for the SRX/STX and SRXn/STXn info. Makes sense.?

Still confused about adding power and station class to the log. The contest organizers aren't that clear on the format other than to recommend using N1NN to burn the Cabrillo log....

Latest recipe version enclosed. Talk to you later.

Jack

Scott,

Thanks for all your help!

I've attached the latest and greatest Portable Operations Challenge recipe.

Jack
NG2E