TIM function return code descriptions

Success

This error may be caused by an error that the TIM was not designed to report or the TIM module is missing from the C:\MV90xi\ directory.

This error indicates a problem with the software scheduling the interrogation. Report the issue to Itron Support Services.

This error indicates a problem with device-specific information that is passed to the TIM or corruption to the TIM local database. This can be caused when applying a new TIM to the system where the TIM local data structure is not compatible with the previous version. This issue should not occur. Report the issue to Itron Support Services.

The TIM could not run because there was not sufficient memory or disk space available. Ensure that the temporary work directory path is pointing to the local hard drive of the workstation performing the interrogation and adequate disk space is available.

The TIM cannot perform the requested function because it was never implemented or it cannot be supported by the meter. Review the TIM Application notes to confirm.

A file error usually indicates that the disk is full, an error occurred while writing to a file, the file is too large, or an expected file is missing. Check the local disk space for the xiComm workstation and ensure that the temporary work files directory is pointing to a local directory, for example, c:\mv90xi\work or c:\xicomm\work.

The load profile configuration information in the meter does not match the information in the IEE Configuration. The meter may have been reprogrammed or the configuration may not have been set up correctly. Most TIM modules report the configuration that was read from the meter in the Comm Log. The Chan: (channels) and InPHr: (intervals per hour) should contain the values that were read from the meter. Modify the configuration to match this information.

The TIM could not correctly run due to an invalid parameter defined for the MV90 xi system or for data that was manually entered. Verify that the meter is correctly defined for the MV90 xi system or check the data that you manually entered. Refer to the TIM Application note to identify the required fields and setup instructions.

The clock in the meter cannot be changed since the time difference is too significant from the system time. Be sure that the system time is correct. This usually indicates that changing the time in the meter will cause the meter to cross a load profile interval boundary. The reason for the time difference should be investigated and may require that you use the meter manufacturer's software to correct the meter clock. In general, the MV90 xi will not set the time across an interval boundary. If the time difference is less than the load profile interval length of the device, schedule a manual timeset at the beginning or ending of the interval (allowing sufficient time for xiComm to connect to the meter, log on, and set the time.)

The meter ID read from the meter does not match the device ID that was expected. Check to ensure the proper meter is being read. If this is not the problem, the wrong device ID may be entered into the Recorder Master File in MV90 xi. Press CTRL-L on the failed task in Monitor, or list the latest Comm Log Report entry for the recorder ID. The device ID that was read from the meter is listed in the device ID field of the meter. Update the Recorder Master with the correct Device ID listed in the Comm Log.

The firmware version read from the meter is not recognized or is specifically identified that it cannot be read correctly. Verify the version of the TIM and contact Itron Support Services. You can also access the eKnowledge website to see if a later version exists for MV90 xi.

A communication failure occurred that could not be identified. Verify the physical connection with the meter and review the TIM Application note to ensure the Master File is set up correctly. This could also indicate that there is a substantial amount of noise on the communication link with the meter (which may be the case for circuit-switched communications) that is preventing the TIM from successfully reading the meter.

An input/output timeout occurred during the communication session with the meter. This is usually caused by a problem with the physical connection with the meter or the communication settings being used are incorrect. Communication settings may refer to an incorrect baud rate or meter address. If this error occurs at the beginning of the interrogation, it could represent a setup issue with the Comm option of the meter, or the baud rate in xiComm is not switching to a different baud rate that is established by the modem. Try increasing the TIM Message Level to 7 in TIM Assignments under System Parameters. Restart xiComm and reread the meter. An .rds file is created in the temporary work file directory and should include a CONNECT message, followed by a baud rate. If this baud rate is different than what is displayed in the Recorder Master File, modify the Recorder Master baud rate to match the baud rate reported in the .rds file.

A cyclic redundancy check (CRC) or checksum is used to ensure that the data sent and received with the device being interrogated is correctly transferred. A CRC/checksum error may indicate a problem with the physical connection with the meter or the communication channel is too noisy to allow an interrogation to complete.

A protocol error occurs when the response or data retrieved from the meter cannot be interpreted properly. This may be an indication that a wrong TIM is being used, a problem with the physical connection, or the meter firmware is not currently supported. In wireless communications, it usually indicates that there is too much noise on the communication channel to the meter, or there is too much latency for the wireless network to successfully read the meter.

A port error is usually an indication that the communication port that is being used is invalid or is being used by another program. If the interrogation being performed is over TCP/IP, it indicates that the TCP/IP session was rejected by the network interface with the device. This is usually caused by another TCP/IP session that has already been established with the device and blocks the current interrogation.

A security error indicates that an incorrect password is being used for the meter for the functions that are attempted to be performed. Check the password to ensure it is correctly entered. If a read-only password is used, this error will be generated if any write functions are performed (for example, auto-timeset, manual timeset, or initialization).

This error indicates an attempt to establish a remote connection with a meter was unsuccessful. Check the phone number or IP address and ensure the device is powered. For TCP/IP communications, this could indicate that the TCP/IP session is blocked by a firewall on the network. In this case, contact your IT department for assistance.

This error is only applicable for modem communications. It indicates that the modem connection was unexpectedly lost. This is likely due to poor telephone line or coverage issues with a circuit-switched, wireless interface.

The TIM encountered an unexpected error that cannot be determined. Report the issue to Itron Support Services, if the error occurs again. The TIM module should not use this error message and could represent a communication protocol error.

The meter time is outside of a pre-defined tolerance from the MV90 xi. Ensure the system time, date, time zone, and daylight saving time setting are correct. If the system time is correct, the meter's clock needs to be corrected. If the time difference between the system and device is greater than the load profile interval length, you may need to use the meter manufacturer's software.

Meter is not programmed to record load profile interval data, so no load profile interval data can be retrieved.

A load profile interval has not ended since the last time load profile data was retrieved from the meter. Wait until the next interval boundary and read the meter again.

This error indicates a hardware problem with the meter. Contact your meter department to report the problem. Any data retrieved from the meter may be suspect and invalid.

The stop time of the load profile data retrieved from the meter does not match what was expected. This issue may be caused by a problem with the meter or the retrieval of load profile data. Report the issue to Itron Support Services.

The load profile data in the recorder is corrupt or the time was incorrectly set. Any data retrieved from the meter may be suspect and invalid. Attempt to perform a limited partial read by adjusting the last stop time in the Recorder Master to the time where the corruption is expected.