IMS - Datalogging - File size and content

During a machine cycle, files containing a header and data are sent at regular intervals to the ftp server.
Between cycles, a file containing just a header is sent at the same time interval to act as a watchdog and confirm that the network is fuctional.
Typical settings and data rates are shown below.

Machine type            Washer/Disinfector        Autoclave/Steriliser 				
Typical cycle time      45 to 90 mins             20 to 45 mins
datalog interval        5 seconds                 1 second
ftp interval            5 minutes                 1 minute		
          
 read more 
  

IMS - details

Data Logging memory

The CubeIP meter has sufficient non-volatile memory to store over 20,000 records of kwh and kvarh. This will use four datalog channels as they are each long integers and each require two modbusi addresses.

Alternatively, up to 20 channels may be data logged in each record. The CubeIP is then able to store some 5,500 records.

If the CubeIP is configured to log kwh and kvarh every 30 minutes then records spanning more than one year will be stored. Records are maintained in a cicular recording which means that the oldest records will be overwritten when the recording is full.

CubeIP - Backing up files

The code snippets shown below are for demonstration purposes only and should only be used by qualified personnel. (Microsoft Windows Vista - see note below.)

The CubeIP contains four files which determine the pages shown on the Web pages and the data sent over ftp and shown in the Energy Profile.

       dir.txt         a directory listing      read only
       clone.icf       the IP configuration     read/write
       log.csv         the entire datalog file  read only
       webpages.fat    all the individual       read/write
                       webpages as one file

Access to the files is through tftpi and a command can be carried out by creating a single line file with a .bat extension. Vista users will have to ensure that the tftp, which is always included as a standard feature, is enabled.

tftp -i 192.168.1.127 GET dir.txt dir.txt 

This will GET the clone file from a CubeIP with an IP address of 192.168.1.127 and create a read only file in the same directory called clone.icf. (Tftp uses port 69 so can normally only be used locally thus preventing any unauthorised remote access to these files. The port can be deliberately opened with port forwarding or a DMZ.) Adding pause to the file then enables you to check that the command completed successfully before acknowledging it and closing the command window.

tftp -i 192.168.1.127 GET dir.txt dir.txt 
pause

All four files can be saved by including the four tftp GET commands in one file.

tftp -i 192.168.1.127 GET dir.txt dir.txt 
tftp -i 192.168.1.127 GET log.csv log.csv
tftp -i 192.168.1.127 GET webpages.fat webpages.fat
tftp -i 192.168.1.127 GET clone.icf clone.icf
pause

As the files are read only this will not normally overwrite earlier files.

Advanced

The sample code shown below creates file names which include the IP address and the local time and date. This enables better records to be maintained and files are unlikely to be overwritten.

set WP_defaultIP=192.168.1.127

for /F "tokens=1-4 delims=/:., " %%a in ('date/T') do set f_name=%%c%%b%%a
for /F "tokens=1-2 delims=:., " %%a in ('time/T') do set f_name=%f_name%_%%a%%b
tftp -i %WP_defaultIP% GET dir.txt __%WP_defaultIP%_%f_name%_dir.txt 
rem notepad __%WP_defaultIP%_%f_name%_dir.txt  


for /F "tokens=1-4 delims=/:., " %%a in ('date/T') do set f_name=%%c%%b%%a
for /F "tokens=1-2 delims=:., " %%a in ('time/T') do set f_name=%f_name%_%%a%%b
tftp -i %WP_defaultIP% GET clone.icf __%WP_defaultIP%_%f_name%_clone.icf
copy  __%WP_defaultIP%_%f_name%_clone.icf __%WP_defaultIP%_clone.icf
rem notepad __%WP_defaultIP%_%f_name%_clone.icf  

for /F "tokens=1-4 delims=/:., " %%a in ('date/T') do set f_name=%%c%%b%%a
for /F "tokens=1-2 delims=:., " %%a in ('time/T') do set f_name=%f_name%_%%a%%b
tftp -i %WP_defaultIP% GET log.csv __%WP_defaultIP%_%f_name%_log.csv 
rem notepad __%WP_defaultIP%_%f_name%_log.csv  

for /F "tokens=1-4 delims=/:., " %%a in ('date/T') do set f_name=%%c%%b%%a
for /F "tokens=1-2 delims=:., " %%a in ('time/T') do set f_name=%f_name%_%%a%%b
tftp -i %WP_defaultIP% GET webpages.fat __%WP_defaultIP%_%f_name%_webpages.fat 
rem notepad __%WP_defaultIP%_%f_name%_webpages.fat  

pause

Note.
Microsoft Windows Vista.
tftp may need to be enabled - see http://windowshelp.microsoft.com/Windows/en-US/Help/1e62706b-ef53-4ecd-a217-0e7bcf82009b1033.mspx

Carbon emission factors

This information is correct at the time of writing but is subject to regulatory revision and should not be relied upon.

The factors given below are from Annex A of UKETS(01)05 (Guidelines for the measurement and reporting of emissions in the UK Emissions Trading Scheme). These figures are consistent with the National Air Emission Inventory and with the carbon factors given in the generic PP3.02 (Underlying Climate Change Agreement for the [ ] sector).

Carbon emission factors 
Fuel                          kg C/kWh    kg C02/kWh  
          
 read more 
  

2.7 Display Scaling
Measured values displayed on the LCD are scaled by 
the user settings of CT and/or
PT primaries to provide optimum resolution.

2.7.1 Voltage Scaling)
PT 	Setting                  Resolution
10VL-L - 80VL-L                 0.01 V
81VL-L - 800VL-L                0.1 V
801VL-L - 8,000VL-L             1 V
8,001VL-L - 80,000VL-L          0.01 kV
80,001VL-L - 440,000VL-L        0.1 kV

2.7.2 Current Scaling
          
 read more 
  

NC300 Configuration Save and Restore

The full configuration can be downloaded as a text file, clone.icf, from the NC300 by using tftpi.

For example, replace 192.168.2.45 with the correct address for the NC300.

tftp -i 192.168.2.45 GET clone.icf

The file contains a list of addresses and their corresponding settings. The file can be edited with a simple editor such as Wordpad but this is not recommended as the file may be rendered useless if any erroneous values are entered.

The NC300 configuration file should be kept in a secure location to provide a backup of the configuration and form part of any future audit.

Correction