asyn READBACK tag allows for waveform record to be updated whenever the
callback is called in code.

Without this, OPIs usually can't properly put or get to uninitialized
waveform records.

For user to be able to visualize what values are converted into
parameters.

Added enable/disable option, which now requires for all records to be
instantiated so we can properly communicate.

This particular IOC spits some error messages with the current test
setup because it only has two hybrids.

In this case the semicolon ended up being part of the property name in
the db file. Of course, this is not good but I wanted to avoid having to
add $(C)=':' for now.

Its easy to change in the future if needed.

Added logging details to several functions. Also added log messages to
IOCMessage parameter.

As noted on st.cmd, instead of naming records <Device>:HybN we will name
them <Device><N>:<Property> (So the number is actually part of the
device).

So records with two digits refer to the whole IOC, records with three
digits refer to hybrid-specific parameters and records with four digits
refer to VMM3A specific parameters.

It was looking for parameter VMM_FEN_ACQUIRE but not finding it.
Now it can properly read the parameter, although it shouldn't be needed
to be read most of the times...

All parameters that share the same ADC are now added: Pulser, Threshold,
Temperature and Bandgap.

All except temperature are showing weird values though, so that needs to
be investigated. I suspect something to do with configHybrid or configFE
or configVmm, but I am not sure.

This reads Temperature from API memory and sets the structure for future
parameters such as BandgapADC, etc...

The timestamp is also read and put into a PV in order to be explicit for
user when was the last time it was read from hardware.

Now if API returns a bad status, asyn knows about it.

To use the correct term.

removed proof of concept. Made it work for all VMMs of all hybrids.

Turns out it wasn't that different from others. All it needs is to
change a bo record to ao.

Didn't add SD because the mechanism is a bit different.

This commit was done with an inescrupulous "git add ." after several
radical modifications.

Anyway, the API was radically modified and basically the old way the
code worked does not make any sense anymore.

The desired architecture is the following: the API is going to be used
as a class component. Each parameter will be created according to the
desired number of enabled hybrids.

Each parameter should use one simple API function. No information about
the VMM or hybrids itself is stored in the VMMTbl class unless extremely
needed.

This commit leaves a few old parameters that should be removed in the
future such as ADC_VALUE_VMM1, READ_ADC_VMMS, etc. This is only to serve
as a reminder to add those later.

Mostly just change names of files or classes.

Use new API architecture.

See merge request !5

If check is not made, ioc will try to write to register in the beginning and fail, crashing the application.

It wasn't supposed to be here. Should be named configFE only.

According to new VmmTblConfig definition

VmmTbl now inherits from asynPortDriver instead of FrontEndBase.
It has VmmTblAPI as a class component.

Thus, everything that used pRMM->foo(); such as pRMM->setStringParam(addr_list, vmmHybFwVersion_[hyb], pVMMConfig.readFwVersion(hyb).c_str());
are simply foor(); (equivalent to this->foo();)

Everything that used pVMMConfig.foo(); now uses pVmmTblAPI->foo();

configFEN had its name changed to configFE since the last configFE did
nothing.
Old configFE was removed.

In the end, findRegister() was not moved to VmmTblAPI because it seems
to be searching for a given register name based on an epics parameter.

As far as I know this would only be used if we wanted to install the
module and use it's headers.

I don't see why we would do that now.