Implement Single Channel Power Supply Interface
Adds an abstract single channel power supply object that wraps around an IPowerSupply
. It can either be initialized manually (by passing IPowerSupply
and channel number to the constructor) or by using EquipConf
.
The syntax for equipment configuration files is as follows. The input-hw.json
example has been updated.
"channels": {
"first-channel-name" : {
"hw-type": "PS",
"device": "PS name from hardware block",
"channel" : #,
"program": {
/* potential programming */
}
},
"second-channel-name" : {
"hw-type": "PS",
"device": "PS name from hardware block",
"channel" : #,
"program": {
/* potential programming */
}
}
}
A few other changes that are an effect of this:
- Remove some unused
EquipConf
member methods -
EquipConf::getPowerSupply
now connects/checks the power supply on first fetch - Rename
hardware
->devices
for the block where physical power supplies are declared
Merge request reports
Activity
added 5 commits
- d96c487f - Remove EquipConf::getProperty as it no longer makes sense.
- cd9496c1 - libEquipConf: Rename hardware to devices in hardware configuration files.
- c86d2705 - EquipConf::getPowerSupply also takes care of connection.
- 2bfdcc8e - Add hw-type argument to PowerSupplyChannel configuration and rename some field...
- 411d10e6 - Add single channel support to powersupply.
Toggle commit list- Resolved by Karol Krizka
- Resolved by Karol Krizka
I have a question. With the code as it's at the moment, if one uses PowerSupplyChannel (that is the recommended approach for users), he/she will loose access to all the PS specific functions. How do we want to deal with it?
Should we add any PS-specific function also to both IPowerSupply and PowerSupplyChannel?
Thanks, Elisabetta
added 1 commit
- cc4d21b1 - Add channel/PS getters to PowerSupplyChannel.
added 1 commit
- 392e27c3 - change name to power-supply example, and add code snippet to access PS-specific functions
mentioned in merge request !60 (merged)
mentioned in issue #8 (closed)