Hi, I have 2 issues related to properties in UHD 4.0. The first is regarding the concept of a read-only property where the property is monitoring some HW status. This was discussed in another thread (which I copied below) but I decided to move it here to a new thread. The proposed solution doesn't seem practical if ALWAYS_DIRTY causes numerous register reads as it appears to.
The second issue is related to setting a property to a value that does not change. This may seem stupid but in the past (UHD 3.15), I could use a block arg as representing a string filename (e.g., a file containing Window coefficients). If I registered a function as a publisher for this arg, then my function would run whenever this property was set (whether or not it changed) so that I could read my file and load the coefficients. But, with UHD4 properties, my function is not getting called when the property is set to the same filename as it was before the set. So, even though the coefficients in the file are changed, they are never loaded because the filename itself did not change. Let me know if you have any suggestions on either issue. Rob > Rob, you might want to check out host/tests/rfnoc_graph_mock_nodes.hpp, > and look at the RSSI property. It's supposed to mock a property that > only represents a value that is read back from the radio (none of our > RFNoC radios actually have that property, but we provisioned for it in > the specification, and this is an example of that). > > Instead of updating a counter (which we only do because this is a mock > for unit testing), you would peek a register. Hi Martin, I looked at this and implemented a property using the ALWAYS_DIRTY dependency shown in the mock case. This does work, but it causes my actual register peek to occur quite a lot - not just when a user calls get_property for that property.
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
