This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
operations:documentation.dbbcsetupivs_v2 [2015/01/23 04:41] cjordan [Setting the IFs] |
operations:documentation.dbbcsetupivs_v2 [2016/10/08 16:08] Jesse Swan |
||
---|---|---|---|
Line 30: | Line 30: | ||
Enter Command: pps_sync | Enter Command: pps_sync | ||
</code> | </code> | ||
+ | |||
+ | During observations, the log monitor will ring an alarm if the internal delay in the dbbc has changed. This is automatically tested every scan. To trigger the command yourself, use | ||
+ | ''dbbc=pps_delay=1''. | ||
===== Setting the IFs ===== | ===== Setting the IFs ===== | ||
Line 36: | Line 39: | ||
You now need to set up the IF system. The commands to do this depend on the IVS observation. | You now need to set up the IF system. The commands to do this depend on the IVS observation. | ||
- | For R1, R4, AUSTRAL, CRF, CRDS and RDV experiments they should be: | + | For R1, R4, AUSTRAL, CRF, CRDS, AUG, AUA and RDV experiments they should be: |
<code> | <code> | ||
ifa=1,agc,1 | ifa=1,agc,1 | ||
Line 47: | Line 50: | ||
- | For APSG, OHIG and T2 experiments they should be: | + | For APSG, OHIG, AOV and T2 experiments they should be: |
<code> | <code> | ||
ifa=1,agc,1 | ifa=1,agc,1 | ||
Line 73: | Line 76: | ||
**Chris: I don't think the following has been an issue for some time. Candidate for removal?** | **Chris: I don't think the following has been an issue for some time. Candidate for removal?** | ||
+ | |||
There is a known issue where the target levels loaded by the DBBC through load=dbcc... are incorrect. For now, the workaround is to specify the target power levels in the ifdsx section of the proc file. | There is a known issue where the target levels loaded by the DBBC through load=dbcc... are incorrect. For now, the workaround is to specify the target power levels in the ifdsx section of the proc file. |