Page History
...
You can see optical powers on the kcu1500 with the pykcu command (and pvget). See the timing-system section for an example of how to do this. On the hsd's themselves it's not possible because the FPGA (on the hsd pcie carrier card) doesn't have access to the i2c bus (on the data card).
Note: on the kcu1500 running "pykcu -d /dev/datadev_1 -P DAQ:CPO" this happens when I unplug the fiber farthest from the mini-usb connector:
| Code Block |
|---|
(ps-4.5.10) drp-neh-cmp024:lcls2$ pvget DAQ:CPO:DRP_NEH_CMP024:MON
DAQ:CPO:DRP_NEH_CMP024:MON 2022-03-21 16:41:49.139
RxPwr TxBiasI FullTT nFullTT
2.0993 41.806 0 0
0.0001 41.114 0 0
0.0001 41.008 0 0
0.0001 42.074 0 0
And the first number fluctuates dramatically:
(ps-4.5.10) drp-neh-cmp024:lcls2$ pvget DAQ:CPO:DRP_NEH_CMP024:MON
DAQ:CPO:DRP_NEH_CMP024:MON 2022-03-21 16:41:29.127
RxPwr TxBiasI FullTT nFullTT
3.3025 41.946 0 0
0.0001 41.198 0 0
0.0001 41.014 0 0
0.0001 42.21 0 0
(ps-4.5.10) drp-neh-cmp024:lcls2$ pvget DAQ:CPO:DRP_NEH_CMP024:MON
DAQ:CPO:DRP_NEH_CMP024:MON 2022-03-21 16:41:39.129
RxPwr TxBiasI FullTT nFullTT
0.0001 41.872 0 0
0.0001 40.932 0 0
0.0001 40.968 0 0
0.0001 42.148 0 0 |
When I plug the fiber back in I see significant changes but the first number continues to fluctuate dramatically:
| Code Block |
|---|
(ps-4.5.10) drp-neh-cmp024:lcls2$ pvget DAQ:CPO:DRP_NEH_CMP024:MON
DAQ:CPO:DRP_NEH_CMP024:MON 2022-03-21 16:45:19.343
RxPwr TxBiasI FullTT nFullTT
1.1735 41.918 0 0
0.744 41.17 0 0
0.4544 41.008 0 0
0.6471 42.032 0 0
(ps-4.5.10) drp-neh-cmp024:lcls2$ pvget DAQ:CPO:DRP_NEH_CMP024:MON
DAQ:CPO:DRP_NEH_CMP024:MON 2022-03-21 16:45:39.363
RxPwr TxBiasI FullTT nFullTT
0.4084 41.972 0 0
0.7434 41.126 0 0
0.4526 41.014 0 0
0.6434 42.014 0 0 |
Running pykcu with datadev_0 all powers read back as zero, unfortunately:
| Code Block |
|---|
(ps-4.5.10) drp-neh-cmp024:lcls2$ pvget DAQ:CPO:DRP_NEH_CMP024:MON
DAQ:CPO:DRP_NEH_CMP024:MON 2022-03-21 16:47:40.762
RxPwr TxBiasI FullTT nFullTT
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0 |
PvaDetector
- If you're seeing std::bad_alloc, see note above in 'datadev Driver' about configuring tdetsim.service
- use "-vvv" to get printout of timestamp matching process
- options to executable: "-1" is fuzzy timestamping, "-0" is no timestamp matching, and no argument is precise timestamp matching.
- the IP where the PV is served might not be the same as the IP returned by a ping. For example: ping ctl-kfe-cam-02 returns 172.21.92.80, but the PV is served at 172.21.156.96
- netconfig can be used to determine the IP where the PV is served. For example:
/reg/common/tools/bin/netconfig search ctl-kfe-cam-02-drp
ctl-kfe-cam-02-drp:
subnet: daq-drp-neh.pcdsn
Ethernet Address: b4:2e:99:ab:14:4f
IP: 172.21.156.96
Contact: uid=velmir,ou=People,dc=reg,o=slac
PC Number: 00000
Location: Same as ctl-kfe-cam-02
Description: DRP interface for ctl-kfe-cam-02
Puppet Classes:Found 1 entries that match ctl-kfe-cam-02-drp.
...
Overview
Content Tools