Until now, they are a convoluted way of saying "0" or "1".
Also, for some reason it set a register, but read the values set from
program.
On the original driver, domXcvr is set to 0 on the constructor and then
never changed.

For some reason, here it was being called inside the tearDownRing
function. Changed that to be set on the constructor.

Remove domXcvr functions.

See merge request !65

It checks reading status before write on masked field value on the register.

userFieldWrite reading check

Closes ICSHWI-22215

See merge request !66

Improve log

Closes ICSHWI-21398

See merge request !67

Eventcode

Closes ICSHWI-22072

See merge request !68

The other bits only tell you which fibers generated the error, so it should only be checked
if there is an error message at all.

Also, ignore timeout error if message didn't come from a ring. Timeouts
only come from rings.

Make replyStatus only check last four characters.

See merge request !69