This project has moved. For the latest updates, please go here.

Measurement.AdjustedValue Vs Value

Aug 4, 2011 at 6:02 PM

When we listen to DataSubscriber.NewMeasurements() on a client, the measurements coming through have an AdjustedValue of 0 now and the Value has the measurement value. We had our client built to use the measurement.AdjustedValue earlier, after updating the source code of TSF to latest, the AdjustedValue does not work for us any more, so we changed the client code to look for measurement.Value. That now works for us. But we would like to make sure we are doing the right thing and if you could provide some information on the Value and AdjustedValue usage, that would be helpful. Thanks!

I noticed the following:

1. Measurement.Multiplier is always 0 and measurement.AdjustedValue = 0 in the measurements that come from DataSubscriber.NewMeasurements() event

2. Measurement seems to have the right adjusted value in the .Value itself (takes multiplier into account)

3. Openpdc manager UI code behind seems to use the measurement.Value to plot the signals

Coordinator
Sep 9, 2011 at 9:20 PM

I think this was a bug that has been corrected - if not, just let me know!

Thanks!
Ritchie