Customizations of the D-Tacq are contained in /ffs and /bigffs, two non-volatile file systems on the busybox linux implementation. As part of the /ffs file system, /ffs/dropbox is the master root file system that is being copied verbatim to / in RAM at boot time. Any configuration change, to be permanent, have to be written to /ffs/dropbox. Any configuration change to / in RAM is lost at the next reboot.
The custom files are available as a tar ball called dtacq_ffs.tgz in the software repository.
The instructions below are matching the current Linux host configuration Ubuntu 16.04? . A switch is used to interconnect PC, Dtacq, PA, and external modem/router. Gateway is assumed to be 192.168.1.1 as seen from the internal private network relayed by the switch. If another private net is used, 192.168.1 has to be updated everywhere (i.e. 172.16.3 as used originally in Mexico).
To upload the custom /ffs onto a factory-new D-Tacq:
- boot the linux wera/lera server
- copy dtacq_ffs.tar to /home/wera/data on the server
- connect the D-Tacq front-panel ethernet to the dedicated ethernet port of the server with a cross-over (yellow) cable
- configure the port on the server to 192.168.1.1 (/etc/network/interfaces)
- connect a Keyspan RS232-USB converter to the console port of the D-Tacq and to a USB port on the server (use a null-modem cable!!!)
- boot the D-Tacq
- access the D-Tacq console from the server with screen /dev/ttyUSB0 38400.
- login as root, password d-t1012q (all units)
- vi /ffs/rc.local.options and insert the IP configuration line with IP0=192.168.1.12
- in /ffs/rc.local.options, make sure NTPCLIENT="192.168.1.1 2784786"
- in /ffs/start.ntpclient, make sure that NTPHOST points to 192.168.1.1
- in /ffs/user/rc.user, make sure that nfsmount points to 192.168.1.1
- reboot the D-Tacq
- login as root on the D-Tacq console (or over ethernet from the server with ssh root@192.168.1.12)
- /bin/nfsmount 192.168.1.1:/home/wera/data to mount server onto D-Tacq
- cd /;tar -cf /mnt/dtacq_ffs_$(hostname)_orig.tar ./ffs ./bigffs
- cd /;tar -xzf /mnt/dtacq_ffs.tgz
- reboot the D-Tacq
- verify that the network interface on eth0 is 192.168.1.12
- it should start acquiring data at the next scheduled crontab as soon as clock and trigger are applied
- any changes in crontabs, to be permanent, should be in /ffs/dropbear/var/spool/cron/crontabs/root , which will be active at next reboot
- any changes in the acquisition script, to be permanent, should be in /ffs/dropbear/usr/local/bin/lera_control , which will be active at next reboot
