Classification: UK OFFICIAL Hi, Is it possible to use calls to OCPI::API::Application's getProperty() method to get the value of properties of a platform worker? For example, the "LEDs" or "switches" properties. The documentation only references application and instance properties. If not, is there any other way that I could get the value of such properties by using the ACI? Thanks, Dominic Walters "This e-mail and any attachment(s) is intended for the recipient only. Its unauthorised use, disclosure, storage or copying is not permitted. Communications with Dstl are monitored and/or recorded for system efficiency and other lawful purposes, including business intelligence, business metrics and training. Any views or opinions expressed in this e-mail do not necessarily reflect Dstl policy." "If you are not the intended recipient, please remove it from your system and notify the author of the email and centralenq@dstl.gov.uk"

One quick, but not adequate answer is that the "-M" option to ocpirun, or the "dumpPlatforms" boolean PValue to the Application constructor in the ACI, will dump *all* properties from platform and device workers in addition to others. There is currently no interface in ACI for this.  For a hardware FPGA, the "ocpihdl get" command would work under some circumstances. If there was such an interface, it would be a getProperty method on the container class... I'll add an issue for this. On 12/12/19 11:05 AM, Walters Dominic A via discuss wrote: > Classification: UK OFFICIAL > > > Hi, > > Is it possible to use calls to OCPI::API::Application's getProperty() method to get the value of properties of a platform worker? > For example, the "LEDs" or "switches" properties. The documentation only references application and instance properties. > If not, is there any other way that I could get the value of such properties by using the ACI? > > Thanks, > > Dominic Walters > > "This e-mail and any attachment(s) is intended for the recipient only. Its unauthorised use, > disclosure, storage or copying is not permitted. Communications with Dstl are monitored and/or > recorded for system efficiency and other lawful purposes, including business intelligence, business > metrics and training. Any views or opinions expressed in this e-mail do not necessarily reflect Dstl policy." > > "If you are not the intended recipient, please remove it from your system and notify the author of > the email and centralenq@dstl.gov.uk" >