Power Flow Emulator Configuration
The Power Flow Emulator runs within the same DMSService instance when the --emulator command-line option is specified; it does not run as a separate process. The emulator submits Power Flow solution data back into NMS to emulate SCADA data that would generally come from the field. It simulates SCADA telemetry, fault events, and user control actions initiated from NMS.
The following steps are required to configure the Power Flow Emulator:
1. Power Flow services must run reliably on the data model.
2. In system.dat, configure the existing DMSService program or instance entry with -run DMSService immediately after the executable. Add --emulator after the normal DMSService-specific options and before emulator-specific options. Restart the DMSService instance to apply startup-option changes. For example:
program DMSService DMSService -run DMSService -dbname pf --emulator -scadaId RTAdapter -inputDir ${NMS_SCADA_SCAN_FILE_DIR} -outputDir ${NMS_ROOT}/scada_out
• -scadaId: Specify the RTAdapter identifier whose devices are emulated.
• -inputDir: Specify the directory where the emulator writes measurement and control files for RTAdapter. RTAdapter scans this directory for incoming telemetry.
• -outputDir: Specify the directory that the emulator scans for inbound control files written by RTAdapter.
3. The RTAdapter command-line options in system.dat must enable the -controls parameter:
program RTAdapter RTAdapter ‑scada RTAdapter ‑interval 3 ‑operate ‑dir ${NMS_SCADA_SCAN_FILE_DIR} ‑controls rti‑emulator
4. The EMULATOR_FREQUENCY, EMULATOR_VOLTAGE_RANGE, and EMULATOR_CURRENT_RANGE SRS rules need to be set up properly to control the emulation range of values and the frequency run.
Power Flow Emulator High Level Messages
The Power Flow Emulator runs within DMSService when training emulation is enabled with --emulator. Its high level messages support troubleshooting and simulation of training conditions, including load profiles, measurement quality, device operations, and generated SCADA measurements. These requests require the intended training/test environment and the prerequisites stated for each command.
Send emulator requests to the running DMSService process, using its configured process name if it differs from DMSService:
Action any.DMSService <command> [arguments]
Command names are normalized to lowercase; argument case follows the individual command. Output normally appears in the DMSService log. An acknowledgement can precede validation or completion, so verify the resulting state and measurements in the training environment.
In the syntax below, angle brackets identify required values, square brackets identify optional values, and an ellipsis permits repetition. Enter values without the brackets and preserve the spelling and case shown.
Caution: Consult Oracle Support before first using these commands. They can change emulator state and generate measurements or operations that pass through the configured SCADA input path into NMS. Use only under the intended training procedure and observe the command-specific restrictions.
DMSService startup options, including --emulator and the options that follow it, remain in the Power Flow Services High Level Messages and Command Line Options reference.
Emulator Messages
clear_amp_load
Clear all fixed amp-load overrides, remove the corresponding real-time load-change conditions, request a new solution, and regenerate emulated measurements.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
Notes: This command does not select individual devices. It clears the emulator's complete fixed-load list; acknowledgement precedes completion.
clear_emulator_options
Unlock the emulator profile, restore real-time profile parameters, and request a new solution cycle.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
Notes: Use after set_emulator_options to resume automatic profile updates at the new hour. This does not clear fixed amp-load overrides, simulated device operations, or measurement-quality overrides; use their corresponding clear commands separately. Acknowledgement precedes completion.
clear_measure_qualities
Remove all emulator measurement-quality overrides so subsequent generated measurements use their normal quality values.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
Notes: Does not change device status or profile/fixed-load overrides. Use dump_measure_qualities to confirm that the override list is empty.
clearoldforecastdata
Remove old forecast records from the emulator database.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
create_flisr_event <handle> [phases]
Create a training FLISR event at a device.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
Notes: Creates a training FLISR/FLA event, rather than just printing diagnostics. Acknowledgement precedes validation. Confirm the resulting event in the training environment.
• handle: a valid device object handle.
• phases: optional decimal bitmask A=1, B=2, C=4, neutral=8; ABC=7. Omission uses all phases (15).
dump_measure_qualities
Print overridden measurement quality mappings.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
eliminate_dist_gens
Eliminate distributed generation from the emulated model.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
emulate_measures
Generate emulated measurements immediately.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
pause
Pause measurement emulation.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
periodic_solution
Run an emulator periodic model solution.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
refuel <device>
Refuel an emulated distributed-generation device.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
resume
Resume measurement emulation.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
scada_op <open|close> <handle> [phases]
Simulate an unsolicited SCADA open or close operation and submit the resulting measurement to NMS through the emulator output path.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
Caution: Can change real-time state through the configured SCADA input path and clears feeder fault indicators. Use only in the intended training environment.
Notes: First clears relevant fault indicators on the feeder and submits those measurements, waits five seconds, then changes emulator state and submits the device operation. Acknowledgement occurs before this sequence completes. Verify the device state and measurements in the training environment. To reverse a test operation, issue the opposite operation under the training procedure; there is no scada_op clear command.
• operation: open or close; clear is not accepted.
• handle: a valid device object handle, not an alias.
• phases: optional decimal bitmask A=1, B=2, C=4, neutral=8; ABC=7 and the default all-phases mask is 15. Phases are intersected with the device's configured phases.
set_amp_load <alias> <value> [alias value ...]
Set fixed amp loads on selected devices.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
Notes: Overrides normal emulator load selection for the selected devices, requests a solution, regenerates measurements, and applies real-time load_change conditions. Use clear_amp_load to clear all fixed-load overrides. The request is acknowledged before processing; inspect the log for invalid devices and do not assume that a multi-device request is atomic.
• Supply one or more complete device/value pairs. A device can be an object handle or an alias; each value is the requested fixed amp load per phase. The target must have existing emulator SCADA measurements.
set_emulator_options <scale_factor> <day_type> <hour> [season]
Override training load-profile scaling and time selection.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
Caution: Changes training measurements that may be published through RTAdapter to NMS. Use configured profile and season identifiers; inappropriate numeric values are not reliably rejected.
Notes: Changes the emulator session, retains real-time DER forecast selection, locks the selected profile against automatic hourly changes, and requests a new solution cycle. Use clear_emulator_options to unlock the profile and restore real-time profile parameters. The handler acknowledges before validating or applying the request and performs basic numeric conversion rather than complete range validation. Check the DMSService log and resulting training measurements.
• scale_factor: dimensionless numeric multiplier for training load profiles; 1.0 means unscaled.
• day_type: integer daytype identifier present in the configured load profiles (pf_load_interval_data). Use the identifiers configured for the environment, rather than assuming a universal weekday/weekend numbering.
• hour: hour of day, normally 0 through 23, converted at minute 0 into the configured load-profile interval. This is not a profile interval index.
• season: optional integer seasonal-rating identifier for the environment; omission retains the emulator session's current season.
Example:
Action any.DMSService set_emulator_options 1.0 <configured-daytype> 14 <configured-season>
Action any.DMSService clear_emulator_options
set_measure_quality <handle> <attribute> <quality>
Set an emulated measurement quality code.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
Notes: Exactly three arguments are required. The handler acknowledges before argument checks and converts quality in base 10. dump_measure_qualities lists current overrides; clear_measure_qualities removes all overrides. Changes affect subsequently generated emulator measurements; they do not directly repair source SCADA data.
• handle: a valid device object handle, not an alias.
• attribute: the integer measurement attribute number for that device.
• quality: an unsigned decimal SCADA quality bitmask using the environment's quality-bit definitions. Supply the numeric mask, not hexadecimal notation or quality display letters. Zero removes an existing override for the device/attribute.
Example:
Action any.DMSService set_measure_quality <device-handle> <attribute-number> <decimal-quality-mask>
Action any.DMSService dump_measure_qualities
simulate_op <open|close|clear> <handle> [phases]
Override a device's open/closed state in the emulator session, or clear an existing simulated-state override.
Use: Oracle Support diagnostics.
Prerequisites: Training emulator enabled with --emulator; use only in the intended training/test environment.
Caution: This is not an isolated private-model change: training measurements and real-time conditions can become visible to NMS users.
Notes: Also adds or removes the simulated_op condition in the real-time session. It does not directly submit the unsolicited-operation measurement used by scada_op, but subsequent emulator measurements can propagate the changed state to other sessions. Acknowledgement precedes validation and completion. Use simulate_op clear for the same device/phases to remove the override.
• open or close: force the selected device phases and mark the device as simulated. clear: remove that override and copy the current DDService status for the selected phases.
• handle: a valid device object handle, not an alias.
• phases: optional decimal bitmask: A=1, B=2, C=4, neutral=8; combine by addition (ABC=7). Omission selects all phases (15). The operated phases are intersected with the device's configured phases.
Example:
Action any.DMSService simulate_op open <device-handle> 7
Action any.DMSService simulate_op clear <device-handle> 7