The following instructions assume that the base of your MIDAS installation is /MIDAS.
The files hawk.o and D2VBexec.o are in the standard release of the VxWorks package. However they can also be obtained from the source archive. Unpack the Data_Acq_020200.tar.gz archive and copy the Data_Acq/hawk.o file to /MIDAS/obj/hawk.o and the Data_Acq/D2VBexec.o to /MIDAS/obj/D2VBexec.o.
Modify the VxWorks startup.cmd file for your event builder system to look like this:

cd "/MIDAS/obj"
ld < rdwr.o
ld < message.o
ld < register-server.o
ld < registers.o

ld < ersconfig.o
ld < generic.o
ld < VME.o

msgInitialise
taskDelay 100  /* we seem to need a pause before starting the register server */

/* start the register server */
  
ersInstall "vme", "/MIDAS/config/null"
taskDelay 200
ersconfig "/MIDAS/vxi/registers_defn"
taskDelay 200 

#    data acquisiton from D2VB/F2VB
ld < hawk.o
Hawk_Ram_Addr = 0x40400000
EGTS_UDP_PORT = 10305
hawkInstall "128.0.0.1", "128.0.0.2"  /* IP addresses   Event Builder ,  TapeServer on the data network */

taskDelay 250

ld < D2VBexec.o
D2VB_init

The VME base address of the HAWK ethernet buffer RAM is defined by the statement Hawk_Ram_Addr = 0x40400000 (This is the default value in the software). The VME base addresses of the D2VB module are 0xe00000 (A24 space) and 0x1000000 (A32 space). These cannot be changed without recompiling the D2VBexec module (they are defined in the d2vb.h file).
The IP addresses are the addresses of the event builder system and the tape server system on the data network. Note that these are the IP addresses on the data network and not the IP addresses which the system is normally accessed by. In the case of the Tape Server it is now possible to use the primary ethernet interface if a second interface dedicated to the data network is not available. In this case only the Tape Server IP address is the same as used for normal accesses to the system.

The VxWorks event builder system has a register server for VME access and program control. This requires an apparatus file of the form:

   ((name vme)
    (host xxx)
    (role vme)
    (type register)
    (ipaddress 123456)
    (port 10220))

Testing

There are test facilities built into both the D2VBexec task and the hawk task. These both permit test data to be generated.

Testing with data generated within the Hawk task.

1) Using the MIDAS GUI mount and open a tape file
2) Set the Server state: choice to Go from the Tape Control window.
3) On the VxWorks console enter the command

       testmode=1

You will get 1 block per second. You can control the rate by again from the Vxworks console

       delayticks=n

Default is 60. This is number of 1/60 sec ticks between blocks. So n=6 will generate 10 blocks/sec.
You can also run this test without a tape server. In this case omit steps (1) and (2). On the VxWorks console enter the command

       runmode=1

4) To stop on the VxWorks console enter the commands

       testmode=0
       runmode=0

Testing with data generated within the D2VBexec task.

1) Using the MIDAS GUI Mount and open a tape file
2) Set the Server state: choice to Go from the Tape Control window.
3) On the VxWorks console enter the commands

       D2VB_go
       D2VB_GenEnable=1
       D2VB_TxEnable=1

You will get 1 block per second. You can control the rate by again from the Vxworks console

       D2VB_GenTicks=n

Default is 60. This is number of 1/60 sec ticks between blocks. So n=6 will generate 10 blocks/sec.
You can also run this test without a tape server. In this case omit steps (1) and (2). On the VxWorks console enter the command

       runmode=1

4) To stop on the VxWorks console enter the commands

       D2VB_GenEnable=0
       D2VB_TxEnable=0
       D2VB_stop

 return to MIDAS download home page