You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some devices, despite being identical in behavior and IOTypeId have different properties on different hubs. Examples are Voltage and Current. Their value ranges (and amount of zeros for the names/units) differ because the hubs use different batteries.
To enhance the devices to reflect these, different static port info, we add an overload for the GetStaticPortInfo with a backward compatible forward.
Requirement for MarioHub (#91) and TwoPortHub (#39)
The text was updated successfully, but these errors were encountered:
- Known SystemType allows the protocol to react to HubAttachedIO w/
the right static port data specified for a given device.
- Adjusted existing IPoweredUpDevice
#98 non-breaking (internal API, default values)
- Known SystemType allows the protocol to react to HubAttachedIO w/
the right static port data specified for a given device.
- Adjusted existing IPoweredUpDevice
#98 non-breaking (internal API, default values)
Some devices, despite being identical in behavior and IOTypeId have different properties on different hubs. Examples are Voltage and Current. Their value ranges (and amount of zeros for the names/units) differ because the hubs use different batteries.
To enhance the devices to reflect these, different static port info, we add an overload for the GetStaticPortInfo with a backward compatible forward.
Requirement for MarioHub (#91) and TwoPortHub (#39)
The text was updated successfully, but these errors were encountered: