Version-Up Information(Ver.2.60 to Ver.2.61) (April 1, 2021 Update)
The following points have been upgraded.
[Modify the errors]
- Fixed the problem of sending commands even in STOP mode when a timeout occurred in RS-232C communication and RS-485 communication.
- Fixed the problem that the system history file and trigger history file could not be generated in the setting conditions.
Version-Up Information(Ver.2.50 to Ver.2.60) (November 1, 2019 Update)
The following points have been upgraded.
[Add functions]
- "Mewtocol connection timeout" can be set in the range of 5 to 60 seconds. Old version is fixed 60 seconds.)
[Change specifications]
- Changed "Sending cycle of collecting command" to "Waiting time of collecting command" in RS232C/485 setup dialog and added radio button to select "Time from send command" or "Time from receive command".
[Modify the errors]
- Cannot write 2-word data to Special Data Register.
- Data collection stops due to error response (Ex. format error) in RS-232C communication.
- "Output" in System history log file is recorded with incorrect value when reset trigger in data setup occurs.
Version-Up Information(Ver.2.40 to Ver.2.50) (September 1, 2016 Update)
The following points have been upgraded.
[Add functions]
- Add ability to synchronize with the clock of KW1M-H.
- Add a new trigger that occurs when a register value is different from the previous one.
- Add a function to check the data length of MEWTOCOL and MODBUS (RTU).
[Modify the errors]
- Trigger condition occurs every time.
- Anonymous FTP users cannot get the accumulation file from USB port.
- In the list of accumulation files from USB, the files or folders containing spaces or Chinese characters have abnormal display or will not open.
- In the data setting, data was recorded wrongly on special register.
Version-Up Information(Ver.2.20 to Ver.2.40) (November 10,2015 Update)
The following points have been upgraded.
[Add functions]
- Add 'Main unit' as an option for I/F communication at 'Logging device registration'.
- Add ‘1,2,3,4’ as options for FTP retry interval.
- Add resister for software reset.
- Collect 64-bit data.
- Available to set that it doesn't save the setup data history in system file.
- Available to download csv file via USB cable.
[Change specifications]
- Change the no communication time-out of TCP/IP(port 9094,9095) from 5 sec. to 60 sec.
- Change initial value
-'Check battery voltage' : from No to Yes
[Modify the errors]
- It will become not to connect FTP via FTP client.
- It sometimes doesn't upload the logging file after recovery the connection when it can't connect to FTP server for long time.
- It doesn't set time-out for sending mail correctly.
- It sometimes doesn't attach the current file when the trigger for sending mail is same as the trigger for logging.
- It can't shift to RUN mode for 30 minutes when LAN I/F link down during it set to obtain an IP address by DHCP.
- Accumulated ON time and total switching time show minus value when it is over 32767.
- It occurs the device error when the logging file name has space at the last.
- FTP client connect with No.21 when it set except No.21.
- Trigger doesn't occur at the end of month even if it set 'Month-end'.
- It retry even if it has no file for FTP upload.
Version-Up Information(Ver.2.11 to Ver.2.20) (February 3. 2014 Update)
The following points have been upgraded.
[Add functions]
- Below error codes are added.
E0025 Device error (Logical error of SD memory card)
E0029 Write protect error (When using SD memory card with lock)
- Initializing the settings and setting time via Configurator DL are recorded with system history.
[Modify the below errors]
- Revise a problem that SD memory card is broken when insert it.
- Improve the exclusion control in case of competing access to log files.
- Revise a problem that time setting is initialized.
- Revise a problem that file name or folder name is got garbled.
[Change specifications]
- Error LED will be blinking at below errors, SD memory card capacity shortage, Device error, Write protect error.
(At the other errors, error LED turn on.)
- When lower communication error is happened, logs of communication error and recovery are recorded with system history.
Version-Up Information(Ver.2.10 to Ver.2.11) (June 3. 2013 Update)
The following points have been upgraded.
[Add functions]
- Record station number into sentences in sending e-mail when data collecting errors occur.
[Modify the below errors]
- Revise a problem of a device driver.
- Stabilize procedures during power on.
- Revise a problem of PWD command (FTP command)
- Revise a problem that a setting value is not recorded in the system history after changing data configuration.
Version-Up Information(Ver.2.06 to Ver.2.10)
The following points have been upgraded.
[Add functions]
- Retry function for FTP client.
[Change specifications]
- Change the error code.
E0050 battery error/file attachment failure -> E0049 file attachment failure, E0050 battery error
[Modify the below errors]
- It sometimes doesn’t send mail when sending mail to several destinations.
Version-Up Information(Ver.2.05 to Ver.2.06)
The following points have been upgraded.
[Modify the below errors]
- Calculating procedures of differential value measurement when the logging trigger is detected.
Version-Up Information(Ver.2.04 to Ver.2.05)
The following points have been upgraded.
[Modify the below errors]
- I revised malfunction of the clock IC abnormality.
- I revised the exclusive control disposal of communication ports.
Version-Up Information(Ver.2.03 to Ver.2.04)
The following points have been upgraded.
[Modify the below errors]
- I revised the problem that might become the file opening error.
- FTP communication revised the problem that might become suspended.
Version-Up Information(Ver.2.02 to Ver.2.03)
The following points have been upgraded.
[Modify the below errors]
- In the case of data form of 32 bits, I revise the malfunction that a CRC error produces by MODBUS communication.
Version-Up Information(Ver.2.01 to Ver.2.02)
The following points have been upgraded.
[Modify the below errors]
- I revised communication re-try malfunction in MODBUS.
Version-Up Information(Ver.2.00 to Ver.2.01)
The following points have been upgraded.
[Modify the below errors]
- I revised the malfunction of the DT register number of the system history.
Version-Up Information(Ver.1.11 to Ver.2.00)
The following points have been upgraded.
[Add functions]
- MODBUS (RTU) protocol is added.
[Change functions]
- When set it simply; "Make the destination folder name of logging file [CF]. " I should remain in effect.
[Modify the below errors]
- When I attach logging file (CURRENT file) and transmit a message, there is not designation of the transmission,I revised malfunction to become the file opening error after progress at time.
- In the case of half size 32 characters, an logging device name revised malfunction to be out of the header of the logging file.
Version-Up Information(Ver.1.10 to Ver.1.11)
The following points have been upgraded.
[Modify the below errors]
- The number of Logging device registration revised the malfunction that I could not register to the maximum (300).
[Add functions]
- For an email attachment file name, half size space is valid.
*Depending on an email server, there is a case of the invalidity.
Version-Up Information(Ver.1.04 to Ver.1.10)
The following points have been upgraded.
[Add functions]
- Improve the data collecting process.
- Improve the system history information.
[Modify the below errors]
- When the integral part of logging data is "0", it can't make minus value.
- File creating timing of "POW" .