1. Select tab -- Delta
2. Using the Delta tool, select one cycle of the waveform you want to measure frequency.
3. Put cursor over the text box.
4. Right-click and select properties.
5. Select “1/Time (Hz)” and click OK.
6. Measurement will change from time to Hz.
See the formulas below. If power is shown “+” on Dranetz PX5/HDPQ, that means power is flowing in the direction of the arrow on the CT. If power is flowing opposite arrow on CT, then instrument show power with “- “sign.
To access the menu, select Analytics à System Events, and select the “Filters” tab:
Correct, this allows the user to search/filter on the test that has been entered in the System Event Details. This isn’t the screen where you insert that information. Right now, the only way to edit system events is via PQDM. (The PQView .exe software I quickly went over at the end of the class).
No, this is not a plan, as PQView has always displayed these as “RMS Variations.” You can easily see the difference between a sag and swell as you indicated by looking at the percentage. Additionally, it’s very simple to filter out one or the other using the Options tab.
These values should affect the times of events and data logs presented in PQWeb and PQDA.
Email is the only supported notification at this time. We have discussed and looked into other options. Our plan has been to support one or more 3rd party messaging platforms such as Twilio, however this is still in the discussion/design phase and likely won’t be available for some time.
Any ION meter that communicates via ION Protocol should be compatible with the PQView PQDMS. If you have a question about a specific meter model, we can let you know if we’ve communicated with it in the past and/or if we anticipate any issues with it.
1. Double check the wiring connection is EXACTLY like shown below. Note: Do not assume C is connected to earth. Do not make any connections directly to earth from HDPQ.
2. If these connections are correct. Then verify there is no multiplier set in the instrument setup. If these are correct, go to step 3.
Remove all voltage connections from the HDPQ and the panel board under test.
- Connect 1 voltage cable from Phase + (black jack) to A phase terminal in the panel board.
- Connect a 2nd voltage cable from the Phase – (white jack) to Phase B phase terminal panel board under test. Sketch below
Read the voltage on HDPQ screen Phase A should read about 400V (assumes a standard 230 V system Phase to Neutral.) << If the voltage does not read 400Vs. If it reads 230V, you are connected phase to neutral at the panel. Check your connections at the panel. If the voltage reads some large voltage there are 3 possibilities.
If it reads correct voltage, move the jacks to channel B, leave the connections at the panel board the same. Channel B should now read 400Vac.
If it reads the correct voltage, Move the jacks on the HDPQ to Channel C. it should now read about 400V.
3G/4G carriers do not assign a public IP address to a device when it connects to the network. So, it is IMPOSSIBLE to connect from the outside to HDPQ that is connected to a 3G/4G modem.
You have two options:
Please follow these 3 steps:
1. PRESS & HOLD your finger on any part of the HDPQ screen when it is power-UP
2. it should come up with a screen and ask if you want to reset.
3. answer it by pressing "OK" and follow instruction on the screen
Power Visa portable has a function called “Characterizer mode”. This software is running behind the recording software to provide an event description when an event occurs. When the instrument detects excessive events, the characterizer takes time to analyze all the events. If this occurs at the end of monitoring session, there may not be time to finish before the start of next session. So that can cause file error.
To reduce the risk of error, follow the recommendation below
In ESS, turn off communication to the Data Node:
2. Using web browser login to the DataNode with username DranetzBMI and password #password#
4. Set the virtual analyzer to none, and make the other changes shown below. After you click “Submit”, the instrument will reboot.
5. Put everything back the same as it was originally (Step 2) and click “Submit”. Instrument will reboot
6. Go back to ESS and turn on communication to the DataNode
rem Select the InfoNode root directory
cd "C:\Program Files\Dranetz-BMI\Encore Series InfoNode\"
rem Stop the InfoNode service
rem copy the data files
xcopy /D /R /Y settings.bin .\backup\
xcopy /D /R /Y settings.db .\backup\
xcopy /D /R /Y d*.db .\backup\
rem Signal the InfoNode service to start. Note: this will return before the service is actually running.
Yes, measurements and other purgable data (e.g., log entries).
Separate files are created for each “expiration” day. Each object’s data is stored in the file corresponding to the object expiration date. File names are derived with the days-since-12/31/1899 as “d” + the encoded day value in hexadecimal + “.db” (e.g., “d0000800c.dat”).
The actual file date depends on the expiration date of the data which is configurable (normally time + 30 days). You can use EXCELL to figure out the file name. The formula is =DEC2HEX( INT( C4 ) +30) where “C4” is a cell containing a date. For example:
Date Day File
11/1/2009 9CD4 d00009cd4.db
11/2/2009 9CD5 d00009cd5.db
11/3/2009 9CD6 d00009cd6.db
12/1/2009 9CF2 d00009cf2.db
A special name, “settings.db” is reserved for the non-purgable data; this file is however of the same structure as the purgable “d*.db” files.
The entire object state is stored in the record. This allows the entire database to be rebuilt from nothing but the storage files. To ensure robustness, the indexed auxiliary database tables that are used to access the data storage database files, can be rebuilt at startup if required. Further, each database file is fully independent. Deleting one file does not compromise the indices of another. It is however important to remember that some objects are interdependent. For example measurements in a “d*.db” file require DataNode objects stored in the “settings.db” file.
“infonode.db” is the database file where the auxiliary tables (index tables) are stored. It can be rebuilt from the data storage files and so does not need to be archived.
The system can “ride through” that. However, some operations (e.g., a trend plot) will fail until the database is “reindexed” (i.e., infonode.db is rebuilt from the settings.db and d*.db.
A database can always be rebuilt from settings.db and 0 or more d*.db files. To do so you:
- Stop the ESS service
- Delete all files in system\data directory
- Copy settings.db and d*.db to the system\data directory
- Start the ESS service
No – data is partitioned by its expiration day. The expiration day is the day the record was collected plus the “days to keep data” as specified on the InfoNode\Data setup page (Log entries have expiration offsets as well). Files are deleted to make room for new data when the database is full. This significantly improves purging performance of the 4.5.x database structure. It also allows for much more efficient archiving since older files become static. Differential backups are now possible (you only copy the files that have changed).
No. Actually I’d recommend keeping the limit as low as practical. If the database is larger than the limit (e.g., 20 GB) the ESS will restart, purge data, and reindex the database to reduce the database size. As with the earlier database structure this is lengthy process. If the limit is greater than the current database size the ESS will simply continue without interruption.
Once a database size reaches the limit, the ESS will begin purging old data (by expiration date which corresponds to file name) to make room for new data. This does increase the ESS load; however, our testing has not shown any significant performance degradation.
Limiting the database size also ensures that the database files are more manageable. Let’s face it, even the fastest computers will struggle to move 100GB of data.
No, you still need to compact the database to recover space (shrink files). Deleting data makes database records as free space; however, it does not shrink the size of the file containing the records.
The ESS maintains a “console (text) output log for diagnostic messages. The most recent console output is stored in a circular memory buffer. At startup and at shutdown this buffer is automatically written to disk. Optionally, the console output can be continually streamed to disk.
The console files are stored in the .\system\log directory in the ESS installation directory. This directory is mapped to the HTTP log/ path (i.e., http://localhost/log/) which allows log files to be downloaded via a web browser.
The startup and shutdown log files are named “in_start*.log”, “in_stop*.log”, and “in_abort*.log”. A start/stop or start/abort pair is created each time the service cycles. The most recent pair has a “0” suffix (i.e.,” in_start0.log”). Older pairs have “1”, “2”, “3”, “9” suffixes. You can also check the Window Event log (using the event viewer) to see if the service is cycling.
If console logging is enabled the console output is continuously written to a “circular” set of files. The files are also stored in the .\system\log directory. They are named “in_console_*.log The date on which the file was written is suffixed to the name (e.g., “in_console20110708.log”). Because of file locking, the current days file is not directly accessible when logging is on.
To maximize performance, console logging is disabled by default. It should only be enabled at the request of the factory when trying to diagnose problems.
The console output is controlled with two options: a logging enable and a message level (0-7. The logging enable determines if the console output should be streamed to a disk. The message level controls the verbosity of the console output: 0 specifies least output (default), 7 selects the most detailed output. These levels are mapped to the corresponding SysLog levels.
The Console Output settings can be configured via a Telnet session. For example, to enable logging at level 7 the sequence is as follows:
Start a DOS session.
Enter the follow command “telnet localhost”
Press the Enter Key. The InfoNode should response with a “user:” request. Enter the “user” name.
The InfoNode should prompt with a “password” request. Enter the “password”.
The InfoNode should prompt for a command “>”. Enter “log on,7”
Enter “quit” to exit the session.
The console output can also be echoed to a telnet session. Use the “Telnet” console command to monitor the console output in a real-time session.
The console output can also be controlled and viewed via a web browser. The log web page is accessed via the”contolcgi.dll?cmd=Log” (e.g., http://localhost/controlcgi.dll?cmd=Log).
The ESS implements a Syslog server capable of listening for incoming syslog packets and echoing them to the ESS console output. If logging is enabled then the ESS Syslog server is enabled.