After booting the DOMhub the following commands need to be executed:

sudo nohup domhub-services &

Check the process really exists:
ps -ef | grep services
 
Because there is no GPS clock attached, execute command:
 
clock all internal
The following commands may be useful in case of problems...
reload all dor card fpgas
for card in /proc/driver/domhub/card*; do echo ‘reload 3’ > ${card}/fpga; echo ‘reload 1’ > ${card}/fpga; done
 
 
Additional checks which are good to make the first time at beginning of FAT:
'on all' (gives this)
 
'gotoiceboot' (gives this)
 
Note about LEDs on the back of the domhub:
Before 'on all': DSB small red LED on, DOR: small yellow LED on (steady)
After 'on all': DSB no change. DOR: both big red LEDs on . Blinking big green LEDs for 30 secs.
After 'gotoiceboot': DSB no change. DOR: both big red LEDs still on. small green LED blinks, then big yellow and big green and then big yellow off, then big green off. This happens on all cards in sequence.  
 
 
Run gotoiceboot twice, ONLY if you need the main board IDS!
If you run it twice, you will have to do 'off all' beofre any tests! 
 
ultuna1 root /home/testdaq/ gotoiceboot (gives this)
 
each DOM draws about 40 mA, so you should see a corresponding change 
on the LED display of the domhub
To see the currents do this on ultuna1:
cat /proc/driver/domhub/card*/pair*/current