R2DBE system setup

    Version as of 12:25, 9 Nov 2024

    to this version.

    Return to Version archive.

    View current version

    Pre-Checks

    • Check that the 1pps is connected to all R2DBE units (frontside)
    • Check that the IFs are connected to the Block Down Converter (BDC) with RCP and LCP as labeled on the backside
    • Check that the 10MHz signal is connected to the clock synthesizer unit
    • Check that the 10MHz signal is connected to the BDC unit
    • Check that the both IF input pins of all R2DBE units (frontside) are connected by cable
    • Check that all R2DBE units are connected by ethernet (PPC net port)  to the network hub box (backside)
    • Check that the noise generator unit is connected by ethernet to the network hub box (backside)
    • Check that all mark6 units are connected by ethernet cable to the the network hub box (backside)
    • In case you want to inspect the R2DBEs autocorrelation spectra make sure you insert a tone into the noise generator unit (backside)

    Startup sequence

    1. power on pv-mark6-1 and pv-mark6-2
    2. power on the clock synthesizer unit
    3. power on the BDC
    4. power on the noise generator
    5. power on the R2DBEs

    Verify startup

    • log into pv-mark-1 as user oper. If logging-in does not work the mark6 machine is probably stuck in booting. Connect a display and keyboard and check.
    ssh pv-mark6-1 -l oper -X
    ssh pv-mark6-2 -l oper -X
    
    • do the same with pv-mark6-2
    • log into pv-mark6-1 as user oper. Verify that all the R2DBEs units have booted up by trying an ssh connection:
    ssh r2dbe-1 -l root
    ssh r2dbe-2 -l root
    ...
    exit from r2dbe-1, r2dbe-2, ...
    

    if one of the units does not boot consult the Troubleshooting section below.

    Configuring the R2DBEs

    • log-into pv-mark6-1 as user oper
    • initialize all the R2DBE units by running:
    start-r2dbe-1
    start-r2dbe-2
    ...
    

     

     

    Troubleshooting

    R2DBE unit does not boot