6.2 piWebCAT - Database table - buttonsciv See buttons configuration notes timing.disable
- rig The current radio - drop down selector (from radios table)
Must have same spelling through the tables.
- description Descriptive text- no function
- colour Button's background colour at startup.
Can be a standard HTML color, eg teal,indigo etc or a numeric colour:
ie: #RRGGBB eg #223344 where 0x22 is red level (0x00 - 0xFF)
- caption The caption to be applied to the button at start up. Must fit the button's width.
Try something and then observe. (Lower case letters are MUCH narrower!)
- btnno The button's unique, fixed, numeric identifier. See: Button and slider numbering
- active Y = button active N = button inactive S = active + sync (repetitive state update from rig)
L = sync and 'LED' read-only indicator lamps ( See: LED buttons )
- code 3 or 4 upper case characters. This links a button command to its action
on the server. It must match the code for the linked record in catcodes.
See below for more explanation.
- vx V for client to send A or B according to current VFO. (A and B catcodes records)
X to send X (single non-VFO dependent server record. U no action to server.
(U = do not participate in buttons state store and retrieve) See: vx and abx
- action S = single momentary. Button flashes briefly. Sends von column value.
T = toggled. Alternates on/off. Client code highlights it when on and remembers
its current state. Sends von or voff column value.
G = grouped. Is in a group of other G buttons with the same code.
Only one of the group is highlighed. The data value associated with each button is in
the bgsdata field (which is also used in setting button state from the radio at startup.
M = a meter button. R = a slider reset buttons
- von ON value for an on/off button ie: action = S or T (usually 1 )
- voff ON value for an on/off button ie: action = S or T (usually 0 )
- bgsdata Used for grouped buttons data (ie: action = G). Each button in the group has an
identifying code value in bgsdata.
The buttonciv table fields have to be set up in cooperation with the corresponding record(s)
in the catcodesciv table.
piWebCAT's buttonsciv table editor is shown below:
I choose to leave unused inactive entries in the buttons and buttonsciv tables,
They carry the unused, fixed, unique btnno values. See: Button and slider numbering
The shift up and down buttons must use codes FRUP and FRDN as this is a hard coded function on the server.
See: Frequency up /down buttons
Unmatched button conditions
If a button group does not have a button to match all corresponding states on the rig, then an error arises.
My FTdx101D has fifteen modes. If I only configure buttons for seven, then selecting one of the other eight
on the rig will cause a problem. This is discussed at the end of section 2.11 Learning guide Transceiver-H-A
Tx meter buttons
These do not communicate with the server - they select the Tx meter on the client
action = M and the code field is fixed as TXME
Clicking the button does not issue a command to the radio. It records the Tx meter selection
on the client so that the repetitive meter read process read the correct meter.
TXME also identifies the group members in order to clear the group before highlighting the clicked button.
Meter reading codes are set up in the meter table.
The link to the meter table is the button numbers 61 to 65. See section 4.5 Table meter