Login/password

Check the label behind the monitor. Check the keyboard layout (set to en, it will start fr).

After power-up

Routine checks that all hardware is properly configured and actions to take in order to restart monitoring programs.

Network setup

First check network situation

[rd53daq@lpnws5145 ~]$ ip route
default via 134.158.152.1 dev enp0s25 proto dhcp metric 101 
134.158.152.0/22 dev enp0s25 proto kernel scope link src 134.158.155.145 metric 101 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 
172.18.0.0/16 dev br-4de46983819a proto kernel scope link src 172.18.0.1 
172.19.0.0/16 dev docker_gwbridge proto kernel scope link src 172.19.0.1 
172.20.0.0/16 dev br-43e4a3f8dda4 proto kernel scope link src 172.20.0.1 
192.168.10.0/24 dev p3p2 proto kernel scope link src 192.168.10.1 metric 100 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 

Monitoring programs

Open a terminal and start a screen session, then enter the python2 environment mqtt2 and start the mqtt-to-influxdb forwarder

[rd53daq@lpnws5145 ~]$ screen
[rd53daq@lpnws5145 ~]$ cd mqtt-to-influxdb-forwarder/
[rd53daq@lpnws5145 mqtt-to-influxdb-forwarder]$ conda activate mqtt2
(mqtt2) [rd53daq@lpnws5145 mqtt-to-influxdb-forwarder]$ sh ./start_fwd.sh 

then type ctrl-a c to open a new terminal

[rd53daq@lpnws5145 ~]$ cd mqtt-to-influxdb-forwarder/
[rd53daq@lpnws5145 mqtt-to-influxdb-forwarder]$ conda activate mqtt2
(mqtt2) [rd53daq@lpnws5145 mqtt-to-influxdb-forwarder]$ sh ./start_fwd_climats.sh 

then type ctrl-a c to open a new terminal

[rd53daq@lpnws5145 ~]$ cd mqtt-instrument-interface/
[rd53daq@lpnws5145 mqtt-instrument-interface]$ conda activate mqtt
(mqtt) [rd53daq@lpnws5145 mqtt-instrument-interface]$ python mii-climats.py --mqtt-user canary1 --mqtt-pass atlasitk --mqtt-host localhost

GPIB Adapter

Check the device number on the bus (look for 'Agilent'), for example:

[rd53daq@lpnws5145 ~]$ lsusb | grep Agilent
Bus 003 Device 003: ID 0957:0518 Agilent Technologies, Inc. 82357B GPIB Interface

In this case it's Bus 003 and Device 003.

Then load the firmware using the proper bus/device numbers:

[rd53daq@lpnws5145 ~]$ sudo fxload -t fx2 -D /dev/bus/usb/003/003 -I /usr/lib/firmware/agilent_82357a/measat_releaseX1.8.hex 

Now repeat the operation:

[rd53daq@lpnws5145 ~]$ lsusb | grep Agilent
Bus 003 Device 004: ID 0957:0518 Agilent Technologies, Inc. 82357B GPIB Interface
[rd53daq@lpnws5145 ~]$ sudo fxload -t fx2 -D /dev/bus/usb/003/004 -I /usr/lib/firmware/agilent_82357a/measat_releaseX1.8.hex 

After this second restart the light on the adapter should turn green.

Check YARR PCIe card

[rd53daq@lpnws5145 ~]$ dmesg | grep specDriver
[    1.553656] specDriver: loading out-of-tree module taints kernel.
[    1.553815] specDriver: module verification failed: signature and/or required key missing - tainting kernel
[    1.554278] specDriver: Major 244 allocated to nodename 'spec'
[    1.554367] specDriver: Found unknown board (10ee:7024) at 0000:07:00.0
[    1.554386] specDriver 0000:07:00.0: enabling device (0004 -> 0006)
[    1.554394] specDriver: 64bits bus master DMA capable
[    1.554436] specDriver 0000:07:00.0: irq 46 for MSI/MSI-X
[    1.554509] specDriver: Device /dev/spec0 added
[    1.554533] specDriver: Mapped BAR0 at 0xE7100000 with length 1048576
[    1.554627] specDriver: 
</varbatim>

-- Main.FrancescoCrescioli - 2021-10-07
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2022-03-21 - FrancescoCrescioli
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback