{"id":44,"date":"2017-10-11T16:01:23","date_gmt":"2017-10-11T20:01:23","guid":{"rendered":"http:\/\/sites.nd.edu\/attpc\/?p=44"},"modified":"2017-10-11T16:01:23","modified_gmt":"2017-10-11T20:01:23","slug":"attpc-daq-hardware-and-first-setup","status":"publish","type":"post","link":"https:\/\/sites.nd.edu\/attpc\/2017\/10\/11\/attpc-daq-hardware-and-first-setup\/","title":{"rendered":"ATTPC DAQ hardware and first setup"},"content":{"rendered":"

The hardware of the ATTPC DAQ consist of one workstation (two network cards at least, one could be SFP+ network card), one $$\\mu$$TCA crate. Inside the\u00a0$$\\mu$$TCA crate, a MTH module (must have a fiber port and an ethernet port), a power module and a series of Cobo boards are installed.<\/p>\n

<\/p>\n

The topological map<\/a> is attached. The workstation is indirectly connected to Cobo through MCH, by connecting one ethernet card of the workstation to the ethernet port of MCH and also the SFP+ network card to the MCH SFP+ port.<\/p>\n

\"\"
Fig 1. A schematic from the GET electronic official website<\/figcaption><\/figure>\n

 <\/p>\n

However, for better expansion in the future, we implement the structure with an additional fast switch (10Gbit\/s)<\/p>\n

\"\"
Fig 2. Current schematic implemented in NSL.<\/figcaption><\/figure>\n

 <\/p>\n

The switch is transparent, so user\u00a0should\u00a0should really think in Fig. 1.<\/p>\n

The current Linux Workstation is installed with Ubuntu 16.04 LTS. Only LTS version should be considered, as the GET data acquisition software may not work with any other version.<\/p>\n

    \n
  1. Two network cards are needed in the workstation<\/li>\n
  2. one should be setup manually as 192.168.40.*, the other should be 192.168.50.<\/i>*<\/li>\n
  3. The crate needs MCH, Cobo, and power module<\/li>\n
  4. connect the network card with 192.168.40.* to the MCH GibE port (either one of the two), one of the SFP port needs to connect to the other network card \u00a0through fiber connection<\/li>\n
  5. install DHCPD server and start the service (assign ip addresses for two cobo hardware: control and data)sudo apt-get install isc-dhcp-server;\u00a0<\/i>sudo service isc-dhcp-server start<\/i>;if the device can not get ip address, you need to click the net card in the network tap and restart dhcp service: somehow this is required for the linux systemin the \/etc\/defaults\/isc-dhcp-server, add “e*” to the interfaces=”” for the two ethernet cards. For my case, it was interfaces=”eno1 enp2s0″<\/i>the \/etc\/dhcp\/dhcpd.conf<\/a> needs to be configured as attached. Remember to change the mac address<\/strong> according to the description on the cobo module.<\/li>\n
  6. \u00a0The uart port of the cobo can be connected using a regular microusb port to the workstation, a special driver is needed. (the driver is ready for Ubuntu 16.04 Lts, so no need for this)
    \n    http:\/\/www.silabs.com\/products\/mcu\/pages\/usbtouartbridgevcpdrivers.aspx
    \na<\/a>fter the installation, connect uart port to the workstation and type minicom -D \/dev\/ttyUSB0 (notice the “ttyUSB0” may be different depending on the specific setting of user’s PC), minicom setting is in link below
    \n    https:\/\/dsm-trac.cea.fr\/get\/wiki\/HowToSetupCoBo<\/a><\/li>\n<\/ol>\n
      \n
    1. We also need to set up the nfs sharing service. In Ubuntu 16.04 LTS, nfs-server can be installed by typing sudo apt-get install nfs-server; then use the replace the existing \/etc\/exports<\/a>\u00a0(pls remove the .txt extension after downloading) with file below and create a folder \u00a0\/mnt\/local\/export\/filesystem. Put getHwServer.out<\/a> and startup.vxsh<\/a> in this folder.<\/li>\n<\/ol>\n

       <\/p>\n

        \n
      1. Before the MCH can redirect signals to the cobo control and data ports. Settings below are required.\u00a0https:\/\/wikihost.nscl.msu.edu\/attpc\/doku.php?id=microtca_development<\/a>\u00a0in the link a total 9 steps are shown, but only the first 7 are required, and\u00a0it does not hurt to do step 9 (step 8 are not available for current get firmware).also these 7\/8 steps can be performed either using ssh with the ethernet 192.168.40.* cable connected to the MCH ethernet port, or you have a serial port to “GbE0\/1” ethernet port and you connect the PC serial port to the “SER” ethernet port on the MCH.For the first scenario, \u00a0you do\n
        ssh root@192.168.40.250<\/pre>\n
        after login you type in the MCH terminal<\/p>\n
        vt\u00a0set\u00a0rs232sel=0
        \nexport\u00a0TERM=vt100;\u00a0stty\u00a0rows\u00a01024\u00a0cols\u00a080
        \nminicom\u00a0-w\u00a0-o\u00a0ttyS2<\/div>\n
        press enter you will see<\/p>\n
        10GbE_Mgmt login:<\/code><\/div>\n
        edit \/etc\/rc.d\/rc.local<\/p>\n
        vi \/etc\/rc.d\/rc.loca<\/code><\/div>\n
        append the following<\/p>\n
        axel_1g_port\u00a015\u00a0#\u00a0(AMC\u00a001)
        \naxel_1g_port\u00a07\u00a0#\u00a0(AMC\u00a002)
        \naxel_1g_port\u00a00\u00a0#\u00a0(AMC\u00a003)
        \naxel_1g_port\u00a08\u00a0#\u00a0(AMC\u00a004)
        \naxel_1g_port\u00a016\u00a0#\u00a0(AMC\u00a005)
        \naxel_1g_port\u00a013\u00a0#\u00a0(AMC\u00a006)
        \naxel_1g_port\u00a019\u00a0#\u00a0(AMC\u00a007)
        \naxel_1g_port\u00a011\u00a0#\u00a0(AMC\u00a008)
        \naxel_1g_port\u00a03\u00a0#\u00a0(AMC\u00a009)
        \naxel_1g_port\u00a04\u00a0#\u00a0(AMC\u00a010)
        \naxel_1g_port\u00a012\u00a0#\u00a0(AMC\u00a011)
        \naxel_1g_port\u00a017\u00a0#\u00a0(AMC\u00a012)<\/div>\n
        save and restart<\/p>\n
        you can also choose to physically isolate the 10GbE and the 1GbE switches. Disconnect the 1GbE switch from the 10GbE by typing:<\/p>\n
        A-\u00a0login\u00a0to\u00a010GbE\u00a0switch\u00a0using\u00a0ssh\u00a0or\u00a0rs232\u00a0(as\u00a0indicated\u00a0above)
        \nB-\u00a0when\u00a0you\u00a0see\u00a0the\u00a0prompt\u00a0type\u00a0cli
        \nC-\u00a0in\u00a0CLI\u00a0type\u00a0set-port-state\u00a016\u00a0disable
        \nD-\u00a0then\u00a0type\u00a0save-config<\/div>\n<\/li>\n<\/ol>\n
        <\/div>\n
        <\/div>\n
        <\/div>\n
         <\/p>\n","protected":false},"excerpt":{"rendered":"
        The hardware of the ATTPC DAQ consist of one workstation (two network cards at least, one could be SFP+ network card), one $$\\mu$$TCA crate. Inside the\u00a0$$\\mu$$TCA crate, a MTH module (must have a fiber port and an ethernet port), a … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2309,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[264825],"tags":[],"class_list":["post-44","post","type-post","status-publish","format-standard","hentry","category-get-electronics"],"_links":{"self":[{"href":"https:\/\/sites.nd.edu\/attpc\/wp-json\/wp\/v2\/posts\/44","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sites.nd.edu\/attpc\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sites.nd.edu\/attpc\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sites.nd.edu\/attpc\/wp-json\/wp\/v2\/users\/2309"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.nd.edu\/attpc\/wp-json\/wp\/v2\/comments?post=44"}],"version-history":[{"count":1,"href":"https:\/\/sites.nd.edu\/attpc\/wp-json\/wp\/v2\/posts\/44\/revisions"}],"predecessor-version":[{"id":45,"href":"https:\/\/sites.nd.edu\/attpc\/wp-json\/wp\/v2\/posts\/44\/revisions\/45"}],"wp:attachment":[{"href":"https:\/\/sites.nd.edu\/attpc\/wp-json\/wp\/v2\/media?parent=44"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sites.nd.edu\/attpc\/wp-json\/wp\/v2\/categories?post=44"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sites.nd.edu\/attpc\/wp-json\/wp\/v2\/tags?post=44"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}