In the drivers (DAGmx,NI-Scope/Fgen,...) if a value enters a config vi and it could be coerced, the vi should directly output the coerced value

[Henrik_Volkers]

In the drivers (DAGmx,NI-Scope/Fgen,...) 

If a value (usually as DBL)  enters a config vi,  it could be coerced by the driver.

That vi should directly output the actual value.

Most often seen in the Forum: A user declares a non valid DAQmx Timing Sampleclock and wonder why the wfrm(data) is not what he expected.

Yes, RTFM help, you can read the properties after configuration  but it would easy to add an output to the config vi with the actual (maybe coerced) value. Making the user avare of that 'feature' (instead of popping an error 😉 )

Should not only cover samplerate ,  other values like FGEN standard funktion parameters (frequency, Phase), actual range, ...