Temporary workaround for new helicity decoder board (HD) firmware

[baltzell]

Closes #532. On 21280, it now does this:

***** >>> adding : /runcontrol/fcup / table = /runcontrol/fcup
***** >>> adding : /runcontrol/slm / table = /runcontrol/slm
***** >>> adding : /runcontrol/hwp / table = /runcontrol/hwp
***** >>> adding : /runcontrol/helicity / table = /runcontrol/helicity
***** >>> adding : /daq/config/scalers/dsc1 / table = /daq/config/scalers/dsc1
[DB] --->  database disconnect  : success
ERROR:  HelicityDecoder EVIO data is corrupted. Trigger time word not found.
ERROR:  HelicityDecoder EVIO data is corrupted. Trigger time word not found.
ERROR:  HelicityDecoder EVIO data is corrupted. Trigger time word not found.
ERROR:  HelicityDecoder EVIO data is corrupted. Trigger time word not found.
ERROR:  HelicityDecoder EVIO data is corrupted. Trigger time word not found.
ERROR:  HelicityDecoder EVIO data is corrupted. Trigger time word not found.
ERROR:  HelicityDecoder EVIO data is corrupted. Trigger time word not found.
ERROR:  HelicityDecoder EVIO data is corrupted. Trigger time word not found.
ERROR:  HelicityDecoder EVIO data is corrupted. Trigger time word not found.
ERROR:  HelicityDecoder EVIO data looks like v2 firmware(?), ignoring it.
ERROR:  HelicityDecoder EVIO data looks like v2 firmware(?), ignoring it.
ERROR:  HelicityDecoder EVIO data looks like v2 firmware(?), ignoring it.
ERROR:  HelicityDecoder EVIO data looks like v2 firmware(?), ignoring it.
ERROR:  HelicityDecoder EVIO data looks like v2 firmware(?), ignoring it.
ERROR:  HelicityDecoder EVIO data looks like v2 firmware(?), ignoring it.
>>>>> progress :  (       37722) :  time :    10.00 (sec) =>>> average time =     0.265 msec
>>>>> progress :  (       86605) :  time :    20.00 (sec) =>>> average time =     0.231 msec
........