Wish - Scale Values


#1

I would like the ability to assign a scale to the displayed values of sliders. My analog outputs are 4-20mA so my choice for displayed values is either 4 - 20 or a percentage of the value. I want to assign a value scale that means something in the real world besides a percentage of what is happening. For instance Ft./min., RPM, Cups/min., etc.


Best practices for sharing charts across control engines
#2

Hello nickvnlr,
(Your attachment didn’t come through.)

We do support this nifty “Scaler” tool for your Modbus Tags. For example in this image, the “raw” value coming in was 0-4045 and I changed that to 0-10 for my tag/gadget. Outputs should work too, though I’ve not yet tried them myself w/that scaler.


If you’re using an Opto 22 controller, you can scale the value when you’re configuring that your point in you strategy.

What type of device are you connecting to? Can you use one of these options?

Thanks,
-OptoMary


#3

I second this request.

It would be very helpful to have high level commands to query and set the analog scale values from a chart or OptoScript.

The addition of two operations:

  • GetAnalogFullScale(ioName)
  • SetAnalogFullScale(ioName, newFullScaleValue)

would allow programmers to add logic to access and manipulate analog scaling values.

These functions would be useful in applications where the end equipment users can make equipment modifications in the field. We would like to limit device specific changes to a single configuiation include file, so when we update software, we do not overwrite device specific changes.

The config file would contain the scaling factor for this specific device:


100.0 ^ConfigMyConfigurableMfcFullScaleFlowInSCCM @!

or

500.0 ^ConfigMyConfigurableMfcFullScaleFlowInSCCM @!

Code-wise, it would look like this:

, in the Power Up chart:

SetAnalogFullScale(MyConfigurableMfc, ConfigMyConfigurableMfcFullScaleFlowInSCCM);

in other charts, the current full scale value could be accessed as follows:

UserSetpointError = (SetPointFromUser > GetAnalogFullScale(MyPresetMfc));

Apparently, the hardware memory map can be used to access this information, however there are drawbacks to using the hardware memory map –

  1. Figuring out what memory address is to feed to the ReadNumTableFromIoUnitMemMap() function is, well, painful and prone to error.
  2. If the Analog I/O point is ever moved, there are now multiple places in the strategy that need to be changed.
  3. Embedding the scale value in the controller configuration make it difficult to install logic upgrades on devices as we sometimes need to make other changes to the controller configuration.