piWebCAT

3.10  Please read:  The vx and abx fields restated!!

The use of the vx and abx data fields is discussed elsewhere.

It is easy to initially overlook their correct use ...

(in view of the large amount of other configuration information!)

I guess that I feel the need to restate vx and abx use because it took me quite a number

of iterations to get this correct.
Part of the problem was not fully understanding the behaviour of the IC-7000 in relation
to which receiver settings are VFO A or B specific.

piWebCAT loads up to 90 button states and 22 sliders states at start up.

Settings may be different for different bands and/or between VFO A and VFO B.

This will vary between radios.
piWebCAT  can store the latest setting for each of these controls. This avoids having to reload
settings from the radio on VFO A/B switching.

In order to do this, it needs to know which settings can change with VFO change.

(If the settings are VFO specific, then it stores separate A and B VFO settings)

IC-7000   IC-7610

My IC-7000 piWebCAT configuration controls the receiver parameters including those listed below.

The details given in the table refer to  the behaviour of the radio,

Buttons: If  separate per VFO then needs two catcodesciv records: one for A and one for B

         (These two records are identical ... but not so for other radios (Yaesu) ... compatibility need)

 If there is group of buttons,  then one buttonsciv record per button.
        (buttonsciv is client data, catcodesciv is server data)

Sliders:  Two records in slidersciv if 'separate'.  
       (slidersciv has both client and server data)

The IC-7000 manual provides CAT codes for all the above but does not appear to give any indication of

whether single or separate per VFO.   - I had to experiment.

The CI-V manual for the current, dual receiver  IC-7610 does not appear to state which settings

are separate per VFO.     piWebCAT needs to know this information. You have to experiment !

Yaesu FTdx101D   - 

Most receiver settings are separate between the two VFOs.    

So most settings have two (A & B) catcodes and sliders table entries
and have buttons.vx = V  catcodes.abx = A and B  sliders.vx = V  and sliders.abx = A and B.

Why this level of complexity??  
Reason  - Buttons and slider related settngs change on VFO switching and would need reloading. This perhaps
takes longer on a web server based solution compared to direct connection from PC to radio.
I therefore store the latest settings against each VFO to avoid a reload.   I need to know which settings change.